The Impact on Communication Identifiers on AWIPS

**[Version III -- 11/04/2004]{.underline}**

This manual will identify the steps needed for sites to undertake when
there are certain changes to the Communication Identifiers (CID) of
products. This section deals with only the changes caused by XXX part of
the CCCNNNXX Communication ID. Although there may be many reasons why
this would occur, there are two primary reasons for such change. The
first reason is that sites would transition from their legacy XXX to
their modernized XXX (e.g.., LITZFPLIT becoming LITZFPLZK). A second
reason would be that a new site being commissioned or an old site being
decommissioned. Below is outline of steps needed for short fuse warning
(WarnGen created) products, other products and appropriate IFPS/GFE
changes. For short fuse warning (WarnGen created) products, you need to
review the steps in Sections I and II, if they are applicable. For those
products created via IFPS/GFE, you need to review the steps in Sections
II and III. For all other products, sites just need to review Section
II.

**[\* - Editor's Note:]{.underline}** This document is quick outline of
steps needed when the XXX of Communication Identifier changes. It is a
work in progress. Your input into these changes is welcome. If you have
problems, please direct them through the NCF ((301)-713-9344) and have
them open a Trouble Ticket. The NCF should then direct the Trouble
Ticket to the AWIPS SST (Awips_Sst@noaa.gov)

# Section I -- Short Fuse Warning Products (WarnGen created)

1.  LLL-mainConfig.txt changes for primary site

2.  LLL-mainConfig.txt changes for backup site

## Section II -- Changes needed for all products

1.  afos2awips.txt changes

2.  textCCChelp.txt changes

3.  afosMasterPIL.txt changes

4.  Asynchronous Product Scheduler (APS) changes

5.  Trigger changes

    a.  LDAD

    b.  Local (CRS and FAX)

    c.  Hydro

    d.  Adapt

    e.  Trigger Localization

6.  Text Workstation Alarms

    a.  Personal Text Alarms

    b.  Site Protected Text Alarms

**[Section III -- IFPS/GFE related changes]{.underline}**

**[Section I -- Short Fuse Warning Products (WarnGen
created)]{.underline}**

# 

# 1. CHANGING THE WARNGEN XXX FOR YOUR WFO

File LLL-mainConfig.txt (where **[LLL]{.underline}** is the site ID)
needs to be edited, then a localization needs to be run.

The LLL-mainConfig.txt file is on the workstation in
/awips/fxa/data/localiztion/LLL. There may also be a localization
override file in /data/fxa/customFiles. All versions of the
LLL-mainConfig.txt file should be edited to change the "XXX" variable.

For example, at site BOX, the BOX-mainConfig.txt file looks like:

@@@XXX BOX

@@@WFO BOX

@@@CCC BOS

@@@XXXL MA ME RI NH VT CT NY BOS NYC ALB PWM BTV PHL TIR

@@@XXXR BOS NYC ALB PWM BTV PHL TIR BGM CTP MA ME RI NH VT CT NY

@@@PUP_TABLES TRUE

To change your D2D Local Warnings Graphic, you must edit the XXXR line
to delete the old and add in the new site ID changes. To change you D2D
Flash Flood Guidance Graphic, you must edit the XXXL line to delete old
and add in the new site ID changes. You must also have an updated copy
of the latest afosMasterPIL.txt files. Instructions on updating this
file are Section II Part 3 of this document. The --text localization at
the end of Section II Part 3 will activate this change.

Some sites may hard code the "XXX" in their WarnGen templates. If so,
this also needs to be changed before the localization is run. It's
better to use the "xxxValue" variable in the templates than to hard code
the "XXX". In this case, the LLL-offtIncl.txt file needs to be available
in the template by using the following line:

#include \"\${CURRENT_CWA}-offtIncl.txt\"

After editing the "XXX" line in LLL-mainConfig.txt (and templates if
needed), each workstation needs to be localized, using "./mainScript.csh
--wwa" (lower case "wwa"). Now restart D2D and WarnGen and WarnGen will
use the new "XXX" value.

The instructions above also pertain to the WWA software.

**[2.) CHANGING THE WARNGEN XXX FOR YOUR FULL SERVICE BACKUP
SITES]{.underline}**

If a site for which you perform service backup has an "XXX" change,
follow these procedures.

File LLL-wwaConfig.txt (where LLL is your local site ID) needs to be
edited, then a localization needs to be run.

The LLL-wwaConfig.txt file is on the workstation in
/awips/fxa/data/localiztion/LLL. There may also be a localization
override file in /data/fxa/customFiles. All versions of the
LLL-wwaConfig.txt file should be edited to change the "SBID" variable.

For example, at site EWX, the EWX-wwaConfig.txt looks like:

EWX-wwaConfig.txt

@@@SRWARN FALSE

@@@ORABOUT TRUE

@@@SBID \"CRP\", \"SJT\", \"HGX\", \"FWD\"

@@@OFFH AUSTIN/SAN ANTONIO TX

@@@OFFT IN AUSTIN SAN ANTONIO

@@@COPE

@@@CIPE

@@@

If the HOU site ID is changing, the "HGX" entry in the "SBID" line will
be changed. Some sites may hard code the "XXX" in their WarnGen
templates. That is, if site EWX has HOU templates, the HOU templates may
have "HOU" hard coded. If so, this also needs to be changed before the
localization is run. It's better to use the "xxxValue" variable in the
templates than to hard code the "XXX". In this case, the
LLL-offtIncl.txt file needs to be available in the template by using the
following line:

#include \"\${CURRENT_CWA}-offtIncl.txt\"

After editing the "SBID" line in LLL-wwaConfig.txt (and templates if
needed), each workstation needs to be localized. For example, if the
local site is BOX and they need to back up site ALB, localize using
"./mainScript.csh --WWA ALB BOX" (upper case "WWA"). Now restart D2D as
the backup site and WarnGen will use the new backup site "XXX" value.

WarnGen partial backup sites are defined in the usa_cwa_total and
marine_total shape files and are not site configurable.

**[Section II -- Changes needed for all products]{.underline}**

**[1. How to edit the afos2awips.txt file]{.underline}**

A.) As user fxa, change directories to the location of the
afos2awips.txt file

**cd /awips/fxa/data**

B.) For safety sake, make a copy of your current afos2awips.txt file.

**cp --p afos2awips.txt afos2awips.txt.orig**

C.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the afos2awips.txt
file. (In the example below, the vi editor is used.)

**vi afos2awips.txt**

D.) When completed to save and exit from vi. After completing your
edits, the SST have found that problems can occur with afos2awips.txt,
if it is not sorted.

**:wq!**

E.) Copy the afos2awips.txt file to all other workstations and servers
(Note: where, BOX is lx1, ds1,px1 etc)

**rcp --p afos2awips.txt BOX:/awips/fxa/data/afos2awips.txt**

An example of a section from the afos2awips.txt is below:

#### ABIAWWABI WWUS84 KSJT

#### ABQABVABQ UFUS45 KABQ

**ABQADAABQ NOUS45 KABQ**

**.**

**.**

**.**

\^ \^

***[Comms ID]{.underline} [WMO ID]{.underline}***

**[Additional Information on the afos2awips.txt file:]{.underline}**

The afos2awips.txt file is used on the text and graphics workstations
when issuing products to convert the AFOS PIL into a WMO Header for
product transmission. To activate the afos2awips.txt file on the text
and graphics workstations, it is probably safest to logout/login to each
text and graphics workstation after updating the file. This ensures that
all applications that may be running on the graphics and text
workstation read the updated copy of the afos2awips.txt file.

On ds1, I believe the afos2awips.txt file is only utilized by
applications that read this file on the fly. Therefore, there is no need
to stop or restart any processes.

The afos2awips.txt file should also be updated on ds2 in case of a
ds1-\>ds2 failover.

**[2. How to edit the textCCChelp.txt file]{.underline}**

A.) As user fxa, log into a workstation.

B.) Change directories to the location of the textCCChelp.txt file

**cd /awips/fxa/data**

C.) For safety sake, make a copy of your current textCCChelp.txt file.

**cp --p textCCChelp.txt textCCChelp.txt.orig**

D.) ftp into the NOAA! Server and download the latest textCCChelp.txt
file.

**ftp 165.92.25.15 (NOAA1)**

**login: ftp (use your e-mail address for password)**

**cd pub/ndm**

**get textCCChelp.txt**

**bye**

E.) Change the attributes and ownership of the TextCCChelp.txt.

**chmod 775 textCCChelp.txt**

**chown fxa:fxalpha textCCChelp.txt**

F.) Copy the TextCCChelp.txt file to all other workstations and servers
(Note: where, BOX is lx1, ds1,px1 etc)

**rcp --p TextCCChelp.txt BOX:/awips/fxa/data/TextCCCHelp.txt**

G.) ***[Note:]{.underline}*** You must run a --text localization on each
workstation and log out and log back in of each Text and Graphics
Workstation. This will be done at the end of the next step when updating
the afosMasterPIL.txt file.

**[Additional Information on the textCCChelp.txt file:]{.underline}**

This file contains help strings associated with CCC or XXX entries in
the Text

Browser.

An example of a section from the textCCChelp.txt is below:

**0 Bulletin No. 0**

**1 Bulletin No. 1**

**2 Bulletin No. 2**

####  3 Bulletin No. 3

**4 Bulletin No. 4**

**5 Bulletin No. 5**

**6 Bulletin No. 6**

**7 Bulletin No. 7**

**.**

**.**

**.**

**9V9 Chamberlain, SD**

**9W7 Currituck Cnty AP, Currituck, NC**

**AAA K-Lincoln/Logan Co, IL; U-Almaty, RA**

**AAF Apalachicola Muni, FL**

**.**

**.**

**[3. How to download the afosMasterPIL.txt file]{.underline}**

The updated afosMasterPIL.txt dataset belongs in /data/fxa/nationalData.
Localization then creates the afosMasterPIL.CCC from it and adds this
site-specific version to /awips/fxa/data/localizationDataSets/LLL.

A.) Log into ds1 as the fxa user

B.) Change directory to /data/fxa/nationalData

**cd /data/fxa/nationalData**

C.) For safety sake, make a copy of your current afosMasterPIL.txt file.

**cp -p afosMasterPIL.txt afosMasterPIL.txt.orig**

D.) ftp into the NOAA! Server and download the latest afosMasterPil.txt
file.

**ftp 165.92.25.15 (NOAA1)**

**login: ftp (use your e-mail address for password)**

**cd pub/ndm**

**get afosMasterPIL.txt**

**bye**

E.) Change the attributes and ownership of the afosMasterPIL.txt.

**chmod 775 afosMasterPIL.txt**

**chown fxa:fxalpha afosMasterPIL.txt**

F.) On each workstation, log into the workstation as the fxa user,

and run localization (-text option).

**cd /awips/fxa/data/localization/scripts**

**./mainScript.csh -text**

H.) Logout / login to the each Text Workstation and Graphics
Workstation.

An example of a section from the afosMasterPIL.txt is below:

**@@@18AA11**

**@@@18AA13**

**@@@18AA21**

**@@@18AA23**

**.**

**.**

**@@@24AU11**

**@@@5TCNMC**

**@@@90NUS**

**@@@ADADEN**

**.**

**[4. Asynchronous Product Scheduler Changes]{.underline}**

A.) Log into as1 as the fxa user

B.) Change directories to /data/fxa/workFiles/asyncProdScheduler

**cd /data/fxa/workFiles/asyncProdScheduler**

C.) For safety sake make a copy of your current aps_pil.tbl file.

**cp --p aps_pil.tbl aps_pil.tbl.orig**

D.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the aps_pil.tbl
file. (In the example below, the vi editor is used.)

**vi aps_pil.tbl**

D.) When completed to save and exit from vi.

**:wq!**

E.) Copy the aps_pil.tbl file to as2 for failover purposes.

**rcp --p aps_pil.tbl
as2:/data/fxa/workFIles/asyncProdScheduler/aps_pil.tbl**

**item E: the /data/fxa/workFiles/asyncProdScheduler directory is**

**mounted, so aps_pil.tbl is available to both as1 and as2. No need
for**

**failover copy.**

F.) Ensure that the afos2awips.txt file is update. Then stop and start
the ingest on as1 with the following commands. Remember, you must be the
fxa user on as1 to run these commands.

**stopTextDB.as1**

**startTextDB.as1**

**[5. Trigger Changes]{.underline}**

**[5a. LDAD Triggers]{.underline}**

A.) Log into ds1 as the fxa user

B.) Change directories to /awips/fxa/data/localization/LLL, where LLL is
your site ID

**cd /awips/fxa/data/localization/LLL**

C.) For safety sake make a copy of your current LLL-ldadSiteConfig.txt
file.

**cp --p LLL-ldadSiteConfig.txt LLL-ldadSiteConfig.txt.orig**

D.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the
LLL-ldadSiteConfig.txt file. (In the example below, the vi editor is
used.)

**vi LLL-ldadSiteConfig.txt**

D.) When completed to save and exit from vi.

**:wq!**

E.) Copy the LLL-ldadSiteConfig.txt file to ds2 for failover purposes.

rcp --p LLL-ldadSiteConfig.txt \\

ds2:/awips/fxa/data/localization/LLL/LLL-ldadSiteConfig.txt

**[5b. Local Triggers (CRS and FAX)]{.underline}**

A.) Log into ds1 as the fxa user

B.) Change directories to /data/fxa/siteConfig/textApps

**cd /data/fxa/siteConfig/textApps**

C.) For safety sake make a copy of your current siteTrigger.template
file.

**cp --p siteTrigger.template siteTrigger.template.orig**

D.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the
siteTrigger.template file. (In the example below, the vi editor is
used.)

**vi siteTrigger.template**

D.) When completed to save and exit from vi.

**:wq!**

**[5c. Hydro Triggers]{.underline}**

A.) Log into ds1 as the fxa user

B.) Change directories to /data/fxa/nationalData

**cd /data/fxa/nationalData**

C.) For safety sake make a copy of your current hydroTrigger.template
file.

**cp --p hydroTrigger.template hydroTrigger.template.orig**

D.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the
hydroTrigger.template file. (In the example below, the vi editor is
used.)

**vi hydroTrigger.template**

D.) When completed to save and exit from vi.

**:wq!**

**[5d Adapt Triggers]{.underline}**

A.) Log into ds1 as the fxa user

B.) Change directories to /data/fxa/nationalData/adaptTrigger.template

**cd /data/fxa/nationalData**

C.) For safety sake make a copy of your current adaptTrigger.template
file.

**cp --p adaptTrigger.template adaptTrigger.template.orig**

D.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the
adaptTrigger.template file. (In the example below, the vi editor is
used.)

**vi adaptTrigger.template**

D.) When completed to save and exit from vi.

**:wq!**

**[5e Trigger Localization]{.underline}**

The localization command uses the various trigger configuration files to
create a site specific master trigger file,
/awips/fxa/Informix/fxatextTriggerActions.txt. The command then deletes
the existing Informix watchWarn table and uses the
fxatextTriggerActions.txt file to recreate the Informix watchWarn table.

A.) Either log into ds1 as user fxa or make sure you are user fxa on ds1
before issuing the localization command.

B.) Change directories to /awips/fxa/data/localization/scripts

**cd /awips/fxa/data/localization/scripts**

C.) Run the localization command with the --text option

**./mainScript.csh --trigger**

**[6. Text Workstation Alarms]{.underline}**

**[6a. Personal Text Alarms]{.underline}**

A.) At the Text Workstation GUI, press the Alarm/Alert button.

B.) The Current Alarm Queue GUI will appear. From this GUI press the
Product List button.

C.) A GUI containing a list of the Alarm/Alert (AA) Products (Top) and
the Proximity Alarm (PA) Products (Bottom) will appear.

D.) Delete any old products from the appropriate AA/PA section by left
clicking on the Product ID and then hitting the Delete Entry button.

E.) Add any an AA and PA products by hitting the New AA Entry and/or New
PA Entry buttons respectively.

F.) The appropriate New AA or New PA GUI will appear. Enter the
appropriate Product ID in the GUI and determine whether you want it to
alarm (noise) or not by selecting or de-selecting the Alarm button.

G.) When finished, press the OK button.

H.) Also, press the Save & Close button before exiting the GUI.

**[6b. Site Protected Text Alarms]{.underline}**

A.) Log into a workstation as the root user

B.) Change directories to /awips/fxa/data/localizationDataSets/LLL,
where LLL is your site ID.

**cd /awips/fxa/data/localizationDataSets/LLL**

C.) For safety sake make a copy of your current
textAlarmAlertProducts.txt file.

**cp --p textAlarmAlertProducts.txt textAlarmAlertProducts.txt.orig**

D.) Use an editor of your choice to edit (i.e. remove any old and/or add
any new changes) the Communication Identifiers into the
textAlarmAlertProducts.txt file. (In the example below, the vi editor is
used.)

**vi textAlarmAlertProducts.txt**

D.) When completed to save and exit from vi.

**:wq!**

**[Section III -- IFPS/GFE formatter related changes]{.underline}**

**[Note:]{.underline}** For sites at pre-IFPS 16, the update to the
afos2awips.txt file mentioned in Section II is all that needs to be
completed. But for those sites, who have installed IFPS 16 or greater,
please carefully read and follow the instructions below.

A.) After the afos2awips.txt file has been updated, log onto px1 as user
ifps.

B.) Change directories to /awips/GFESuite/primary/data/textInstall

**cd /awips/GFESuite/primary/data/textInstall**

C.) Execute the formatter configuration script:

**python configureTextProduct.py**

**[Note:]{.underline}** The baseline version of the GFE formatters has
been updated to contain the correct WMO and PILs based on the updated
afos2awips.txt file. If you have modified any of these files (which will
appear at the SITE or USER level in the data/databases/TEXT/TextProduct
and data/databases/Text/TextUtility directories), you will manually need
to go into those files and correct the WMO and PILs based on the updated
afos2awips.txt configuration file. Use of the "diff" command may be
helpful in determining what changes may need to be made.