The Hotline has received several calls on NWS Mod Note 39 (DoD TCTO 551 or DoT EEM 6460.2 Change 17 Chapter 18) and NWS Mod Note 43 (DoD TCTO 555 or DoT EEM 6460.2 Change 21 Chapter 21) over the past week.

The following information should help you in completing these modifications.

NWS Mod Note 39, DoD TCTO 551, and DoT EEM 6460.2 Change 17 Chapter 18 -- Retrofit of RDA and PUP Fixed Disk Drive

1. Attachment 1, page A9, step 8t(1), line 2: Change 6j to 8t(3).

2. Attachment 1, page A10, step 8t(4): Replace the command option SIZ=250<Return> with the command option DEL/NOD<Return>.

3. Attachment 1, page A10, step 8v, line 2: Change 8j to 8x.

4. Attachment 2, page B9, step 7s(4): Replace the command option SIZ=250<Return> with the command option DEL/NOD<Return>.

5. Attachment 2, page B9, step 7s(5): After the line EBMFILE.DAT<Return>, add:

   PSFILE.DAT<Return>
   AUXMAP-.-<Return>

This will ensure your AUXMAPs are restored properly.

Note: If you have already performed this modification when this fax arrives, you can manually restore the information stored in these files (PSFILE.DAT & AUXMAP-.-) by having the Operations Focal Point perform these steps:

1. Read your AUXMAPs from optical disk using the A,R,B,<RPG>,<file no.> command at the PUP Applications Terminal. For additional information on using this command, see the WSR-88D Operator Handbook PUP - Volume II, page 2-150 & 2-151.

2. Configure the PUP to use your edited background maps using the C,B command at the PUP Applications Terminal. Place an M under the column for maps you have edited. For additional information on using this command, see the WSR-88D Operator Handbook PUP - Volume II, page 2-26 & 2-27.

3. Configure the WER Plane Assignment using the C,W command at the PUP Applications Terminal. For additional information on using this command, see the WSR-88D Operator Handbook PUP - Volume II, page 2-28 & 2-29.

NWS Mod Note 43 DoD TCTO 555 or DoT EEM 6460.2 Change 21 Chapter 21 -- Expansion of Narrowband Communications Ports in the RPG Communications Cabinet for Connection of AWIPS

In Attachment 3, Steps 3 & 4 (if step 4 is needed), you are told to update the configuration menu using Attachment 2, Figure 1.

1. Attachment 2, Figure 1 inadvertently left off the PUPID/PASSWD data for all APUP lines. This entry is required! Therefore, you should leave the PUPID/PASSWD that was set for existing APUPs and set the new AWIPS port entry to AWIP.

   Note: If you have multiple AWIPS ports on your RPG, set the PUPID/PASSWD to a more descriptive 4-character mnemonic for the location of the AWIPS system (e.g. for the NWSTC AWIPS port at Kansas City, the PUPID/PASSWD could be NWST). This mnemonic should assist your staff in knowing who will use this port.

2. Attachment 2, Figure 1 also inadvertently changed the LINE CLASS for one of the NAPUP lines. For all sites except Pittsburgh, Cleveland, Molokai, & South Kauai, the line with the PUPID/PASSWD of RDAT, should have the LINE CLASS set to NAPUP instead of RFC.

Formal publication change pages applicable to your agency will follow through official channels as soon as possible.