*COMDECK HISTORY FS3892  IDENT TO INTRODUCE MULTI-HOST A-A FEATURE CODE.
          CJB     82/11/09     TEXTNVF,TXTANVF,NVFCBPA,TXINNVF,NVFUMQE, 
                               NVFTCCT,NVFIBWD,NVFTICR,NVFTPVR,NVFAIAP, 
                               NVFTIAM,NVFIBOF,NVFTRVD,NVFADQE,NVFIAST, 
                               NVFAACC,NVFARAP
 *L580*    ************************************************ 
 NA5A001  RESOLVE NON-FATAL LOADER ERROR ON NON-DEBUG NIP BUILD.
          JCL    82/11/10    OCTCON 
  
 NA5A003  NETREL SHOULD ROUTE FILE ACCORDING TO JOB ORIGIN TYPE.
          DKE     82/11/23     NETREL 
 NA5A010  COLLECTOR JOB SHOULD ROLLOUT BEFORE THE TAPE REQUEST IS 
          MADE. 
          DKE     82/11/16     NAMSTRT
 NA5A014  DEFAULTING HD ON DEVICE STATEMENT IF HD IS NOT SPECIFIED
          FOR NON USER DEFINED TIPTYPES.
          IF THERE IS ONLY ONE LOGICAL LINK TERMINATING AT A NPU WHERE THE
          DEVICE IS DEFINED ON, OR IF FOR ALL LOGICAL LINKS TERMINATING AT
          THE SAME NPU, THE SAME HOST NAMES ARE USED THEN NDLP DEFAULTS 
          HD TO "NO". 
          IF HOST NAMES ARE DIFFERENT FOR ALL LOGICAL LINKS TERMINATING AT
          THE SAME NPU THEN NDLP DEFAULTS HD TO "YES".
          YCY     82/11/23     NDLNFCM
 NA5A016  SUPPRESSING DUPLICATE ERROR MESSAGES WHEN THERE ARE 
          MORE THAN ONE PORT NUMBER NOT BEING CONSECUTIVELY ASSIGNED ON 
          A GIVEN NODE. 
          YCY     82/11/22     NDLNFTM
 NA5A017  REMOVING DOP AND NOP AS RESERVED NAMES NOT TO BE USED 
          AS LEGAL APPLICATION NAMES. 
          YCY     82/11/19     NDLP2LF
 NA5A019  CHANGING THE RANGE OF MC FROM 0 TO 127 TO THE FOLLOWING 
          LEGAL RANGES : 03-1F,21-2F,3A-3C,3E-40,5B-60,7B-7E,AND 0. 
          USER DEFINED TIPTYPE WOULD STILL BE VALID FOR MC BETWEEN 0 TO 255.
          YCY     82/11/22     NDLNFCM,NDLCKRG
 NA5A020  INSERTING RANGE CHECKS FOR DHOST ON OUTCALL STATEMENT.
          DHOST CAN RANGE BETWEEN 00 TO HEX FF ONLY.
          YCY     82/11/22     NDLP2LF
 NA5A021  CHANGING THE UPPER LIMIT FOR FRAME ON LINE STATEMENT FROM 
          127 TO 7 AND CHANGING THE THE UPPER LIMIT FOR DFL ON LINE STATEMENT 
          FROM 65535 TO 1024. 
          YCY     82/11/22     NDLCKRG
 NA5A022  IMPLEMENTING XAUTO AS AN NDL KEYWORD. 
          XAUTO AND AUTO CAN APPEAR ON THE LINE STATEMENT IN ANY SEQUENCE,
          BUT THE LAST OCCURRENCE OF EACH OF THESE TWO KEYWORDS WOULD BE
          THE ONLY AUTO RECEC INDICATOR IN THE LINE STATEMENT.
           TSPEED IS EXTENDED TO 9600 WHEN LINE IS XAUTO AND CROSS CHECKING 
           IS DONE FOR LOW TSPEED AND HIGH AUTO REC INDICATOR OR HIGH 
           TSPEED AND LOW AUTO REC INDICATOR. ERROR 162 IS GENERATED FOR
           BOTH CASES.
          YCY     82/11/19     DATANDL,ER2CNDL,NDLPSS1,NDLSDAT,NDLLIST, 
                               NDLNFCM,NDLTBLT
 NA5A023  FIX FOR STATE TABLE ERROR 
          NIP/HBSTTP ERR AN=1,CN=3,18,12 ON AN
          APPLICATION INTERRUPT.
          CYB    82/12/02    STATTBL
 NA5A025  FIX NSTORE TO PARSE FIELD=VALUE ONE BY ONE. 
          FIX SUPERFLUOUS CODE GENERATED BY NFETCH MACRO. 
          FIX NFETCH/NSTORE TO USE MACREF FOR CROSS REFERENCE.
          FIX BAD FORMAL PARAMETER NAME IN NFETCH/ECHO STATEMENT. 
          JCL    82/12/03    NFETCHM,NSTOREM
 NA5A030  PROBLEM - PIP ISSUES FUNCTION CODE 100 TO HALT THE NPU.  THIS 
                    FUNCTION CODE ONLY STOPS MACRO MEMORY BUT THE REST
                    OF THE 2550 CONTINUES RUNNING.
          SOLUTION - PIP HAS BEEN CORRECTED TO ALWAYS ISSUE FUNCTION
                     CODE 200 TO HALT THE NPU.
          EG     11/30/82    PIP
 NA5A031  PROBLEM - PIP KILLS THE NPU WHEN THE FOLLOWING SITUATION
                    OCCURS.  PIP TELLS CCP TO RESUME INPUT.  AT THE 
                    SAME TIME, CCP IS SENDING PIP A BATCH INTERRUPT 
                    FOR THE INPUT DEVICE.  THE BATCH INTERRUPT CAUSES 
                    PIP TO CHANGE STATES AND NO LONGER ACCEPT BATCH 
                    DATA FROM CCP.  CCP PROCESSES THE RESUME INPUT AND
                    THEN SENDS MORE BATCH DATA TO PIP.  PIP DETECTS THE 
                    BATCH DATA AS A CCP PROTOCAL ERROR. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ACCEPT BATCH DATA AFTER
                     RECEIVING A BATCH INTERRUPT ON A CARD READER 
                     CONNECTION.
          EG     11/30/82    PIP
 NA5A034  IF CS RECEIVES A BREAK WHILE AN OUTBOUND *MSG* BLOCK IS 
          QUEUED FOR THE CONNECTION WITHIN CS, CS PROCESSES THE BREAK 
          INCORRECTLY (HANGS THE CONNECTION). 
          DGD     82/11/19     CSCBPA,CSCCPA,CSCPNQ,CSCUFS
 NA5A036  FIXING NDLP SO THAT IT ACCEPTS MORE THAN 13 NPU NAMES.
          YC.     82/11/12     NDLPSS1
 NA5A038  REMOVING W AS A VALID PARAMETER ON LINE STATEMENT,
          LEAVING THE ONLY W PARAMETER ON TERMINAL STATEMENT. 
          YC.     82/11/12     NDLPSS1,NDLNFCM,NDLLIST,NDLSDAT
 NA5A040  INCLUDING 752 AS A TERMINAL CLASS 
          IT WILL PASS 7 AS TC CODE TO NCF WHILE 751 AND 713 PASS 2 TO NCF. 
          YC.     82/11/12     NDLPSS1,NDLNFCM,NDLLIST
 NA5A041  NVF ACCOUNT FILE MESSAGE CONTAINS COLONS. 
          DKE     82/11/30     NVFIAST
 NA5A043  CORRECTIVE CODE FOR NIP ABORT WHEN APPLICATION SENDS
          A NETGET ON A NON-EXISTING ACN. 
          JCL    82/11/30    HPGET
 NA5A045  NDA ERROR MESSAGE UPDATE. 
          JCL    82/11/30    NDAS 
 NA5A046 MODIFIES ROUTINE NDAS TO CORRECTLY PROCESS CARDS FOLLOWING 
 A DIRECTIVE CARD THAT HAS ERRORS.
          ECT     82/11/24     NDAS 
 NA5A047 CHANGES "FILE XXXXXXX NOT FOUND" ERROR MESSAGE TO "DUMP FILE 
         XXXXXXXXEMPTY"". 
          ECT     82/11/17     NDAS 
 NA5A048  CORRECTIVE CODE FOR APPLICATION ABORTS WITH CPU ERROR EXIT
          ON A NETLOG CALL. 
          LTN    82/11/15    NETLOG 
 NA5A049  NVF ACCOUNT FILE MESSAGE HAVE COLONS. 
          DKE     82/11/30     NVFTIAM
 NA5A051  FIX FOR NAMI ABORTED BY DSP WHEN A NON-EXISTING 
          RECORD NAME WAS ASSIGNED. 
          JCL    82/11/30    NAMI 
 NA5A063  FIX FOR PIP TAKING DOWN BOTH NPUS ON SAME CHANNEL PROBLEM.
          SW    82/11/24    PIP 
 NA5A066  FIX FOR BUFFER MANAGEMENT ERROR ON BAD BSN. 
          BUILD ACKNOWLEDGE QUEUE ON TERMINATING PRU CONNECTIONS. 
          REMOVE OCTCON FROM RESIDENT AREA. 
          CYB    82/11/10    OCTCON,SKENIP,NPBACK,NPPCT 
  
 NA5A067  FIX FOR STATE TABLE ERROR 
          NIP/NBSTTP ERR HN=2,TN=3,CN=36,2,62 
          ON BAD BSN. 
 NA5A073  NIP FIX FOR ROLLIN/ROLLOUT PROBLEM WHEN THE 
          NETWORK IS UP FOR SEVERAL DAYS. 
          CYB    82/11/18    ACB,NWLNTRY
 NA5A077  FUNCTION LIST BUFFER ASSOCIATED WITH THE NO ACB SWAPIN
          ENTRY SHOULD BE MADE NON-MOVABLE TO PREVENT GARBAGE 
          COLLECTION FROM MOVING THE BUFFER, CAUSING XSAPP OR 
          HAPFAIL TO ABORT WITH BUFFER MANAGER ERROR. 
          CLEANUP NEIB TO SAVE SOME SPACE.
          JCL    82/12/01    HPNOFF,XSAPPRC,NEIB
 NA5A081  ALLOWING DBL PARAMETER ON DEVICE STATEMENT WHEN TIPTYPE IS
          USER DEFINED. DEFAULT VALUE OF 2 IS PROVIDED WHEN DBL IS NOT
          SPECIFIED.
          YCY     82/11/29     NDLNFCM
 NA5A082  FIX FOR PROTOCOL ERROR ON BAD ICT ON A
          CON/REQ/N . 
          CYB    82/12/01    HCSTTP 
 NA5A083  FIX FOR CCP HALT 10 - INVALID STATE TABLE ACTION
          ON ERROR CONDITION.  MOD TO DAYFILE A MESSAGE 
          BEFORE HALTING THE NPU.  ALSO CORRECT THE TEXT
          LENGTH ON NPI/IN MESSAGE. 
          CYB    82/11/29    NIPDEF,NBSTTP,NCSTTP,NNPIIN
 NA5A084 NDLP NOEW DEFAULTS UBL TO 7 FOR ALL PASSIVE DEVICES. 
          YCY     82/12/03     NDLNFCM
 NA5A085  FOR ALL TIPTYPES AT LEAST ONE CONSOLE DEVICE MUST BE DEFINED
          BEFORE A SET OF PASSIVE DEVICES, OTHERWISE A WARNING IS GENERATED.
          IF THERE IS MORE THAN ONE CONSOLE PRECEDING A SET OF PASSIVE
          DEVICES, THE LAST CONSOLE DEFINED BEFORE A SET OF PASSIVE 
          DEVICE DEFINITION BEGINS IS THE OWNING CONSOLE FOR ALL PASSIVE
          DEVICES THAT FOLLOW UNTIL A NEW CONSOLE DEFINITION BEGINS.
          YCY     82/12/03     ER1CNDL,NDLPSS1,NDLNFCM
 NA5A122  FIX FOR STATE TABLE ERROR 
          NIP/NBSTTP ERR HN=2,TN=12,CN=2,19,6.
          THIS OCCURS WHEN AN APPLICATION 
          ATTEMPTS A GET WHEN THE CONNECTION IS 
          TERMINATING.
          CYB    82/12/14    XSTTP
 NA5A126  PROBLEM - PIP DETECTS CCP PROTOCOL ERRORS WHEN BATCH INTERRUPT
                    FROM CCP CROSSES DOWNLINE SUP MSG FROM PIP.  THIS 
                    CAUSES PIP TO HALT THE NPU WITH A COUPLER ERROR 90. 
                    ALSO PIP SENDS ERR/LGL TO RBF IF IT PROCESSES AN
                    SET/DEV SUP MSG AFTER PROCESSING AN OFC/ABORT FROM
                    RBF.   RBF SENT THE SET/DEV SUP MSG BEFORE SENDING
                    THE OFC/ABORT SUP MSG.
          SOLUTION - PIP HAS BEEN CORRECTED TO BE MORE TOLERANT OF CCP
                     WHEN A BATCH INTERRUPT OCCURS AND MORE TOLERANT
                     OF RBF WHEN IT PROCESSES A OFC/ABORT SUP MSG.
          EG     12/13/82    PIP
 *L596*    ************************************************ 
 NA5A111  STATE TABLE UPDATE TO TURN OFF TLO FLAG WHEN RECEIVED A 
          DOWNLINE -MSG- BLOCK FROM APPLICATION ON AN BREAK 
          OUTSTANDING CONDITION.
          JCL    82/12/13    XSTTP,HPPUT,HBSTTP,STATTBL,SKENIP
 NA5A129  NIP ABORTED ON NBSTTP ERROR UPON RECEIVING AN UNEXPECTED
          -BACK- FROM CCP ON AN IVT CONNECTION THAT WAS JUST
          CONVERTED FROM A PRU CONNECTION BECAUSE OF RBF FAILURE. 
          NIP ABORTED ALSO ON HBSTTP ERROR WHEN RBF NETTED OFF AND THEN 
          FAILED, HAPFAIL SHOULD NOT ISSUE RECONNECT TRIGGER TO HBSTTP
          WHEN APPLICATION IS AWAITING NET/OFF/N FROM NVF.
          JCL    83/01/10    NPPCT
 NA5A153  A-A INTER-HOST FIXES. 
          CYB    83/01/17    HCONREQ,HCRRAPR,NCSTTP,
                             NNPIIN,HCSTTP,HAPFAIL
          JCL    83/02/04    QTGET,QTPUT,QTLINK,QTRMCOM 
 NA5A155  CS IMS NEEDS UPDATING.
          DKE     83/02/09     CSIBOT,CSSATM,CSSCHB,CSSCTR,CSSDNS,
                               CSSAEN,CSSATR,CSODOO,TEXTCS,CSESLE,
                               CSESLS,TEXTOV,TXCMDCS,CSDDNT,CSIBOF, 
                               CSIBWD,CSIBXT,CSIIMT,CSSROC,CSTITR,
                               CSTSCD,CSTSCT,CSESCM,CSESDE,CSOAHL,
                               CSOBOE,CSOGHL,CSOROO,CSSACO,CSSAED,
                               CSSASD,CSSDTC,CSSICT,TXTCTCS 
 NA5A161  MULTI HOST A-A ENHANCEMENT CODE.
          CJB      83/02/23 
 NA5A165  NOP CONNECTION HANGS WHEN REQUESTING THE STATUS OF
          ALL TERMINALS ON A LOGICAL LINK THAT IS NOT CURRENTLY 
          BEING SUPERVISED. 
          DKE     83/02/10     CSSRCA 
  FA4206  NPU STATISTICS MONITORING.
          REPORTS CPU UTILIZATION THRESHOLD EXECEED, AND
          BUFFER AVAILABILITY THRESHOLD EXECEED.
          AML     83/03/05     TEXTCS,CSICCC,CSSROC,CSIBXT,CSSDRC,
                               CSSASD,CSESES,CSSRCA,CSUCDB,CSSAAC 
  FA5161  SEND COPYRIGHT WITH BANNER
          AML     83/03/05     NVFTITE,NVFTCRN
  FA5167B  CLEAR SCREEN AFTER PASSWORD
          AML     83/03/05     TMSGNVF,NVFTILP
  FA5167C  LOG UNSUCCESSFUL LOGINS
          AML     83/03/05     TEXTNVF,TXTANVF,NVFTIAM,NVFTPUV,NVFTETI
 FA5214   MODIFY NVF TO ACCEPT NEW CPM 56 BLOCK FORMAT.  THIS IS IN 
          CONJUNCTION WITH THE NEW OS VALIDATION BLOCK STRUCTURE. 
          DKE     83/04/04     TEXTNVF,NVFAVVD,NVFIAST,NVFTPSV, 
                               NVFTVAA,NVFTVVD
 FA5392   NIP MOD TO SUPPORT NATIONAL CHARACTER SET.
          CYB    83/04/04    BCONV
 FN4376A   RBF TERMINAL TIMEOUT 
  
          THIS MOD DEFINES A NEW FIELD IN THE CON/REQ, CR/SWH,
          CR/ITE, AND ICN/TE SUPERVISORY MESSAGES.  THE CM LENGTH OF
          THESE MESSAGES IS NOT CHANGED.  A NEW FIELD IS ALSO DEFINED IN
          THE VALIDATION CONTROL BLOCK.  EACH OF THE NEW FIELDS DEFINED 
          IS 1-BIT IN LENGTH AND IS DESIGNED TO CONTAIN A HARDWIRED 
          TERMINAL FLAG(SET TRUE IF HARDWIRED, FALSE IF DIAL-UP). 
          THE TERMINAL TIMEOUT CODE IN RBF WILL USE THIS FLAG TO
          DETERMINE IF THE TERMINAL IS A CANDIDATE TO BE AUTO-LOGGED
          OUT DUE TO INACTIVITY.  ONLY DIAL-UP TERMINALS WILL BE
          CHECKED FOR INACTIVITY. 
  
          DEPENDENCIES - THIS MOD IS DEPENDENT ON THE RBF FEATURE CODE
                         AND THE MODIFICATION TO CCP TO INCLUDE 
                         THE LINE TYPE(SWITCHED/HARDWIRED) IN THE 
                         ICN/TE/R MESSAGE TO NIP. 
  
          ALT            01/10/83       SMAPPL, SMNVF, TEXTNVF, TXTANVF,
                                        SMNIP, HCRITER, NVFTACC,
                                        NVFTDSP, NVFTITE, NVFTRVD 
  
          FN4376A 
  
 FN4378A   CHANGE THE PASSWORD MASK TO 3-CHARACTERS 
  
          MODIFY NVF TO SPEED UP LOGIN PROCESSING BY ISSUEING 
          A PASSWORD MASK OF THREE CHARACTERS(H,I, AND #).
          THIS 3-CHARACTER MASK OFFERS EQUIVALENT SECURITY AS THE 
          PREVIOUS 4-CHARACTER MASK(M, (, ), AND X).
  
          ALT                01/10/83       TMSGNVF, NVFTILP
  
          FN4378A 
  
 FN5167A  SL PARAMETER ON LINE STATEMENT CHANGED TO AL. 
          THE RANGE OF AL IS NOW 0 TO 7 DECIMAL INSTEAD OF 1 TO 15. 
          THE FV FIELD OF THE AL NCB HAS BIT 2**3 FLAGGED FOR VALID 
          ACCESS LIMIT LEVEL. 
          YCY     82/12/10     DATANDL,ER1CNDL,ER2CNDL,NDLNFCM,NDLSDAT, 
                               NDLLIST,NDLCKRG,NDLPSS1
 FS2873A  NAM QBLK/QMSG FEATURE CODE. 
          JCL    83/03/23    HBSTTP,HPPUT,HFASTQ,HPGET
                             NFOB,NXBLINK,NEIB1,ACNB,MISCOM 
 FS2873B  NIP USER BREAK AND A-A BRK/RST BLOCKS FEATURE CODE. 
          ABA    83/03/30    XSTTP
                             NEIB1,NBSTTP,NPBRK,HPGET,HPPUT 
                             HBSTTP,UPACNB3,HSFCBRK,NXBLOCK,UPDACNB 
 FS2873C  FEATURE CODE TO CHANGE THE RECONNECT PROTOCOL 
          EXCHANGE BETWEEN NVF AND NIP SO THAT A RECONNECT NORMAL 
          RESPONSE IS NOT ISSUED ON A-A CONNECTIONS.
          CJB     83/04/06     NVFATAC
 FS2873D  CHANGE PIP TO ACCEPT NEW QBLK AND QMSG BLOCK TYPES AND
          PROCESS THEM THE SAME WAY AS BLK AND MSG BLOCKS 
          RESPECTIVELY. 
          EG     03/31/83    PIP
 FS4334A  QTRM USER BREAK FEATURE CODE. 
          JCL    83/03/22    QTGET
 FS4334B  NAM USER BREAK FEATURE CODE.
          JCL    83/03/22    SUPMSG,SMAPDEF,SMAPPFC 
 FS4334C  TVF USER BREAK FEATURE CODE.
          JCL    83/03/22    TVF
 FS4334E  ADD SUPPORT OF NEW USER BREAK PROTOCOL TO CS. 
          DKE     83/04/08     TEXTCS,CSCANT,CSCDQE,CSCPNT,CSCUFS,
                               CSDDNT,CSCBPA
 FS4334F  ADD NEW USER BREAK PROTOCOL TO NVF. 
          DKE     83/04/08     TXTANVF,NVFCAUT,NVFCCPA,NVFCDQE,NVFCUFS, 
                               NVFDDNT,NVFTBRK,NVFTDQE
 FS4398A  NAM K-DISPLAY ENHANCEMENTS. 
          PROCESS DB,DE,LB,LE,RS,LR,DU COMMANDS 
          FOR NAM.
          CYB    83/04/01    NIPDEF,NIPTXT,INIP,NEIB, 
                             NIP,KNAMMOD,KNAMCOM,XEXEC, 
                             NNETREL,NXDCB,INIPD
 FS4398B  NAM HOST REGULATION LEVEL SUPPORT FEATURE CODE. 
          JCL    83/03/28    MGETC
 FS4398C  NAM HOP TO HOP MESSAGE FEATURE CODE.
          JCL    83/03/25 
 FS4400A  NAMI ENHANCEMENT - ALLOW RESTART OF APPLICATIONS. 
          ALSO CREATE NRF1 AND NRF2 FILES FOR NIP IN ORDER TO 
          SUPPORT NAM K-DISPLAY LOG RELEASE FEATURE.
          CYB    83/04/04    NAMI,NMI=IO1,NMI=RTE 
 FS4400B  UPDATE TO NAMSTRT-ADD NFR1 AND NRF2 RECORDS 
          TO JOBNIP.
          CYB    83/04/11    NAMSTRT
 FS4400C  MOD TO NAMSTRT TO HANDLE THE NIP TRACE FILE 
          WITH THE MC PARAMETER.
          CYB    83/04/18    NAMSTRT
 FS4401B  DEFERRED SUPERVISION FEATURES FOR CS. 
          DKE     83/04/08     SMCS,SMCSDEF,CSSACO,CSIBWD,CSEDEQ, 
                               CSSANS,CSESSM,CSSAGO,CSSTNO,CSSAED,
                               CSSDNR,CSSASD,CSSROC,CSSAIN,CSSANO,
                               CSESAM,CSESCM,CSESEC,CSESCS,CSESIM,
                               CSESLL,CSESLS,CSESNS,CSESOD,CSESOM,
                               CSESTR,CSESTS,CSSDRC,CSOAHL,CSOBOE,
                               CSOGHL,CSIBOT,CSIBPT,CSOROO,TEXTCS,
                               CSLSIT,CS,CSSAST,CSSCSR,CSSAEN,
                               CSSTNS,CSSAMS,CSSCHB,CSSATM,CSSATR,
                               CSSCTR,CSSATD,CSESDE,CSSADL,CSSTCM,
                               CSSRCA,CSSARE,CSSASO 
 FS4401A  DEFERRED SUPERVISION FEATURE. 
          STATUS OF MULTIPLE NPUS.
          AML     83/04/05     HOC$NS,NS$HST,NS$HCP 
 FV5167A  CORRECT FIELD WIDTH OF AL FIELD IN NVF/APPL SM-S. 
          DKE     82/12/13     SMNVF,SMAPPL,TEXTNVF,TXTANVF 
 NA5A006  PROBLEM - PIP CANNOT HANDLE THE CASE WHEN IT RECEIVES PRU 
                    INPUT ON A CARD READER CONNECTION THAT HAS BEEN 
                    CONVERTED TO AN IVT CONNECTION DUE TO RBF FAILING.
                    PIP STARTS PROCESSING THE INPUT AS PRU INPUT, BUT 
                    AFTER READING IN THE NETWORK HEADER AND DETERMINING 
                    THE CONNECTION TO BE A IVT CONNECTION, PIP BEGINS 
                    PROCESSING THE INPUT AS IVT INPUT.  THE RESULT IS 
                    THAT PIP USES THE FBA, CBA, AND LBA INTERNAL ADDRESS
                    POINTERS WITHOUT INITIALIZING THEM.  THIS CAUSE PIP 
                    TO OVERWRITE THE LIMBO BUFFER TABLE AND NIP OVERLAY 
                    TABLE.
          SOLUTION - PIP HAS BEEN CORRECTED TO CHECK FOR PRU INPUT ON 
                     IVT CONNECTIONS AND DISCARD THE PRU INPUT AFTER
                     SENDING NIP A WORKLIST WITH A NEW ERROR CODE.
          EG     01/05/83    PIP
 NA5A039  THIS IDENT ALLOWS USER TO SPECIFY VALUES FOR PARAMETERS ON
          LINE,TERMINAL AND DEVICE STATEMENT UP TO DECIMAL 255 FOR ONE
          WORD FN/FV ENTRY AND UP TO  65535 FOR TWO WORD FN/FV ENTRY, 
          WHEN TIPTYPE IS USER DEFINED. 
          ERROR 100 IS STILL GENERATED IF PARAMETERS IS OUTSIDE THIS RANGE. 
          YCY     82/12/21     NDLNFCM
 NA5A079  CS ABORTS WITH *BAD NCF READ* DAYFILE MESSAGE.
          DKE     82/12/17     CSIBXT 
 NA5A088  NDLP GENERATES DAYFILE MESSAGE CONCERNING WARNING NUMBER
          WITH RESERVED FIELD WIDTH OF 12 BITS FOR WARNING COUNT ONLY.
          YCY     82/12/10     NDLMAIN
 NA5A092  NDLLIST IS CHANGED TO REPORT TA VALUES FOR USER TIPTYPES. 
          YCY     82/12/10     NDLLIST
 NA5A101  NDLP NOW MAKES DIRECT ENTRY TO NCF FOR UBZ AND DBZ WHEN 
          TIPTYPE IS USER DEFINED.
          YCY     82/12/07     NDLNFCM
 NA5A105  NTOTBTS SHOULD CHECK FOR MATCHING HOST NODE NUMBER
          BEFORE DISCARDING QUEUED NPU/IN/R FOR NS. 
          JCL    82/12/08    NTOTBTS
 NA5A109  FIX HPUTF TO RETURN FIRST WORD OF BAD NETPUTF TEXT ARRAY
          ON AN ERROR LOGICAL CONDITION.
          JCL    82/12/09    HPUTF
 NA5A110  NVF ADDS AN EXTRA DAY TO NOVEMBER.
          AML     83/01/28     NVFTCCT
 NA5A112  CS DOES NOT CRACK ITS CONTROL CARD. 
          DKE     82/12/14     CSLSIT 
 NA5A113  INTRODUCE NEW NS CONTROL STATEMENT PARAMETER NDFCT TO 
          ALLOW INSTALLATION TO SPECIFY FILE CATAGORY OF NPU
          DUMP FILES. 
          JCL    82/12/13    NDF$NS,COM$NS,NS$CRA 
 NA5A118  REMOVE QTGET CODE THAT PROCESSES UPLINE FC/STP AND
          FC/STRT SUPERVISORY MESSAGES WHICH ARE NO LONGER VALID
          FOR MULTI-HOST NETWORK. 
          JCL    82/12/17    QTGET
 NA5A119  NIP SHOULD DAYFILE COUPLER ERRCOR CODE FROM HE/CP.
          JCL    82/12/14    NPHECP 
 NA5A120  COMMAND RECOGNIZER CANNOT RECOGNIZE ANY VALUE 
          (KEYWORD=VALUE) STARTING WITH "A" AS THE FIRST
          CHARACTER.
          AML     83/01/28     SSRRCS 
 NA5A121  MACREF NFETCH AND MACREF NSTORE CAUSE ASSEMBLY ERRORS.
          JCL    83/01/14    NFETCH,NSTORE
 NA5A123  NVF ABORTS WITH *NVFTACC - CANNOT FD PDCT ENTRY*
          MESSAGE IN DAYFILE
          DKE     82/12/17     NVFTRCN
 NA5A124  MODIFY NAMI TO SAVE THE NETWORK MEMORY FILE 
          AS A PRIVATE FILE INSTEAD OF A PUBLIC FILE. 
          CYB    83/04/18    NMI=IO1
 NA5A130  A NEGATIVE NETWAIT TIME SPECIFIED FOR NETWAIT CALL
          WOULD CAUSE APPLICATION TO STAY IN NETWAIT STATE JUST 
          ABOUT FOREVER IF NO UPLINE MESSAGES ARE QUEUED FOR IT.
          JCL    83/01/14    NETWAIT
 NA5A140  AIP ROUTINE NP$ERR IS NOT DAYFILING THE SECONDARY ERROR 
          MESSAGE FOR RC = 99.
          JCL    83/01/26    NP$ERR 
 NA5A142  NAMSTRT PROCEDURES DO NOT SUPPORT SECONDARY INVOCATIONS.
          DKE     83/04/21     NAMSTRT
 NA5A146  INSERTING A NEW DECK IN NDLP FOR ITS IMS. 
          A NEW DECK IS CREATED TO INSERT A SUMMARY IMS FOR NDLP IN THE 
          NAMPL. SOME CHANGES ALSO OCCUR IN NDLP EXISITNG DECKS IN ORDER
          THAT THE "DOCMENT" PROGRAM CAN RETRIEVE IMS FOR EVERY DECK IN 
          NDLP INCLUDING THE NEW DECK ADDED.
          YCY     83/01/17     NDLNFCM,SYNGEN,NDLNFTM,NDLP2LF 
 NA5A148  NVF ABORTS WITHOUT ERROR MESSAGES ON UNKNOWN
          RECORD ON LCF.
          AML     83/02/11     NVFIAST
 NA5A151  ANAME ON INCALL STATEMENT WAS ACCEPTING HEXIDECIMAL DIGITS
          RATHER THAN ALPHANUMERIC CHARACTERS. NOW IT ACCEPTS CHARACTER 
          AND CONVERTS EACH CHARACTER INTO 8 BIT ASCII. ADDITIONAL
          CHECKS ARE INSERTED INTO UDATA TO ENSURE THAT IT ACCEPTS ONLY 
          HEXIDECIMAL DIGITS. 
          YCY     83/01/28     NDLLIST,NDLPSS1,NDLP2LF
 NA5A154  NVF IMS NEEDS UPDATING. 
          DKE     83/02/10     TEXTNVF,TXTANVF,NVFUMVD,NVFURDS,NVFUROS, 
                               NVFUAFV,NVFUFVO,TXVCBNV
 NA5A156  SERVICES AND SCHEDULING IMS NEEDS UPDATING. 
          DKE     83/02/09     SSSPES 
 NA5A160  BAD CTRL/TCD IF INPUT CHARACTER TPYE 3 IS USED FOR
          SYNCHRONOUS COMMANDS. 
          JCL    83/02/09    BDELINK,HPGET,XEXEC,KDIS,ACNB,BLINK,BFSCAN 
 NA5A159  NVF ACCEPTS 8-CHARACTERS USER NAME, AS LONG 
          AS THE FIRST 7-CHARACTERS ARE CORRECT.
          AML     83/02/10     NVFTETI
 NA5A162  FIX FOR RELEASE COLLECTOR JOB ON NAMSTRT RECORD.
          JCL    83/02/05    NAMSTRT
 NA5A166  PFAM AND PUSER ARE ADDED AS PARAMETERS ON USER STATEMENTS.
          ONLY ONE OF PFAM, DFAM AND MFAM OR ONE OF DUSER, PUSER AND
          MUSER MAY EXIST ON ANY ONE USER STATEMENT.
          YCY     83/03/21     DATANDL,ER2CNDL,NDLSDAT,NDLPSS1,NDLP2LF
 NA5A168  ON INCALL STATEMENT, FAMILY NAME AND USER NAME ARE NOW
          ZERO FILLED.
          YCY     83/02/22     NDLLIST,NDLP2LF,IBLCF
 NA5A170  RESOLVE INVALID RETURN PARAMETER FROM ROUTINE -LOCLLCB- 
          IF THE SPECIFIED LOGICAL LINK DOES NOT EXIST. 
          JCL    83/02/16    LOCLLCB
 NA5A172  ROUTINE SSTETS ERRONEOUSLY USED NEW TABLE LENGTH
          WHEN COMPUTING NUMBER OF WORDS TO MOVE AFTER ENLARGEMENT
          OF TABLE. CALCULATE COUNT PRIOR TO ALLOCATING NEW TABLE 
          SPACE.
          DKE     83/02/23     SSTTMR 
 NA5A173  NIP TAKES LOGICAL LINK DOWN UPON RECEIVING A REG/LL 
          IN NETWORK SHUTDOWN MODE. 
          JCL    83/03/01    BLDLLCB,NPREGLL
 NA5A175  NIP STRUCTURE REORGANIZATION TO FREE UP SPACES TO REDUCE
          NIP FL SIZE.
          JCL    83/04/25    XEXEC,BFSCAN,KPTYPIN,XCHKPCR,XSACB 
                             IRECVR,XENDRPV,RMAIN,KPCLNUP,KDSTIN
                             KDIS,NEIB,SKENIP 
 NA5A177  USER STATEMENT LIMIT TOO LOW.  CHANGEDSIX, 12-BIT LCF FIELDS
          TO 18 BITS.  ALSO CHANGED MAXIMUM USER STATEMENT LIMIT
          (IN NDLP2LF) FROM 2**12-1 TO 2**18-1. 
          MSC     83/05/20     ATLCF,UTLCF,IBLCF,OBLCF,NDLP2LF
 NA5A178  PROBLEM - PIP IMS WAS NOT COMPLETELY UPDATED AT LEVEL 580.
          SOLUTION - PIP IMS HAS BEEN UPDATED TO DESRIBED NEW DATA
                     STRUCTURE AND INITIALIZATION PROCEDURE INTRODUCED
                     AT LEVEL 580.
          EG     03/07/83    PIP
 FA5206   IMPLEMENT CHANGES FOR *EST EXPANSION* IN NOS V2.2.
          DKE    04/19/83    PIP
  NA5A179  COMMAND RECOGNIZER NOT RECOGNIZING SINGLE CHARACTER VALUE. 
          AML     83/03/07     SSRRCS 
 NA5A180  NVF SETS DT INCORRECTLY FOR AN INTER-HOST A-A CONNECTION. 
          DKE     83/04/11     NVFARAP
 NA5A182  CODE TO BLANK THE SWITCH APPLICATION NAME OF THE
          CR/SWH/R SM FOR A-A CONNECTIONS.
          CJB     83/03/10     NVFARAP,NVFAIAP,NVFAVVD
 NA5A183  THE REASON NDLP ABORTS WITH CM OUT OF RANGE IS
          THAT THE BUFFER SIZE AT 7R2 FOR NCB IS 200 CM WORDS AND 
          ANY NCB BIGGER THAN THAT WILL CLOBBER THE NCF INDEX WHICH 
          IMMEDIATELY FOLLOWS THE NCB TABLE. NEW BUFFER SIZE OF 600 
          CM WORDS IS ALLOCATED FOR NCB.
          YCY     83/05/10     NDLTBLT
 NA5A185  LOGICAL LINK STATUS NOT DISPLAYED AFTER ST,TES,LL=LL410 
          COMMAND ISSUED. 
          DKE     83/04/18     CSSAST 
 NA5A187  PROVIDE SYMBOLIC REFERENCES FOR SYNCHRONOUS SUPERVISORY 
          MESSAGES IN APPLICATION CHARACTER TYPE 3 FORMAT TO
          AIP NFETCH AND NSTORE PROCEDURE USERS.
          JCL    83/06/13    SUPMSG,SMAPPL
 NA5A189  IDLING DOWN IAF CAUSE NVF TO ABORT WITH AN *SM NOT
          ROUTED MESSAGE. 
          DKE     83/04/07     NVFOPSC
 NA5A190  QTRM RETURNS REASON CODE *LOGICAL ERROR* IF APPLICATION 
          ATTEMPTS TO SEND DATA ON A NON-EXISTENT CONNECTION. 
          JCL    83/04/20    QTGET,QTPUT
 NA5A191  ON TERMINAL STATEMENT, RIC IS DEFAULTED TO "YES" FOR
          BISYNC AND HASP TIPTYPE AND "NO" FOR ALL OTHER TIPTYPES RESPECTIVELY. 
          YCY     83/03/21     NDLNFCM
 NA5A192  UBZ SHOULD BE INTERNALLY ENCODED AS MULTIPLES OF 100 IN 
          APPROPRIATE LOCATION WITHIN THE LCF FOR EACH OCCURRENCE OF INCALL 
           AND OUTCALL STATEMENTS. ALSO DEFAULT IS 200 WHICH IS 2 IN LCF. 
           LEGAL RANGE FOR UBZ IS 1 THROUGH 200.
          YCY     83/03/25     NDLLIST,NDLCKRG,NDLP2LF
 NA5A193  TC=3 IS ALLOCATED TO 721 TERMINAL. IT WILL BE THE SAME AS 
          TC=2 EXCEPT THAT THE HOME CURSOR AND CLEAR SCREEN SEQUENCE SENT TO
          THE TERMINAL WILL BE FF(X'OC) 
          YCY     83/03/24     NDLNFCM,NDLLIST,NDLPSS1
 NA5A195  ADDING EOF AS A PARAMETER ON TERMINAL STATEMENT. EOF=NO OR
          EOF=YES WILL PASS A EOF FNFV TO THE LINE RECORD. EOF IS VALID FOR 
          MODE 4  AND USER TERMINAL ONLY. THE DEFAULT FOR MODE 4 TERMINAL 
          IS NO. FN VALUE FOR EOF IS 111 AND KEYWORD ID FOR EOF IS 127. 
          YCY     83/03/28     DATANDL,NDLNFCM,NDLSDAT,NDLLIST,NDLPSS1
 NA5A196  ADDING ARSPEED PARAMETER TO LINE STATEMENT. ARSPEED 
          IS DEFAULTED TO YES FOR AUTO RECOGNITION LINES AND TO NO
          OTHERWISE. WHEN ARSPEED IS SET OR DEFAULTED TO YES, BIT 1 OF
          THE TT BYTE IS SET, OTHERWISE BIT 1 IS IS CLEARED.
          YCY     83/03/29     DATANDL,NDLNFCM,NDLSDAT,NDLLIST,NDLPSS1, 
                               NDLTBLT
 NA5A199  FIX NIP TO ASSIGN PROPER CONNECTION PRIORITY TO 
          APPLICATION-TO-APPLICATION CONNECTIONS. 
          ABORT NIP ON RECEIVED BAD BSN ON A -BACK-.
          JCL    83/04/06    BLDNCNB,NICNAPX,NPBACK 
 NA5A200  ADDING USER VALUES SDT12 TRHOUGH SDT15 AS LEGAL VALUES
          FOR SDT PARAMETER ON DEVICE STATEMENT. SDT12 THROUGH SDT15 HAVE 
          INTERNAL VALUES 12 THROUGH 15 RESPECTIVELY. ALSO, THESE VALUES ARE
          USED INDEPENDENT OF TIPTYPE AND DEVICE TYPE. CONSTRAINTS ON 
          TIPTYPE AND DEVICE TYPE VERSUS ALL OTHER VALUES OF SDT STILL MAINTAIN.
          YCY     83/03/31     NDLNFCM,NDLLIST,NDLPSS1
 NA5A201  ADDING DEVICE TYPE "AP" TO DEVICE STATEMENT. THE INTERNAL 
          VALUE FOR AP IS 6. ALSO, WHEN  DT=AP, UBZ IS DEFAULTED TO 200,
          NDLP SETS TO 2 AND DBZ IS DEFAULTED TO 128. AP IS ALLOWED ONLY
          FOR STIP=X25 . ALSO CHECKS FOR CTYP=PVC USED ONLY FOR STIP=X25
          IS INCLUDED.
          YCY     83/04/05     NDLNFCM,NDLLIST,NDLPSS1
 NA5A202  REMOVING FACILITIES FAC1-FAC31 BEING SPECIFIED ON INCALL
          STATEMENT. THE SAMAP FOR FAC1 THROUGH FAC31 IN DECK NDLSDAT IS
          CHANGED  SUCH THAT THEY MAY ONLY APPEAR ON OUTCALL STATEMENTS.
          YCY     83/04/05     NDLSDAT
 NA5A203  CORRECTIVE CODE TO INSERT THE LENGTH OF CALL USER 
          DATA INTO THE FOURTH OCTET OF CALL USER DATA PROTOCOL ID
          FIELD.
          CJB     83/04/06     NVFAIAP
 NA5A204  CORRECTIVE CODE TO INTRODUCE NEW ALGORITHM FOR
          CHECKING THE FACILITIES OF AN INCALL TO THE FACILITIES
          OF THE INCALL BLOCKS. 
          CJB     83/04/06     TEXTNVF,NVFARAP,NVFAVVD
 NA5A206  CORRECTIVE CODE TO CORRECTLY DEFINE THE FIELDS FOR
          UPLINE BLOCK SIZE AND UPLINE BLOCK LIMIT IN NVF AND THE 
          COMMON DECK SCANNED BY NIP. 
          CJB     83/04/06     SMNVF,TEXTNVF,NVFARAP,NVFAIAP
 NA5A207   FIX FOR X.25 APPLICATION TO APPLICATION CONNECTION 
          PROCESSING. 
          JCL    83/03/31    NCNB,NPNIPSM,BLDNCNB,HCSTTP
                             NCSTTP,NICNAPX 
 NA5A208  BEFORE HOST TABLE IS PACKED INTO NCB WORDS, HOST NAMES
          ARE NOW SORTED IN ALPHABETICAL ORDER BEGINNING FROM THE LOWEST
          TO THE HIGHEST ACCORDING TO THEIR DISPLAY CODE VALUE. HENCE 
          IDENTICAL HOST NAMES WILL BE GROUPED TOGETHER AND BLANK HOST
          NAMES WILL BE APPEARING AT THE BOTTOM OF THE HOST DISPLAY.
          YCY     83/04/07     NDLNFTM,NDLTBLT
 NA5A209  ALERT HOST OPERATOR WHEN AN UPLINE BLOCK ADDRESSED TO 
          AN UNKNOWN HOST NODE IS RECEIVED. 
          JCL    83/04/22    NGIGO,NPHOPMS,KHOPMSG
 NA5A212  ALLOW TERMINATOR FOR K.* COMMAND WHILE NAM-S K
          DISPLAY IS IN APPLICATION MODE. 
          JCL    83/04/21    KPTYPIN
 NA5A213  A CONTROLLING NOP LOGGING OUT CAUSES CS TO ABORT. 
          DKE     83/04/21     CSSANS,CSSTNS,CSSTNO,CSSAED
 NA5A214  ADDING SHOST ON OUTCALL STATEMENT. IT ACCEPTS 1-6 HEXIDECIMAL 
          DIGITS AND DEFUALTS TO SNODE IF IT IS NOT SPECIFIED. IF UDATA 
          IS NOT USED AND SHOST IS SPECIFIED THEN NDLP WILL BUILD UDATA FROM
          SHOST,DENODE AND ANAME. 
          YCY     83/04/18     NDLSDAT,NDLP2LF
 NA5A215  NVF SHOULD NOT IGNORE BLK BLOCKS DURING LOGIN DIALOGUE. 
          DKE     83/04/21     TEXTNVF,NVFCAUT,NVFCUFS,NVFTDQE
 NA5A216  CHANGE PROTOCOL OF TURNING ECHO PLEX OFF AFTER THE PASSWORD 
          PROMPT SO THAT NO TYPE AHEAD DATA WILL BE LOST. 
          DKE     83/04/21     NVFTILP,TEXTNVF,NVFCAUT,NVFTDQE,NVFCCPA, 
                               NVFCDQE,NVFTITE,NVFTBRK,NVFTCRN,NVFTETI, 
                               NVFUMQE,NVFTTCD,NVFDDNT,TXTANVF
 NA5A217  ADD NEW PARAMETER RECORDS FOR MULTI-HOST ENVIRONMENT. 
          DKE     83/05/03     NAMSTRT
 NA5A218  CORRECT THE INTRHOST CONNECTION ABL SETTING.
          CJB     83/04/19     TEXTNVF
 NA5A219  SEND COMMAND HANGS OPERATOR CONNECTION. 
          DKE     83/04/21     CSSASD 
 NA5A220  IBUBL, IBUBZ, OBUBL AND OBUBZ ARE NOW REDEFINED IN ITEM 
          WIDTH. THEY ARE ALL 8 BIT ITEMS WITH UBL STARTING FROM BIT 36 
          AND UBZ FROM BIT 44.
          YCY     83/04/21     IBLCF,OBLCF
 NA5A221  NVF SHOULD SUPPORT PRIMARY FAMILY AND USER. 
          DKE     83/04/21     NVFTILP,NVFTPVR
 NA5A224  INFO COMMAND AT THE K-DISPLAY CAUSES CS TO ABORT. 
          DKE     83/04/22     CSSAIN 
 NA5A225  PROBLEM - TRACE FILES NOT BEING COPIED PROPERLY.
          THE FORMAT OF THE TRACE FILES HAVE BEEN MODIFIED
          TO BE MULTI-FILE FILES.  EACH FILE WILL HAVE A
          SEPARATE HEADER RECORD. 
          CYB    83/06/01    NAMSTRT
 NA5A226  NAMSTRT MOD FOR SERVICE CLASS CHANGES IN NOS 2.2
          CYB    83/05/18    NAMSTRT
 NA5A227  PROCESSING OF CR/CB AND TIME OUT AT THE SAME TIME CAUSES NVF
          TO SEND OUT TWO CS/TRM-S FOR THE SAME CONNECTION. 
          DKE     83/04/22     TXINNVF
NA5A228   CHANGED INITIAL MEMORY ALLOCATION FROM 600 TO 200.  NOW USING 
          DYNAMIC MEMORY ALLOCATION RATHER THAN STATIC ALLOC. FOR NCB.
          TO VERIFY FIX, USED NDLMUG2 (UN=YCY2423) WITHOUT CURRENT
          MODS TO PRODUCE AN NCF.  COMPARED THAT WITH AN NCF GENERATED
          WITH AN NDLP WHICH HAD THE MODS.  USED VERIFY AND TDUMP 
          UTILITIES TO CHECK DIFFERENCES (TIME AND VERSION NUMBER DIFFERED).
          MSC     83/06/07     NDLNFTM,NDLTBLT
 NA5A230  FIX FOR MONITOR CALL ERROR WHEN CS OR NS FAILS. 
          CYB    83/04/25    PT,HPNOFFN,KNAMMOD,NCREGCP,
                             NTOTBTS,HPNONSA,HPPUT,KAPIGP,
                             HCSUPCB,NPREGCP,NPREGLL
 NA5A231  PROBLEM - PIP RECEIVED PRU INPUT WHEN IT WAS TOLD BY CCP TO 
                    EXPECT IVT INPUT.  PIP GOT CONFUSED AND OVERWROTE 
                    RA+1.  THIS CAUSED NAM TO FAIL WITH A MONITOR CALL
                    ERROR.
          SOLUTION - PIP HAS BEEN CORRECTED TO DETECT THIS CCP ERROR
                     CONDITION AND KILL THE NPU WHEN IT OCCURS.  THE
                     SAME PROBLEM WAS FIXED IN NOS VERSION 1 WITH PSR 
                     NA20605. 
          EG     05/31/83    PIP
 NA5A234  CODE TO SET THE WINDOW AND PACKET SIZE OF THE PAAC
          ENTRY WHEN THERE ARE NO FACILITIES REQUESTED. 
          CJB     83/04/29     NVFARAP
 NA5A235  CHANGE KNAMDFL TO ACCEPT FL=XXXXXX TYPE-IN WHICH
          WOULD REDUCE FL ALERT THRESOLD. 
          JCL    83/05/26    KNAMDFL
 NA5A236  REORGANIZE K DISPLAY ROUTINES TO MOVE KADD/KDEL ROUTINES
          ROUTINES TO OVERLAYS TO HELP MEETING DR. WORKLIST 
          PROCESSING IS INTRODUCED TO ADD AND DELETE ENTRY(S) 
          FROM NAM STATUS DISPLAY.
          JCL    83/05/04    KDIS,KINITBF,KSTTAB,KADD,KDEL
                             BLDACB,BLDLLCB,XCHKCET,RELACB, 
                             RELLLCB,NPESTOF,BLDKWL,KCHANGE,
                             KDSTIN,NPREGLL,MISDEF,OVLNAME, 
                             OVLSTAT,SKENIP 
                             BLINK,BDELINK,NPREGLL,XSACB,BLDACNB
                             BLDNCNB,RELACNB,RELNCNB,KAPIGP,HPNONVF 
 NA5A237  NIP WOULD DAYFILE *PROTOCOL VIOLATION, NPU DUMP REQUEST 
          SENT* WHEN IT DETECTS A PROTOCOL VIOLATION FROM CCP 
          AND SENDS A NPI/IN TO CAUSE A CCP HALT 10. A NIP FL DUMP
          WILL ALSO BE TAKEN AT THE SAME TIME.
          JCL    83/05/05    KNAMCOM,XDUMPFL,NNPIIN 
 NA5A238  NIP MAY FAIL WITH CPU ERROR EXIT UPON RECEIVING A 
          BAD BSN -BACK- BLOCK FROM THE NPU. NPBACK AND NBADBSN 
          ROUTINES ARE REWRITTEN TO RESOLVE THE PROBLEM.
          JCL    83/05/01    NRELBLK,NPBACK,NBADBSN,NPBRK 
 NA5A239  NIP SHOULD SUPPORT CONTROL STATEMENT PARAMETER WITH VALUE 
          GREATER THAN 9. 
          CLEANUP INPARU COMDECK TO REMOVE UNUSED INSTALLATION
          PARAMETERS. 
          FIX INIP TO RECOGNIZE MC=0. 
          FIX INIP TO RECOGNIZE N1PRUB,N2PRUB,N3PRUB PARAMETERS 
          PROPERLY. 
          JCL    83/05/03    INPARU,INPARUT,HPRUON,INIP 
 NA5A240  MAKE NETWORK MAINTAINENCE COMMANDS DB,DE,LR,RS,LB,LE
          VALID FOR ALL APPLICATIONS. 
          JCL    83/05/06    KNAMMOD
NA5A244   NAMSTRT MODIFIED SO THAT TRACE FILES ARE NOT PURGED FOR 
          APPLICATION ABORTS.  ALSO, TRACE FILES ARE NOT PURGED 
          FOR APPLICATION RESTART FOLLOWED BY NORMAL TERMINATION
          (SEE NA5A355).
          MSC     83/07/12     NAMSTRT
 NA5A245  FIX TO SAVE THE CORRECT OIN (OLD INVOCATION 
          NUMBER) WHEN THE OIN IS SPECIFIED IN THE
          NAMI CALL.
          CYB    83/05/11    NAMI 
 NA5A246  FIX FOR CPU ERROR EXIT AT 017134 ON 
          EXECUTING A NIP TRACE.
          CYB    83/05/06    DLSCAN 
 NA5A247  NAM SHOULD BE INCLUDED FOR THE HOP "ALL" COMMANDS.
          CYB    83/05/06    KPTYPIN
 NA5A248  RS AND MXCOPYS ARE ADDED TO APPL STATEMENT IN LFILE.
          RS = YES OR RS MEANS REQUEST RESTARTABLE INDICATOR IS ON AND OFF
          OTHERWISE. MXCOPYS IS BETWEEN 1-15 DECIMAL AND DEFAULTS TO 1. 
          YCY     83/05/06     DATANDL,ATLCF,NDLSDAT,NDLPSS1,NDLCKRG, 
                               NDLP2LF,NDLLIST
 NA5A249  NIP ABORTS ON GARBAGE COLLECTION BECAUSE KDSTIN IS
          CALLED TO UPDATE THE STATUS DISPLAY WHILE K DISPLAY 
          IS IN APPLICATION MODE. 
          JCL    83/05/04    KPCLNUP
 NA5A251  ADD SUPPORT OF DIAGNOSTIC OPERATORS.
          DKE     83/05/09     CSSAIN,CSSANO
 NA5A252  CS PUTS EXTRA CHARACTER AT END OF ONLINE DIAGNOSTIC 
          MESSAGE.
          DKE     83/05/09     CSESOD 
 NA5A253  TVF ABORTED TRYING TO SEND A DOWNLINE BLOCK ON A
          PRINTER CONNECTION WITH ABL=0. TVF SHOULD ONLY ACCEPT 
          CONSOLE DEVICE CONNECTIONS, BATCH DEVICE CONNECTIONS
          WILL BE REJECTED. 
          JCL    83/06/06    TVF
 NA5A254  CS CONTINUES TO SEND *GO REQUIRED* MESSAGE AFTER THE
          SUPERVISION OF THE NPU REQUESTING A GO IS LOST. 
          DKE     83/05/09     TEXTCS,CSSAGO,CSSANS,CSSTNS,CSESSM 
 NA5A255  RESOLVE NAM NON-DEBUG VERSION PROBLEM. NIP TIMERS ARE 
          NOT GETTING INITIALIZED IN NON-DEBUG SYSTEM, FIX IS PUT 
          INTO XEXEC TO INITIALIZE THE REAL TIME CLOCK ON EVERY 
          MAIN LOOP.
          JCL    83/05/10    XEXEC
 NA5A256  RESOLVE NIP MEMORY FRAGMENTATION PROBLEM WHEN THE 
          NPU EST ENTRY ARE TURNED OFF. ALL INBOUND AND 
          OUTBOUND BUFFERS ASSOCIATED WITH AN *OFF*ED NPU 
          ARE RELEASED TO THE FREE BUFFER POOL. 
          JCL    83/05/10    NBT,NPESTOF
 NA5A259  NAMI DOES NOT DEFAULT THE PASSWORD FOR USER NAME NETOPS.
          DKE     83/06/20     NMI=IO1
 NA5A262  FIX NBSTTP STATE TABLE ERROR ON APPLICATION FAILURE WHILE 
          CONNECTION BLOCK STATE IS IN DOWNLINE BREAK CASE. 
          JCL    83/05/10   STATTBL 
 NA5A264    SEND TO HOST CAUSES CS TO ABORT.
          DKE     83/05/13     CSSASO 
 NA5A265   NVF CLEARS THE TERMINAL SCREEN AFTER EACH INVALID APPLICATION
          IS TYPED IN.  NVF SHOULD ONLY CLEAR THE SCREEN FOR THE FIRST
          APPLICATION PROMPT. 
          DKE     83/05/13     NVFTILP
 NA5A271  CHANGED LIMIT FOR MAXIMUM NODE NUMBER ON COUPLER STATEMENT
          FROM 31 TO 63.  NCF FIELD LENGTH DID NOT HAVE TO BE CHANGED SINCE 
          IT ALREADY IS 8 BITS LONG.  THIS CHANGE EXPANDS THE NUMBER OF 
          THESE BITS USED FROM 5 TO 6.
          MSC     83/05/24     NDLNFNT,NDLCKRG
 NA5A274  WHEN SWITCHING FROM ONE APPLICATION TO ANOTHER, NVF 
          RESPONDS WITH "ILLEGAL APPLICATION" IF A CARRIAGE RETURN
          IS ENTERED IN RESPONSE TO THE APPLICATION PROMPT.  NVF
          SHOULD INSTEAD SWITCH TO THE PRIMARY (DEFAULT) APPLICATION. 
          CHANGE NVF TO CHECK IF THE VOLUNTEERED APPLICATION IS 
          EITHER ZERO OR BLANK AND IF SO, SWITCH TO THE PRIMARY 
          APPLICATION INSTEAD OF THE VOLUNTEERED APPLICATION. 
          PAM     83/06/15     NVFTVAA
 NA5A275  NIP WILL ISSUE NPI/DD TO HALT THE NPU UPON DETECTING
          PROTOCOL VIOLATION FROM THAT NPU. 
          JCL    83/05/24    SMPFC,NNPIIN 
 NA5A276  RESOLVE NIP/PIP TIMING PROBLEM WHEN NPU EST ENTRY 
          IS TURNED OFF AND THEN BACK ON AGAIN. PIP MAY ABORT 
          NAM WITH PIP ERROR 24.
          JCL    83/05/13    NPESTOF
 NA5A277  NIP/NVF SUPERVISORY MESSAGE FORMAT NOT COMPATIBLE WITH
          THE CCP SUPERVISORY MESSAGE FORMAT. 
          JCL    83/05/17    SMNVF
 NA5A278  NPESTOF AND NPHECP MAY NOT RELEASE ALL OUTBOUND BUFFERS 
          IF PIP HAS NOT PROCESSED ANY QUEUED MESSAGES YET. NPESTOF 
          AND NPHECP SHOULD START RELEASING OUTBOUND CHAIN AT THE 
          FIRST POINTER INSTEAD OF THE OUT POINTER. 
          JCL    83/05/18    NPESTOF,NPHECP 
 NA5A280  NVF NEEDS TO WIDEN THE WORD COUNT FIELDS IN THE TABLES THAT 
          IT READS FROM THE LCF.  TO FIX THIS, EXPAND THE WORD COUNT
          FIELDS TO 18 BITS IN THE INCALL, OUTCALL, AND LCFWSA ARRAYS.
          THIS FIX WAS NEEDED TO CORRESPOND WITH NA5A177. 
          PAM     83/05/27     NVFIAST,NVFAIAP,NVFARAP
 NA5A289  NIP FAILED ON CPU ERROR EXIT UPON RECEIVING THE 
          NAM K DISPLAY COMMAND IG=APPNAME. FIX KAPIGP TO 
          PRESET THE ACB BASED ARRAY POINTER FOR SUBSEQUENT 
          ACB DATA STRUCTURE REFERENCES.
          JCL    83/05/23    KAPIGP 
 NA5A290  QTRM GOES INTO TIGHT LOOP IF ABL IS REACHED ON THE
          CONNECTION AND A USER BREAK IS ENTERED. CHANGE QTGET
          TO NOT USING THE INDUCTION VARIABLE TEMP2 AS A
          TEMPORARY VARIABLE. 
          JCL    83/05/20    QTGET
 NA5A291  NPU STATISTICS FORMAT CHANGED TO MAKE NPU NODE I.D. 
          FOUR CHARACTERS INSTEAD OF THREE. 
          DKE     83/06/15     CSESES 
 NA5A292  HBSTTP SHOULD DISCARD DOWNLINE DATA FROM APPLICATION IF 
          THE CONNECTION IS IN UPLINE INTERRUPT STATE. IN ADDITION, 
          IF THE CONNECTION IS IN HALF-DUPLEX MODE AND THE BLOCK
          RECEIVED IS A -MSG- BLOCK, THE LIST PROCESSING SHOULD BE
          TURNED BACK ON. 
          JCL    83/05/25    STATTBL
 NA5A293  ADDING DTEA TO INCALL STATEMENT. IT IS THE PSN ADDRESS OF 
          REMOTE DTEA INTERFACE TO THE SOURCE HOST/APPLICATION. EQUIVALENT
          TO THE "CALLING DTEA ADDRESS" IN THE X.25 INCOMING CALL REQUEST 
          PACKET. 
          YCY     83/05/31     IBLCF,NDLP2LF,NDLSDAT,NDLLIST
 NA5A294  FIX TO NAMI TO PROCESS A XXD3FIL FOR NIP-S
          ZZZZTMP FILE (CREATED ON HOP/DU COMMAND). 
          CYB    83/05/18    NMI=IO1
 NA5A295  WRITE END OF RECORD AFTER THE HEADER RECORD 
          ON THE ZZZZZDN FILE IN NETREL.
          CYB    83/04/29    NETREL 
 NA5A296  WRITE END OF RECORD AFTER THE NIP 
          HEADER ON THE ZZZZZDN.
          CYB    83/04/29    NNETREL,INIPD
 NA5A297  FIX TO DLFP TO PROCESS MULTI-FILE FILES.
          CYB    83/05/12    DLSCAN,DLRDW,DLREP,DLFP
 NA5A298  NVF ABORTS WITH *NVFTACC - CANNOT FIND P* IN DAYFILE. 
          DKE     83/06/13     NVFTACC
 NA5A300  NETWORK CONNECTION STATISTIC DATA FOR NUMBER OF CHARACTERS
          TRANSMITTED IS INCORRECT. THE CHARACTER COUNT SHOULD BE 
          PICKED UP FROM THE APPLICATION BLOCK HEADER WORD INSTEAD
          OF THE NETWORK HEADER WORD. 
          JCL    83/06/01    NFOB 
 NA5A301  CHANGE NIP ALGORITHM FOR RELEASING EXTRA MEMORY TO REDUCE 
          FL DURING GARBAGE COLLECTION TIME. A LAST BUFFER WITH A 
          MINIMUM SIZE OF 320 WORDS IS ALWAYS RESERVED FOR SUBSEQUENT 
          BUFFER REQUEST. THE REMAINING SPACE IN THE LAST BUFFER IS 
          RELEASED BACK TO THE SYSTEM.
          JCL    83/06/02    INPARU,FREETAB,ITABS,MGBGCLT,
                             XCHKPCR,XEXEC
 NA5A302  NVF SHOULD SCAN THE RIGHT MOST 48 BIT IN AAVW WORD FOR
          DEFAULT APPLICATION.
          DKE     83/06/06     NVFTPSV
 NA5A306  PROBLEM - PIP IGNORED OFC/START WHEN IT WAS IN EXTERNALLY 
                    STOPPED STATE (41D) AND SO IT NEVER STARTED 
                    OUTPUT. 
          SOLUTION - PIP WILL NOT PROCESS OFC/START WHEN IT IS IN 
                     STATE 41 OR STATE 51 AND WILL WAIT FOR THE STATE TO
                     CHANGE BEFORE PIP WILL PROCESS IT. 
          EG     06/06/83    PIP
 NA5A307  RESOLVE NAM FAILURE ON PIP ERROR 026B. PIP MAY ABORT
          NAM IF IT IS IN A STATE OF DUMPING/LOADING A LOCAL NPU
          AND WAITING FOR INBOUND BUFFER SPACE FROM NIP, AND THE
          EST ENTRY FOR THAT NPU HAS JUST BEEN TURNED OFF. PIP
          THEN MAY JUMP TO AN ERRONEOUS ACTION PROCESSOR. 
          JCL,SW    83/06/03    PIP 
 NA5A308  USER BREAK DOES NOT WORK WHEN CONNECTION IS IDLE. 
          DKE     83/06/07     CSCPNT,CSCUFS
 NA5A309  NVF DOES NOT A CR/TRM WHEN DBL IS REACHED.
          DKE     83/06/07     NVFCCPA
 NA5A310  SPECIFYING THE NPU PARAMETER TWICE ON THE REPORT COMMAND
          CAUSES CS TO ABORT.  CODE WAS ADDED TO THE COMMAND
          RECOGNIZER TO DIAGNOSE THE CASE WHERE A PARAMETER WAS 
          SPECIFIED TWICE.
          DKE     83/06/15     SSRRCS 
 NA5A311  THE FAMILY ORDINAL FIELD IN THE RAU TABLE NEEDS TO BE 
          EXPANDED TO NINE BITS.
          DKE     83/06/07     TEXTNVF
 NA5A313  NVF DOES NOT TIME OUT T-A CONNECTION. 
          DKE     83/06/07     NVFTILP
 NA5A314  UPDATE DLFP IMS.
          CYB    83/06/15    DLFP,DLREP,DLSCAN
 NA5A315  UPDATES TO AIP IMS. 
          CYB    83/06/08    NETCHEK,NETDMB,NETOFF,NETPUT,
                             NETPUTF,NP$DBG,QTCLOSE,QTENDT, 
                             QTGET,QTLINK,QTOPEN,QTPUT, 
                             NP$RCL,NP$DMB,DRHDIMS
 NA5A316  UPDATES TO NIP IMS. 
          CYB    83/01/17    NIP....XWTLC 
 NA5A317  SERVICE AND SCHEDULING SHOULD ALLOW THE APPLICATION 
          PROGRAM TO SET ITS OWN *TLMAX* IN THE NETGETL CALL. 
          AML     83/06/07     TEXTSS,SSACNI,CSLSIT,NVFLSIT 
 NA5A318  SEVERAL APPLICATION IN NETWAIT STATE MAY CAUSE SEVERE 
          BUFFER FRAGMENTATION PROBLEM IN NIP. NIP SHOULD RELEASE 
          THE NETWORK WORKLIST BUFFER IF THE NETWAIT WORKLIST 
          ENTRY IS PROCESSED AND THE NUMBER OF REMAINING WORKLIST 
          ENTRY(S) TO PROCESS IS ZERO.
          JCL    83/06/08    ACB,HPAWL,HWLP,HPWAIT,HRELWWL
NA5A320   TERMINAL CLASS MNEMONIC "X364" NOW MAPS TO TC=7.  OLDMVALUE 
          "752", WHICH PREVIOUSLY MAPPED TO TC=7, NOW IS TC=2.
          CHANGES IN NUMBER OF TERMINAL CLASSES, TERMINAL CLASSES 
          AND NUMBERS, ONE NEW MNEMONIC ADDED.
          MSC     83/06/16     NDLNFCM,NDLPSS1
 NA5A321  CS NEEDS SUPPORT NEW TERMINAL CLASSES -- 721 AND X364.
          DKE     83/06/13     CSESTS 
 NA5A322  TVF SUPPORT CODE FOR TC=3 AND 7.
          JCL    83/06/07    TVF
 NA5A324  CON/REQ CONTAINS AN EXTRA WORD.  DELETE THE ELEVENTH WORD 
          FROM CON/REQ (CONASWI) AND CR/SWH (CRSAAVW), AS IT IS 
          NOT USED. 
          PAM     83/06/23     SMNVF,SMDEF,SMAPPL,SMAPDEF,NVFTDSP 
 NA5A327  DBG/STOP PROCESSING CODE SHOULD BE PART OF THE DYNAMIC
          DEBUG CODE THAT CAN BE TURNED ON AND OFF VIA THE NAM K
          DISPLAY DB COMMAND. 
          JCL    83/06/07    HPPUT,HPDBGST,NEIB1,OVLSTAT,OVLNAME, 
                             SKENIP 
 NA5A329  PROVIDE AN EASY MEANS OF IDENTIFYING *EBCDIC* DATA IN AN
          NPU DUMP. 
  
          THIS MODSET ADDS THE CONVERSION SELECTION PARAMETER, *CV*,
          TO THE *NDA* CALL CARD.  LEGAL VALUES FOR *CV* ARE *AS* 
          (ASCII) AND *EB* (EBCDIC).  *AS* IS THE DEFAULT VALUE IF
          *CV* IS NOT SELECTED. 
  
          RWW     80/02/18     NDAS 
          RWW     81/01/27     NDAS (531) 
          RWW     83/02/14     NDAS (NOS 2.1-580) 
  
 NA5A331  PROBLEM - PIP TIMED OUT THE NPU WHICH HAD SAM.  PIP THEN
                    PROCESSED THIS CONDITION AS IF THE EST HAD BEEN 
                    TURNED OFF.  THIS CAUSED PIP TO WRITE OUT THE ORDER 
                    WORD TO INFORM CCP THAT THE REGULATION LEVEL WAS 0. 
                    IF THE PREVIOUS ORDER WORD HAD NOT BEEN READ UP,
                    PIP WAITED 2 SECONDS FOR IT TO BE READ.  WHEN IT DID
                    NOT GET READ, PIP HALTED THE NPU/SAM.  DEPENDING
                    ON WHEN SAM WAS LOADED INTO THE NPU, THE PROBLEM
                    COULD OCCUR MANY TIMES. 
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT INFORM CCP THAT THE
                     REGULATION LEVEL IS ZERO UNLESS THE EST ENTRY WAS
                     ACTUALLY TURNED OFF. 
          EG     06/09/83    PIP
 NA5A334  DSP/CIO REQUEST PARAMETER BLOCK SHOULD BE RELEASED
          BY XCHKPCR UPON COMPLETION OF THE CIO/DSP REQUEST.
          JCL    83/06/13    NPPCT,XCHKPCR
 NA5A335  NVF DOES NOT SEND A FAIL/APPL/N FOR AN A-A CONNECTION 
          THAT NVF STILL OWNS.
          DKE     83/06/29     NVFAIAP
 NA5A336  NVF ABORTS WITH MONITOR CALL ERROR WHEN CR/RAP CONTAINS 
          FACILITY CODES. 
          DKE     83/06/29     NVFARAP
 NA5A337  THE SCREEN IS NOT CLEARED TO BLANK OUT THE PASSWORD IF NO 
          APPLICATION PROMPT IS SENT.  CHANGE NVF TO CLEAR THE SCREEN 
          UPON SUCCESSFUL USER VALIDATION (INSTEAD OF CLEARING IT 
          WHEN THE APPLICATION PROMPT IS ISSUED). 
          PAM     83/06/30     TMSGNVF,MISCOM,NVFTILP,NVFTPSV 
 NA5A340  IMS CODE FOR NDA. 
          JCL    83/06/20    NDA
 NA5A341  IMS CODE FOR NS.
          AML    83/06/16    NS$IMS 
 NA5A342  PROBLEM - PIP DOES NOT CONVERT FILE TYPE VALUE FOR 8
                    BIT TRANSPARENT OUTPUT FILES WHEN IT CREATES
                    A BATCH/FILE SUP MSG FOR CCP FROM A SET/FILE
                    SUP MSG FROM RBF.  THIS CAUSES CCP TO TREAT 
                    THE 8 BIT TRANSPARENT OUTPUT FILE AS A DISPLAY
                    CODE NONTRANSPARENT OUTPUT FILE.
          SOLUTION - PIP SUBROUTINE COSF HAS BEEN CORRECTED TO CONVERT
                     FILE TYPE VALUE FOR 8 BIT TRANSPARENT OUTPUT FILES 
                     TO THE APPROPRIATE VALUE FOR CCP TO RECOGNIZE THAT 
                     THE FILE CONTAINS TRANSPARENT DATA.
          REMARKS - THIS CODE IS ONLY FOR NOS 2.1 AND LATER SYSTEMS.
                    THE PROBLEM HAS BEEN FIXED WITH PSR NA2B783 IN THE
                    NOS VERSION 2.0 AND NOS VERSION 1 SYSTEM
          EG     04/30/81    PIP
 NA5A343  NAM MAY DELIVER BAD UPLINE DATA AFTER THE BLOCK WAS 
          PREVIOUSLY MARKED AS UNDELIVERABLE TO APPLICATION.
          HPGET SHOULD RESTORE THE ACT OF THE UPLINE BLOCK WHEN 
          IT DETECTS THE BLOCK CANNOT BE DELIVERED TO THE APP.
          JCL     83/06/20     HPGET
NA5A344   NDLP NOW CHARACTER-ZERO FILLS (TO THE RIGHT) ALL X25 TERMINAL 
          NAMES THAT ARE LESS THAN 5 CHARACTERS LONG. 
          MSC     83/06/27     NDLPSS1
 NA5A354  PROBLEM - IF PIP RECEIVES A OUTPUT STOPPED SUPERVISORY MESSAGE
                    FROM CCP FOR AN OUTPUT DEVICE, PIP WILL ALWAYS PASS 
                    THE CURRENT PRU POSITION OF THE FILE TO RBF EVEN IF 
                    NAM DOES NOT HAVE A FILE ASSIGNED TO IT YET.  THIS
                    CAN CAUSE RBF TO STORE A BAD CURRENT PRU POSTION IN 
                    ITS TABLE.  WHEN THE OUTPUT IS RESTARTED, RBF PASSES
                    THE BAD VALUE BACK TO PIP.  PIP USES THAT VALUE 
                    WHICH MAY THEN CAUSES CIO TO ABORT NAM SPECIFYING A 
                    BAD PRU POSITION IN A CIO CALL. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ZERO OUT THE CURRENT PRU 
                     POSITION FIELD WHENEVER IT FINISHES PRINTING A 
                     OUTPUT FILE.  IF THE ABOVE CONDITION OCCURRS, PIP
                     WILL THEN PASS A VALUE OF ZERO FOR CURRENT PRU 
                     POSITION.  RBF IS BEING CORRECTED TO NOT STORE THE 
                     CURRENT PRU POSITION IF THE VALUE IS ZERO. 
          REMARK - RB2AXXX SHOULD ALSO BE INSTALLED WITH THIS PSR.
 NA5A356  REFORMAT THE BANNER AND COPYRIGHT CODE TO BE SHORTER, 
          CONTAIN THE CURRENT YEAR, AND INCLUDE A BLANK LINE AT 
          THE END.
          PAM     83/06/29     TMSGNVF,NVFTCRN,NVFTITE
 NA5A359  *HISTORY,ALL,* SHOULD NOT BE A VALID COMMAND. 
          AML     83/07/06     SSRRCS,CSSROC,NVFOROC
 NA5A360  CS ABORTS AFTER CALLING NETREL. 
          DKE     83/07/01     NETREL 
 NA5A361  CS FAILS WHEN GIVEN BOTH *ON* AND *OFF* PARAMETERS
          ON THE REPORT COMMAND 
          AML     83/07/06     SSRRCS 
 NA5A363  SS USES TOO MUCH OF CPU.
          DKE     83/07/06     TEXTSS,SSACNI,SSSWNR 
 NA5A377  USING NAM K DISPLAY FL COMMAND TO RESET NAM MAXIMUM 
          FIELD LENGTH DOWN TO CURRENT RUNNING FIELD LENGTH MAY 
          CAUSE NAM TO ABORT WITH BUFFER MANAGEMENT ERROR.
          NIP SHOULD NOT ALLOW HOP TO ENTER FL VALUE LESS THAN
          THE CURRENT FIELD LENGTH PLUS 2K, SO AS TO ENABLE NIP 
          TO REQUEST MORE MEMORY FROM OS WHEN BUFFER REQUEST
          COMES IN. 
          SWITCHING NAM K DISPLAY FROM SLOW MODE TO FAST MODE 
          CAN RESULT IN ERRONEOUS DISPLAY DATA. WHEN MO=FAST IS 
          PROCESSED, KDSTIN SHOULD BE CALLED TO UPDATE THE
          STATUS DISPLAY BEFORE THE FAST MODE IS ACTIVATED. 
          JCL    83/07/18    KNAMDFL,KPTYPIN
 NA5A380  CODE TO INITIALIZE THE FACILITY START BIT LOCATION, 
          TO CHANGE STRUCTURE FOR EXAMINING FACILITY CODES AND TO 
          GUARANTEE REFUSAL OF REQUESTS USING FACILITIES UNKNOWN TO 
          NHP NETWORK.
          CJB     83/08/02     NVFARAP
 NA5A381  NIP ABORTS WITH REG/LL = 0.  BEFORE PROCESSING THE REG/LL 
          CHECK IF THE LLCBWOF FLAG IN THE LLCB IS SET.  IF IT IS,
          THEN THE LOGICAL LINK IS GOING DOWN ANYWAY, SO DO NOTHING.
          ABA     83/08/01     NPREGLL
NA5A384   FIXED STIP DEFAULT FOR TC=752,X364. 
          MSC     83/08/03     NDLNFCM
 NA5A385  NVF WRITES GARBAGE ACCOUNT FILE MESSAGES FOR A-A CONNECTIONS. 
          CHANGE NVFAIAM TO:  CORRECTLY STORE THE MESSAGE IDENTIFIERS 
          IN THE ACCOUNTING MESSAGE, SEPARATE THE MESSAGE PARAMETERS
          WITH COMMAS, TERMINATE THE MESSAGES WITH A ZERO BYTE, RIGHT 
          JUSTIFY THE SNODE AND DNODE FIELDS SO THEY CAN BE CORRECTLY 
          INSERTED INTO THE MESSAGE, INCLUDE "AEAA" MESSAGE PROCESSING, 
          AND DELETE THE EXTRA COMMA IN THE "AEAA" C2 MESSAGE.
          PAM     83/08/10     NVFAIAM
 NA5A386  NVF SENT AN INTR/RSP AFTER A CR/SWH.  THIS RESULTED IN AN 
          ERR/LGL SM BEING SENT, CAUSING NVF TO ABORT WITH THE
          "SM NOT ROUTED" MESSAGE.  IN NVFCUFS, PRIOR TO ISSUING
          THE INTR/RSP SM, CHECK IF THE ACN IS IN THE PROCESS OF
          BEING SWITCHED OR TERMINATED AND IF SO, DO NOT ISSUE THE SM.
          PAM     83/08/02     NVFCUFS
NA5A387   CHECKSUM FOR NCB NOW CALCULATES CORRECTLY, USING THE
          INTERNAL VERSION/LEVEL NUMBER.
          MSC     83/08/03     NDLNFTM
 NA5A395  ADD COLLECT OF NEW APPLICATIONS FILE TO THE COLLECTOR.
          DKE     83/08/09     CLT=INI
NA5A399   THE PHYSICAL LINK XREF TABLE IS NOW SORTED BEFORE 
          IT IS PUT INTO THE NCF.  THIS FIX MAKES COUPLER 
          AND TRUNK STATEMENTS INDEPENDENT OF THEIR ORDER IN
          THE NDL SOURCE FILE.
          MSC     83/08/12     NDLNFTM
 NA5A402  ADD CODE TO SUPPRESS THE HALTING OF AN NPU WHEN RECEIVING A 
          BACK, ICMD, MSG, DURING AN A-A BREAK. 
          ABA     83/08/18     XSTTP
 NA5A403  ADD CODE TO SUPPRESS THE HALTING OF AN NPU WHEN RECEIVING A 
          ICN/TE WHEN NVF HAS NOT NETTED ON YET AND DURING HOST 
          SHUTDOWN. 
          ABA     83/08/18     NCSTTP 
 NA5A404  NAMSTRT - LOCAL FILE NAME FOR NID3FIL WRONG IN NIP
          STARTUP JOB.
  
          CHANGE NIP STARTUP JOB IN NAMSTRT TO ASSIGN CORRECT 
          LOCAL FILE NAME TO NID3FIL. 
  
          RWH            08/16/83       NAMSTRT 
  
NA5A405   NEW UPPER UBL LIMIT FOR PASSIVE DEVICES IS 7. 
          ALSO, NDL MODIFIED TO SUPPORT THE FOLLOWING DEVICE
          TYPES FOR THESE TIPTYPES: 
  
            HASP  - CON, CR, LP, CP, PL 
            MODE4 - CON, CR, LP 
            BSC   - CON, CR, LP, CP 
  
          THESE ARE DOCUMENTED IN BOTH THE NDL ERS AND NDL RM.
          MSC     83/08/24     NDLNFCM
 NA5A411  PROBLEM - IF PIP IS DRIVING ONLY A SINGLE NPU, THAT PIP 
                    WILL NOT ACKNOWLEDGE THE NIP INTERLOCK FOR 12 
                    SECONDS IF THE EST ENTRY OF THAT NPU IS TURNED
                    OFF OR PIP TIMES OUT THAT NPU AND THAT NPU HAS
                    SAM.  THIS MAY CAUSE NIP AND OTHER PIPS TO HANG 
                    FOR UP TO 12 SECONDS WAITING FOR THIS PIP TO
                    ACKNOWLEDGE THE INTERLOCK.  CCP MAY THEN TIME 
                    OUT THE HOSTS BECAUSE THE OTHER PIPS ARE NOT
                    TALKING TO CCP AND TAKE THE LOGICAL LINKS DOWN. 
  
          SOLUTION - PIP HAS BEEN CORRECTED TO CHECK THE NIP
                     INTERLOCK IF IT IS DRIVING ONLY A SINGLE NPU 
                     AND THAT NPU IS TURNED OFF OR TIMED OUT IF IT
                     HAS SAM. 
          EG     08/24/83    PIP
 NA50006  CE ERROR LOG FILE MESSAGE FOR COUPLER ERROR IS
          INCORRECT. THE CORRECT MEESAGE FORMAT SHOULD BE 
          *NW01,HHHH,FFCC* WHERE HHHH IS THE COUPLER NODE NUMBER
          AND CC IS THE ERROR CODE. 
          JCL    83/06/03    NPHECP 
 NA50008  COLLECT JOB DOES NOT RECOVER FROM A *READY DROP*. 
          DKE     83/05/03     NAMSTRT
NA5A312   NAMSTRT MODIFIED TO SUPPORT SUBSYSTEM CHECKPOINT. 
          MSC     83/07/12     NAMSTRT
 NA50009  THE *AST* CONTAINS EXTRANEOUS WORDS OF ZEROES.  TO FIX THIS,
          IN THE SSTATS CALL, CHANGE THE ARITHMETIC STATEMENT IN THE
          PARAMETER LIST TO CORRECTLY COMPUTE THE NUMBER OF WORDS TO
          REMOVE FROM THE *AST*.
          PAM     83/05/27     NVFIAST
 NA50011  NVF NEEDS TO ISSUE A CARRIAGE RETURN AND LINE FEED WHEN 
          ISSUING THE USER NUMBER PROMPT AFTER THE SYSTEM HEADER. 
          DKE     83/05/03     TMSGNVF
 NA50014  IDLE,HOST CAUSES NVF TO ABORT.  THIS IS CAUSED BY AN
          APPLICATION NETTING OFF WITH AN UNRECOGNIZABLE APPLICATION
          NUMBER. 
          DKE     83/05/24     NVFSNON
 NA50021  CS SENDS ERRONEOUS TRUNK STATUS MESSAGE WHEN THE PORT 
          NUMBER FOR THE TRUNK MATCHES A COUPLER NODE I.D. FOR
          THE SAME NPU. 
          DKE     83/05/24     CSESTR 
NA50024   MOVED DECRYPTION MULTIPLIER CONSTANTS FOR ACTIVE AND PASSIVE
          DEVICE TYPES FROM NDLNFCM TO GLOBAL TEXT IN NDLPS2T.  IF
          NON-USER-DEFINED TIPTYPE, THEN APPROPRIATE MULTIPLIER IS
          USED TO DECODE UBZ TABLE ENTRY FOR USE IN NCF SUMMARY LISTING.
          MSC     83/06/13     NDLLIST,NDLNFCM,NDLPS2T
 NA50045  RBF HUNG AFTER A SST RETURN CODE 2. NPPSM USES
          SUBSCRIPT ZERO INSTEAD OF THE APPLICATION NUMBER
          FOR SETTING THE ATPSO FLAG IN APPLICATION TABLE 
          ENTRY, THUS CAUSING NIP TO LOSE *PRU APPLICATION
          SWAPPED OUT AND PWL RING EXISTS STATUS*. ALSO A 
          TIMING PROBLEM EXISTS WHEN NPPSM RECEIVES SST REASON
          CODE 2 THE APPLICATION IS IN *AWAITING SWAP IN
          REQUEST COMPLETION AFTER NETWAIT TIMER WAS UP*. 
          WHEN THIS HAPPENS, XSACB WILL NOT DELINK PWL(S) 
          FROM THE PWL RING AND CHAIN IT BACK TO RBF-S DATA 
          RING, THUS CAUSING ALL UPLINE DATA FOR RBF TO BE
          CONTINUALLY CHAIN TO THE PWL RING.
          JCL    83/07/15    NPPSM,XSACB
NA50048   NDLP CHANGED FOR CORRECT ACTION ON NOLOAD PARAMETERS
          OF TRUNK STATEMENT. 
          MSC     83/07/27     NDLNFTM
 NA50049  INCREASE THE NS TIME OUT VALUE TO ALLOW FOR DUMPING AND 
          LOADING OF REMOTE NPU-S WITH A SLOW LONG DISTANCE TRUNK.
          DKE     83/07/20     DEF$NS 
 NA50066  THE INTENSIFIED MESSAGE *REQUEST NAM K-DISPLAY* IS NOT
          CLEARED WHEN K-DISPLAY IS ASSIGNED TO NAM.
          DKE     83/08/05     OMSG 
 NA5A415  CODE TO ALLOW NVF TO RECORD WHEN AN APPLICATION 
          THAT IS REQUESTING AN A-A OUTCALL HAS FAILED WHEN IN A REPEAT 
          OUTCALL SEQUENCE. 
          CJB     83/09/07     NVFAIAP
 NA5A417  CHECKSUM FOR NPU NOT MISCALCULATED. 
          DKE     83/09/02     NDLNFTM
 *L614*    ************************************************ 
 NA5A260  NAMSTRT - JOBTVF IN ERROR.
          CODE IN NA5A142 REFERENCES FILE ZZZZZSN/TVS0FIL WHICH IS
          NOT USED BY TVF.
          REMOVE REFERENCES TO ZZZZZSN/TVS0FIL. 
          RWH     10/14/83     NAMSTRT
NA5A347   NDL MODIFIED TO ALLOW USAGE OF HD PARAMETER ON DEVICE 
          STATEMENT FOR BSC TIPTYPES (2780/3780 CONSOLES).
          MSC     83/07/21     NDLNFCM
NA5A367   CS MODIFIED SO THAT STATUS MESSAGES CONTAINING X.25 
          TERMINAL INFO. ARE LISTED IN PROPER FORMAT. 
          MSC     83/08/19     CSESTS 
 NA5A391  NVF ABORTED UPON RECEIVING THE CTRL/TCD SM.  THIS HAPPENED
          BECAUSE NO ENTRY EXISTED IN THE PFC/SFC TABLE FOR CTRL/TCD. 
          ADD THE CTRL/TCD TO THE PFC/SFC ARRAY IN NVFDDNT.  PUT IT 
          IN THE CATEGORY OF "IGNORED SMS". 
          PAM     83/08/18     NVFDDNT
NA5A394   DOCUMENTATION WAS ADDED TO DESCRIBE ACCOUNT DAYFILE 
          MESSAGE FORMAT. 
          MSC     83/09/01     CSESES 
NA5A410   NEW MAXIMUM FOR HN PARAMETER ON DEVICE STATEMENT IS 63. 
          MSC     83/09/02     NDLCKRG
 NA5A413  NIP MAY ABORT WITH CPU ERROR EXIT IF AN APPLICATION 
          ISSUES A NETGET CALL ON AN ILLEGAL ACN. 
          JCL    83/09/01    HPGET
 NA5A418  NIP ABORTS WITH A BAD PWL.
          ABA     83/09/21     NPREGCN
 NA5A426  NIP DOES NOT RESUME AN PRU-APPLICATION'S WORKLIST 
          PROCESSING IF A SST REASON CODE 2 (APPLICATION SWAPPED
          OUT) IS RETURNED DURING THE OFC/STRT PROCESSING. THE
          ATASBS BIT IN THE APPLICATION TABLE SHOULD BE SET TO
          ALLOW WORKLIST PROCESSING TO RESUME ONCE THE APPLICATION
          IS SWAPPED BACK IN. 
          JCL    83/09/06    HPRUSM 
 NA5A427  CS/NS NETON STATUS MAY NOT BE COMMUNICATED TO NAM/CCP 
          IF CS/NS IS SWAPPED OUT DURING THE NETON ATTEMPT. THIS
          CAUSE NPU(S) NOT GETTING LOADED OR SUPERVISED, AND CS/NS
          NOT RESPONDING TO K DISPLAY TYPEINS.
          HPNONSA IS MODIFIED TO SET ATASBO IN AT ENTRY TO INDICATE 
          APPLICATION SWAPPED OUT AT NETON STATUS SO THAT XSACB 
          CAN ISSUE ANOTHER CALL TO HPNONSA WHEN IT DETECTS THE 
          APPLICATION IS SWAPPED BACK IN. 
          JCL    83/09/26    HPNONSA
 NA5A431  NAMI - MAKING NRF1 FILE GREATER THAN ONE PRU CAUSES 
          *BUFFER ARGUMENT ERROR*.
  
          ALSO OCCURS FOR NRF2 FILE.  NAMI DOES A SINGLE READ AND 
          WRITE PER NRF FILE, EXPECTING TO SEE END OF RECORD.  AS 
          THE BUFFER IS ONE PRU IN LENGTH, THE SIZE OF THE NRF FILES
          IS LIMITED. 
  
          CHANGE THE COPY SEQUENCE TO TEST FOR FULL BUFFER OR END OF
          RECORD.  IF FULL BUFFER, DO ANOTHER READ AFTER THE WRITE. 
          CODE ALSO IS INCLUDED TO ALLOW A JOB RECORD TO CONTAIN
          MORE THAN 200 LINES.
  
          RWH     09/30/83     NMI=RTE,NAMI 
  
 NA5A430  NAMI - NULL PASSWORD NOT SUBSTITUTED IN JOB RECORD. 
  
          NAMI ACCEPTS A NULL PASSWORD ON THE CFO COMMAND, AND
          CORRECTLY SETS IT INTO THE MASTER FILE.  HOWEVER, NO
          SUBSTITUTION IS PERFORMED ON THE JOB RECORD FILES (WHAT 
          WAS IN THE PASSWORD FIELD REMAINS). 
  
          CHANGE THE PASSWORD SUBSTITUTION LOGIC TO SUBSTITUTE
          THE PASSWORD REGARDLESS OF ITS CONTENTS.
  
          RWH     09/30/83     NAMI 
NA5A432   CS NOW ALLOWS A NOP TO LOAD AN NPU THAT IS BEING
          SUPERVISED WITH AN NCF MISMATCH.
          MSC     83/10/19     CSSRCA 
NA5A434   CPU IS NOW RELEASED IF THERE ARE NO OUTSTANDING 
          MESSAGES TO PROCESS.
          MSC     83/10/14     SSSWNR 
NA5A436   TABLE LENGTH FIELD HAD NOT BEEN TAKEN INTO ACCOUNT WHEN 
          CREATING THE NCB, CAUSING A GAP IN A HOST NAME.  THE
          HOST NAMES ARE NOW INTACT.
          MSC     83/10/11     NDLNFTM
 NA5A441  CHANGE NVF TO SEND THE CLEAR SCREEN FORMAT EFFECTOR AS A
          BLK BLOCK INSTEAD OF A MSG BLOCK. 
          PAM     83/10/06     NVFTPSV
 NA5A442  IMS OF NDLP MODIFIED TO REFLECT CHANGES IN NDL 2.2. 
          YCY     83/10/10     NDLP2LF,NDLNFCM,NDLNFTM
 NA5A443  QTRM SHOULD NOT IGNORE TRANSPARENT DATA ON A-A CONNECTION.
          DKE     83/10/03     QTGET
 NA5A448  PERFORMANCE MOD TO REDUCE NUMBER OF RECALLS ISSUED
          BY 2.2 NAM. RECALL WILL BE ISSUED IFF THERE IS NO PENDING 
          APPLICATION REQUEST AND NO UPLINE NETWORK TRAFFIC.
          JCL     83/10/04     HHIR,NEIB
NA50081   LINE XREF TABLE WAS SEARCHED ONE TOO MANY ELEMENTS -- FIXED.
          MSC     83/09/22     CSESTS 
NA50082   LINE XREF TABLE WAS SEARCHED ONE TOO MANY ELEMENTS -- FIXED.
          MSC     83/09/22     CSESLS 
NA50083   LOGICAL LINK XREF TABLE WAS SEARCHED ONE TOO MANY ELEMENTS -- FIXED.
          MSC     83/09/22     CSESLL 
NA50084   LINE XREF TABLE WAS SEARCHED ONE TOO MANY ELEMENTS -- FIXED.
          MSC     83/09/22     CSESEC 
NA50086   PHYSICAL LINK XREF TABLE WAS SEARCHED ONE ELEMENT TOO MANY, 
          AND ENTRIES WERE NOT BEING CHECKED FOR "COUPLER" STATUS 
          (SAME FIX FOR NA50086). 
          MSC     83/09/22     CSESCS 
NA50087   PHYSICAL LINK TABLE HAD BEEN SEARCHED ONE ELEMENT 
          TOO MANY -- FIXED.
          MSC     83/09/22     CSESTR 
 NA50092  ADD A NEW FIELD TO THE PTAC TABLE -- PTA$IUVF.  THIS FIELD
          IS A FLAG THAT IS SET IF THIS IS THE INITIAL USER VALIDATION. 
          WHEN THIS FLAG IS SET, NVF WILL ISSUE THE ABUN ACCOUNTING 
          MESSAGE UPON SUCCESSFUL USER VALIDATION.
          PAM     83/10/14     NVFTPSV,TEXTNVF,NVFTITE,NVFTCRN,NVFTETC
 FN4170B  NEW STATEMENTS, PATH AND PID WITH STATEMENT IDS 22, AND 23
          RESPECTIVELY ARE IMPLEMENTED. EACH PATH STATEMENT MUST BE FOLLOWED^ 
          BY AT LEAST ONE PID STATMENT. THE STATEMENT LABEL OF EACH PID 
          STATEMENT IDENTIFIES THAT PID STATEMENT AND MUST BE EXACTLY THREE 
          CHARACTERS LONG. A NEW PATHPID TABLE IS GENERATED WITH RECORDS
          OF PID FOLLOWED BY ALL THE LOGICAL LINKS REFERENCED BY THAT PID.
          YCY     83/06/30     DATANDL,ER2CNDL,ER1CNDL,NDLPSS1,NDLSDAT, 
                               NDLTBLT,NDLP2LF,NDLLIST
 FN4201A  CODE FOR 2.3 LEVEL. INTRODUCING FILE TRANSFER FACILITY IN TO
          AIP, IT IS CALL NETXFR. 
          LTN     83/09/23     NETWAIT,NETPUT,NETGET,NP$ERR,NP$MSG
 FN4201B  CODE FOR 2.3 LEVEL. INTRODUCING NETXFRC INTO NETPUT ROUTINE.
          LTN     83/09/23     NETPUT,NP$PUT,NETOFF,NETON 
 FN4201C  CODE FOR 2.3 LEVEL. STAR CALL THE NEW COMDECKS OF NETXFR. 
          LTN     83/09/23     AIPDEF,AIPTXT,NP$DBG 
 FN4201D  CODE FOR 2.3 IN NIP. NIP HANDLES THE NEW PROTOCAL INTERFACE 
          BETWEEN PIP-NIP-AIP. DYNAMIC PRU BUFFER ALLOCATION AND GABAGE 
          COLLECTION. 
          LTN     83/09/23     HCSTTP,NCSTTP,XSTTP,PCNB,NBT 
 FN4201E  VODE FOR 2.3 LEVEL IN NIP. CLEAN UP NIP FOR BETTER PERFORMANCE. 
          ABA     83/09/23     NCSTTP,HCSTTP,NPPCT,NPPWL
 NETXFR   NEW ROUTINE IN AIP TO HANDLE FILE TRANSFERRING
 NETXFRC  CONTINUING FILE TRANSFER ROUTINE. 
 NP$INIT  INITIALIZE ALL TABLE FOR FILE TRANSFERRING. 
 NP$BFET  BUILD ALL FET'S FOR FILE TRANSFERRING.
 NP$ITMG  INTERCEPT SM TO FILE TRANSFERRING APPLICATION.
 CALLSYS  SYSTEM INTERFACE ROUTINE OF AIP.
 CMMINT   CMM INTERFACE ROUTINE OF AIP. 
 NP$CIO   CIO INTERFACE ROUTINE OF AIP. 
 NP$ZRWD  ZERO BUFFER ROUTINE IN AIP. 
 NP$ZRBK  REPLACE ZERO WITH BLANK IN AIP. 
 CSET63   INITIALIZE CHARACTER SET 63 IF NEED.
 NP$ZLOC  LOCATE FTT ENTRY. 
 NP$XCMP  COMPLETING FILE TRANSFERRING. 
 XCHKABC  CHECKING THE TYPE OF PRU BUFFER NEEDED. 
 NPRLB    RELEASE LIMBO BUFFER IN PIP.
 NP$CDD   CONVERT INTEGER INTO DECIMAL DISPLAY. 
 NP$STTP  STATE TABLE PROCESSOR IN AIP. 
 NP$STPR  STATE TABLE DRIVER IN AIP.
 NP$SMSG  PROCESS ALL ASYN SM FOR FILE TRANSFERRING CONNECTION IN AIP.
 NP$DATA  PROCESS ALL DATA FOR FILE TRANSFERRING CONNECTION IN AIP .
 NP$BTO8  CONVERT BINARY TO ASCII.
          LTN     83/23/09      NEW AIP ROUTINES FOR 2.3
                                XCHKABC,NPRLB 
  
 RHF      FEATURE CODE IDENT THAT INTRODUCES CHANGES TO NVF 
          FOR THE FOLLOWING:  
            1) REQUEST STARTABLE APPLICATIONS.
            2) MULTIPLE COPIES OF APPLICATION.
            3) LOGICAL LINK STATUS MESSAGE FOR PID UPDATING TO OS.
            4) A-A REQUESTS USING LID/PID MANAGEMENT. 
            5) NEW HOP OPERATOR COMMAND OUTPUT FORMATS. 
            6) AUTOMATIC ENABLING/DISABLING OF PIDS.
            7) INCALL REQUESTS VALIDATION BASED ON ORIGIN DTE ADDRESS.
          CJB     83/08/10     SMDEF,SMNVF,SMAPPL,SMPFC,TEXTNVF,
                               NVFOFAD,NVFOPAC,TXVCBNV,NVFVPSR,NVFOFVD, 
                               NVFOPSS,TXTANVF,NVFIAST,NVFCDQE,NVFTDSP, 
                               NVFSNON,NVFSCAD,NVFTCB,NVFTRCN,NVFTRVD,
                               NVFTDQE,NVFTINA,NVFTICR,NVFAIAP,NVFARVD, 
                               NVFARAP,NVFAVVD,NVFDDNT,NVFAPVD,NVFATAC, 
                               NVFTACC,NVFTPVD,NVFTURT,NVFTVAA,NVFAACC, 
                               NVFVFSD,NVFADQE,MACREL 
 FN4201F  CLEAN UP THE FIRST GENERATION OF CODE FOR 2.3.
          LTN    83/09/29    HCSTTP,NCSTTP,NPPSM,NPPCT
                             NETXFR,NERXFRC,NP$XCMP 
 RHF2     SECOND SET OF MODS FOR RHF/NVF FEATURE. 
          CJB     83/09/27     TEXTNVF,TXTANVF,NVFTSPC,NVFASPC,NVFTDSP, 
                               NVFAVVD,NVFARAP,NVFSCAD,NVFATAC,NVFTINA, 
                               NVFTCB,NVFTRCN,NVFUCRS,NVFOPSS,NVFTICR,
                               NVFSNON,NVFOPAC,NVFARVD,NVFTRVD
 FN4201G  NEW PIP TO SUPPORT 2.3 LEVEL. 
          RKK     83/09/28  PIP 
 FN4201I  THIS MODSET EXPANDS THE FIELD LENGTH OF FTTTBN FROM 
          A THREE BIT FIELD  TO AN 18 BIT FIELD IN WORD 5 OF FTT. 
          ALSO INITIALIZE THE CURRENT PRU POSITION TO 1.
          LTN     83/10/25     NX$ACBX,NP$INIT,NP$SENF
  
 THIS MODSET IMPLEMENTS THE K-DISPLAY PARAMETER ON THE
 APPL STATEMENT TO ALLOW NON-SUPERVISORY APPLICATIONS 
 TO USE THE K-DISPLAY.
 FS4420A  ECT     83/03/10     NDLSDAT,NDLDATT,NDLTBLT,NDLLIST,NDLPSS1,NDLP2LF
 NA5A144  NIP KEEPS TRACK OF UP-LINE BSN AND SAVE THE NEXT NUMBER IN
          NCNT. 
          UPON SWITCHING FROM PRU TO IVT, NIP WILL CREAT AN ACK-QUEUE 
          ACORDING TO THE NUMBER OF OUTSTANDING BACK COUNT GIVEN BY 
          PIP 
          LTN     83/10/26     NEIB1,HPRUON,NBSTTP,BLDNCNB,NPBACK 
                               XSTTP
  
 FN4170C  CORRECTIVE CODE TO MODIFY THE NEW GETFIL MACREL PROCEDURE 
          AND TO UPDATE THE NVF PROCEDURES THAT ARE AFFECTED BY THE MACREL
          CHANGES.
  
          ADD CODE TO NVF TOPRINT OUT THE FOLLOWING ACCOUNTING
          MESSAGES: SANW,SBNW,SBER,SENW.
          PAM     83/09/29. 
          CJB     83/10/31     NVFTICR,NVFSCAD,NVFSNON,TXTANVF,NVFSNOF, 
                               NVFSIAM
 FN4201K  BASE ON ACTIVE AND NON-ACTIVE ENTRIES IN PIT TO RELEASE 
          LIMBO POINTER.
          LTN     83/11/01    NPRLB 
  
 NA5A059  NAMI REPEATS THE LAST LINE OF THE PARAM RECORD
          LIST IN THE DAYFILE IF THERE ARE ZERO OR A MULTIPLE 
          OF 4 PARAM RECORDS, AND IF THE LAST RECORD IN THE 
          MASTER FILE IS A JOB RECORD.
  
          THE SOLUTION IS, IN DFL$RCDS, TO OUTPUT THE MESSAGE 
          BUFFER WHEN THE END OF THE DIRECTORY IS REACHED 
          ONLY IF THERE IS SOMETHING IN THE BUFFER. 
  
          NOS 2.1, 2.2.  NO DEPENDENCIES. 
  
          EMH    83/10/23    NAMI 
  
 NA5A089  NAMI DOES NOT ABORT WHEN CALLER IS NOT SYOT.
  
          NAMI DOES NOT CHECK THE ORIGIN OF THE CALLER. 
          THIS CODE CAUSES NAMI TO ABORT IF NOT SYOT, UNLESS
          USER HAS *CSOJ* AND THE SYSTEM IS IN DEBUG. 
  
          NOS 2.1, 2.2.  NO DEPENDENCIES. 
  
          EMH      83/10/23    NMI=ENV,NAMI 
  
 NA5A103  NAMI TRIED TO START NAM WITH BAD USER NAME AND
          PREVIOUS MASTER FILE. 
  
          IF NAMI HAS A VALID MASTER FILE *MFN*, AND A DIFFERENT
          USER NAME IS ENTERED VIA THE *UN* PARAMETER, AND IT 
          CAN NOT FIND A FILE *MFN* UNDER THE NEW USER, IT ISSUES 
          A DIAGNOSTIC BUT CONTINUES TO USE THE ORIGINAL *MFN*. 
  
          THE SOLUTION IS TO RETURN *MFN* BEFORE TRYING TO GET IT 
          SO THAT NO FILE WILL BE THERE IF THE GET IS NOT 
          SUCCESSFUL. 
  
          NOS 2.1 AND 2.2.  NO DEPENDENCIES.
  
          EMH    83/10/25    NMI=IO1
  
 NA5A243  NAMI REQUIRES PUBLIC NAMSTRT FILE.
  
          SINCE NAMI RUNS WITHOUT A USER STATEMENT, IT CANNOT GET 
          THE NAMSTRT FILE FROM ANOTHER USER UNLESS THE FILE IS 
          PUBLIC.  THIS CODE PERFORMS A SETPFP TO SYSTEMX, IF THE 
          CALLER HAS SYSTEM ORIGIN, SO THAT NAMI CAN GET A FILE 
          PERMITTED TO SYSTEMX. 
  
          THANKS TO J. HUSTON, WHOSE SUGGESTED METHOD WAS IMPLEMENTED.
  
          THE NAMSTRT FILE MUST BE PERMITTED TO SYSTEMX.
  
          NOS 2.2 AND LATER.  IF THIS MODSET IS INSTALLED, IT IS
          STRONGLY RECOMMENDED THAT NA5A089 ALSO BE INSTALLED.
  
          EMH    83/10/23    NMI=ENV,NAMI,NMI=IO1 
  
 NA5A325  NAMI WRITES CFO MESSAGE TO DAYFILE FOLLOWED BY COLONS.
  
          IF A NAMI CFO COMMAND IS ENTERED OF LENGTH 2 CHARS LESS THAN
          A MULTIPLE OF 10, THE CFO COMMAND IS WRITTEN TO THE DAYFILE 
          FOLLOWED BY 2 COLONS.  THIS IS BECAUSE THE CHARACTER FILLED 
          MESSAGE IS RIGHT SHIFTED ONE CHARACTER, THEREBY BREAKING
          THE 2-CHAR ZERO BYTE TERMINATOR OVER A WORD BOUNDARY. 
  
          SOLUTION IS TO DETECT THAT SITUATION AND ZERO OUT THE NEXT
          WORD, FORCING THE END OF MESSAGE CORRECTLY. 
  
          NOS 2.1, 2.2.  NO DEPENDENCIES. 
  
          EMH    83/10/25    NAMI 
  
 NA5A349  NAMI DOES NOT EXPAND OIN PARAMETER TO THREE 
          CHARACTERS. 
  
          WHEN AN OIN OF LESS THAN 3 DIGITS IS ENTERED, THE NUMBER
          IS NOT EXPANDED WITH DISPLAY CODE ZEROES.  THIS MODSET
          CAUSES THE OIN TO BE DISPLAY CODE ZERO FILLED TO
          THREE DIGITS. 
  
          EMH    83/10/26    NAMI 
  
 NA5A379  NPU HARDWARE ERROR MAY CAUSE NAM TO REACH MAXIMUM 
          FIELD LENGTH CONDITION. 
          NS WOULD FLOOD NAM WITH NPU LOAD DATA MESSAGES IF IT
          CANNOT SUCCESSFULY LOAD SAM INTO THE NPU DUE TO 
          HARDWARE PROBLEMS. NS SHOULD ONLY ALLOW 2 CONSECUTIVE 
          SAM LOAD PREEMPTION TO REDUCE THE AMOUNT OF MESSAGES
          SENT TO NAM.
          JCL    83/10/21    NST$NS,NS$ERR,NS$XPD 
 NA5A388  MODIFY NS TO SUPPORT THE ABBREVIATED FORM OF FILE 
          COMMAND.
          JCL    83/10/23    NS$HCP 
 NA5A422  NS ABORTED ON - LOAD TSB NOT FOUND - DURING THE NPU 
          LOAD PROCESS. THE LOAD TSB ACTIVITY COUNT IS NOT
          DECREMENTED WHEN DUMP/LOAD ACTIVITY ON A NPU TERMINATES,
          WHEN THE ACCUMULATED ACTIVITY COUNT EXCEEDS THE 6-BIT 
          FIELD ASSIGNED TO IT, THE LOAD TSB WILL BE RELEASED 
          EVEN THERE MAY BE ONGOING NPU ACTIVITY. 
          PROCEDURE NS$TNA SHOULD DECREMENT THE ACTIVITY COUNTER
          IN THE LOAD TSB CONTROL WORD WHEN ACTIVITY ON A NPU 
          TERMINATES. 
          JCL    83/10/22    NS$TNA 
 NA5A450  NAM ABORTS WITH CPU ERROR EXIT ON TRYING TO MOVE
          A BAD ACKNOWLEDGE QUEUE BUFFER DURING GARBAGE COLLECTION. 
          RBF NETTING ON COULD CAUSE A NAM BUFFER GETTING CLOBBERED 
          IF THE NETON PROCESS RESULTS IN THE APPLICATION TABLE (AT)
          EXPANSION. PROCEDURE HPNON SHOULD RESET THE BASED ARRAY 
          POINTER TO AT AFTER PROCEDURE BLDACB IS CALLED. 
          JCL    83/10/23    HPNON
 NA5A455  PM MESSAGE IS TRUNCATED TO HALF THE SIZE
          BECAUSE RBF PICKS UP 11 BITS. 
  
          SOLUTION CHANGE RBF TO PICK UP 12 BITS OF CHAR COUNT. 
  
          BOTH NAM AND RBF SHOULD BE REBUILT
  
          CYC     10/27/83     SMRBF
  
NA50034   CS NOW RECOGNIZES X.25 SVC DEVICE NAMES.  THE PROBLEM HAD BEEN
          THAT THE WHOLE 7-CHARACTER NAME WAS BEING SEARCHED FOR IN THE 
          DEVICE TABLE, WHICH CONTAINS ONLY THE 5-CHAR. ROOT NAME FOR SVC 
          DEVICES.  REFERENCES TO SVC NAMES WERE CHANGED TO 5-CHAR LENGTHS. 
          MSC     83/10/31     TXCMDCS,TEXTCS,CSSRCA
 NA50046  NAMI DOES NOT DIAGNOSE ILLEGAL KEYWORDS.
  
          SOLUTION - ILLEGAL KEYWORDS AND MISSING VALUES ARE DIAGNOSED. 
          IF ERRORS ARE FOUND, DAYFILE MESSAGES ARE ISSUED AND NAMI 
          WAITS FOR A NEW CFO COMMAND.
  
          DEPENDENT ON MODSETS NA5A245 AND FS4400A. 
  
          EMH    83/10/22    NAMI 
  
 NA50079  KEEP NAMI FROM DISPLAYING A PASSWORD ON ITS CALL STATEMENT
          IN THE DAYFILE. 
  
          THIS IS ACCOMPLISHED BY ADDING THE SDM= ENTRY POINT 
          TO NAMI, AND BY DELETING ANY PASSWORD ON THE NAMI 
          CALL STATEMENT BEFORE WRITING IT TO THE DAYFILE.
  
          HOWEVER, THIS MODSET DOES NOT ADDRESS THE PROBLEM OF THE
          CFO COMMAND, WHICH ALSO CAUSES THE PASSWORD TO APPEAR 
          IN THE DAYFILE.  UNTIL THAT IS CHANGED, IT IS RECOMMENDED 
          THAT SITES USE DISCRETION IN ENTERING A PASSWORD ON THE 
          NAMI CFO COMMAND. 
  
          NOS 2.1 AND LATER.
  
          THIS MODSET IS DEPENDENT ON THE DECKOPL MODSET WHICH
          ADDS SDM= TO THE NAMI NOGO STATEMENT, IN ORDER TO 
          WORK CORRECTLY. 
  
          EMH    83/10/23    NAMI,NMI=IO1 
  
 NA50105  NS SHOULD ALWAYS ALLOW DUMPING OF A FAILED NPU
          AFTER THE INITIAL DOWNLINE LOAD IS SUCCEEDED. 
          SETTING THE NS CONTROL STATEMENT PARAMETER FDP TO 
          -NO- WOULD ONLY INHIBIT DUMPING DURING THE INITIAL
          LOAD OF A NPU WHEN THE NETWORK IS STARTING UP.
          JCL    83/10/23    NS$N04 
NA50120   NDLP DOES NOT UPDATE TABLE ADDRESSES WHEN WRITING 
          RECORDS TO THE NCF.  IF THE TABLES ARE MOVED BY THE 
          MEMORY MANAGEMENT ROUTINE BEFORE THEY ARE ACCESSED, THE 
          WRONG WORDS ARE ACCESSED. 
  
          SOLUTION - WHEN CALLING NDLWNCF WITH A BASED ARRAY, PASS
          THE BASED ARRAY POINTER OF THE TABLE TO BE WRITTEN, 
          RATHER THAN PASSING A VARIABLE CONTAINING THE ADDRESS.
          THIS WAY IF THE TABLE IS MOVED, THE MEMORY MANAGEMENT 
          ROUTINES WILL UPDATE THE POINTER, AND NDLWNCF WILL
          READ FROM THE NEW LOCATION. 
          EMH    83/10/31    NDLNFCM,NDLNFTM,NDLWNCF
  
          ALSO, 50 WORDS HAD BEEN ALLOCATED FOR THE INDEX TABLE, WHICH
          ALLOWED AN OVERFLOW TO OCCUR WHEN MANY NPUS WERE DEFINED.  NOW
          THE INDEX TABLE IS ENLARGED DYNAMICALLY SO THE NUMBER OF NPUS 
          DOES NOT CAUSE AN OVERFLOW. 
          MSC     83/11/08     NDLNFTM,NDLNFCM,NDLWNCF
 NA5A333   BAD NETWORK BLOCK DISCARDED APPEARS ALSO FOR LOAD/LUMP.
           CHECK IF THE CASE IS NS/CS NOT UP, THEN IGNORE THE BLOCK.
           ABA     11/4/83     NEIB1,PT 
 NA5A459  INDEX INTO NCNT BY CONNECTION NUMBER OF THAT ENTRY. 
          LTN     83/11/10     NBSTTP 
  
 FN4201J  MAKING NETIOD/NETIO INDEPENDENT OF MACREL.
          YCY     83/11/01     NP$DATA,NP$STPR,NP$SMSG,NP$RECV,NP$SENF, 
                               NP$STTP
  
 NA5A467  DELETE EXTRANEOUS CODE BETWEEN AND INCLUDING $BEGIN AND 
          $END.  THERE ARE NO INTERDEPENDENCIES AND THE CODE IS 
          PRERELEASABLE.
          MSG     83/11/14     HPGETSM,HPNONVF
 FN4170D  FEATURE IDENT FN4170 SUPPLEMENT CODE TO FIX FOLLOWING 
          PROBLEMS  NVF SITTING AT CONTROL POINT IN TIMED RECALL, 
          RECEIVING APPLICATION BUSY MESSAGE WHEN SECOND ATTEMPT MADE 
          TO CONNECT TO REQUEST STARTABLE APPLICATION, PERFORM PROPER 
          CLEANUP ON DISABLE APPLICATION COMMAND. 
  
          DEPENDENT ON PSR FN4044.
  
          CJB     83/11/12     NVFSNON,NVFTICR,NVFUCRS,NVFCUPS,NVFTDSP, 
                               NVFSCAD,NVFAIAP,NVFAVVD,NVFIAST,TXSMNVF
 NA5A462  CORRECTIVE CODE TO FIX NVF FAILURE PROBLEM. CAUSED BY 
          TERMINAL STATUS LINE NOT BEING FORMATTED CORRECTLY. CODE ALSO 
          FIXES PROBLEM OF ERRONEOUS STATUS INFO IN RESPONSE TO ST,TES
          COMMAND (PSR NA5A460).
          CJB     83/11/12     TXTANVF,NVFAACC,NVFOFVD,NVFOPSS,NVFAIAP
 NA5A435  CHANGE THE DBZ FIELD FROM 12 BITS TO 16 BITS IN THE CR/IAP
          AND CR/RAP SMS, AND IN THE INCALL AND OUTCALL BLOCKS. 
          PAM     83/10/28     TEXTNVF,SMNVF,NVFAIAP,NVFARAP
                               OBLCF,IBLCF
 FN4201L  SET THE MAX NUMBER FOR EACH TYPE PRU'S BY VALUES FROM 
          NIP CONTROL CARD.    ITABS. (ANSWER FOR RB5A082)
          BEFORE SENDING CR/SLL TO NVF, CHECK IF NVF IS ALREADY 
          NETTED ON. DURING NETTING ON OF NVF, SEND CR/SLL TO ALL 
          EXITING LLCB.        BLDLLCB,HPNON,RELLLCB. 
          CALL SETIL WITH PARAMETER. SETIL. 
          CAN NOT HAVE INTRA-HOST PRU A-A CONNECTION.  HPRUON.
                               BLDLLCB,HPNON,RELLCB,ITABS,SETIL.
                               HPRUON.
          RESET TEXT ADDRESS WITHIN THE LOOP IN NP$GET. (FIX ADDRESS
          OUT OF RANGE DURING QTF/QTFS JITTING) NP$GET. 
          ZERO OUT FTT ENTRY FOR EACH FILE TO BE TRANSFERED BEFORE
          THE REAL PROCESS BEGINS.       NP$INIT. 
          LTN       12/01/83
  
 NA5A474  PRESET POINTER BEFORE LOOPING TO FIND THE END OF LIST.
          LTN    83/11/16    XCHKABC
  
 NA5A491  CHANGE MIN AND MAX EXTERNAL TRIGGER IN HBSTTP.
          LTN    12/01/83    STBLDEF
  
 NA5A492  INSERT STATE/TRIGGER INTO NCSTTP. 
          LTN    12/01/83    STATTBL
  
 NA5A479  NAMI FAILS WITH *FL TOO SHORT FOR PROGRAM*. 
  
          FIXED-VALUE RFL= TOO SHORT BECAUSE OF SEVERAL RECENT
          MODSETS.
  
          CHANGE RFL= TO BE A FLOATING VALUE.  THIS WILL ACCOMODATE 
          ALL FUTURE MODSETS. 
  
          RWH            11/28/83       NMI=IO1 
  
NA5A440   NDLP NOW ALLOWS A MAXIMUM OF 5 CHARACTERS FOR THE APPLICATION 
          NAME IF MXCOPYS IS SPECIFIED AND > 1.  IF MXCOPYS IS NOT SPECIFIED, 
          IT DEFAULTS TO 1, AND A FULL 7 CHARS. IS ALLOWED FOR THE NAME.
          MSC     83/11/14     ATLCF,ER2CNDL,NDLP2LF
 FN4201M  NEW PIP FOR V2.3. 
          RMK     83/12/06     COMPCHNM,PIP 
 NA5A508  CODE TO ALLOW THE X25 PID TO BE NAM ACCESSIBLE IN 
          AN A-A CONNECTION REQUEST.
          TEMPORARY CODE AND ROUTINE TO ALLOW LID/PID A-A REQUESTS
          FROM APPLICATIONS WITHOUT THE NOS 2.3 SYSTEM MACRO INTER- 
          FACE FOR LID/PID VERIFICATION.
          CJB     83/12/13     GETPIDA
 NA5A429  NIP ABORTED WITH A MONITOR CALL ERROR BECAUSE NVF SENT A
          CR/IAP/A WITH AN INVALID REASON CODE.  THIS HAPPENED WHEN 
          THE APPL NETTED OFF AFTER THE CR/IAP/R SM WAS SENT TO NVF.
          CHANGE NVF TO SEND THE CORRECT REASON CODE (APPLICATION 
          FAILED) IN THIS CASE. 
          PAM     83/09/28     NVFAIAP
 NA5A480  CLEAR NWL POINTERS IN ACB WHEN SCP REQUEST
          IS COMPLETED AND AFTER NWL IS RELEASED. 
          MSG     83/12/13     HPNONSA,XABTAPP
 FN4201N   DO STATISTIC FOR BLOCK TYPE 6 AND 7. 
           LTN      12/07/83       NP$STAT,NP$SN. 
           FIX LOOPING IN CHAR MODE FILE TRANSFER. YCY
           CORRECTING FTTINDEX FOR SECOND FILE IN PARARELL MODE.
           FIX FOR BROKEN TEXT FILE OF MULTIPLE RECORD FILE. YCY
           FIX FOR EXTRA EOF MARKERS IN CHAR MODE. YCY
  
           CHECKING THE RANGE OF EXTERNAL TRIGGER FROM 6 TO 13 IN 
           HBSTTP.
           UNTIL IN SYMPL WILL INCLUDE THE LAST VALUE. CHANGE MSETPTR 
           NOT TO INCLUDE THIS VALUE. 
           DECRECMENT THE NUMBER OF BUFFER IN INTERLOCK TABLE WHEN
           A LIMBO BUFFER GOT RELEASE.
  
           LTN      12/07/83       HBSTTP,MSETPTR,NPRLB.
  
 FN4201O   RELEASE THE LAST LIMBO OR SYSTEM PRU BUFFER THEN ZERO
           OUT THE COUNTERS, THIS FIX THE PROBLEM WITH STARTING 
           THE SECOND PRU FILE TRANSFERRING.
           CHANGE DEFAULT VALUES FOR NUMBER OF BUFFERS PER EACH TYPE
           OF PRU'S TO 4,8,4; TO HAVE PIP REQUEST MORE BUFFERS IF 
           NEEDED.
           LTN      83/12/15       INPARUT,NPRLB. 
           CHANGE INPUT PARAMP TO NGIGO FROM PARAMP2 TO PARAMP4 
           TO FIX INTERNAL NIP ERROR IN NCSTTP2.
           LTN      83/12/20       NBSTTP,NEIB1,NPPWL,NGIGO,NCSTTP, 
                                   HPPUT
 NA5A407  PROBLEM: APPLICATIONS DEFINED IN THE LCF TO BE PRIVILEDGED
          WERE NOT ALLOWED TO NETON.
  
          SOLUTION: MODIFY NIP TO LOOK AT THE CORRECT BIT POSITION WHERE
          PRIV IS SPECIFIED.
          DKE     84/01/10     SCPCOM 
 NA5A483  CODE TO CHANGE THE VCB LOGIC AND COMMAND LOGIC FOR
          ST,TES TYPE COMMANDS WHERE THE VCB FILE MUST BE SEARCHED. 
          CJB     84/01/09     NVFARVD,NVFOPAC
 NA5A534  RBF DOES NOT TIME OUT TERMINALS SELECTIVELY.
  
          THIS MODSET IS REQUIRED TO SUPPORT RB50034, WHICH 
          ENHANCES RBF TO, IN ADDITION TO THE OTHER TESTS MADE
          IN DETERMINING TO TIME OUT A TERMINAL, CHECK THE
          CONSOLE CONNECTION VALIDATION ACCESS WORD FOR THE BIT 
          WHICH SPECIFIES NO TERMINAL TIMEOUT.  THIS MODSET 
          DEFINES THE NO-TERMINAL-TIMEOUT BIT IN THE CON/REQ. 
  
          RWH            12/12/83       SMAPPL
  
 NA5A540  CODE TO ENHANCE AND CORRECT APPLICATION DEPARTURE 
          PROCESSING. ALSO CODE TO CORRECT MISCELLANEOUS OTHER MINOR
          PROBLEMS. 
          CJB     84/01/09     SMNVF,NVFAACC,NVFATAC,NVFUCRS,NVFARAP, 
                               NVFASPC,NVFSCAD,TEXTNVF,NVFAIAP,NVFACTC
 NA5A503  CHANGE NVF TO CHECK IF THE USER-VOLUNTEERED APPLICATION 
          IS EITHER ZERO OR BLANK (INSTEAD OF JUST CHECKING FOR ZERO).
          THIS IS ACTUALLY A DUPLICATE OF NA5A274, BUT THE FIX FOR
          THIS PSR WAS ACCIDENTLY DELETED BY SOME NEW FEATURE CODE. 
          PAM     84/01/16     NVFTVAA
 NA5A519  PIP ERROR 64 CAUSED BY PRU BUFFERS GOT MOVED WITHOUT CHECKING 
          CURRENT NUMBER OF BUFFER IN CHAIN.
          I.E. MOVE BUFFERS ONLY WHEN COUNT IS NON-ZERO.
          LTN    84/01/23    MSETPTR,MAJPTR 
  
 NA5A535  NAM HUNG BECAUSE PIP WAS NOT POLLING DUE TO TOO MANY INTER- 
          LOCK REQUESTS TO PIP. 
          SOLUTION IS NOT TO SET INTERLOCK REQUEST BIT IN PIT IF THE
          ACKNOWLEDGE FLAG IS STILL SET FROM THE PREVIOUS REQUEST.
          LTN    84/01/17    MSETIL 
  
 NA5A539  PIP ERROR 75 CAUSED BY THE DIFFENCES BETWEEN THE OLD PIP (2.0)
          AND NEW PIP(2.3). NEW PIP FOR EACH TIME IT ACTIVATES, PIP 
          DOSE NOT LOOK AND RESET ALL PIP POINTERS BUFFER. I.E. 
          WHEN THERE ARE CHANGES LLCB,NCNT,TNT NIP MUSTS REQUEST
          FOR INTERLOCK.
          LTN    84/01/18    BLDLLCB,BLDNCNB,RELLLCB,RELNCNB
  
 NA5A543  CPU ERROR EXIT IN NPPWL DUE TO A BLOCK PROTOCAL ERROR PWL 
          OP=6, FROM PIP GOES ONTO A COUPLER ( PWL WITH HN=TN, CN=0). 
          IN THIS CASE, NIP WILL BY PASS THE ALLOCATION OF LLCB, NCNT 
          AND THE TERMINATION OF CONNECTION, JUST DAYFILE THE MESSAGE.
          LTN    84/01/12    NPPWL
  
 FN4201P  THIS MOD CHANGE THE PRU BUFFER SIZE 
             - TO 103B FOR TYPE 1 PRU.
             - TO 205B FOR TYPE 2 PRU.
             - TO 307B FOR TYPE 3 PRU.
          DUES TO THE PROBLEM IN TRANSFERRING FILE IN PRU-MODE WITH 
          DD = 0. 
          LTN       84/01/17       HPRUON,XCHKACB 
  
 NA5A490  SOME OF THE DEBUG MESSAGES IN NVF WERE INCORRECTLY FORMATTED, 
          CAUSING NVF TO HANG AT TIMES.  THE SOLUTION IS TO DELETE
          ALL OF THE NVF DEBUG MESSAGES SINCE THEY HAVE TO BE 
          DELETED SOMETIME ANYWAY.
          PAM     84/01/30     NVFAVVD,NVFTDSP,NVFTPSV,NVFTVAA, 
                               NVFTVVD,NVFSNON
 NA5A577  NS WOULD REMAIN UP AFTER K.ID,HO WAS ENTERED AT THE CONSOLE.
          THIS WAS BECAUSE NVF THOUGHT THAT NS HAD SOME OUTSTANDING 
          A-A CONNECTIONS.  NVF HAD BEEN ACCIDENTLY DECREMENTING THE
          A-A CONNECTION FIELD IN AST ENTRY 0 (HAPPENED TO BE NS).
          THIS FIX WILL PREVENT NVF FROM DOING THIS WHEN A SECONDARY
          APPLICATION DOES NOT EXIST. 
          PAM     84/02/07     NVFARVD
 NA5A575  NIP ABORTS WITH CPU ERROR EXIT.  NIP USES 
          A BAD POINTER BECAUSE PIP CHANGED THE POINTER 
          AFTER NIP CHECKED ITS VALIDITY.  CORRECT NIP
          TO RECHECK THE POINTER AFTER INTERLOCKING 
          PIP.
          MSG     84/01/31     XCHKPCR
 NA5A546  PIP ERROR 64. 
          RETURN IMMEDIATELY FROM CHAIN ROUTINE IF FIND A NON-LIMBO 
          TYPE BUFFER IN LIST.
          CHECK FOR NUMBER OF PRU BUFFER IN CHAIN BY PIPNP[INDEX].
          LTN       84/02/08       MSETPTR. 
  
 NA5A558  MRELS BUFFER ERROR (NA5A558)
          18 BITS OF PFCSFC HAS GABAGE (NA5A581,NA5A559)
          CPU ERROR EXITS (NA5A567) 
          ALSO ACN GET CHANGED IN ACNB ( NA5A568) 
          DUE TO ERROR IN NPPCT WHEN IT TRIES TO BUILD THE
          FAKE ACKNOWLEGE QUEUE AT THE END OF PRU CONN. TERMINATION.
          LTN       02/06/84       NPPCT
  
 NA5A565  MONITOR CALLED ERROR DUE TO NIP DID NOT REJECT AN INTRA 
          A-A PRU CONNECTION. 
          IF APPLICATION IS TRYING TO ESTABLISH A PRU A-A INTRA-
          HOST CONNECTION, NIP WILL REJECT WITH PRU/ON/A REASON 
          CODE IS 4.
          LTN     02/06/84         HPRUON 
  
 FN4170F  FEATURE CODE MODSET FOR LID/PID 2.3 MANAGEMENT
          CODE. 
          CJB     84/01/20     TXTANVF,NVFTICR,NVFCUPS,NVFIBWD,NVFADQE, 
                               NVFLSIT,NVF,NVFACTC,TEXTNVF,NVFAIAP, 
                               MACREL,TEXTSS,SSSPAT 
 FN4201T  THIS IDENT FIXES INCORRECT FETCH OF TLC IN SCANNING 
          ABH IN NETWORK BUFFER WHEN QTFS IS RUNNING IN AN X25
          ENVIRONMENT. IT ALSO ALLOCATES 6 MORE WORDS IN THE
          NETWORK BUFFER OF THE RECEIVER TO ACCOMMODATE ABH'S 
          FROM CCP BECAUSE THE MAXIMUM BLOCKSIZE WAS CHANGED
          FROM 512 TO 1024. 
          YCY     84/02/06     NX$ADEF,NP$N2D 
 FN4201W  NEW PIP THAT FIXES ALL OUTSTANDING PROBLEMS OCCURED IN
          QTF/PTF JITS AND SVL TEST/MUG SESSIONS. 
          RMK       84/02/09       COMPCHNM,PIP 
  
 NA5A595  CS ABORTED AFTER RECEIVING AN ERR/LGL.  THIS SM WAS RECEIVED
          BECAUSE AN EMPTY SM WAS SENT BY CS.  THE PROBLEM WAS AFTER A
          NOP REQUESTED FOR AUTO CONTROL OF ALL NPUS THE HOP STATUS-ED
          THE LINE AND CS THEN SENT THE EMPTY SM. 
  
          CS WAS SETTING A BIT IN THE WRONG BIT MAP AFTER THE NOP 
          REQUESTED AUTO CONTROL.  THE SOLUTION WAS TO RE-SET THE BASED 
          ARRAY EVERY TIME THE BIT WAS TO BE SET. 
          DKE     84/02/18     CSSACO 
 NA5A561  NVF GOT A CR/CB WITH AN=1 (APPL 1 IS NVF).  NVF FAILED
          BECAUSE WHEN IT DID NOT FIND AN AST ENTRY FOR APPL 1, 
          IT MODIFIED WHATEVER WAS AFTER THE AST.  TO FIX THIS
          PROBLEM, NVF WILL SPECIAL CASE APPL 1.  NVF WILL MODIFY 
          THE AST ONLY IF AN AST ENTRY IS FOUND.  ALSO, IF NVF
          CANNOT FIND AN AST ENTRY FOR ANY OTHER APPLICATION, IT
          WILL ABORT (IN DEBUG MODE ONLY).
          PAM     84/02/16     NVFATAC
 NA5A593  NVF WAS SETTING THE SNODE AND DNODE PARAMETERS IN THE 
          CR/RAP/N TO THE VALUES IN THE INCALL BLOCK INSTEAD OF 
          THE VALUES IN THE CR/RAP/R.  SOMETIMES THE SNODE AND
          DNODE VALUES COULD BE ZERO IN THE INCALL BLOCK AND
          NONZERO IN THE SM.  IN THIS CASE, NVF WOULD SET THE 
          SNODE, DNODE PARAMETERS TO ZERO IN CR/RAP/N AND TREAT 
          THE INTERHOST A-A CONNECTION AS AN INTRAHOST CONNECTION.
          TO FIX THIS, WHEN NVF IS COPYING WORDS FROM THE INCALL
          BLOCK TO THE PAAC ENTRY, DO NOT COPY OVER THE SNODE AND 
          DNODE VALUES, AS THEY HAVE BEEN PREVIOUSLY SET FROM THE 
          CR/RAP/R SM.
          PAM     84/02/20     NVFARAP
 FN4201Q  THIS IDENT FIXES GARBLED DATA IN TRANSMITTING BINARY FILE.
          IT ALSO SETS THE TRANSMISSION BLOCK NUMBER FOR BOTH 
          SENDER AND RECEIVER TO START FROM 0.
          YCY     84/01/10     NP$RECV,NP$SENF,NX$ACBX
 FN4201R  THIS IDENT EXTENDS THE ALLOWABLE BLOCKSIZE FOR CHARACTER
          MOD FILE TRANSFER FROM 512 TO 1024. 
          YCY     84/01/25     NP$ADEF
 FN4201S  THIS IDENT FIXES TIMING PROBLEM WHICH OCCURS WHEN 
          TRANSFERRING FILES IN PRU MODE. IT CHANGES STATE TABLE 0
          FOR FILE TRANSFER SO THAT IN STATE 0 WHERE AN FCACK IS
          EXPECTED IT MAY ALSO EXPECTS AN SR TO ARRIVE BEFORE THE FCACK.
          IF THIS  SITUATION HAPPENS, IT SENDS PRU/ON AND GOES TO STATE 
          2 WHERE FCACK AND FT/ON ARE IGNORED.
          YCY     84/01/18     NP$STTP
 NA5A592   PROBLEM OCCURRED BECAUSE *HPNONSA* SET ID OF NWL TO
           MOVEABLE (FLIDVALUE), THEREFORE IN A VERY BUSY SYSTEM, 
           NETON TIME, NETTING-ON APPLICATION CAN BE ROLLOUT, LEAVE 
           THIS BUFFER FLOATING IN MEMORY.
           CHANGE THIS BUFFER ID TO NON-MOVEABLE (NAFLIDVALUE). 
           LTN      84/02/21       HPNONSA
  
 FN4201V  NEW PIP THAT FIXES ALL OUTSTANDING PROBLEMS OCCURED IN
          QTF/PTF JITS AND SVL TEST/MUG SESSIONS. 
          RMK       84/02/21       COMPCHNM,PIP 
  
 FN3270A  FEATURE CODE FOR NDLP SUPPORT OF 3270 TIP.
          DKE     84/02/21     NDLLIST,NDLNFCM,NDLPSS1
 FN4201X  NEW PIP THAT FIXES ALL OUTSTANDING PROBLEMS OCCURED IN
          QTF/PTF JITS AND SVL TEST/MUG SESSIONS. 
          RMK       84/02/23       COMPCHNM,PIP 
  
 NA50156  NPU FAILS TO RELOAD AND/OR LOGICAL LINKS DO NOT COME UP AFTER A RELOAD
  
          PROBLEM - NIP IS DECREMENTING THE COUNT IN THE NBT OF LLCB S IN PRU 
                    CONNECTION TERMINATION WAIT STATE WHENEVER IT DELETES A 
                    LOGICAL LINK THAT WAS PLACED IN PRU CONNECTION TERMINATION
                    WAIT STATE. AS THIS COUNT IS USED TO DETERMINE WHETHER ALL
                    THE LOGICAL LINKS THROUGH A GIVEN COUPLER HAVE BEEN DELETED 
                    SO THAT THE REG/CP/R RESPONSE SERVICE MESSAGE CAN BE SENT TO
                    PIP, DECREMENTING IT WHEN THE LOGICAL LINK WAS DELETED DUE
                    TO A REG/LL LINK DOWN SERVICE MESSAGE IS IN ERROR. THE COUNT
                    IS CORRUPTED BY THIS AND SO CAN BE NON ZERO WHEN ALL LOGICAL
                    LINKS THROUGH A COUPLER HAVE BEEN DELETED. THIS RESULTS IN
                    THE REG/CP/R SERVICE MESSAGE NEVER BEING SENT, AND SO PIP 
                    WILL NEVER ATTEMPT TO BRING THAT NPU BACK UP. 
  
                    THE CHECK FOR THE NUMBER OF LLCB S IN PRU CONNECTION
                    TERMINATION WAIT STATE ALWAYS REFERENCED NBT ENTRY ZERO AND 
                    SO COULD RESULT IN REG/CP/R SERVICE MESSAGES SENT BEFORE ALL
                    OF THE LOGICAL LINKS THROUGH A COUPLER HAD BEEN DELETED, AND
                    SPURIOUS REG/CP/R SERVICE MESSAGES IF A LOGICAL LINK FAILED 
                    WITH ACTIVE PRU CONNECTIONS.
  
          SOLUTION- ONLY DECREMENT THE COUNT OF LLCB S IN PRU CONNECTION
                    TERMINATION WAIT STATE IF THE LLCB DELETED AT THE COMPLETION
                    OF PRU CONNECTION TERMINATION WAIT STATE IS INCLUDED IN THE 
                    COUNT. IE THE LLCB WAS DELETED IN RESPONSE TO A REG/CP FROM 
                    PIP.
  
          THIS MODSET ALSO INCREASES THE SIZE OF THE FIELD THAT CONTAINS THE
          COUNT OF LOGICAL LINKS IN PRU CONNECTION TERMINATION WAIT STATE FROM
          SIX BITS TO NINE BITS AS THE MAXIMUM NUMBER OF LOGICAL LINKS POSSIBLE 
          THROUGH ONE COUPLER IS 254. 
  
          RMF                84/02/21              NBT
                                                   NPPCT
  
 NA5A598  CHANGE NVF TO SET THE APPLICATION LIST NUMBER FIELD IN THE
          CR/IAP/N AND CR/RAP/N SMS TO 1. 
          PAM     84/02/23     NVFAIAP,NVFARAP
 NA5A603  NVF RECEIVED AN ERR/LGL ON A CR/IAP/A WITH AN ACN OF ZERO.
          NVF SENT OUT THE CR/IAP/A BECAUSE A LOCAL SHUTDOWN WAS IN 
          PROGRESS.  AT THIS POINT, A PAAC ENTRY HAD NOT BEEN CREATED.
          NVF, HOWEVER, TRIED TO STORE THE ACN IN THE CR/IAP/A FROM A 
          NONEXISTENT PAAC ENTRY, AND THE ACN ENDED UP AS ZERO. 
          TO FIX THIS, NVF WILL SAVE THE ACN FROM THE CR/IAP/R IN A 
          TEMPORARY CELL.  WHEN BUILDING THE CR/IAP/A, IF THE PAAC
          ENTRY IS DEFINED, NVF WILL GET THE ACN FROM THE PAAC.  IF 
          THE PAAC ENTRY IS NOT DEFINED, NVF WILL GET THE ACN FROM
          THE TEMPORARY CELL. 
          PAM     84/02/21     NVFAIAP
 NA5A604  NVF WAS NOT KEEPING TRACK OF THE NUMBER OF A-A CONNECTIONS
          TO AN APPLICATION.  WHEN NVF RECEIVED A REPEAT CR/IAP/R SM, 
          IF THE APPL FAILED AND NVF HAD TO ISSUE A CR/IAP/A SM,
          NVF WOULD DECREMENT THE A-A CONNECTION COUNT BUT WOULD NOT
          CHECK IF THE COUNT WAS ZERO.  THIS CAUSED THE FAILED APPL 
          TO STAY AROUND.  TO FIX THIS, WHEN NVF ISSUES A CR/IAP/A
          SM, NVF WILL CALL NVFSCAD TO COMPLETE APPLICATION 
          DEPARTURE.  THEN, IF THE CONNECTION COUNT IS ZERO AND 
          THE APPL HAS FAILED OR NETTED OFF, NVF CAN GET SEND THE 
          NET/OFF/N OR FAI/APP/N. 
          PAM     84/02/23     NVFAIAP
 NA5A613  WHEN COPYING THE APPL INFORMATION FROM THE LCF TO THE AST,
          NVF WILL CHECK IF THE MXCOPY FIELD IN THE LCF IS ZERO, AND
          IF SO, IT WILL SET THE MXCOPY FIELD IN THE AST TO 1.
          PAM     84/02/24     NVFIAST
 NA5A612   PIP ERROR 33 (NA5A612) 
           BUFFER ARGUMENT ERRORS (NA5A616) 
           SET UP THE CIRCULAR BUFFER CHAINS COMPLETELY, THEN 
           CHECK FOR LIMBO FLAG.
           MAKING SURE TO CALL MSETPTR 2*N TH TIME WITH PARAMP1 
           NON-ZERO.
           CHANGE BUFFER ID OF PRU BUFFERS IN CHAIN TO BE MOVEABLE
           IF IT IS ALLOWABLE TO MOVE PRU BUFFERS.
           SET LIMIT POINTER IN PRU BUFFER TO LESS 1 THAN FIRST + BS. 
           LTN      84/02/27       MSETPTR,XEXEC
  
 NA5A621  FIXED Q-MSG PROBLEM ENCOUNTERED DURING QTF/PTF JITTING
          IN ARDEN HILLS. 
  
 NA5A623  THESE CORRECTIONS WERE SUGGESTED BY SHINZO WATABANE 
          DURING THE INITIAL JITTING. 
  
 NA5A622  PIP ERROR 26 AND ALSO BUFFER MAGMENT ERROR (NA5A606)
  
 NA5A611  PIP ERROR 24 AND ALSO A HALT A WHILE RUNNING NIP. 
  
 NA5A588  PP HUNG DURRING JIT TIME IN ARH.
  
 NA5A463  COLON MISSING AT TERMINAL IN NVF BANNER.
  
          RMK    84/02/28    PIP
  
 NA5A632  IN THE CR/IAP/N AND CR/RAP/N, THE WS FIELD WAS 4 BITS LONG. 
          IT SHOULD HAVE BEEN 8 BITS LONG.  CHANGE THE FORMAT OF THE
          WS FIELD IN THE CR/IAP/N FROM 4 BITS TO 8 BITS.  IN NVFARAP,
          COPY WORD 3 OF THE CR/RAP/N SM FROM THE PAAC INSTEAD OF FROM
          THE INCALL BLOCK.  THE WS FIELD IS 8 BITS LONG IN THE PAAC
          AND ONLY 4 BITS LONG IN THE INCALL BLOCK. 
          PAM     84/03/06     SMNVF,NVFARAP
 NA5A625  PIP MAY HANG AT DROPPING MULTIPLE PRU CONNECTIONS.
  
          PAUSE IS TO BE ADDED TO DRIVER BUFFER RELEASE ROUTINE.
  
          FOLLOWING MINOR CORRECTIONS ARE ADDED IN THIS MOD SET.
          1. CE ERROR MESSAGE PFC/SFC VALUES ARE CORRECTED. 
          2. SHIFT VALUE FOR CONNECTION TABLE DISPLACEMENT IS CORRECTED.
          3. CALL FOR ABSOLUTE MEMORY ADDRESS IN INITIALIZATION PHASE 
             IS CORRECTED.
          4. MACRO DEFINITION FOR JUMP INSTRUCTION IS CORRECTED.
  
          RMK    03/06/84    PIP
 NA5A611  PIP HALT A
  
          WHEN NPU EST ENTRY IS SET ON, PIP MAY GET OLD NPU STATUS
          THAT IS NO LONGER VALID.  PIP SHOULD DISCARD OUTSTANDING
          NPU STATUS WORD.
  
          CORRECT DRIVER STRUCTURE PROBLEM WHICH RESULTS IN JUMPS 
          TO OVERLAY CODE WHEN OVERLAY HAS NOT BEEN LOADED
  
          RMK            84/03/01       PIP 
 NA5A645  REMOVE CMMINT CMM INTERFACE ROUTINE FROM NETIO
          MSG     84/03/09     CMMINT 
 NA5A646  NDLP SHOULD ALLOW DO PARAMETER FOR 3270 TIPTYPE.
          DKE     84/03/09     NDLNFCM
 NA5A630  NIP WAS TRYING TO LINK A BLOCK TO PIPOUT BOUND OF 
          A PCNB. NFOB ONLY CHECKING FOR NCNB, I.E. NFOB REGARDS
          AS LINKING TO LLCB. THIS LEADS TO INDEXING INTO OUTSIDE 
          OF NBT. 
          ALSO DUP OF NA5A637.
          PWL'S REASON CODE WAS 20B, INVALID VALUE, NIP DISCARD THE 
          WORKLIST BUT DID NOT RESET THE STATE IN NCSTTP. 
          PIP SENT PWL WITH BT=0, NIP SHOULD DISCARD THIS BLOCK AND 
          CONTINUE PROCESS TIS PRU CONN. ( PRU/ON/A ERROROUSLY SENT 
          TO APPLICATION DURING QTF/PTF TESTING)
          LTN       84/03/07       NCSTTP,NPPWL,NEIB1 
  
 NA5A600  WHEN NVF RECEIVES AN FC/BRK SM ON AN A-A CONNECTION, IT 
          WILL NOW SEND BACK AN FC/RST INSTEAD OF ABORTING. 
          PAM     84/03/13     NVFDDNT,NVFCUFS,NVFCDQE,TXTANVF
 NA5A651  CORRECT FIXED FREE SPACE CALCULATION IN 
          TABLE MANAGER.
          MSG     84/03/13     SSTTMR 
 NA5A650  CHECK FOR BLOCK TYPE ONLY WHEN IT IS NOT A PWL. 
          LTN       84/03/12       NEIB1,STBLDEF
  
 NA5A637  PRU TYPE DBC GIVEN TO Q-MSG CAUSES TROUBLE
  
          PRU TYPE DBC ADDED BY PIP FOR DOWNLINE Q-MSG CAUSES TROUBLE 
          WHEN PIP RECEIVES IT UPLINE IF THE CONNECTION IS IVT TYPE.
  
          PIP WILL NOT SET PRU FLAG IN DBC FOR Q-MSG AND WILL NOT CHECK 
          FOR IT WHEN Q-MSG IS RECEIVED.
  
          SW     84/03/12    PIP
 NA5A638  NPU BOOTSTRAP LOAD TIME OUT CLOBBERS NIP MEMORY 
  
          BOOTSTRAP LOAD TIMED OUT PROCESSOR DOES NOT SET CENTRAL 
          WORD COUNT. 
          GET SPACE IN DRIVER OVERLAY 2IQ.
  
          RMK    84/03/12    PIP
 NA5A644  PIP DISALLOWS INITIALIZATION COMPLETE STATUS FROM ACTIVE NPU
  
          PIP DOES NOT ALLOW INITIALIZATION COMPLETE NPU STATUS FROM
          NPU IN OPERATIVE STATE. 
          ERROR PROCESSOR CHANGED FROM BLOCK PROTOCOL ERROR TO CHANNEL
          ERROR WHEN BLOCK PROTOCOL HEADER RECEIVED IN ERROR. 
  
          RMK    84/03/12    PIP
  
 NA5A653  CORRECT FOLLOWING DRIVER PROBLEMS:  
  
          1.  CORRECT INTERFACE TO DRIVER OVERLAY STRUCTURE.
  
          2.  PROTECT AGAINST A DOWNLINE BLOCK TYPE OF ZERO.
  
          3.  CHECK NBL BEFORE ATTEMPTS TO ISSUE PRU OFF COMMAND
              OR A RESET TO THE NPU DURING PRU STREAM TERMINATION.
              CORRECTS DRIVER ERROR 73. 
  
          4.  CORRECTION TO SAVE WORKLIST LENGTH IN A DIRECT
              CELL THAT IS NOT DESTROYED BY THE CALL TO CIBS. 
  
          RMK    3/14/84     PIP
  
 NA5A609  CORRECTIONS TO PIP 2.3 FROM PIP 2.2 
  
          1.  CHANGE DRIVER TO ISSUE CLEAR NPU INSTEAD OF HALT NPU. 
              FROM 2.2 PSR NUMBER NA5A030.
  
          2.  ZERO CURRENT FILE POSITION AT END OF TRANSFER.
              FROM 2.2 PSR NUMBER NA5A354.
  
          3.  ABORT NAM ON A REGULATION ZERO SERVICE MESSAGE
              TO AN OPERATIONAL NPU.  FROM 2.2 PSR NUMBER NA50165.
  
          4.  CHANGE STREAM STATE RESPONSE TABLES TO BE MORE TOLERANT 
              OF BLOCK PROTOCOL.  FROM 2.2 PSR NUMBERS NA5A031, NA5A126,
              NA5A306 AND NA50181.
  
          RMK    3/14/84     PIP
 NA5A658  CORRECT PIP TO READ BUFFER POINTER WORDS IN ORDER 
          SO AS TO AVOID ANY POSSIBLE TIMING PROBLEM WITH NIP.
  
          MOVE CALL TO PAUSE TO ALLOW NIP TO BUFFER AHEAD.
  
          ALLOW RESTART PRU STREAM IN WAIT NO 
          OUTPUT ACTIVITY STREAM STATE. 
  
          RMK    3/15/84     PIP
 NA5A634  NPU/IN CAN BE SENT ON A HOST-TO-HOST LOGICAL LINK.
          LTN       84/03/12       NNPIIN,
  
 NA5A635  DOWNLINE MESSAGE OF 2043 CHARACTERS CAUSES PIP ERROR 33.
  
          PIP ASSUMES MAXIMUM ALLOWABLE MESSAGE SIZE IS 2042 CHARACTERS.
          IT MUST BE INCREASED BY ONE.
  
          SW     84/03/14    PIP
 NA5A647  NIP DOES NOT HAVE TO REQUEST INTERLOCK WHEN ALLOCATING
          PRU BUFFERS FOR PIP.
          NIP HAS TO ARBITRARILY ZERO OUT THE PBCABC FIELDS IN
          INTERLOCK TABLE TO AVOID PIP GETTING INTO DOULBE TIED 
          LOOP. 
          LTN       84/03/13       XEXEC,MSETIL 
  
 NA5A659  NIP SHOULD NOT ALLOW CONNECTION TO BE CONVERT TO PRU MODE 
          IF THERE IS OUTSTANDING BACK'S. I.E. IF PRU/ON/R WHILE
          NBO NON-ZERO, PRU/ON/A WILL BE RETURNED WITH REASON CODE
          5.
          UPDATE NBO COUNT WHEN CONN SWITCHED FROM PRU TO IVT.(THIS 
          FIXES THE PROBLEM OF QMSG BLOCK COULD NOT GET DELIVERED TO
          THE OTHER SIDE OF A-A PRU FILE TRANSFERRING CONN.) NPPCT
          LTN       84/03/16       HPRUON,SMDEF,NPPCT 
  
          MODIFIED AIP TO PROCESS PRU/ON/A RC=5 ACCORDINGLY.
          YCY       84/03/27       AIP
  
 NA5A662  AT INITIALIZATION TIME, NVF WILL SEARCH THE PATHPID TABLE 
          FOR SNODE/DNODE VALUES OF 0,0.  FOR EVERY 0,0 PATH, NVF 
          WILL ISSUE A CALL TO SPIDA TO SET THE PATH ACTIVE.  THIS
          WILL INSURE THAT AT LEAST ONE PATH WILL ALWAYS BE ACTIVE
          FOR INTRA-HOST CONNECTIONS. 
          PAM     84/03/28     NVFIIPS,NVFCUPS,TEXTNVF
 NA5A664  MODE 4 TERMINALS HUNG 
  
          MODE 4 OUTPUT STOPS AND INTERFACE BETWEEN NPU AND PIP IS LOST.
  
          PIP INCORRECTLY HANDLES EIO RECEIVED FLAG AT THE COMPLETION 
          OF CIO ACTIVITY AND WAITS FOR NPU RESPONSE TO EOI WHEN EOI IS 
          NOT SENT YET. 
  
          SW     84/03/30    PIP
 NA5A665  CORRECT FOLLOWING PIP PROBLEMS: 
  
            1.  SAVE CONTENTS OF A-REGISTER ON ADDRESS OUT OF RANGE.
  
            2.  NA5A653 ADDED CODE THAT WAS CORRECT FOR APPLICATION TO
                APPLICATION CONNECTIONS BUT CAN CAUSE A TERMINAL TO 
                APPLICATION CONNECTION TO NOT TERMINATE PRU MODE WHEN 
                THE NETWORK BLOCK LIMIT HAS BEEN REACHED AND THE LINE 
                OR TERMINAL HAS GONE DOWN.  CORRECT NA5A653 TO HANDLE 
                BOTH APPLICATION TO APPLICATION CONNECTIONS AND TERMINAL
                TO APPLICATION CONNECTIONS. 
  
            3.  IF A CHANNEL ERROR OCCURS ON OUTPUT TO A PRU STREAM THE 
                OUTPUT BACK COUNT HAS BEEN INCREMENT BUT THE SAME STREAM
                STATE WILL BE EXECUTED FOR THE STREAM ON THE NEXT CYCLE.
                THIS CAN CAUSE A DRIVER ERROR 73 IF THE NETWORK BLOCK 
                LIMIT HAS BEEN REACHED FOR THE STREAM.  CHANGE THE ERROR
                PROCESSORS TO EXECUTE NPU INOPERATIVE FOR THE STREAM WHEN 
                AN ERROR HAS OCCURRED TO PREVENT PROCESSING THAT STREAM 
                AGAIN.
  
          RMK    3/20/84     PIP
 NA5A667  LISTPPM CAN NOT PROCESS PIP DUMP WITH ORDINAL OTHER THAN
          1 DUED TO THE DIFFERENCES BETWEEN PIP 2.2 AND PIP 2.3.
          LTN       84/03/22       LISTPPM
  
 NA5A668 THIS IDENT REMOVES PATH AND PID STATEMENTS FROM NDL. 
         A NEW PARAMETER, "PID" IS ADDED TO OUTCALL STATEMENT SUCH THAT 
         WHEN IT IS SPECIFIED, NDLP WILL FORMAT A PATH-PID TABLE ENTRY
         WITH THE DNODE, AND SNODE UNDER THE RECORD IDENTIFIED BY THE PID.
         NDLP WILL MAINTAIN UNIQUE ENTRIES OF DNODE AND SNODE UNDER THE 
         SAME PID. THE PID PARAMETER ON OUTCALL STATEMENT WILL ALSO 
         SERVE THE FUNCTION OF THE NAME2 PARAMETER. HENCE, EITHER NAME2 OR
         PID BUT NOT BOTH MAY BE SPECIFIED. 
          YCY     84/03/22     OBLCF,DATANDL,ER2CNDL,NDLLIST,NDLPSS1, 
                               NDLP2LF,NDLSDAT
 NA5A673  THIS BUG MIGHT CAUSE THE FOLLOWING RESULTS: 
             - PRU CONNECTION WILL NOT BE TERMINATED ( RELOAD OR MASTER 
               THE NPU ). 
             - BAD INTERUPT CHARACTER OR BAD USER INTERUPT CHAR, FROM 
               CCP REJECTED BY NIP. 
             - BAD REASON IN PWL FROM PIP.
          THIS CAN HAPPENED IN 2.1, 2.2 LEVEL.
  
          LTN       84/03/26       BEIB,TWRITE
  
 NA5A685  NVF ABORTS ON A BUSY SYSTEM WHILE MANY FILE TRANSFERS ARE 
          GOING ON.  NVF IS NOT CANCELLING A TIMER REQUEST FOR A
          CONNECTION WAITING FOR A RESTARTABLE APPLICATION TO 
          NETON.
  
          THIS FIX INCLUDES CANCELLING THE TIMER REQUEST, 
          CHANGING THE SEARCH CRITERIA WHEN A TIMER FIRES, AND
          STORING THE CORRECT ACN VALUE FOR THE CONNECTION IN THE 
          TIMER REQUEST.
  
          DKE     84/04/03     NVFASPC,NVFATAC,NVFAVVD,NVFCUPS, 
                               NVFARVD
 NA5A482  CORRECT NIP STATUS K-DISPLAY TO SUPPORT 
          PAGING TO ALLOW LARGE CONFIGURATIONS
          TO BE ABLE TO DISPLAY ALL NETWORK INFORMATION.
          THIS IS DONE BY REPLACING THE THREE DISPLAY 
          BUFFER SCHEME WITH A THREE SEGMENT VITUAL 
          DISPLAY WINDOW. 
  
          SECOND, IMPLEMENT 721 CONSOLE SUPPORT.
          MSG     84/01/25     KDIS,ACB,OVLNAME,OVLSTAT,KDEF, 
                               KDSTIN,KADD,KDEL,KSTTUPD,KPTYPIN,
                               KPCLNUP,BDELINK,BLDNCNB,BLINK,HALLOCN, 
                               HPNONVF,MAJPTR,NPREGLL,RELACNB,RELNCNB,
                               XSACB,KAPIGP,SKENIP,KCHANGE,IKDIS, 
                               KUPVTAB,KDISLN,KSTPAGE,KOVDIS,CSTATUS
FS4389A   ADDED NDLP SUPPORT FOR PUBLIC DATA NETWORKS CDSN AND UNINET,
          WHICH HAVE NCF FV VALUES OF 5 AND 6, RESPECTIVELY.
          MSC     83/12/19     NDLNFCM,NDLPSS1,NDLLIST
 NA5A512  IMPLEMENT EXTENDED SLEEP FIELD TO ALLOW QTRM APPLICATION
          PROGRAMS TO SLEEP LONGER THAN 31 SECONDS
  
          MSG       83/12/13        QTRMNIT,QTOPEN,QTGET
 FN4170E  THIS MODSET IMPLEMENTS THE FEATURE WHICH ALLOWS 
          OT AND SC FOR A STARTED APPLICATION TO BE SPECIFIED 
          ON THE JOB LINE IN THE PARAMETER RECORD.
  
          RWH            03/29/84       NMI=RTE,NMI=UPC,NAMI,COLLECT
  
 FA5915B  ADD 721 CONSOLE SUPPORT TO CS.
          THIS IS MERELY DONE BY PICKING UP THE HOP PAGE LENGTH FROM THE
          HOP/START SM. 
          DKE     84/02/17     CSCPHT,CSCUHS,CSSANO,TEXTCS
 FA5915C  ADD 721 CONSOLE SUPPORT TO NVF. 
          THIS IS MERELY DONE BY PICKING UP THE HOP PAGE LENGTH FROM THE
          HOP/START SM. 
          DKE     84/02/17     NVFCPHT,NVFCUHS,NVFOAPE,NVFOPHC,TXCMDNV
 FA5915D  ADD 721 SUPPORT TO NS.
          THIS IS MERELY DONE BY PICKING UP THE HOP PAGE LENGTH FROM THE
          HOP/START SM. 
          DKE     84/02/17     SMAPPL,COM$NS,DEF$NS,NS$STR
 FS4389B  THIS IS NVF FEATURE CODE TO SUPPORT THE CCITT X.25
          SPECIFICATION.  THIS INCLUDES THE FAST SELECT FACILITY
          AND ACCEPTING UNSUPPORTED FACILITY CODES FOR A-A
          CONNECTIONS.  ALSO INCLUDED IN THIS FEATURE CODE IS A 
          MOD TO NVF TO CHECK THAT THE DTE ADDRESSES IN THE 
          CR/RAP/R AND THE INCALL BLOCK MATCH.
          PAM     84/02/16     SMNVF,NVFAIAP,NVFARAP
 NA5A580  IMPLEMENT RIGHT K-DISPLAY SUPPORT IN NIP.  THIS 
          INCLUDES A GENERAL HELP TEXT, A DETAILED NIP HELP 
          DISPLAYED IN RESPONSE TO THE -HELP- COMMAND,
          AND SUPPORT OF THE APPLICATION MODE RIGHT DISPLAY.
          MSG     84/02/07     KDIS,OVLSTAT,OVLNAME,SMAPPL,IKDIS, 
                               KPCLNUP,KHOPDIS,KDSTIN,XCHKPCR,XEXEC,
                               SKENIP,KPTYPIN,KAPIGP,KRIGHT,KRIGHTD 
 NA5A583  CORRECT ERROR IN NIP K-DISPLAY 721 SUPPORT CODE.
          USE LEFT DISPLAY SIZE VARIABLE TO FIND LOCATION 
          OF ERROR LINE INSTEAD OF OLD K-DISPLAY BUFFER 
          SIZE CONSTANT.  DELETE OLD CONSTANT TO PREVENT
          SIMILIAR ERRORS.
          MSG     84/02/03     KDEF,KDISRC
 NA5A596  THIS MOD IS TO IMPLEMENT PROBLEM LOG 32. I.E. INTRODUCING 
          BITS FOR APPLICATION ACESSING TO K-DISPLAY, AND ALLOWING
          ONLY PRE-DEFINED PRU APPLICATIONS ( IN NDLP FILE )
          LTN    84/01/20    ACB,SMNVF,TEXTNVF,HPRUON,HPNONVF,
          PAM                NVFIAST,NVFSNON,ATLCF,DATANDL,NDLSDAT, 
          YCY                NDLP2LF,NDLLIST,NDLPSS1
  
 NA5A597  NIP SHOULD QUEUE DOWNLINE -BACK- TO THE SERVICE MESSAGE 
          PRIORITY OUTBOUND BUFFER TO PREVENT DEADLOCK PROBLEM
          WHEN CCP GOES INTO REGULATION LEVEL 1 AND 2.
          DKE     84/02/22     NFOB 
 NA5A288  THIS CODE REMOVES THE AUTOLOG FLAG FROM THE NCF AND THE 
          CR/ITE/R SM.  NOW, DURING USER VALIDATION, NVF WILL 
          ALWAYS CHECK FOR AUTOLOGIN DATA IN THE ALTB AND, IF 
          FOUND, WILL USE THAT DATA FOR USER VALIDATION.  IF NO 
          AUTOLOGIN DATA IS FOUND, NVF WILL PROMPT THE USER FOR 
          LOGIN INFORMATION.
          PAM     84/02/22     SMNVF,NVFTITE
 NA5A657  IMPLEMENT CODE TO VERIFY THAT THE NCF LEVEL 
          MATCHES THE CCP LEVEL ON THE SUP/IN MESSAGE.
  
          MSG     84/03/27     TEXTCS,CSESSM,CSSADL,CSSRCA,CSIBXT,
                               CSSANS 
 FS4389F  ADD THE FOLLOWING PARAMETERS TO THE INCALL BLOCK: WS, 
          DPLS,COLLECT, AND FASTSEL.  ALSO ADD THE PORT AND DTEA
          VALUES TO THE PATHPID TABLE.
          YCY     84/03/29     PPLCF,DATANDL,IBLCF,ER2CNDL,NDLP2LF, 
                               NDLPSS1,NDLSDAT,NDLLIST
 FS4389E  THIS FEATURE CODE SUPPORTS APPLICATION SUPPLIED OUTCALL 
          PARAMETERS ON THE CR/IAP/R SM.  PRIVILEGED PROGRAMS CAN 
          SPECIFY A COMPLETE OUTCALL BLOCK MINUS THE SNODE, DNODE,
          PORT AND DTE ADDRESS PARAMETERS.  NVF WILL SUPPLY THESE 
          PARAMETERS FROM INFORMATION IN THE PATHPID TABLE.  THIS 
          ELIMINATES THE NEED FOR NVF TO PERFORM AN OUTCALL BLOCK 
          SEARCH. 
          PAM     84/03/29     TEXTNVF,NVFAIAP,NVFACTC
 NA5A639  UPON RECEIVING A FAIL/APPL SM, NVF WILL NOW BREAK ALL 
          A-A CONNECTIONS THAT ARE TRYING TO ACCESS THE FAILED
          APPL.  THIS IS DONE BY DELETING THE PAAC ENTRIES AND
          DECREMENTING THE A-A CONNECTION COUNT OF THE APPL.
          PAM     84/03/28     NVFCCPA,NVFSNOF,NVFSFAI
 NA5A676  CHANGE IN NIP TO PROCESS PWL WITH OP CODE 6.
          NIP BREAKS THE PRU CONNECTION UPON RECEIVING PWL WITH 
          OP = 6 ( BLOCK PROTOCAL ERROR WORKLIST ). 
          INTRODUCING NEW STATE NCPRUBRK AND NEW TRIGGER NCBRLPC TO 
          NCSTTP TO INITIATE BREAKING OF NETWORK CONNECTION AS WELL 
          AS THE HOST-SIDE CONNECTION.
          LTN       84/03/27       NPPWL,XSTTP
  
 NA5A675  NIP ABORT NVF UPON RECEIVING FC/RST BEFORE CONNECTION IS
          FULLY INITIALIZED.
          FC/BRK SHOULD ONLY BE DELIVERED TO THE APPLICATION
          WHEN FC/INIT/R AND FC/INIT/N EXCHANGES COMPLETED. 
          CORESPONDING, NVF MUST HAS MOD TO HANLDE THE FC/BRK (NA5A600) 
          LTN    84/03/15    XSTTP,STATTBL,STBLDEF
  
 FS4389D  DYNAMIC SVC MANAGEMENT FEATURE. 
  
          THIS IS THE CS PORTION OF THE DYNAMIC SVC MANAGEMENT FEATURE
          WHICH ALLOWS A NETWORK OPERATOR TO ENABLE, DISABLE, AND 
          STATUS ARCHETYPE SVC CIRCUITS.  INCLUDED IN THIS FEATURE IS 
          THE REPORTING OF THE PAD AND A-A CALL REQUESTS THAT ARE 
          REJECTED DUE TO INSUFFICIENT ENABLED CIRCUITS.  THE REJECTS 
          ARE REPORTED IN THE SCLI...C3 ACCOUNT FILE AND ERRLOG FILE
          MESSAGE.
  
          DEPENDENCIES - CCP PORTION OF SVC MANAGEMENT
  
          ALT       01/01/84         CSDDNT, CSEDEQ, CSESES, CSESTS,
                                     CSESVC, CSSADI, CSSAEN, CSSAST,
                                     CSSRCA, CSSROC, DLPSIN, SMCS,
                                     SMCSDEF, SMPFC, SSRRCS, TEXTCS,
                                     TXCMDCS, TXTAPSS, TXSMNVF, SUPMSG, 
                                     CSESCT, TXTSMCS
FS4389C   FEATURE CODE FOR 2.3 RELEASE, PAD PARAMETER, UDATA ENHANCEMENTS.
          MSC     84/03/29     DATANDL,LRNCF,ER1CNDL,NDLNFCM,NDLPSS1, 
                               NDLP2LF,NDLLIST,NDLSDAT,NDLTBLT
 NA5A679  NETWORK STARTUP JOBS RUN TOO SLOWLY IN SHARED RMS 
          ENVIRONMENT.
  
          NETWORK STARTUP JOBS (NAMSTRT) DEFINE ALL PERMANENT FILES 
          FOR DUMPS, TRACES, ETC.  AT STARTUP.  THIS IS INEFFICIENT,
          ESPECIALLY IN A SHARED RMS ENVIRONMENT.  ALSO, IF THE 
          NETWORK IS RUNNING IN NON-DEBUG MODE, TRACE FILES WILL NOT
          BE USED, EVEN THOUGH THEY ARE DEFINED.  IN ADDITION, THERE
          ARE INTERLOCK/RECOVERY PROBLEMS IN A SHARED RMS ENVIRONMENT 
          WHEN A PF DEVICE GOES DOWN.  THIS CONDITION IS COMPOUNDED 
          BY THE NETWORK HAVING 30-35 DIRECT ACCESS FILES OPEN IN 
          WRITE MODE AT ALL TIMES.
  
          THE NETWORK STARTUP JOBS HAVE BEEN MODIFIED TO DEFINE FILES 
          AT JOB TERMINATION, AND ONLY IF CORRESPONDING LOCAL FILES 
          EXIST.
  
          RWH            04/19/84       NAMSTRT 
  
 NA5A533  SPECIAL WORKLIST INTRODUCED TO VALIDATE AN APPLICATION
          BEFORE USING FILE TRANSFERRING FACILITY IN NETXIOD/NETXIO 
          LIBRARIES.
          LTN       84/03/29       NIPDEF,NIPTXT,HWLP,HPXFR 
                                   AIPDEF,AIPTXT,NETXFR,NP$XFR
  
 NA5A643  IMPLEMENT NEW PARITY OPTION, PA=I(GNORE), FOR ASYNC AND 
          X.25 TERMINALS.  THIS OPTION IS JUST LIKE PA=N, EXCEPT
          THAT THE PARITY BIT WILL BE IGNORED ON TRANSPARENT
          DELIMITER.  IN OTHER WORDS, THE TRANSPARENT DELIMITER WILL
          BE MATCHED ON 7 BITS ONLY.
  
          EMH    84/03/15    NDLLIST,NDLNFCM,NDLPSS1
  
 NA50147  BEFORE SENDING OUT THE CLEAR SCREEN FORMAT EFFECTOR DURING
          LOGIN, NVF WILL CHECK IF THE USER VOLUNTEERED AT LEAST ONE
          OF FAMILY, USER NAME, OR PASSWORD.  IF AT LEAST ONE OF
          THESE VALUES WAS VOLUNTEERED, NVF WILL SEND OUT THE CLEAR 
          SCREEN.  IF NONE OF THESE VALUES WAS VOLUNTEERED, AUTOLOGIN 
          MUST BE IN EFFECT, SO NVF WILL NOT SEND OUT THE CLEAR SCREEN. 
          PAM     84/03/07     TEXTNVF,NVFTPSV
 NA5A649  CLEAR UPLINE QUEUE AND DOWNLINE QUEUE COUNTER 
          WHEN READY TO GIVE APPLICATION RC/RST.
          MSG     84/03/30     HSFCBRK
 NA5A677  CORRECT SEARCH OF LLCB-S TO INCLUDE ALL LLCB-S. 
          ALSO, DO NOT CALL KDISLN IF NEW LINE IS BLANK.  AND 
          ADD NEW LINES IN PROPER LOCATION. 
          MSG     84/04/03     KDEL,KADD
 FS4389G  THIS CODE FIXES VARIOUS PROBLEMS WITH THE X.25 FAST 
          SELECT CODE.
          PAM     84/04/20     NVFAIAP,NVFARAP
 NA5A690  CORRECT NIP TO RELEASE OUTBOUND BUFFERS AS
          SOON AS POSSIBLE. 
          MSG     84/04/10     XEXEC
 NA5A687  WHEN AN APPLICATION FAILED OR NETTED OFF, SOMETIMES NVF 
          WOULD NOT SEND THE FAIL/APPL/N OR NET/OFF/N.  THE APPL NAME 
          WOULD STILL SHOW UP IN THE K-DISPLAY.  THIS WAS BECAUSE 
          THE A-A CONNECTION COUNT FOR THE APPLICATION WAS NOT ZERO.
          TO FIX THIS, THE FOLLOWING THINGS WERE CHANGED: 
            1) IN NVFARAP, WHEN INCREMENTING THE A-A CONNECTION COUNT,
               USE A DIFFERENT VARIABLE FOR THE AST ORDINAL.  THE 
               PREVIOUS VARIABLE USED WAS ALSO USED FOR OTHER THINGS. 
            2) WHEN INCREMENTING OR DECREMENTING THE A-A CONNECTION 
               COUNT, MAKE SURE IT IS DONE FOR BOTH THE PRIMARY AND 
               SECONDARY APPLS. 
            3) IF NVF RECEIVES A CR/CB FOR A CONNECTION THAT HAS NOT
               YET BEEN SWITCHED, GET THE APPL NAME FROM THE PAAC AND 
               USE THAT NAME WHEN DECREMENTING THE A-A CONN. COUNT. 
          PAM     84/04/10     NVFAIAP,NVFARAP,NVFASPC,NVFATAC,NVFAVVD
 NA5A698  NS WOULD ABORT WHEN DETECTING ERRORS WHILE DEFINING 
          A DUMP FILE.  THIS WAS CAUSED BY A BUFFER NOT BEING LARGE 
          ENOUGH.  THE BUFFER HAD OVERFLOWED AND WROTE OVER SOME
          EXECUTABLE CODE.
  
          THE SOLUTION WAS TO ENLARGE THE BUFFER TO ACCOMODATE THE
          LARGEST MESSAGE.
          DKE     84/04/12     MACREL 
 FS4201Z  THIS FEATURE CODE ENABLES *COLLECT* TO PICK UP FILES
          GENERATED BY PSU (PR), QTF (QT), QTFS (QS), AND 
          PTFS (PS).  IT ALSO CHANGES *COLLECT* TO NOT MAKE 
          DUMPXXX AND DUNPXXX PERMANENT.
  
          RWH            04/10/84       CLT=INI,CLT=IO2 
  
 NA5A672  CORRECT DRIVER NPU CHANNEL TABLE USAGE TO ALLOW FOR MORE THAN 
          MAXNPU NPUS DRIVER BY THE DRIVER AT DIFFERENT TIMES.
  
          RMK    3/29/84     PIP
 NA5A655 CORRECTIVE CODE OF PSR NA5A363 OVERRODE PART OF THE CORRECTIVE 
         CODE OF PSR NA5A317 IN SERICE AND SCHEDULING ROUTINE *SSACNI*. 
         THE LINE TO SET THE MAXIMUM TEXT LENGTH IN CM WORDS IN 
         NETGETL CALL DELETED BY NA5A317 IS PUT BACK BY NA5A363, WHICH
         CAUSE AN INPUT-BLOCK-UNDELIVERABLE CONDITION IN FILE SERVER
         AND AOF. 
         AML     84/04/02     SSACNI
 NA5A700  FOR XFR PRU A-A CONNECTIONS, CON/END/R FROM APPLICATION WILL
          BE PROCESSED TO TERMINATE PRU MODE OF CONNECTION. 
                             XSTTP
  
          UPON PROCESSING IFT, OFT/START, IF FILE TYPE OF FILE TO BE
          SWITCHED IS ILLEGAL FILETYPE, NIP WILL SEND ERR/LGL WITH
          RC=13 TO APPLICATION. 
                             HPRUSM 
  
          UPON PROCESSING IFT/END, OFT/END, XFT/IER,
          NIP SHOULD CHECK FOR FILE IS STILL WITH NAM BEFORE CALL SST 
          TO SWITCH FILE TO ALLICATION CONTROL POINT. 
                             NPPSN
  
          LTN    84/04/11    XSTTP,HPRUSM,NPPSM 
  
  
          THIS IDENT ADDS RETURN ACTION IN THE STATE TABLE FOR PRU
          SENDER AND RECEIVER WHEN AN ILLEGAL TRIGGER IS RECEIVED.
          THE RETURN ACTION WILL THEN ASSIGN REASON CODE TO THE 
          STATUS WORD OF QTFXFER AND RETURN CONTROL TO THE CALLER 
          ISSUING APPROPRIATE DAYFILE MESSAGES. 
  
          YCY     84/04/10     NP$STTP
  
 NA5A702  FIX NIP STATE TABLE ERROR WHEN NIP RECEIVE NPI/DD FROM ANOTHER
          HOST. THIS MOST BE BUILT WITH NA5A634.
          LTN    84/04/13    NPNIPSM
  
 NA5A688  PIP PP HUNG POSSIBLY FOR COUPLER CHANNEL HARDWARE PROBLEM.
  
          DEADSTART DUMP SHOWS A PIP HUNG AT A CHANNEL INSTRUCTION
          THAT DOES NOT HAVE NO-HUNG BIT SET EVEN THOUGH THAT 
          INSTRUCTION IS GUARDED LOGICALLY POSSIBLE CHECKS. 
  
          NO-HUNG BIT SHOULD BE SET FOR A PRODUCTION ENVIRONMENT AS 
          IT WILL SAVE THE SYSTEM EVEN IF IT MAY PRODUCE LESS VALUABLE
          DEBUG INFORMATION AT A RARE HARDWARE TROUBLE. 
  
          SW     84/04/11    PIP
 NA5A641  NOS 23E HAS NOSTEXT SYMBOLS CONFLICTING WITH PIP SYMBOLS. 
  
          ROSS AND SOSS ARE SYMBOLS PIP HAS DEFINED LOCALLY.
          NOW THESE ARE IN NOSTEXT. 
  
          THESE SHOULD BE LEFT LOCAL FOR PIP ASSEMBLY.
          SW     84/04/02    PIP
 NA5A475  AN APPLICATION ISSUED A QTLINK TO ANOTHER APPLICATION.  THE 
          CALLED APPLICATION WAS AN UNKNOWN, UNDEFINED APPLICATION. 
          CONTROL NEVER RETURNED TO THE CALLING APPLICATION.  THIS WAS
          BECAUSE NVF ISSUED THE WRONG ERROR CODE IN THE CR/IAP/A SM. 
          THE ERROR CODE THAT NVF ISSUED WAS FOR APPLICATION FAILED.
          THE CALLING APPLICATION NEVER GOT CONTROL BACK BECAUSE NAM
          THOUGHT THAT THE CALLING APPL (INSTEAD OF THE CALLED APPL)
          FAILED.  TO FIX THIS, CHANGE NVF TO ISSUE THE CORRECT 
          ERROR CODE (FOR INVALID REQUEST). 
          PAM     84/04/17     NVFAIAP
 ABIC     ISSUE *ABIC* ACCOUNT FILE MESSAGE FROM NVF. 
  
          CURRENTLY NO DEFAULT CHARGE INFORMATION IS ISSUED 
          TO THE SYSTEM ACCOUNT FILE ON AN INITIAL LOG IN.
  
          THIS MODSET WILL ISSUE THE *ABIC* MESSAGE AFTER EVERY 
          PRIMARY USER ACCOUNT FILE MESSAGE (*ABUN*). THIS NEW
          MESSAGE SPECIFIES THE DEFAULT CHARGE/PROJECT RETURNED 
          FROM CPM FUNCTION 56 - VALIDATE USER. IF CHARGE FIELD 
          IS ZERO, NO MESSAGE IS ISSUED.  FORMAT OF *ABIC*
          MESSAGE IS: 
  
                 ABIC,CHARGE,PROJECT,TERMINALNAME.
  
          DEPENDENCIES:      NA50092
                             ABIC2
  
          LAE    02/22/84    TEXTNVF,TXTANVF,NVFTIAM
                             NVFTPSV,NVFTVVD
  
 NA5A707  NETXFR SHOULD CHECK FOR VALID FILE TYPE BEFORE BEGINNING
          FILE TRANSFERRING PROCESS. IF FILE TYPE IS NOT VALID ( TAPE 
          FILE TO BE SENT, SYSTEM LIBRARY...), STATUS OF 31 WILL BE 
          RETURNED TO APPLICATION. ALSO IF FILE NAME FOR XFRRING IS 
          *INPUT* AND JOB ORIGIN TYPE IS TERMINAL, NETXFR WILL REJECT 
          WITH REASON CODE 32.
          LTN       84/04/19       NETXFR,NP$GJO,NP$INFO
  
 NA5A697  NVF SOMETIMES HANGS IN THE K-DISPLAY.  THIS HAPPENED BECAUSE
          UNDER SOME CIRCUMSTANCES, NVF WOULD BUILD AND SEND A HOP/START
          TO THE I-LAYER, BUT WOULD FAIL TO SUPPLY A VALUE FOR THE
          LEFT AND RIGHT K-DISPLAY LENGTHS.  THESE VALUES WOULD THEN
          DEFAULT TO ZERO, AND THIS CAUSED NVF TO HANG.  TO FIX THIS, 
          HAVE NVF SET THE LEFT AND RIGHT K-DISPLAY LENGTHS TO THEIR
          PREVIOUS VALUES WHEN NVF SENDS A HOMEMADE HOP/START TO THE
          I-LAYER.
          PAM     84/04/19     NVFCCPA
 NA5A705  THIS CODE FIXES FOUR PROBLEMS.
          1)  NVF GETS "SM NOT ROUTED" BECAUSE IT SENDS A SH/ISD WITH 
              AN INVALID ACN.  THIS SM SHOULD NOT EVEN HAVE AN ACN. 
              CHANGE NVF TO CLEAR THE SM BUFFER PRIOR TO SENDING THE
              SH/ISD SM.
          2)  NVF DOES NOT TIME OUT CONNECTIONS.  THIS IS BECAUSE A 
              FLAG THAT NVF USES TO CHECK IF THE USER SHOULD BE TIMED 
              OUT IS NEVER INITIALIZED.  CHANGE NVF TO INITIALIZE THIS
              FLAG. 
          3)  NVF TRIES TO DISABLE THE PID.  THIS IS BECAUSE NVF SENDS
              A SPIDA WITH A FUNCTION CODE OF 0 (INSTEAD OF 1).  NVF WAS
              USING THE WRONG ARRAY SUBSCRIPT WHEN IT STORED THE FUNCTION 
              CODE IN THE SPIDA PARAMETER BLOCK.  CHANGE NVF TO STORE 
              THE FUNCTION CODE IN THE RIGHT ARRAY ENTRY. 
          4)  NVF DOES NOT SET THE PID TO IN SERVICE AT INITIALIZATION
              TIME.  THIS HAPPENED BECAUSE SPIDA CLEARS THE STATUS FIELD
              AND NVF WAS ASSUMING IT WOULD STILL BE SET TO 1.  CHANGE
              NVF TO SET THE STATUS FIELD EACH TIME IT MAKES A CALL TO
              SPIDA.
          PAM     84/04/19     NVFTINA,NVFTICR,NVFOPAC,NVFIIPS
 NA5A695  THIS IDENT FIXES FORMATTING OF DEFAULT  AND 
          SPECIFIED UDATA. IT ALSO FIXES FORMATTING OF FAC PARAMETERS 
          AND MODIFIES NDLLIST ACCORDINGLY. PAD PARAMETERS ARE LISTED 
          IN GROUPS OF FOUR. CODE WAS CUT IN TERMPR FOR EVERY TIPTYPE 
          SUCH THAT IF PAD IS SPECIFIED ON THE TERMINAL STATEMENT,
          NDLP WILL SKIP WORDS ACCORDINLY.
          YCY     84/04/18     OBLCF,NDLLIST,NDLNFCM,NDLP2LF,NDLPSS1, 
                               NDLSDAT
 NA50188  NDLP IS NOT DEFAULTING VALUES OF DBZ TO 640 FOR 
          LINE PRINTER OF A MODE 4A DEVICE WHEN STIP MODE 4A IS 
          SPECIFIED. DEFAULT VALUE OF DBZ IN THIS CASE IS SET TO 640. 
          YCY     84/04/19     NDLNFCM
 NA5A703  THIS IDENT CHANGES THE DEFAULT VALUE OF XBZ FOR MODE 4A 
          FROM 1000 TO 1040. IF STIP MODE 4A IS SPECIFIED THEN DEFAULT XBZ
          FOR ALL DEVICES IS CHANGED TO 1040. IF TERMINAL CLASS 734 OR
          200UT+ IS SPECIFIED THEN THE DEFAULT XBZ IS ALSO CHANGED TO 1040. 
          YCY     84/04/19     NDLNFCM
 NA5A710  PIP ERROR 73 AT NPU MASTER CLEAR
  
          PIP ERROR 73 WHEN PIP RELOADS NPU THAT HAS ACTIVE PRU 
          CONNECTIONS.
  
          SW     84/04/03    PIP
 NA5A711  PIP SHOULD BYPASS INPUTS AFTER LEVEL SEVEN ERROR WAS REPORTED.
  
          PIP REPORTS DRIVER ERROR AT AN INPUT AFTER LEVEL SEVEN
          ERROR WAS REPORTED. IT SHOULD BYPASS INPUTS AND BACKS AFTER 
          THE ERROR.
  
          SW     84/04/11    PIP
 NA5A689  PIP ERROR 75 MAY HAPPEN IF MASTER CLEARED WHILE CCP DUMPING.
  
          PIP BLOCK HANDLER RESPONSE ACTION FOR PROCESSING START/WAIT 
          COMMAND IS NOT CORRECT AND THERE IS NO WAYOUT FROM THE STATE. 
  
          SW     84/04/20    PIP
 NA5A708  A-A PRU MODE FILE TRANSFER FAILS WITH LARGE FILES 
  
          A-A PRU MODE FILE TRANSFER FAILS AT BLOCK NUMBER 4096 AS
          THE BLOCK NUMBER VERIFICATION PROCESSING IS VALID UP TO THIS
          LIMIT.  A CORRECTION FOR HANDLING BLOCK NUMBER RESETTING AT 
          65535 AND A PROPER BLOCK NUMBER INITIALIZATION ARE INCLUDED.
  
          SW     84/04/19    PIP
 NA5A526  MODIFY PIP TO USE A BUFFER FOR BACK-S THAT IS LARGE 
          ENOUGH FOR NIP TO USE IN CONSTRUCTING FC/ACK MESSAGES 
          FROM THE BACK.  THIS WILL REDUCE THE AMOUNT OF
          MEMORY MANAGEMENT IN NIP. 
          MSG     84/04/29     HSFCACK,CSTATUS,PIP
 IVTBACK  PIP MAKES UPLINE IVT BACK AS 3 CM WORD BLOCK IN INBOUND BUFFER
  
          SW     84/04/10    PIP
 NA5A670  WHEN A USER TRIES TO LOGIN TO AN APPLICATION THAT HAS 
          MULTIPLE COPIES RUNNING, THE USER SHOULD NOT HAVE TO
          APPEND THE APPLICATION NUMBER TO THE APPLICATION NAME.
          NVF SHOULD HANDLE LOGGING IN TO A MULTI-COPY APPLICATION
          SIMILAR TO THE WAY IT HANDLES LOGGING IN TO A REQUEST 
          STARTABLE APPLICATION (WITH THE EXCEPTION OF ROUTING A
          JOB TO START UP THE APPLICATION). 
          PAM     84/04/20     NVFTDSP,NVFUCRS
 NA5A693  STOP,LP,END FOLLOWED BY RETURN LP KILLS RBF.
  
          PIP GENERATES ERROR 163 IF OFC/STOP COMES AFTER OFC/ABORT.
          IT SHOULD BE ACCEPTED.
  
          SW     84/04/11    PIP
 NA5A273  CHANGE AN ERROR MESSAGE TO REFLECT WHAT IS DOCUMENTED.
          DKE     84/04/20     NDAS 
 NA5A678  NDLP SHOULD ALLOW THE *IN* PARAMETER FOR DEVICES DEFINE FOR 
          TIPTYPE=X25.
  
          THIS CODE ALLOWS KB AND BK AS VALID VALUES AND DISALLOWS PT.
          DKE     84/04/20     NDLNFCM
 NA5A712  CHANGE NVF TO SET HOST PID TO IN SERVICE
          BY CONSTRUCTING HOST PID FROM MACHINE ID. 
          MSG     84/04/20     NVFIIPS,MACREL 
 NA5A656  ADD REASON CODE STATE FOR SFORM ERROR 
          (FULL SCREEN INTERFACE ERROR) 
          MSG     84/03/23     QTRMNIT
 NA5A626  CORRECT QTRM TO USE THE CHARACTER SET 
          SPECIFIED BY THE USER FOR INTRA HOST
          A-A CONNECTIONS.
          MSG     84/03/23     QTGET,QTPUT
 NA5A691  CORRECT HELP RIGHT K-DISPLAY TO ZERO BYTE 
          BLANK LINES AT THE END OF ITS DATA PROPERLY.
          MSG     84/04/10     KRIGHTD
 NA5A721  THIS CODE FIXES THREE NVF A-A PROBLEMS. 
          1)  NVF ABORTED BECAUSE INTRA-HOST OUTCALL UDATA LENGTH 
              FIELD WAS NOT THE SAME FORMAT AS THE INTER-HOST OUTCALL 
              UDATA LENGTH FIELD.  CHANGE THE INTRA-HOST OUTCALL BLOCK
              TO HAVE THE SAME FORMAT AS THE INTER-HOST OUTCALL BLOCK.
          2)  NVF SENT A CR/TRM WITH AN ACN THAT WAS ALREADY RELEASED.
              CHANGE THE WAY NVF SEARCHES THE PAAC TABLE SO IT DOES NOT 
              READ BEYOND THE PAAC TABLE AND PICK UP WRONG ACN VALUES.
          3)  NVF ABORTED BECAUSE IT COULD NOT FIND AN AST ENTRY FOR
              THE CR/RCN.  THIS WAS BECAUSE IT HAD BEEN DELETED BY
              FAIL/APPL PROCESSING.  CHANGE NVF TO NOT ABORT IN THIS
              CASE EXCEPT IF THE CONNECTION WAS IN LIMBO STATE. 
          PAM     84/05/04     NVFAIAP,NVFATAC,NVFSFAI
 NA5A715  WHEN CS RECEIVED A ST,NPS IMMEDIATELY FOLLOWED BY A 
          DI,LI=LINE,  IT SENT A REQUEST FOR NPU STATUS SM WITH THE 
          WRONG SFC.  WHEN THE NPU RESPONDED WITH A NORMAL RESPONSE 
          TO THE ILL-FORMATTED SM CS ABORTED COMPLAINING IT DID NOT 
          RECOGNIZE THE SM. 
  
          CS NEEDED TO CLEAR A BUFFER BEFORE RECEIVING THE COMMAND
          PARAMETER BLOCK FOR A QUEUE.  THE SOLUTION DOES JUST THAT.
          DKE     84/04/28     CSSDRC 
 NA5A714  CS NOP CONNECTION HUNG WHEN ATTEMPTING TO STATUS ELEMENTS IN
          THE NETWORK.
  
          CS WAS NOT CLEARING THE NPU ORDINAL IN THE OPERATOR CONTROL 
          BLOCK ONCE THE STATUS REQUEST WAS COMPLETED BY THE NPU.  IF 
          THE OPERATOR WAS WAITING FOR ANOTHER NPU TO COMPLETE A STATUS 
          REQUEST AND THEN HIT A USER BREAK, THE PREVIOUSLY COMPLETED 
          STATUS REQUEST WOULD BE SET TO REQUEST TERMINATED AND WOULD 
          NEVER BE CLEARED. 
  
          THE SOLUTION WAS TO CLEAR THE NPU ORDINAL ONCE THE REQUEST WAS
          COMPLETED.
          DKE     84/05/04     CSSCSR 
 NA5A680  THIS IDENT FIXES THE PROBLEM THAT NDLP WAS NOT CLEARING 
          CRNT$TIP IN PASS ONE CORRECTLY AND ADDING EXTRA ZEROES TO NON-X25 
          DEVICE NAMES AS A RESULT. 
          YCY     84/04/25     NDLPSS1
 NA5A709  THIS IDENT CHANGES THE SEVERITY LEVEL OF ERROR
          MESSAGE 127 FROM WARNING TO FATAL. THIS MESSAGE IS GENERATED
          WHENEVER THERE IS NO LOGICAL LINK DEFINED TO A NPU. 
          YCY     84/05/03     ER2CNDL
 NA5A706  PIP NPU INTERFACE LOST AFTER NPU TIMES OUT PIP
  
          PIP DOES NOT RE-INITIATE INTERFACE TO NPU AFTER NPU TIMES 
          OUT PIP FOR SOME REASON.  PIP DOES NOT ACKNOWLEDGE REG/CP 
          RESPONSE FROM NIP AFTER IT SENT REG/CP REQUEST. 
  
          SW     84/04/24    PIP
 NA5A733  THIS IDENT FIXES THE PROBLEM THAT DPLS VALUE WHICH
          IS ENCODED AS THE POWER OF 2 IS NOT CONVERTED BACK TO ITS 
          ORIGINAL VALUE IN THE SUMMARY LIST. 
          THIS APPLIES TO INCALL AND OUTCALL STATEMENTS.
          YCY     84/05/03     NDLLIST
 NA5A735  THIS IDENT FIXES THE PROBLEM THAT DPLR WHICH IS 
          ENCODED AS THE POWER OF 2 IS NOT LISTED IN TERMS OF ITS 
          ACTUAL VALUE IN NDLLIST BUT AS THE POWER OF 2 ONLY. 
          YCY     84/05/04     NDLLIST
 NA5A742  NIP WILL FORCE THE CONTROL CARD PARAMETERS, N1PRUB, N2PRUB
          AND N3PRUB TO BE THE MINIMUM IF ANY OF THOSE PARAMS SPECIFIED 
          BELOW ITS MINIMUM (2,4,2), AND DAYFILE A MESSAGE. 
          LTN       84/04/25       INIP 
  
          WHEN PRU CONNECTION IS INITIATED, ALLOCATE NUMBERS OF PRU 
          BUFFERS ACCORDING TO THE MAXIMUM VALUES OF THAT TYPE OF PRU.
          LTN       84/04/25       HPRUON 
  
          IF NIP HAS REACHED MAXFL AND WENT INTO REGULATION OF ZERO, NIP
          WILL TRY TO CALL GABAGE COLLECTION AS MUCH AS POSSIBLE TO FREE
          NIP FROM FRAGMENTATION. AFTER MOVING BUFFERS COMPLETED, 
          MGBGCLT SHOULD TRY TO CHANGE THE REGULATION ACCORDING TO THE
          BUFFER SIZE OF THE LAST FREE BUFFER IN THE FREE CHAIN.
          LTN       84/04/30       MGBGCLT
  
          WHEN ALOCATING BUFFERS FOR PIP, NIP MAKES SURE TO CHECK 
          REGULATION LEVEL BEFORE GOES ON TO GET NEXT BUFFER. 
          ONLY ALLOCATE PRU BUFFERS IN BUFFER REGULATION THREE. 
          LTN       84/04/24       XEXEC,XCHKABC
  
          CHANGE THE REASON CODE FOR ERR/LGL IN THE CASE OF ILLEGAL 
          FILETYPE TO 11. 
          LTN       84/04/25       HPRUSM 
  
 NA5A742  THIS IDENT PERFORMS A REWIND FOR THE THE FILE AT THE
          RECEIVER'S END. 
          IT MODIFIES ACTION CODE IN THE STATE TABLE FOR BOTH 
          PRU AND CHARACTER MODE SO THAT RESTART REQUEST IS 
          DISABLED. IT ALSO CHANGES NP$SMSG TO TREAT REASON 
          CODE 10  IN XFTIER RATHER THAN REASON CODE 2 TO 
          BE RECOVERABLE. 
          YCY     84/04/05     NP$ADEF,AIPSTDF,NP$SMSG,NP$STTP
 NA5A716  CORRECT CS TO ISSUE CORRECT ERROR MESSAGE ON
          NCF MISMATCH CONDITION. 
          MSG     84/05/01     CSESSM 
 NA5A748  CORRECT ERROR MESSAGE FORMAT IN MGETC.
          MSG     84/05/01     MGETC
 FS4389I  MODIFY NDLP TO CONVERT THE DFL VALUE TO LOG 2.
          DKE     84/01/09     NDLNFCM,NDLCKRG
 FS4389H  THIS IDENT IMPLEMENTS THE IMDISC AND THE LCN PARAMETERS 
          FOR THE LINE STATEMENT. LCN IS VALID ONLY FOR X25 LINES AND IMDISC
          IS VALID FOR ALL TIPTIPES AND IN THE CASE OF A X25 LINE THE USER
          MAY ONLY SPECIFY "NO" FOR IMDISC. 
          YCY     84/04/26     NDLSDAT,NDLCKRG,NDLPSS1,NDLNFCM,NDLLIST
 *L617*    ************************************************ 
 FN3270B  ADD SUPPORT OF 3270 IN TVF. 
          DKE     84/04/18     TVF
 FS4389J  THIS IDENT ADDS C120 AS A PSN NAME TO THE NDLP LINE 
          STATEMENT. THIS PSN HAS AN INTERNAL VALUE OF 7. 
          YCY     84/06/04     NDLPSS1,NDLNFCM,NDLLIST
 NA5A523  WHEN TIPTYPE IS USER DEFINED, NDLLIST WAS 
          LOOKING AT THE WRONG INTEGER TEMPORARY FOR CONVERSION.
          THIS IS CORRECTED.
          YCY     84/07/13     NDLLIST
 NA5A525  ISSUE DAYFILE MESSAGE INDICATING NIP WAS
          BUILT WITH DEBUG OR STAT DURRING NIP STARTUP. 
          MSG     84/05/31     INIP 
 NA5A531  PIP DOES NOT HALT NPU AT NAM TERMINATION
  
          PIP DOES NOT HALT NPU AT NAM TERMINATION FOR AN ERROR 
          EVEN IF IT IS SO SPECIFED BY A REQUEST FLAG IN PIP INTERFACE
          TABLE.
  
          SW     84/05/16    PIP
 NA5A532  NP$PUT RETURNS TO NETPUTF AFTER SETING UP ABH BLOCK.
          RETURN INFOMATION OF BLOCK HEADER AFTER INFO HAS BE CHECKED 
          AND UPDATED.
          LTN       84/05/18       NP$PUT,NP$GSM
  
 NA5A538   CORRECT TLW VALUE LISTED OUT IN TRACE FILE.
           LTN      84/07/17       DLAREP 
  
 NA5A579  DLFP WILL RESET PAGE COUNT AND MESSAGE COUNT WHEN EOF IS
          ENCOUNTERD AND THERE IS STILL INFORMATION TO BE PROCESSED.
          LTN       84/07/17       DLREP
  
 NA5A610   NIP SHOULD TERMINATE WITH DUMP IF DETECTING AN INTERNAL ERROR. 
           FIX NA5A634 ACCORDING TO COMMENTS. 
           LTN      84/02/24       MAJPTR,NPREGLL,RELACB,RELACNB
                                   RELNCNB,BLDLLCB,BLDACNB,HPNONVF. 
  
 NA5A683  PUT IN ALL NEW SUPERVISORY MESSAGES SINCE 2.0 LEVEL, ALSO 
          ALL LEVEL SEVEN SUPERISORY MESSAGES FOR FILE TRANSFERRING 
          FEATURE.
  
 NA5A717  THIS IS AN ADDITIONAL FIX FOR NA5A697 WHICH SET THE 
          LEFT AND RIGHT PAGE LENGTHS IN THE HOP/START MESSAGE SENT 
          TO THE INNER LAYER. 
  
          THE FIX IS TO MERELY INCREASE THE ENTRY WORD COUNT TO INCLUDE 
          THE TEXT AREA.
          DKE     84/05/16     NVFCPHT,NVFCCPA
 NA5A734 THIS IDENT CHANGES THE MAXIMUM NUMBER OF HEX DIGITS
          THAT ONE CAN SPECIFY FOR PRID TO BE SIX. NDLLIST IS ALSO
          CHANGED TO REFLECT THE CHANGE. DEFAULT PRID IS NOW C10000.
          YCY     84/05/29     NDLLIST,NDLP2LF
 NA5A746  NVF WAS ABORTED BY DSP WHEN TRYING TO ROUTE AN EMPTY JOB
          RECORD. 
  
          WHEN DOING A GET ON A FILE NVF WAS ASSUMING THAT IT WAS DONE
          WITH RECALL.  THE GET FUNCTION WAS MODIFY TO ALWAYS DO IT 
          WAITING UNTIL THE COMPLETE BIT IS SET.
  
          DKE     84/05/24     MACREL 
 NA5A749  DLFP SHOULD ACCOMODATE NEW OP CODE FOR XFR. 
          LTN       84/05/24       DLAREP 
  
 NA5A754  THIS CODE FIXES TWO RELATED PROBLEMS OF NVF FAILING WHILE 
          RUNNING A-A CONNECTIONS.
          1) IF A FAIL/APPL IS RECEIVED AFTER A CR/SWH/N IS RECEIVED
             BUT BEFORE A CR/ACC IS RECEIVED, AND 
          2) IF A FAIL/APPL IS RECEIVED AFTER A CR/RCN IS RECEIVED
             BUT BEFORE THE VCB DATA CAN BE READ IN.
          IN THE FIRST CASE, NVF WOULD SEND OUT A CR/TRM, WHICH WOULD 
          THEN ABORT BECAUSE THE ACN ENTRY HAD ALREADY BEEN DELETED.
          IN THE SECOND CASE, THE VCB READ WOULD ABORT BECAUSE THE VCB
          ORDINAL WOULD ALREADY HAVE BEEN RELEASED. 
          WITH THIS CODE, NVF WILL CHECK FOR THESE TWO CASES BEFORE 
          CLEANING UP THE PAAC AND VCB, AND SENDING THE CR/TRM. 
          PAM     84/05/10     NVFCBPA,NVFADQE,NVFAACC,NVFASPC, 
                               NVFSFAI,NVFASWN
 NA5A760  PIP ERROR 103 
  
          AT BHS10 WITH SAM BIT SET, IF LEFTOVER LOAD COMMANDS ARE
          PRESENT, RESPONSE ACTION IS ENTERED WITHOUT SETTING COMMAND 
          ORDINAL. THAT MAY CAUSE PIP ERROR 103.
  
          SUBROUTINE IPD USES T16 WITHOUT SETTING IT. 
  
          LEVEL SEVEN ERROR LEAVES ERRCODE SET, RESULTING ABORTING NAM
          WHEN PIP DROPS FOR NO ACTIVITY. 
  
          SW     84/06/01    PIP
 NA5A762  PIP SHOULD ALLOW UPLINE BACK AFTER OUTPUT PRU STREAM STOPPED. 
  
          PIP SHOULD ALLOW UPLINE BACK AFTER OUTPUT PRU STREAM STOPPED
          EXTERNALLY. 
          (THIS CORRECTION CORRESPONDS TO NA50206 FOR NOS 2.2.) 
  
          SW     84/05/09    PIP
 NA5A763  NAM ABORTS WITH RANDOM ADDRESS NOT ON FILE
  
          PIP SHOULD KEEP CURRENT PRU POSITION IN PCNB CLEARED WHILE NO 
          FNT EXISTS. 
  
          (THIS CORRECTION CORRESPONDS TO NA50140 FOR NOS 2.2.) 
  
          SW     84/05/09    PIP
 NA5A764  PROBLEM OCCURRED WHEN USER DROPPED APPLICATION DURING AB- 
          NORMAL NETTING ON.
          THIS MOD INTRODUCES AN ABNORMAL NETON BIT IS AT, THIS BIT IS
          SET WHEN NET/ON/A IS RECEIVED FROM NVF. HAPFAIL SHOULD CHECK
          FOR THIS BIT BEFORE SENDING APPL/FAIL/R TO NVF; IF THIS BIT 
          IS ON, DO NOT SEND APPL/FAIL/R BUT JUST RELEASING ACB AND 
          RELATED BUFFERS.
          LTN       84/05/08       AT,HPPUT,HAPFAIL 
  
 NA5A770  SETTING ATNVFA WHEN RECEIVING NET/ON/A BY APLLICATION FROM
          THE SUPERVISORY MESSAGE.
          WHEN XSACB FINDS AN ENTRY WITH ATNVFF AND ATNVFA SET, IT WILL 
          JUST GO AHEAD AND RELEASE THE ENTRY.
          LTN      84/06/14       HPPUT 
  
 NA5A774  XEXEC WILL GET PRU BUFFERS ONLY WHEN HOST REGULATION IS THREE.
          UPDATE BUFFER COUNT IN XCHKABC BY NUMBER ALLOCATED. 
          NPRLB RESET COUNT AFTER RELEASE ALL LIMBO BUFFERS.
          LTN       84/05/16       XEXEC,XCHKABC,NPRLB
  
 NA5A775  NDLP ABORTS WHEN MAXIMUM NUMBER OF FACILITY IS DEFINED
          FOR INCALL OR OUTCALL STATEMENTS. THIS IS CAUSED BY THE STATEMENT 
          TABLE COUNT FIELD WIDTH BEING DEFINED AS A SIX BIT DATA ITEM. 
          STWC IS NOW AN EIGHTEEN BIT DATA ITEM.
          YCY     84/05/21     NDLTBLT,NDLP2LF
 NA5A776  UPON RECEIVING PWL WITH OP 6 (BLOCK PROTOCAL ERROR), BREAK
          TRIGGER WILL BE SENT TO NCSTTP, BUT THE CONVERTED NCNB SHOULD 
          NOT BE RELEASED.
          THIS MOD FIXES NCSTTP2 NIP INTERNAL ERROR DUE TO BLOCK
          PROTOCOL VIOLATION ERROR 91 FROM PIP. 
          LTN       84/05/25       NPPCT,NPPWL,MAJPTR,PCNB,NCNB 
  
 NA5A780  IMPLEMENT TIMEOUT OF REQUEST STARTED APPLICATIONS.
          IF A REQUEST STARTED APPLICATION DOES NOT NETON 
          WITHIN THE DEFINED TIME PERIOD, CLEAR THE REQUEST 
          STARTED APPLICATION PENDING FLAG TO ALLOW ANOTHER 
          ATTEMPT.  IF APPLICATION FAILS THREE SUCCESSIVE 
          TIMES, DISABLE APPLICATION. 
          MSG     84/05/30     TEXTNVF,NVFSNON,NVFUCRS,TXSANVF,NVFSDQE, 
                               NVFIAST,NVFSTIM
 NA5A781  THIS IDENT RECONVERTS ENCODED VALUE OF DBZ
          INTO THE ENCODED VALUE MULTIPLED BY 640. EXCEPTIONS ARE 
          DBZ FOR USER DEFINED TIPTYPE, USER DEVICE TYPE, CONSOLE AND 
          AP DEVICE TYPE. 
  
          YCY     84/06/18     NDLLIST
 NA5A782  PIP ERROR 66 AT CHANNEL HARDWARE ERROR
  
          IF CHANNEL HARDWARE ERROR HAPPENS IMMEDIATELY AFTER A COUPLER 
          EST ENTRY IS SET ON, PIP MAY GIVE ERROR 66 INSTEAD OF A 
          CORRECT ERROR CODE. 
  
          SW     84/05/21    PIP
 NA5A783  NVF SHOWS A PHANTOM APPLICATION ACTIVE WHICH NEVER
          REALLY NETTED ON.  ALSO WHEN TRYING TO STATUS THE PHANTOM 
          APPLICTION NVF ABORTS WITH A CPU ERROR EXIT.
  
          THE SOLUTION WAS TO INCREMENT THE ACTIVE APPLICATION COUNT
          ONLY WHEN THE APPLICTION NET-S ON.
  
          DKE     84/05/24     NVFUCRS,NVFSNON
 NA5A785  CHANGE *USER NUMBER* TO *USER NAME* IN COMMENTS ON
          NAMSTRT FILE. 
  
          RWH            05/18/84       JOBNVF,JOBNS,JOBCS
  
 NA5A788  NVF DOES NOT RESPOND TO THE K-DISPLAY.
  
          THE NVF C-LAYER WAS NOT SENDING THE HOP/START INTO THE INNER
          LAYER INTACT.  THIS CODE MODIFIES THE C-LAYER TO SEND THE SM
          UNMODIFIED. 
          DKE     84/05/24     NVFCUHS
 NA5A789  THE CS K-DISLPLAY WOULD HANG WHEN INVOKING A SEND 
          MESSAGE TO ALL NPUS COMMAND WHEN NO NPUS ARE BEING
          SUPERVISED. 
  
          THIS FIX COMPLETES THE ACTION ON THE SEND COMMAND WHEN
          THERE ARE NO NPUS BEING SUPERVISED. 
  
          DKE     84/06/08     CSSAMS 
 NA5A791  NVF ABORTED WHEN, FOR AN A-A CONNECTION, THE CR/SWH/N 
          WAS RECEIVED AT THE SAME TIME AS A FAIL/APPL.  NVF PROCESSED
          THE FAIL SM BEFORE THE SWITCH SM AND THEN PROCEEDED TO
          ABORT.
  
          THE WORKLIST PRIORITIES WERE CHANGED SUCH THAT THE PROCESSING 
          OF THE SWITCH WOULD ALWAYS BE PROCESSED BEFORE A FAIL/APPL. 
  
          DKE     84/06/13     TXINNVF
 NA5A794  PIP ERROR 24 ON THE LOW-COST MACHINE. 
  
          PP ORDER CODE TO SHIFT A-REGISTER OF LOW-COST CYBER 
          SEEMS TO ACCEPT AS THE SHIFT COUNTER UP TO 17 DECIMAL.
          AND ANY VALUE GREATER THAN 17 SEEMS TO BE TREATED AS 17.
          SW        84/05/22       PIP
  
 NA5A795  NVF WAS NOT CORRECTLY COMPARING THE DTE ADDRESS IN THE INCALL 
          BLOCK WITH THE DTE ADDRESS SPECIFIED IN THE CR/RAP/R.  THIS 
          CODE ALLOWS NVF TO COMPARE THE CORRECT NUMBER OF BITS IN THE
          DTE ADDRESS.
          PAM     84/05/22     NVFARAP
 NA5A796  THIS CODE UPDATES THE COPYRIGHT INFORMATION IN THE NVF BANNER 
          AND IN THE NAM PL.
          PAM     84/05/22     TMSGNVF,CRCOM
NA5A797   NVF WAS ONLY CHECKING FOR PENDING A-A CONNECTION REQUESTS 
          IF AN APPLICATION FAILED.  IN THIS CASE THE APPL MERELY 
          NETTED OFF SO THAT NO CONNECTION TERMINATION PROCESSING 
          WAS DONE. 
  
          THIS FIX MOVES THE CHECK OUT SUCH THAT WHETHER AN APPLICATION 
          FAILS OR NETS OFF, THE BREAKING OF CONNECTIONS IS DONE. 
  
          DKE     84/06/06     NVFSNOF
 NA5A800  AIP SHOULD WAIT FOR XFR WORKLIST COMPLETION BIT IS SET
          BEFORE CONTINUE PROCESSING. 
          FIXING SEVERAL PROBLEM DURING X.25 JITTING WITH ROSEVILLE.
  
          LTN       84/05/17       NP$XFR,NP$XFER 
          YCY       84/06/01       NP$STTP,NP$BFET
  
 NA5A801  CORRECT DETAILED RIGHT DISPLAY TO ALLOCATE
          RIGHT DISPLAY BUFFER IF IT DOES NOT ALREADY 
          EXIST.
          MSG     84/05/30     KRIGHTD
 NA5A804  WHEN NVF DETECTED THAT THE PID WAS DISABLED 
          IT CORRECTLY REJECTED THE A-A CONNECTION REQUEST.  IN DOING 
          SO NVF FAILED TO DELETE AN ENTRY IN A TABLE.  ALL SUBSEQUENT
          CONNECTION REQUESTS WERE MAPPED INTO THE SAME ENTRY WHICH 
          RESULTED IN REJECTING THEM ALL EVEN AFTER THE PID WAS ENABLED.
  
          THIS FIX INSURES THAT THE ENTRY IS DELETED SO THAT WHEN THE 
          PID IS RE-ENABLED NVF WILL ALLOW CONNECTION ESTABLISHMENT.
  
          DKE     84/06/14     NVFAIAP
 NA5A806  NIP SHOULD ASSIGN CONNECTION NUMBER WITH SN LESS THAN DN
          FROM 1 UP, AND WITH SN GREATER THAN DN FROM 255 DOWN, 
          ACCORDING TO ISF HAS SPECIFIED. 
          THIS MOD SHOULD BE RUNNING WITH CCP BUILT WITH CC5A329. 
          LTN       84/06/05       HVLLCB 
  
 NA5A807  CHANGES FIELD DEFINITION FOR USER DATA LENGTH FROM
          A TWELVE BIT DATA ITEM TO AN EIGHT BIT DATA ITEM. 
          ALSO CHANGE THE DBZ AND ABL FIELDS IN THE INCALL AND
          OUTCALL BLOCKS BACK TO WHAT THEY WERE AT V2.2.
  
          THIS MODSET CAN ONLY BE APPLIED TO VERSION 2.3 NDLP/NVF.
  
          YCY     84/06/04     IBLCF,OBLCF,NDLP2LF
          DKE     84/06/11     NVFAIAP,NVFARAP
 NA5A809  NVF WOULD NOT RECOGNIZE THE FACILITY CODES IN THE INCALL BLOCK. 
          THIS HAPPENED BECAUSE NVF WAS NOT PICKING UP THE CORRECT FIELD
          IN THE INCALL BLOCK FOR THE NUMBER OF FACILITIES, AND NVF 
          ALWAYS THOUGHT THE NUMBER OF FACILITIES WAS ZERO.  TO FIX THIS, 
          CHANGE NVF TO PICK UP THE CORRECT FACILITY NUMBER FIELD IN THE
          INCALL BLOCK. 
          PAM     84/06/14     NVFARAP
 NA5A812   HPGET SHOULD NOT STORE ICT IN ABH BEFORE MAKING SURE THAT
           DATA IS O.K. TO BE SENT. 
           CHANGE ACTION IN HCSTTP TO SEND CR/CB/U WHEN CON/END/R IS
           RECEIVED, TO AVOID THE INCONSISTENCY OF NUMBERS OF ACTIVE
           CONNECTION IN NVF AND HOST SIDE OF NIP (CUURENTLY, NVF CLEANS
           UP CONNECTION WHEN RECEIVES CR/CB/U, AND NIP CLEANS UP 
           CONNECTION WHEN CON/END IS SENT BY APPLICATION.
  
           LTN      84/06/13       HALLOCN,HPGET
  
 NA5A815  PROBLEM - CON/ACRQ REASON CODES THAT NHP ISSUES DO NOT
                    CORRESPOND TO SAME CODES THAT LCN ISSUES. 
          ANALYSIS - NHP CON/ACRQ REASON CODES SHOULD BE CHANGED. 
          SOLUTION - NVF AND NAM HAVE BEEN CORRECTED TO USE NEW REASON
                     CODES IN THE CON/ACRQ/A SUPERVISORY MESSAGES TO
                     CORRESPOND TO WHAT LCN ISSUES. 
          EG     6/11/84    NVFAIAP, NVFARAP, NVFASPC, NVFATAC, NVFAVVP,
                            SMDEF, SMNVF, SMAPDEF. SMAPPL, QTRMNIT, 
                            QTGET 
          LTN    6/18/84    HVLLCB
  
 NA5A816  CHARACTER MODE TRANSLATION TABLE NOW USES FULL ASCII
          CODE SET INCLUDING THE 7TH BIT. NO FOLDING IS DONE
          TO THE PARITY BIT OF THE NETWORK8 CHARACTER.
          YCY        84/06/12        NX$CHAR,NP$N2D 
 NA5A818  ADD *ALTERNATE CATLIST* PARAMETER TO *DEFINE*.
          FIX *MODE* PROCESSING.
          RAM     84/05/22     MACREL,NS$NDF,NDF$NS 
 NA5A820  ADD CODE TO NVF TO SPECIAL CASE PTF, PTFS, QTF, AND QTFS
          WHEN NVF BUILDS THE AST TABLE.  THESE FOUR APPLICATIONS 
          WILL BE REMOVED FROM COMTNAP. 
          PAM     84/06/18     NVFIAST
 NA5A822  PROBLEM - PIP DID NOT PAUSE FOR STORAGE MOVE BEFORE IT
                    ISSUED RPP MONITOR FUNCTION, WHICH RESULTED 
                    IN A SYSTEM HUNG. 
          SOLUTION - PIP SUBROUTINE RLR HAS BEEN CHANGED TO ISSUE 
                     PRL MONITOR FUNCTION TO PAUSE FOR STORAGE
                     RELOCATION BEFORE ISSUEING RPP MONITOR 
                     FUNCTION.
          EG      6/25/84    PIP
 NA5A824  WHEN ACKNOWLEDGE QUEUE IS FULL, NPPCT SHOULD START BSN
          AT 0. 
          ALLOW INTRA-HOST CONNECTION TO HAVE DOWNLINE BLOCK
          WITH ACT 4. THIS SUPPORTS INTRA-HOST PRU FILE TRANFERRING.
          LTN       84/07/13       NPPCT,HPPUT
  
 NA5A826  NVF WAS NOT ENDING AN A-A CONNECTION WHEN THE INITIATING
          APPLICTION FAILED.  WHEN THE FC/INIT FINALLY CAME IN FROM 
          THE CALLED SIDE NVF WENT AHEAD AND SENT THE CR/SWH/R.  AS 
          A RESULT UPON RECEIVING THE CR/SWH/N NVF ABORTED. 
  
          THE SOLUTION WAS TO MOVE THE CHECK OUT FOR THE PENDING
          SWITCH STATE SUCH THAT THE CR/TRM/R WOULD BE SENT AND THE 
          CR/SWH/R WOULD BE PURGED FROM THE WAITING BLOCK QUEUE.
  
          DKE     84/07/03     NVFCCPA
NA5A827   CR/CB/U IS SENT TO NVF WHEN APPLICATION NETS OFF OR FAILS 
          BEFORE CON/END/R IS RECEIVED BY NIP.
          LTN       84/06/20       HCSTTP,XSTTP 
  
 NA5A829  THIS CODE FIXES TWO PROBLEMS: 
          1)  NVF ABORTED AFTER A NET/OFF/N SM WAS SENT.  THIS HAPPENED 
              BECAUSE NVF TRIED TO CLEAN UP THE AST ENTRY TWICE FOR THE 
              NETTED OFF APPL.  CHANGE NVF TO CALL NVFSCAD ONLY ONCE (VIA 
              NVFSFAI). 
          2)  FOUR APPLS WERE MISSING FROM THE AST.  THIS HAPPENED BECAUSE
              NVF DID NOT ALLOCATE ENOUGH SPACE FOR THE AST TO TAKE INTO
              ACCOUNT THE FOUR NEW APPLS, PTF, QTF, PTFS, AND QTFS.  CHANGE 
              NVF TO ALLOCATE ENOUGH AST SPACE FOR FOUR MORE ENTRIES. 
          PAM     84/06/21     NVFIAST,NVFSNOF
 NA5A831  FOR NETGTFL AND NETGETF, NWL$TA SHOULD NOT BE SET IF
          FRAGMENT ARRAY CAN BE FITED INTO NWL AREA.
          LTN       84/07/12       NP$GET 
  
 NA5A832  NVF WAS NOT COMPLETING THE RESPONSE TO A COMMAND SO 
          THAT ANY SUBSEQUENT COMMAND TYPE-INS WOULD NOT BE 
          HONORED.
  
          THE FIX WAS TO CAUSE NVF TO COMPLETE THE COMMAND REPONSE
          WHEN STATUS-ING ALL THE TERMINALS CONNECTED TO AN APPL
          THAT IS 1)REQUEST STARTABLE, 2)HAS MXCOPYS SET GREATER
          THAN ONE, AND 3)HAS NOT YET NETTED ON.
  
          DKE     84/07/06     NVFOPSS
 NA5A833  NVF WAS NOT DISTINGUISHING WHETHER OR NOT AN APPLICATION
          WAS DISABLED OR HAD REACHED MAXIMUM COPIES/CONNECTIONS. 
  
          THIS FIX CAUSES NVF TO SEND THE *BUSY* MESSAGE ONLY IF
          THE MAXIMUM LIMIT IS REACHED. 
  
          DKE     84/07/03     TXTANVF,NVFARAP,NVFASPC,NVFAVVD,NVFTDSP, 
                               NVFUCRS
 NA5A834   FIX DLFP TO INTEPRET NETLOG FOR FORMAT DATA. 
           LTN      84/07/03       DLSCAN 
  
 NA5A836  INTRODUCE NEW STATE IN HCSTTP TO HAVE CR/CB/U SENT TO 
          NVF WITH APPROPRIATE TRIGGERS.
          LTN       84/06/26       XSTTP
  
 NA5A843  PROBLEM - NVF RECEIVED ERR/LGL SM AND ABORTED IN DEBUG MODE.
          ANALYSIS - NVF RECEIVED AN ERR/LGL SM BECAUSE IT HAD SENT A 
                     CR/TRM SM WHEN IT WAS NOT SUPPOSE TO.  NVF HAD 
                     RECEIVED A CR/IAP SM FOLLOWED BY A NET/OFF SM
                     FOR THE SAME APPLICATION THAT INITIATED THE A-A
                     CONNECTION (I.E. TRIGGERED THE CR/IAP SM).  DUE
                     TO THE QUEUING DESIGN OF NVF, THE NET/OFF SM GOT 
                     PROCESSED FIRST BEFORE THE CR/IAP SM.  THIS
                     RESULTED IN NVF ISSUING THE CR/TRM SM.  NIP DID
                     NOT LIKE THE CR/TRM SINCE IT WAS EXPECTING A 
                     CR/IAP/N SM. 
          SOLUTION - THE PROCESSING OF THE QUEUES IN NVF HAVE BEEN
                     CHANGED SO THAT THE CR/IAP SM WILL BE PROCESSED
                     FIRST. 
          EG     7/3/84    TXINNVF
          EG:     84/07/03     TXINNVF
 NA5A844  PROBLEM - NIP ABORTED WITH STATE TABLE ERROR (STATE 1,
                    TRIGGER 2). 
          ANALYSIS - NIP ABORTED BECAUSE NVF HAD SENT A CR/SWH SM 
                     WHEN IT WAS NOT SUPPOSE TO.  NVF HAD CREATED 
                     A CR/SWH SM WHEN IT PROCESSED A CR/IAP SM. 
                     THE CR/SWH SM WAS SAVED IN THE WAITING BLOCK 
                     QUEUE.  THE APPLICATION THAT INITIATED THE 
                     A-A CONNECTION TERMINATED.  WHEN NVF PROCESSED 
                     THE NET/OFF SM FROM NIP, IT ADDED A CR/TRM SM
                     TO THE WAITING BLOCK QUEUE AND STARTED A 
                     TIMER.  WHEN THE TIMER EXPIRED, NVF EXTRACTED
                     A ENTRY IN THE WAITING BLOCK QUEUE FOR THAT
                     CONNECTION ASSUMING IT WAS THE CR/TRM SM.
          SOLUTION - NVF HAS BEEN CORRECTED TO REMOVE THE CR/SWH FROM 
                     THE WAITING BLOCK QUEUE IF IT QUEUES A CR/TRM SM.
          EG     7/3/84    NVFCCPA
          EG:     84/07/03     NVFCCPA
 NA5A846  MONITOR CALL ERROR -- DURING A-A CONNECTION ESTABLISH-
          MENT, APPLICATION THAT SENT CON/ACRQ/R FAILED AND AT THE
          SAME TIME LOGICAL LINKS WENT DOWN. BEFORE NIP SENDS 
          CON/ACRQ/A TO APPLICATION, IT CHECKS IF APPLICATION STILL 
          THERE OR NOT. 
          LTN       84/06/29       HCSTTP 
  
 NA5A848  DLFP SETS END TIME TO NETON TIME IF SPECIFIED ENDTIME IS
          LESS THAN NETON TIME. 
          LTN       84/07/11       DLSCAN,DLREP 
  
 NA5A853  PROBLEM - NVF DOES NOT ROLLOUT WHEN THERE IS NO DATA FOR IT.
          ANALYSIS - THE FORCED ROLLOUT FLAG AND THE COUNTER OF NUMBER
                     OF NULL NETGETS ALLOWED OVERLAP EACH OTHER.  ALSO
                     THE FORCED NETWAIT TIME IS TOO SMALL.
          SOLUTION - THE FORCED NETWAIT TIME HAS BEEN INCREMENTED AND 
                     THE FORCED ROLLOUT FLAG FIELD HAS BEEN CHANGED TO
                     NOT OVERLAP WITH THE NULL NETGET COUNTER.
          EG     07/15/84    TEXTSS 
 NA5A854  PROBLEM - PIP TIMED OUT A FILE TRANSFER FROM SVL TO ROSEVILLE.
          ANALYSIS - PIP UPDATES ITS TIMER ONLY WHEN IT RECEIVES A MSG, 
                     CMD, OR QMSG BLOCK FROM THE NETWORK.  FOR A FILE 
                     TRANSFER WITH NO CHECKMARKING, PIP WILL NOT RECEIVE
                     ANY OF THESE BLOCK TIMES UNTIL AFTER THE FILE IS 
                     COMPLETELY TRANSFERRED.  FOR A LARGE FILE, THIS
                     CAUSED PIP TO TIMEOUT THE FILE TRANSFER. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ALSO UPDATE ITS TIMER
                     WHEN IT RECEIVES A BACK BLOCK FROM THE NETWORK.
          EG     7/5/84      PIP
 NA5A857  PROBLEM - PIP PROCESSED NPU STATUS WORD THAT IT WAS SUPPOSE TO
                    IGNORE. 
          ANALYSIS - THE NPU THAT WROTE THE STATUS WORD WAS ON THE SAME 
                     CHANNEL AS THE PREVIOUS NPU THAT PIP HAD BEEN
                     COMMUNICATING WITH.  PIP DOES NOT READ UP AND
                     IGNORE THE NPU STATUS WORD IN THIS CASE. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ALWAYS READ UP AND IGNORE
                     THE NPU STATUS WORD IF IS LOADED WHEN PIP FIRST
                     COMMUNICATES WITH A NPU IRREGARDLESS OF WHETHER THE
                     NPU IS ON THE SAME CHANNEL OR A DIFFERENT ONE. 
          EG     07/05/84    PIP
 NA5A858  PIP MAY FAIL TO ACKNOWLEDGE INITIALIZATION REQUEST IN TIME. 
  
          PIP SENDS INITIALIZATION REQUEST ACKNOWLEDGEMENT PP ORDER 
          WORD ONE FULL CYCLE LATER AFTER IT RECEIVES INITIALIZATION
          REQUEST NPU STATUS WORD.
          SAM MAY HAVE TIMED OUT THE REQUEST WHEN PIP RESPONDS. 
  
          PIP WILL SENDS ACKNOWKEDGEMENT IMMEDIATELY AFTER IT SENSES
          THE REQUEST.
  
          SW     84/06/08    PIP
 NA5A859  LEVEL 7 HEADER FOR PRU A-A HAS INCORRECT CHARACTER COUNT. 
  
          LEVEL SEVEN HEADER FOR PRU A-A GENERATED BY PIP HAS THE 
          TEXT CHARACTER COUNT THAT INCLUDES THE HEADER ITSELF. 
          IT SHOULD BE MESSAGE TEXT CHARACTER COUNT.
  
          SW     84/05/29    PIP
 NA5A860  FIX CPU ERROR EXIT DUE TO ACNB POINTER NOT BEING SET
          CORRECTLY.
          LTN       84/07/06       HCSTTP 
  
 NA5A861  PROBLEM - PIP ABORTED NAM WITH PIP ERROR 034. 
          ANALYSIS - PIP RECEIVED TWO REG/CP RESPONSES FROM NIP.
                     NPREGCP SENT A REG/CP RESPONSE TO PIP WHEN 
                     IT THOUGH IT HAD CLEANED UP ALL THE LOGICAL
                     LINKS.  NPPCT ALSO SENT A REG/CP RESPONSE
                     WHEN IT HAD CLEANED UP ALL THE PRU CONNECTIONS 
                     AND RELEASED THE LAST LOGICAL LINK THROUGH 
                     THE DOWNED COUPLER.
          SOLUTION - NPREGCP HAS BEEN CORRECTED TO NOT SENT THE 
                     REG/CP RESPONSE IF IT HAD NOT CLEANED UP ALL 
                     LOGICAL LINKS. 
          EG     07/06/84    NPREGCP
 NA5A862  NVF ABORTS IF ON AN A-A CONNECTION THE REQUESTING APPL
          NETS OFF OR FAILS AT THE SAME TIME NVF SWITCHES THE CONNECTION
          TO THAT APPLICATION.
  
          THIS DELETES THE CODE TO ABORT IF A CR/SWH/N COMES IN AND 
          THERE IS NO PAAC ENTRY FOR IT.
  
          DKE     84/07/10     NVFASWN
 NA5A863  NVF ABORTED WHEN AN APPLICATION NETTED ON AT THE SAME 
          TIME AS THE TIMER FOR THAT SAME APPLICATION HAD EXPIRED.
          WHEN NVF WENT TO CANCEL THAT TIMER REQUEST IT ABORTED 
          WHEN IT COULD NOT FIND IT.
  
          THIS FIX CAUSES NVF TO MERELY IGNORE THE CASE WHERE THE 
          TIMER REQUEST COULD NOT BE FOUND. 
  
          DKE     84/07/10     NVFASPC
 NA5A866  THIS IDENT SETS CHECKMARK WINDOW SIZE TO BE ZERO IN THE 
          PRUON RERQUEST WHEN NO CHECKMARKING FACILITY IS USED. 
          WHEN PIP RETURN XFTIER WITH REASON CODE 2, AIP SENDS
          ES(E) AND GETS ER(E) TO COMPLETE THE ERROR EXIT PROTOCOLS.
          YCY     84/07/12     NP$STPR,NP$SMSG
 NA5A867  PROBLEM - NIP FAILED WITH I/O SEQUENCE ERROR ON FILE XXXX AT
                    YYYYYY. 
          ANALYSIS - NIP HAD ISSUED A RETURN CIO FUNCTION FOR AN A-A
                     FILE TRANSFER FILE.  1MS FOUND THE FTN BUSY AND
                     ABORTED NIP.  THE FNT WAS BUSY BECAUSE PIP HAD AN
                     CIO CALL OUTSTANDING TO WRITE DATA TO THE FILE.
                     BECAUSE OF A BLOCK PROTOCOL ERROR, PIP HAD DIRECTED
                     NIP TO TERMINATE THE A-A FILE TRANSFER.  IN DOING
                     SO, NIP ISSUED THE RETURN FUNCTION AFTER RECEIVING 
                     AN ACKNOWLEDGEMENT FROM PIP TO TERMINATE PRU 
                     PROCESSING.  PIP ACKNOWLEDGED THE TERMINATE PRU
                     WORKLIST WITHOUT CHECKING FOR OUTSTANDING CIO
                     CALLS. 
          SOLUTION - PIP HAS BEEN CORRECTED TO WAIT FOR ALL OUTSTANDING 
                     CIO REQUESTS TO BE PROCESSED BEFORE PROCESSING THE 
                     TERMINATE PRU TRANSFER WORKLIST FROM NIP.
          EG     07/15/84    PIP
 NA5A869  PROBLEM - NPU USERS GOT NO RESPONSE.
          ANALYSIS - AN A-A FILE TRANSFER HAD TERMINATED ABNORMALLY 
                     WHILE CCP STILL HAD A PRU BLOCK TO BE SENT UPLINE. 
                     BECAUSE PIP HAD NO MORE PRU BUFFERS, PIP REJECTED
                     THE UPLINE INPUT.  PIP THEN REQUESTED A PRU BUFFER.
                     HOWEVER, THE BUFFER GOT RELEASED BECAUSE PIP HAD 
                     NO MORE PRU CONNECTIONS.  WHEN CCP TRIED TO SEND 
                     THE PRU BLOCK UPLINE AGAIN, PIP AGAIN REJECTED IT
                     FOR THE SAME REASON. 
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT RELEASE PRU BUFFERS
                     BECAUSE IT HAS NO PRU CONNECTIONS.  ALSO, THE
                     COUNTER OF CYCLES WITH NO BUFFER OVERRUN HAS BEEN
                     CONVERTED TO A 2 SECOND TIMER. 
          EG     07/15/84    PIP
 NA5A870  ADD ITEM DEFINITIONS FOR THE OUTCALL PARAMETERS THAT MAY
          BE SUPPLIED BY AN APPLICATION ON THE CON/ACRQ AND CR/IAP
          SUPERVISORY MESSAGES.  ALSO, INCREASE THE MAXIMUM SIZE OF 
          THE SM BUFFER TO 100 WORDS. 
          PAM     84/07/16     SMAPPL,SMNVF,TXTSMCS,TXTAPSS,TXSMNVF,
                               TEXTSS,NVFAIAP 
 NA5A871  PROBLEM - PIP CALLS TOO MANY COPIES OF 1DL IN A BUSY SYSTEM.
          ANALYSIS - PIP DOES NOT ISSUE A PRIORITY REQUEST FOR 1DL. 
                     THE REPLY BYTE RETURNED WAS NONZERO, PIP ASSUMED 
                     1DL HAD BEEN LOADED INTO A PP, WHEN IT FACT, THE 
                     PP REQUEST HAD ONLY BEEN QUEUED.  PIP TIMED OUT
                     1DL AND THEN REISSUED THE REQUEST.  THIS OCCURRED
                     OVER AND OVER AGAIN UNTIL 1DL WAS FINALLY LOADED 
                     INTO A PP. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ISSUE A PRIORITY REQUEST 
                     FOR 1DL. 
          EG     07/15/84    PIP
 NA5A881  PROBLEM - FILE TRANSFERRED TO ANOTHER HOST VIA PTF AND NAM HAD
                    EXTRA EOF RECORD AT THE END.
          ANALYSIS - PIP WAS CONVERTING THE EOI FLAG INTO A WRITEF CIO
                     FUNCTION.
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT USE THE EOI FLAG TO
                     DETERMINE THE TYPE OF WRITE CIO CALL TO ISSUE. 
          EG     07/19/84    PIP
 NA5A883  PROBLEM - NVF ABORTED WITH THE MESSAGE "NVFDDNT - SM NOT
                    ROUTED".
          ANALYSIS - NVF RECEIVED A REPEAT CR/IAP/R AND A NET/OFF/R 
                     AT THE SAME TIME.  NVF PROCESSED THE NET/OFF/R 
                     SM FIRST, AND SENT OUT A CR/TRM.  NIP WAS
                     EXPECTING A CR/IAP/N, NOT A CR/TRM, AND SO NIP 
                     SENT AN ERR/LGL SM TO NVF. 
          SOLUTION - ADD CODE IN NVF TO NOT SEND OUT THE CR/TRM UNTIL 
                     AFTER THE CR/IAP/R SM HAS BEEN PROCESSED.  ALSO
                     ADD CODE TO NIP TO ACCEPT A CR/TRM BEFORE A
                     CR/IAP/N.
          PAM     84/08/13     NVFSNOF,NVFADQE,TXTANVF,NVFAIAP,NVFSFAI, 
                               NVFAFAI,STATTBL
 NA5A884  CS HAS FAILED AND THERE IS AN SM FOR IT.  NEIB1 DOES NOT CHECK
          IF THE CS/NS APPLICATION IS STILL THERE OR NOT.  NOW NEIB1
          CHECKS FOR THE APPLICATION BEFORE LINKING MESSAGE.
          LTN       84/07/24       NEIB1
  
 NA5A887  PROBLEM -  NIP DID NOT SWAPIN NVF AFTER NVF ISSUED A 3 SECOND 
                     FORCED NETWAIT.  NVF STAYED ROLLED OUT AND THE 
                     NUMBER OF MESSAGES QUEUED FOR NVF WAS CONSTANTLY 
                     GROWING. 
          ANALYSIS - NIP HAD PREVIOUSLY TRIED TO UPDATE AIP-S DATA
                     AVAILABLE WORD IN NVF.  IN RESPONSE TO THE SF.WRITE
                     SCP FUNCTION, NIP GOT A RETURN CODE 44 WHICH 
                     INDICATED NVF WAS SWAPPED OUT.  NIP THEN ISSUED A
                     SWAPIN FUNCTION FOR NVF.  BEFORE NIP PROCESSED THE 
                     SWAPIN COMPLETION, NIP GOT A NWL WORKLIST FROM NVF 
                     WITH A FORCED NETWAIT ENTRY.  NIP PROCESSED THE
                     FORCED NETWAIT ENTRY AND SWAPPED OUT NVF.  NIP 
                     FINALLY GOT AROUND TO PROCESSING THE SWAPIN
                     COMPLETION AND CLEARED THE SWAPPED OUT FLAG.  THIS 
                     CAUSED NIP TO NOT CHECK FOR THE EXPIRATION OF THE
                     NETWAIT TIME.
          SOLUTION - HHIR IN NIP HAS BEEN CORRECTED TO CHECK FOR A
                     SWAPIN REQUEST OUTSTANDING WHEN IT PROCESSES A NWL 
                     WORKLIST FROM AN APPLICATION.  IF THERE IS ONE,
                     NIP WILL GO INTO RECALL WAITING FOR THE SWAPIN 
                     TO COMPLETE.  IT WILL THEN CLEAR THE SWAPIN FLAGS
                     SO XSACB WILL NOT BE PROCESSING A SWAPIN 
                     COMPLETION.
          EG     08/15/84    HHIR 
 NA5A889  THIS IDENT GETS RID OF THE EXTRA EOF AT THE EOI OF THE
          FILE AT THE END OF A CHARACTER MODE FILE TRANSFER.
          YCY     84/07/25     NP$RECV
 NA5A891  PROBLEM - LOC2 AND LOC3 NPUS HAD PRU BLOCKS TO SENT TO THE
                    HOST.  PIP WAS REJECTING THESE PRU BLOCKS BECAUSE 
                    IT COULD NOT GET ANY MORE PRU BUFFERS FROM NIP.  NIP
                    WAS NOT ALLOCATING ANY MORE PRU BUFFERS BECAUSE NIP 
                    THOUGH IT HAD ALREADY ALLOCATED THE MAXIMUM NUMBER
                    ALLOWED.
          ANALYSIS - THE MAXIMUM ALLOWED WAS 4.  THE NIP DUMP SHOWED
                     4 PRU BUFFERS HAD BEEN ALLOCATED BUT ONLY ONE
                     ACTUALLY EXISTED.  THIS WAS DUE TO A BUG IN NIP
                     WHERE IT WOULD RELEASE PRU BUFFERS WITHOUT UPDATING
                     THE COUNTER OF NUMBER OF BUFFERS ALLOCATED.  THE 
                     REMAINING PRU BUFFER THAT DID APPEAR IN THE DUMP 
                     BELONGED TO NO ONE, I.E. NEITHER NIP NOR PIP HAD 
                     OWNERSHIP OF IT.  THIS WAS DUE TO A BUG IN PIP 
                     WHERE IT HAD DELINKED A BUFFER FROM ITS LIMBO
                     QUEUE AND THEN DETECTED AN ERROR WHILE IT WAS
                     INPUTING THE PRU BLOCK FROM CCP.  THIS RESULTED
                     IN PIP JUMPING INTO ERROR PROCESSING AND FORGETING 
                     ABOUT THE PRU BUFFER THAT IT HAD DELINKED. 
          SOLUTION - NPRLB IN NIP HAD BEEN CORRECTED TO UPDATE THE
                     COUNTER OF PRU BUFFERS ALLOCATED EVERY TIME IT 
                     RELEASES A PRU BUFFER.  IPD IN PIP HAS BEEN
                     CORRECTED TO DELINK THE PRU BUFFER FROM ITS LIMBO
                     CHAIN ONLY IF IT SUCCESSFULLY INPUTS THE PRU 
                     BLOCK FROM CCP.
          EG     07/25/84    PIP,NPRLB
 NA5A894  PROBLEM  - NVF WAS SELECTING AN OUTCALL TO A PID IF THE 
                     CON/ACRQ/R ONLY HAD THE LID SPECIFIED AND IF 
                     THAT LID WAS DEFINED AS STORE-AND-FORWARD FOR
                     THE PID. 
          ANALYSIS - NVF WAS CHECKING FOR THE STORE-AND-FORWARD 
                     ATTRIBUTE ON SECOND AND SUBSEQUENT PIDS, BUT NOT 
                     ON THE FIRST PID, IF ONLY THE LID WAS SPECIFIED. 
          SOLUTION - IF ONLY THE LID IS SPECIFIED IN THE CON/ACRQ/R,
                     NVF WILL CHECK FOR THE STORE-AND-FORWARD ATTRIBUTE 
                     ON ALL PIDS. 
          PAM     84/08/14     TEXTNVF,NVFAIAP
 NA5A895  A PRU APPLICATION FAILURE FOLLOWED BY A LLINK FAILURE,
          HOST SIDE CONNECTION BLOCK NEVER GOT RELEASED WHILE ACB AND 
          ACNT ASSOCIATED ARE GONE. WHEN GARBAGE COLLECTION MOVES THIS
          ACNB, IT CAUSES CPU ERROR EXIT. 
          SOLUTION: WHEN LLINK TRIGGER COMES TO HCSTTP, CR/RCN/R WILL BE
          SENT TO NVF FOLLOWED BY CR/CB/U ( ASSUMINGLY, NVF WILL IGNORE 
          THIS SM).  WHEN NVF RESPONDS WITH CR/TRM/R (FOR A-A CONN), NIP
          WILL CLEAN UP THE ACNB. 
          LTN     84/08/07     STATTBL,STBLDEF,XSTTP,HCSTTP 
 NA5A896  THIS IDENT CHANGES NAM NETXFR REASON CODE 15, 16 AND 17 
          TO 21, 22 AND 23 RESPECTIVELY.
          IT ALSO REMOVES SETTING ACN IN THE DAYFILE MESSAGE AND
          FOR A DEBUG SYSTEM, IT OUTPUTS DAYFILE MESSAGE TO BOTH
          USER DAYFILE AND B DISPLAY WHEREAS FOR A NONDEBUG 
          SYSTEM IT OUTPUTS DAYFILE MESSAGE TO B DISPLAY ONLY.
          YCY     84/08/03     COM$XRC,NX$ACBX,NX$MSG,NETXFR,NP$XCMP
 NA5A898  NIP ASSIGNS REASON CODE IN NET/ON/A TO BE 1 WHEN BLDACB FINDS 
          DUPLICATE NAME IN AT. 
          LTN       84/08/16       HPNON
  
 NA5A904  PROBLEM - AIP PROCESSED A STOP MSG FROM MFLINK THAT WAS 
                    INTENDED FOR PTFS TO PROCESS.  THIS RESULTED IN 
                    AIP GENERATING AN ILLEGAL TRIGGER DAYFILE MESSAGE 
                    AND THE FILE TRANSFER TO BE ABORTED.
          ANALYSIS - DUE TO A TIMING PROBLEM IN AIP, AIP DID NOT PROCESS
                     A FC/ACK SUPERVISORY MESSAGE THAT WAS QUEUED FOR 
                     IT.  PROCESSING THE FC/ACK WOULD HAVE CAUSED AIP 
                     TO COMPLETE PROCESSING THE NETXFER CALL AND RETURN 
                     CONTROL BACK TO PTFS.  PTFS WOULD HAVE THEN
                     RECEIVED THE STOP MSG INSTEAD OF AIP.
          SOLUTION - NETXFRC HAS BEEN CORRECTED TO NOT ISSUE A NETGETL
                     UNLESS THE DATA AVAILABLE FLAG IS SET AND THE
                     SUPERVISORY MESSAGE AVAILABLE FLAG IS CLEARED. 
          EG     07/31/84    NETXFRC,NETXFR 
 NA5A913  IF DURING A-A CONNECTION ESTABLISHMENT, AFTER TIMEOUT HAS 
          REACHED, CON/CB/U WILL BE SENT TO NVF OR FC/INACT/SM WILL 
          BE SENT TO APPLICATION. 
          LTN       84/08/08       XSTTP,XCHKPCR
  
 NA5A914  PROBLEM - RBF ABORTED WHEN IT RECEIVED A NONZERO RETURN CODE
                    FROM DSP WHEN IT TRIED TO ROUTE A JOB TO THE INPUT
                    QUEUE.
          ANALYSIS - DSP RETURNED A NONZERO RETURN CODE TO RBF BECAUSE
                     THE INPUT JOB WAS EMPTY.  NO DATA HAD BEEN WRITTEN 
                     TO THE FILE. THIS WAS BECAUSE
                     PIP HAD ISSUED A CIO WRITE FUNCTION FOR
                     LESS THAN ONE PRU OF DATA. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ISSUE A WRITER CIO 
                     FUNCTION IF EOI HAS BEEN DETECTED FOR THE INPUT
                     FILE AND IT IS NOT AN APP-APP CONNECTION.
          EG     08/08/84    PIP
 NA5A922  PROBLEM - PIP DETECTED A BLOCK PROTOCOL ERROR 90. 
          ANALYSIS - THE CONNECTION WAS IN STREAM STATE 19.  PIP
                     RECEIVED A BACK FROM CCP FOR THE FT/ON SUP 
                     MSG.  THIS WAS TREATED AS AN BLOCK PROTOCOL
                     ERROR BECAUSE PIP WAS NOT EXPECTING THE BACK 
                     FOR THE FT/ON SUP MSG. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ACCEPT A BACK WHEN 
                     IN STATE 19. 
          EG     08/09/84    PIP
 NA5A924  NAMI DOES NOT ROUTE CORRECTLY JOBS WHICH GET
          NON-OWNED QUEUE FILES.
  
          SOME JOBS, OTHER THAN SUBSYSTEMS (E.G. PSU, QTF), 
          MUST GET NON-OWNED QUEUE FILES.  NAMI MUST ROUTE
          THESE JOBS SO THIS CAN BE ACCOMPLISHED. 
  
          SET OWNER USER NAME IN DSP CALL BLOCK TO
          SYSTEMX FOR SYOT JOBS AS WELL AS SUBSYSTEMS.
  
          RWH            8/13/84        NMI=RTE 
  
 NA5A905  PROBLEM - AIP TIMED OUT FILE TRANSFER WAITING FOR FC/ACK SUP
                    MSG.
          ANALYSIS - THE NIP TRACE FILE SHOWED NIP RECEIVED THE BACK. 
                     HOWEVER, NEITHER THE AIP TRACE NOR THE GETSM DEBUG 
                     BUFFER IN NIP SHOWED A FC/ACK SUP MSG DELIVERED
                     TO AIP.  ANALYSIS OF THE NIP CODE WHICH CONVERTS 
                     THE NCNB BACK INTO A PCNB EXPOSED A BUG WHICH
                     COULD CAUSE THIS CONDITION.  NIP COPIES THE
                     OUTSTANDING BACK COUNT FROM THE NCNT ENTRY BEFORE
                     INTERLOCKING PIP.  THIS MEANS THAT THERE IS A
                     WINDOW WHERE IF PIP PROCESSES A BACK FOR THAT
                     CONNECTION AFTER NIP HAS COPIED THE OUTSTANDING
                     BACK COUNT, NIP WILL CREATE AN ACKNOWLEDGE QUEUE 
                     TABLE WITH A BAD IN POINTER.  THIS WILL CAUSE
                     NIP TO DISCARD A BACK INTENDED FOR AIP.
          SOLUTION - NPPCT HAS BEEN CORRECTED TO REQUEST THE NIP/PIP
                     INTERLOCK BEFORE IT CREATES THE ACKNOWLEDGE QUEUE
                     TABLE. 
          EG     08/05/84    NPPCT
 NA5A908  NIP WILL IGNORE LOGICAL LINK FAILURE TRIGGER RIGHT AFTER
          PIP BROKE PRU CONNECTION WITH PWL OP = 6. 
          LTN       08/06/84       XSTTP
  
 NA5A909  PROBLEM - AIP TIMED OUT FILE TRANSFER WAITING FOR FC/ACK SUP
                    MSG.
          ANALYSIS - NIP HAD DISCARDED THE BACK THAT WAS TO GENERATE THE
                     FC/ACK SUP MSG.  THIS WAS BECAUSE NIP THOUGHT THE
                     BACK WAS FOR A BLOCK THAT PIP HAD SENT TO CCP. 
                     THE BACK FOR THE BLOCK THAT PIP HAD SENT TO CCP
                     HAD BEEN DISCARDED BY THE PIP AT THE OTHER HOST. 
                     PIP AT THE OTHER HOST DISCARDED THE BACK BECAUSE 
                     THE BACK WAS IN THE IVT OUTBOUND CHAIN AND THE 
                     CONNECTION WAS A PRU CONNECTION.  WHEN AN IVT
                     CONNECTION BECOMES A PRU CONNECTION, PIP ASSUMES 
                     RESPONSIBILITY FOR ALL NETWORK TRAFFIC ON THAT 
                     CONNECTION AND REJECTS ANY DOWNLINE NETWORK
                     TRAFFIC NOT GENERATED BY ITSELF.  NIP HAD QUEUED 
                     THE BACK IN THE IVT OUTBOUND CHAIN BEFORE THE
                     CONNECTION HAD BEEN SWITCHED TO A PRU CONNECTION.
                     HOWEVER, PIP DID NOT PROCESS THIS ENTRY IN THE 
                     IVT OUTBOUND CHAIN UNTIL AFTER THE CONNECTION WAS
                     SWITCHED INTO A PRU CONNECTION.
          SOLUTION - NIP HAS BEEN CORRECTED TO CREATE A NEW DATA
                     STRUCTURE WHEN IT PROCESSES A PRU/ON SUP MSG.  THE 
                     NEW DATA STRUTURE WILL BE A PCNB WITH A NEW BLOCK
                     ID.  AT THE SAME TIME NIP WILL ALSO CREATE A NEW 
                     DOWNLINE BLOCK AND QUEUE IT TO THE IVT OUTBOUND
                     CHAIN.  WHEN NIP RELEASES THE PROCESSED IVT
                     OUTBOUND CHAIN ENTRIES, IT WILL CHECK FOR THIS 
                     NEW DOWNLINE BLOCK.  IF IT IS ONE, THEN THE
                     NEW DATA STRUCTURE WILL BE CONVERTED INTO A
                     PCNB.  PIP HAS BEEN CORRECTED TO ACCEPT THIS 
                     NEW DOWNLINE BLOCK TYPE IN THE IVT OUTBOUND
                     CHAIN AND BYPASS IT.  PIP HAS ALSO BEEN CORRECTED
                     TO ACCEPT THE NEW DATA STRUCTURE IN THE PRU
                     CONNECTION RING AND IGNORE IT THERE ALSO.
          EG     08/14/84    PIP
          LTN    08/14/84    HPRUON, XEXEC, MISDEF, HPPUT, MGBGCLT, 
                             NCSTTP, NPPWL, HPRUSM
 NA5A929  PROBLEM  - NIP ABORTED WITH ERROR MESSAGE NIP/SCP ERROR 
                     RC=63B,JOBID= .
          ANALYSIS - THE APPLICATION APPL119 HAD FAILED AND NIP WAS 
                     WAITING FOR A FAIL/APPL/N RESPONSE FROM NVF. 
                     NIP RECEIVED A CR/IAP/A FROM NVF AND QUEUED A
                     CON/ACRQ/A FOR THE APPLICATION.  WHEN IT DOES
                     THIS, IT CALLS OSCHAPP TO SWAPIN THE FAILED
                     APPLICATION.  THE SWAPIN REQUEST RECEIVED A
                     SCP RC=63B FROM NOS. 
          SOLUTION - OSCHAPP HAS BEN
                     A SCP SWAPIN FUNCTION IF THE APPLICATION HAS 
                     FAILED OR NETTED OFF.
          EG     08/20/84    OSCHAPP
 NA5A931   NIP SHOLUD RETURN FILE BACK TO APPLICATION WHEN CON/CB/U 
           IS SENT TO APPLICATION.
           LTN      84/08/16       NPPCT
  
 NA5A933  AIP ABORTED WITH RC=45 WHEN THE APPL NETTED OFF IF THE
          NETXFR FAILED.
          NETXFR ONLY UPDATES THE NUMBER OF XFR CONNECTIONS WHEN
          EVERY VALIDATION IS O.K.
          LTN        84/08/17        NETXFR 
  
 NA5A934  NDLP SHOULD NOT ENCODE UBZ THAT THE USER SPECIFIES ON 
          INCALL AND OUTCALL STATEMENTS AS MULTIPLES OF 100 SINCE 
          WHAT THE USER SPECIFIES IS ALREADY A MULTIPLE OF 100. 
          YCY     84/08/20     NDLP2LF,NDLLIST,NDLCKRG
 NA5A939   PROBLEM - MFLINK CONNECTION SITS IN AIP AND DOES NOTHING.
           THIS PROBLEM WAS INTRODUCED BY NA5A909, WHEN THERE IS ONLY ONE 
           BUFFER IN THE PIP OUTBOUND CHAIN, AND THIS BUFFER HAS THE
           SPECIAL BUFFER ID, THEN THE CONNECTION WILL NOT BE FULLY 
           CONVERTED TO PCNB UNTIL THERE IS ANOTHR OUTBOUND BUFFER LINKED 
           IN.
           LTN      84/08/20       XEXEC
  
 NA50133  NVF WAS STAYING AT A CONTROL POINT BECAUSE A LINE HAD 
          DATA QUEUED ON IT AND LIST WAS TEMPORARILY OFF ON THAT
          CONNECTION.  FURTHER MORE BECAUSE OF CERTAIN CONDITIONS 
          MESSAGES WERE NOT BEING ACK-ED BY THE NPU SO THE LINE WAS 
          NEVER BE DISCONNECTED BY NVF BECAUSE THE OUTSTANDING BLOCK
          COUNT WOULD NEVER GO TO ZERO.  NVF WOULD BE STUCK AT A
          CONTROL POINT FOREVER.
  
          THIS MODSET ADDS CODE TO ADD AN ADDITIONAL TIMER SO THAT IF 
          THE OUTSTANDING BLOCK COUNT NEVER WENT TO ZERO THE CONNECTION 
          WOULD BE BROKEN ANY WAY.
  
          DKE     84/06/11     TEXTNVF,NVFCCPA,NVFCUFS
 NA50138  CS REPORTS CPU THRESHOLD AT ONE TENTH THE SPECIFIED LEVEL 
  
          PROBLEM - CS IS SENDING ALM/OP MESSAGES INDICATING THAT AN
                    NPU HAS EXCEEDED ITS CPU UTILIZATION THRESHOLD
                    EVEN THOUGH IT HAS NOT. THIS IS DUE TO THE FACT 
                    THAT THE NPU REPORTS ITS CPU LOAD IN UNITS OF 
                    TENTHS OF A PERCENT, BUT CS IS NOT TAKING THIS
                    INTO ACCOUNT WHEN CHECKING THE REPORTED VALUE 
                    AGAINST THE THRESHOLD IN UNITS OF PERCENT FROM
                    THE CS CONTROL STATEMENT. 
  
          SOLUTION- MULTIPLY THE THRESHOLD OBTAINED FROM THE CONTROL
                    STATEMENT BY TEN BEFORE COMPARING IT TO THE VALUE 
                    REPORTED BY THE NPU.
  
          RAC                84/05/24              CSESES 
  
 NA50210  THIS IDENT FIXES THE PROBLEM THAT NDLLIST WAS 
          NOT CORRECTLY SEARCHING FOR THE BEGINNING OF THE LINE 
          CONFIGURATION TABLE.
          THE LINELST PROCEDURE IN NDLLIST IS NOW CHANGED TO
          ONE THAT LOCATES THE BEGINNING OF THE NODE TABLE
          AND FROM THAT POINT IT SKIPS FIVE TABLES PRECEDING
          THE LINE CONFIGURATION TABLE USING THE ENTRY COUNT OF 
          EACH TABLE TO ADVANCE THROUGH THE NCB.
          YCY     84/06/25     NDLLIST
 NA50212  LLCBWOF FLAG SHOULD BE CLEARED IN NPREGLL ONLY WHEN NO MORE 
          PRU CONNECTIONS ASSOCIATED WITH THIS LLINK ARE OUTSTANDING. 
          LTN       84/07/18       NPREGLL
  
 NA50215  NDLP SHOULD ALLOW CSET=ASCII AND TC=X364/752
          TO COEXIST. 
          YCY     84/07/09     NDLNFCM
 NA50241  PROBLEM  - PASSIVE DEVICES DEFINED WITH ALL MANDATORY 
                     AUTO-LOGIN PARAMETERS AND AUTO-CONNECT ARE 
                     DISCONNECTED IF THE MANDATORY APPLICATION IS 
                     NOT PRESENT AT INITIAL LOGIN TIME, OR FAILS
                     AFTER A CONNECTION HAS ALREADY BEEN ESTABLISHED. 
          ANALYSIS - CCP CLEARS THE AUTOCON FLAG UNDER CERTAIN
                     CONDITIONS, AND ONCE THIS HAPPENS, THE DEVICE
                     WILL NEVER BE RECONNECTED UNLESS THE LINE IS 
                     DISABLED AND RE-ENABLED, OR UNLESS THE NETWORK 
                     IS RESTARTED.
          SOLUTION - IF, ON AN INITIAL CONNECTION REQUEST, THE SWITCH 
                     TO THE APPLICATION CANNOT BE MADE, OR IF THE 
                     APPLICATION SHOULD FAIL AFTER THE CONNECTION IS
                     SWITCHED, NVF SHOULD CHECK IF THIS IS A CONSOLE
                     DEVICE TYPE WITH ALL MANDATORY LOGIN PARAMETERS
                     AND IF SO, SHOULD START A 30-SECOND TIMER AFTER
                     WHICH TIME ANOTHER SWITCH SHOULD BE ATTEMPTED. 
          PAM     84/08/21     NVFTCRN,NVFTDAD,NVFTINA,TXTANVF,NVFTRVD, 
                               NVFTRCN
 NA5A942  PROBLEM -  PIP TERMINATED PRU FILE TRANSFER WITH BLOCK
                     PROTOCOL ERROR 91. 
          ANALYSIS - PIP WAS TOLD TO EXPECT A 1 PRU BLOCK FROM CCP.  THE
                     BLOCK RECEIVED WAS ACTUALLY LARGER THAN 1 PRU.  CCP
                     CALCULATED THE BLOCK SIZE BASED ON THE VALUE OF THE
                     TRANSPARENT BIT IN THE DBC.  SINCE PIP DOES NOT SET
                     THIS BIT FOR PRU FILE TRANSFERS, CCP CALCULATED THE
                     WRONG SIZE.
          SOLUTION - PIP HAS BEEN CORRECTED TO SET THE TRANSPARENT BIT
                     IN THE DBC FOR ALL FILE TRANSFERS. 
          EG     08/30/84    PIP
 NA5A946  IF NIP GETS NCSTTP STATE TABLE ERROR IN NON-DEBUG SYSTEM, THIS
          A-A CONNECTION WILL BE HUNG IN PRU MODE, AND LOGICAL LINK 
          WILL NEVER BE RELEASED. 
          LTN       84/08/28       XSTTP
  
 NA5A947  THIS IDENT MAKES SURE THAT WHENEVER A TIMEOUT 
          TRIGGER IS GENERATED FOR PRU OR CHARACTER MODE
          SENDER AND RECEIVER,NETXFR WILL GENERATE
          DAYFILE MESSAGE "TIMEOUT WAITING FOR NETWORKING"
          AND RETURN CONTROL TO MFLINK OR QTF.
          YCY     84/08/29     NP$STTP
 NA5A953  PROBLEM  - REMOTE BATCH INPUT JOB ABORTED WITH INVALID USER 
                     NAME/PASSWORD. 
          ANALYSIS - PIP HAD RECEIVED A SHORT PRU FROM CCP FOR THE JOB
                    R 
                     THE SHORT PRU TO DISK.  SINCE IT WAS A SHORT PRU 
                     NOTHING GOT WRITTEN TO DISK. 
          SOLUTION - IPD IN PIP HAS BEEN CORRECTED TO USE A WRITER CIO
                     FUNCTION IF IT IS A SHORT PRU THAT WAS RECEIVED
                     FROM CCP.
          EG     08/30/84    PIP
 NA5A955  PROBLEM  - NVF ABORTED WITH THE MESSAGE "NVFTURT - CANNOT 
                     FIND RAU ENTRY". 
          ANALYSIS - A RAU TABLE ENTRY ONLY EXISTS FOR INTERACTIVE
                     DEVICES.  NIP SENT NVF A CR/CB WITH A DEVICE 
                     TYPE OF 0 (CONSOLE DEVICE) WHEN IT WAS ACTUALLY
                     A PASSIVE DEVICE.
          SOLUTION - CHANGE NVF TO NOT ABORT WHEN THIS CONDITION OCCURS.
                     A CHANGE TO NIP WILL HAVE TO BE MADE (LATER) TO
                     FIX THE ORIGINAL CAUSE OF THE ABORT. 
                     THIS CODE ALSO DELETES THE "NVFUCRS" MESSAGE.
          PAM     84/08/31     NVFUCRS,NVFTURT
 NA5A956  PROBLEM  - NVF ABORTS WITH THE MESSAGE "NVFDDNT - SM NOT
                     ROUTED". 
          ANALYSIS - AN ERR/LGL WAS SENT TO NVF BECAUSE NVF SENT
                     NIP A FC/INIT/N SM AFTER THE CONNECTION WAS
                     TERMINATED.
          SOLUTION - NVF WILL CHECK IF THE CONNECTION HAS BEEN
                     TERMINATED BEFORE SENDING OUT THE FC/INIT/N. 
                     THE REAL PROBLEM IS THAT NVF TERMINATED THE
                     CONNECTION BEFORE THE FC/INIT/N WAS SENT OUT.
                     THIS PROBLEM IS STILL BEING ANALYZED AND WILL
                     BE ANSWERED BY PSR NA5A923.  MEANWHILE, THIS 
                     CODE SHOULD PREVENT THE PROBLEM FROM OCCURING. 
          PAM     84/08/31     NVFCUFS
 NA5A911  PROBLEM -  NIP CPU USAGE HAS INCREASED OVER 50 PER CENT 
                     BETWEEN THE NOS 2.2 (7R11) AND NOS 2.3 (9RK) 
                     SYSTEMS WHEN THE TRIVIAL PERFORMANCE TEST IS RUN.
          ANALYSIS - NIP IS NOT GOING INTO RECALL AS OFTEN AS IT DID IN 
                     THE 2.2 SYSTEM.  ALSO THE 2.3 NIP CODE SHOULD HAVE 
                     CAUSED SOME INCREASE IN NIP-S CPU UTILIZATION. 
          SOLUTION - XEXEC IN NIP HAS BEEN MODIFIED TO INCORPORATE A
                     LOOP TO GO INTO RECALL WHEN IT HAS NOTHING TO DO.
          EG     06/05/84    NEIB, XEXEC
 NA5A962   PIP ERROR 42 DUE TO BLOCK HANDLERS STATE AND BATCH STREAM
           STATE BEING SET AFTER PCNB GETS FULLY CONVERTED TO PCNB. 
           LTN      84/09/05       XEXEC
  
 NA5A967  RESPONSE LOCATION FOR NETXFR WORKLIST IS NHDR+1, AIP
          SHOULD CHECK FOR COMPLETION BIT AT THIS LOCATION. 
          LTN       84/09/12       NP$XFER
  
 NA5A971  PROBLEM  - THE DEBUG VERSION OF NVF ABORTED WHEN IT COULD NOT 
                     COMPLETE PROCESSING OF A CR/CB SUP MSG.
          ANALYSIS - NVF DID NOT LIKE THE CR/CB SUP MSG BECAUSE THE 
                     CONNECTION WAS FOR A BATCH DEVICE AND THE DEVICE 
                     TYPE FIELD IN THE SUP MSG WAS ZERO.  NIP GETS THE
                     THE DEVICE TYPE FROM THE ACNB.  THE DEVICE TYPE
                     IS COPIED TO THE ACNB FROM THE NCNB WHEN A 
                     CONNECTION IS TERMINATED.  HOWEVER, IF THE NCNB IS 
                     NOT A NCNB, I.E. IT IS STILL A PCNB, THE DEVICE
                     TYPE IS NOT COPIED.  THIS CAUSED NIP TO GENERATE 
                     A CR/CB WITH THE DEVICE TYPE SET TO ZERO.
          SOLUTION - NIP HAS BEEN CORRECTED TO STORE THE DEVICE TYPE IN 
                     THE ACNB WHEN THE CONNECTION IS CREATED AND NOT
                     TO RELY ON PICKING UP THE VALUE FROM THE NCNB. 
          EG     09/07/84    UPDACNB, BLDACNB, HCRACCU, HCRRCNR, ACNB,
                             HCSTTP, NCSTTP, NPPCT, HTCHAR, NVFTURT 
 NA5A931  NIP MONITOR CALL ERROR DUE TO NIP SETTING UP SSTP BLOCK WITH
          PCNBFNT[0] INSTEAD OF WITH PCNBFNTO[0]; FNT[0] IS FOR PIP'S 
          USAGE, AND FNTO IS FOR NIP'S. THIS ONLY HAPPENS WHEN NIP
          HAS GIVEN CONTROL OF THE FILE TO PIP AND PIP HAS NOT
          PROCESSED THE FILE YET. 
          LTN       84/09/10       NPPCT
  
 NA5A981  PROBLEM  - NIP FAILED WITH MONITOR CALL ERROR ON SSF FUNCTION.
          ANALYSIS - HWRAVAL IN NIP WAS ISSUING A SF.WRITE SCP FUNCTION 
                     TO UPDATE THE DATA AVAILABLE WORD IN AIP-S MEMORY
                     BECAUSE OF A NEW UPLINE SUPERVISORY MESSAGE THAT 
                     HAD JUST BEEN RECEIVED.  NOS FOUND THAT THE
                     COMPLETION BIT WAS ALREADY SET IN THE SCP FUNCTION 
                     WORD.  NIP HAD PREVIOUSLY ISSUED A SF.SWPI SCP 
                     FUNCTION WHICH USES THE SAME BUFFER SPACE AS 
                     THE SF.WRITE SCP FUNCTION.  THE SF.SWPI WAS THE
                     RESULT OF A PREVIOUS ATTEMPT BY HWRAVAL TO UPDATE
                     THE DATA AVAILABLE WORD IN AIP-S MEMORY BECAUSE OF 
                     A UPLINE DATA BLOCK THAT HAD BEEN RECEIVED.  THE 
                     PREVIOUS SF.WRITE SCP FUNCTION HAD RESULTED IN A 
                     NONZERO REASON CODE INDICATING THE APPLICATION WAS 
                     SWAPPED OUT.  THUS THE SWAPIN SCP FUNCTION WAS 
                     ISSUED.  THE COMPLETION BIT HAD BEEN SET FOR THE 
                     COMPLETION OF THE SWAPIN FUNCTION. 
          SOLUTION - HWRAVAL HAS BEEN CORRECTED TO CHECK FOR A PREVIOUS 
                     SF.SWPI FUNCTION THAT HAD BEEN ISSUED DUE TO A 
                     PREVIOUS SF.WRITE FUNCTION ISSUED BY HWRAVAL AND 
                     IN THIS CASE, NOT ISSUE ANOTHER SF.SWRITE FUNCTION.
          EG     09/10/84    HWRAVAL
 NA5A982  NIP WILL PUT OUT "NIP/REGLL  DN= XX  SN= YY  RL= Z" 
          WHEN SUCH NPU CHANGES ITS REGULATION LEVEL. 
          LTN       84/09/12       NPREGLL
  
 NA5A983  BUILD SPECIAL OUT-BOUND BUFFER FOR PRU CONNECTION ONLY
          WHEN THERE IS NCNB. 
          LTN       84/09/12       HPPUT
  
 NA5A985  THIS MOD PULLS THE CODE FROM NVF THAT SENDS OUT A CLEAR 
          SCREEN FORMAT EFFECTOR WHEN A TERMINAL USER LOGS OUT. 
          THIS CODE WAS PULLED IN ORDER TO HELP CLEAR UP CCP
          REGULATION PROBLEMS.
          PAM     84/09/12     NA5A985
 NA5A998  PROBLEM  - NIP WAS ABORTED BY NOS FOR A MONITOR CALL ERROR
                     WHEN IT ISSUED A SYSTEM CONTROL POINT SF.WRITE 
                     FUNCTION.
          ANALYSIS - THE APPLICATION WAS SWAPPED OUT DUE TO A NETWAIT 
                     REQUEST.  NIP ISSUED A SST SYSTEM CONTROL POINT
                     FUNCTION TO TRANSFER THE FILE.  THE SST REQUEST
                     RESULTED IN A RC=2 WHICH TRIGGERED NIP TO ISSUE
                     A SYSTEM CONTROL POINT SF.SWPI FUNCTION FOR THE
                     APPLICATION.  A DATA MESSAGE THEN BECAME 
                     AVAILABLE FOR THE APPLICATION.  HWRAVAL WAS
                     CALLED TO UPDATE THE DATA AVAILABLE WORD IN AIP. 
                     HWRAVAL DETECTED THAT THE SWAPIN REQUEST WAS 
                     OUTSTANDING AND SET THE UPDATE-DATA-AVAILABLE
                     WORD FLAG.  A SUPERVISORY MESSAGE THEN BECAME
                     AVAILABLE FOR THE APPLICATION.  HWRAVAL NOW
                     SAW THAT THE UPDATE-DATA-AVAILABLE FLAG WAS
                     SET AND ISSUED THE SYSTEM CONTROL POINT FUNCTION 
                     SF.WRITE FUNCTION TO UPDATE THE DATA AVAILABLE 
                     WORD IN AIP.  THIS RESULTED IN A MONITOR CALL
                     ERROR BECAUSE THE SYSTEM CONTROL POINT SF.SWPI 
                     FUNCTION HAD NOT COMPLETED YET.
          SOLUTION - HWRAVAL HAS BEEN CORRECTED TO NOT ISSUE SYSTEM 
                     CONTROL POINT SF.WRITE FUNCTION WHEN SYSTEM
                     CONTROL POINT SF.SWPI FUNCTION HAS NOT COMPLETED.
          EG     09/16/84    HCSTTP, HWRAVAL
 NA5B001  PROBLEM  - NIP FAILED WITH THE FOLLOWING MESSAGE -
                     NIP/HCSTTP ERR  AN=  8,CN=  1, 6,14. 
          ANALYSIS - THE A-A CONNECTION WAS IN STATE 13 
                     AND THE APPLICATION TERMINATED THE 
                     CONNECTION.  THE A-A CONNECTION WAS
                     THEN CHANGED TO STATE 14 WHILE NIP 
                     WAITED FOR PIP TO ACKNOWLEDGE THE
                     CONNECTION TERMINATION.  THE 
                     APPLICATION NETTED OFF BEFORE THIS 
                     OCCURRED.  THIS CAUSED A HOST-SIDE 
                     CONNECTION STATE TABLE ERROR.
          SOLUTION - XSTTP IN NIP HAS BEEN CORRECTED TO 
                     IGNORE THE NETTED OFF OR FAILED APP
                     TRIGGER WHILE THE CONNECTION IS IN 
                     STATE 14.
          EG     09/16/84    STATTBL
 NA5B004  PROBLEM  - QTF HANGS WAITING FOR CON/ACRQ RESPONSE. 
          ANALYSIS - AFTER NVF VALIDATES THE A-A CONNECTION, NIP PUTS 
                     THE CONNECTION IN STATE 4.  IF THE NETWORK SHOULD
                     THEN TERMINATE THE CONNECTION, THE CONNECTION IS 
                     PUT IN STATE 8.  WHEN NVF RESPONDS TO THE CR/CB
                     SUP MSG WITH A CR/TRM SUP MSG, NIP ONLY CLEANS UP
                     THE CONNECTION AND SENDS THE CR/TRM/N RESPONSE TO
                     NVF.  THE APPLICATION IS NEVER SENT A CON/ACRQ/A.
          SOLUTION - NIP HAS BEEN CORRECTED BY ADDING A NEW STATE TO THE
                     HOST SIDE CONNECTION STATE TABLE.  WHEN THE ABOVE
                     CONDITION OCCURS, NIP WILL SEND A CR/TRM/N SUP MSG 
                     TO NVF AND A CON/ACRQ/A RESPONSE TO THE
                     APPLICATION. 
          EG     091784    STBLDEF, STATTBL 
 NA5B006  NCSTTP STATE TABLE ERROR DUE TO ICN/AP/R SENT BY CCP FOR PRU
          CONNECTION. NIP WILL SEND BACK ICN/AP/A INSTEAD.
          LTN    84/09/17    XSTTP
  
 FNA5457  2.4 NIP MODIFICATIONS FOR PIP SUPPORT.
          1. SUPPORT AUTOMATIC STARTUP OF -INITMDI- 
             UPON RECEIVING THE INID/MDI (HEX0600) SUPERVISORY MESSAGE
             FROM PIP (I.E. DN=SN=HOST NODE), IF THE INDICATED NODE IS A
             "ND" DEVICE, NIP WILL GET THE INDIRECT PERMANENT FILE
             WITH THE RESERVED FILE NAME ZZININD, AND SUBMIT THE FILE TO
             THE INPUT QUEUE. ZZININD CONTAINS THE JOB FILE TO STARTUP
             INITMDI VIA NAMI, IT BASICALLY CONTAINS THE #JOBIMDI.# AND 
             THE #NAMI(RS=IN)# STATEMENTS. ZZININD MUST RESIDE IN THE 
             PERMANENT FILE CATALOG OF THE USER THAT IS USED TO BRING UP
             NAM (I.E. NETOPS OR SYSTEMX). THERE MUST BE AN INITMDI JOB 
             RECORD (JOBIMDI) IN THE NAM STARTUP MASTER FILE AND THE
             PARAMETER RECORD BEING USED MUST CONTAIN THE NAMI #JOB#
             STATEMENT FOR THE INITMDI JOB (I.E.JOB(JOBIMDI,IN,DI)).
             ASSOCIATED DAYFILE MESSAGES- 
             *NIP/NO INITMDI STARTUP - ZZININD NOT FOUND.* - INDICATES THE
             INITMDI STARTUP JOB FILE ZZININD IS NOT FOUND. 
             *NIP/BAD MDI INITIATION REQUEST RECEIVED.* - INDICATES THE 
             INID/MDI SUPERVISORY MESSAGE IS RECEIVED ON A NON-MDI DEVICE.
             THE MESSAGE IS IGNORED BY NIP. 
          2. NAM STATUS DISPLAY WILL DISPLAY MNEMONIC #ND# FOR A MDI
             EST ENTRY. 
          3. DISPLAY MDI ERROR STATUS FROM PIP IN HEXADECIMAL. A MDI
             ERROR STATUS MESSAGE WILL ALWAYS BE PRECEDED BY THE DAYFILE
             MESSAGE *MDI ERROR STATUS RECEIVED*. 
          4. SUPPORT A PIP TRACE BUFFER PER FRONT END UPON OPERATOR 
             REQUEST. NIP WILL ACTIVATE THE PIP TRACE OPTION WHEN THE K 
             DISPLAY COMMAND #TB=HOST NODE NUMBER OF FRONT END# IS ENTERED, 
             AND DISABLE THE PIP TRACE OPTION WHEN THE K DISPLAY COMMAND
             *TE=HOST NODE NUMBER OF FRONT END* IS ENTERED. THE PIP TRACE 
             SUPPORT CODE WILL ONLY BE TURNED ON IF A *DEFINE PTRACE
             UPDATE DIRECTIVE IS INCLUDED IN THE BUILD JOB. 
             ASSOCIATED K DISPLAY MESSAGES- 
             *PIP TRACE OPTION NOT AVAILABLE* - INDICATES EITHER NAM IS 
             IS NOT BUILT WITH THE #PTRACE# OPTION DEFINED OR NAM IS IN 
             BUFFER REGULATION, THE PIP TRACE BUFFER CANNOT BE ALLOCATED. 
             *UNKNOWN HOST NODE* - INDICATES THE HOST NODE NUMBER ENTERED 
             FOR THE #TB# AND #TE# COMMANDS IS NOT VALID OR NOT KNOWN.
          JCL    05/18/84    NUMEROUS ROUTINES
 NA5A999  THIS IDENT HONORS THE TIMEOUT REASON CODE 9 IN
          XFTIER  WHICH PIP SENDS TO AIP. NETXFR WILL THEN
          RETURN TO THE CALLER WITH RESON CODE 5. 
          YCY     84/09/18     AIPSTDF,NP$SMSG,NP$STTP
 NA5A949  SET REASON CODE IN CR/CB/U (SENT TO NVF) TO 9 WHEN TIMEOUT IS 
          DETECTED. THIS FIXES THE PROBLEM OF MFLINK SOMETIMES GETTING
          A CON/ACRQ/A WITH RC = 0 .
          LTN       84/09/11       XCHKPCR
  
 NA5B005  PROBLEM  - NIP MAY FORGET TO UPDATE THE DATA AVAILABLE WORD 
                     IN AIP OR TO COMPLETE PROCESSING OF A FILE 
                     TRANSFER IF THE APPLICATION IS SWAPPED IN AND OUT
                     AT THE WRONG TIME. 
          ANALYSIS - HWRAVAL IS CALLED TO WRITE BACK THE DATA AVAILABLE 
                     WORD IN AIP.  THE SF.WRITE SCP FUNCTION GETS A 
                     REASON CODE OF 44B (APPLICATION SWAPPED OUT).
                     HWRAVAL THEN ISSUES A SWAPIN FOR THE APPLICATION.
                     BEFORE NIP PROCESSES THE SWAPIN COMPLETION, A
                     WORKLIST FROM THE APPLICATION IS RECEIVED (I.E.
                     THERE WAS NO PREVIOUS WORKLIST OUTSTANDING).  NIP
                     WILL THEN FORGET TO CALL HWRAVAL TO UPDATE THE 
                     DATA AVAILABLE WORD IN AIP.  NRCSSTP ISSUES A SST
                     FUNCTION TO SWITCH A FILE FROM NIP TO THE
                     APPLICATION.  IN RESPONSE TO THE SST FUNCTION, NIP 
                     GETS A REASON CODE OF 2 (APPLICATION SWAPPED OUT). 
                     NCRSTTP THEN ISSUES A SWAPIN SCP FUNCTION FOR THE
                     APPLICATION.  AS BEFORE, A WORKLIST FROM THE 
                     APPLICATION IS RECEIVED BEFORE THE SWAPIN
                     COMPLETION IS PROCESSED.  NIP WILL THEN FORGET TO
                     SWITCH THE FILE AND SENT THE ASSOCIATED SUPERVISORY
                     MESSAGE. 
          SOLUTION - HWLP IN NIP HAS BEEN CORRECTED TO NOT COMPLETE 
                     WORKLIST PROCESSING IF THE DATA AVAILABLE WORD IN
                     AIP NEEDS TO BE UPDATED.  XSACB IN NIP HAS BEEN
                     CORRECTED TO CALL HWRAVAL IF THE DATA AVAILABLE
                     WORD NEEDS TO BE UPDATED AND TO PROCESS THE PWL
                     APPLICATION-SWAPPED-OUT RING NO MATTER WHAT STATE
                     THE APPLICATION IS IN. 
          EG     09/19/84   HWLP, XSACB, NPPSM, HHIR
 NA5B009  PROBLEM  - SOMETIMES NVF WOULD ISSUE CR/TRM AFTER NIP SENT
                     A CR/SWH/N.  THIS WOULD CAUSE NVF TO ABORT BECAUSE 
                     THE ACN ENTRY FOR THE CR/TRM WOULD BE DELETED. 
          ANALYSIS - NVF NEEDS TO MAKE SURE THAT THE CONNECTION IS
                     NOT DELETED BEFORE SENDING OUT THE CR/TRM.  THIS 
                     IS ONLY A PROBLEM WHEN NVF SENDS OUT A CR/TRM AS 
                     A RESULT OF A NET/OFF OR FAI/APP.
          SOLUTION - NVF WILL NOT SEND OUT A CR/TRM AFTER THE CR/SWH
                     HAS BEEN SENT.  WHEN IT DOES SEND OUT THE CR/TRM,
                     IT WILL DO IT IN ONE STEP, BYPASSING THE C-LAYER,
                     IN ORDER TO INSURE THAT THE CR/SWH DOES NOT GET
                     SENT OUT WHILE THE CR/TRM IS WAITING IN THE <CTQ>. 
                     ALSO, WHEN NVF RECEIVES A CR/SWH/N, IT WILL
                     DELETE THE ACN IN THE PAAC AND DELETE THE ACN
                     TABLE ENTRY ALL IN ONE STEP IN ORDER TO PREVENT
                     A CR/TRM BEING SENT OUT FOR A CONNECTION COMING
                     INTO NVF RIGHT AFTER THE CR/SWH/N.  (BECAUSE NVF 
                     WOULD SEE THAT AN ACN ENTRY EXISTS AND THE STATE 
                     IS NOT SWSTART -- BUT IT WOULD BE FOR AN ENTIRELY
                     NEW CONNECTION!) 
          PAM     84/09/27     NVFCCPA,NVFASWN,NVFCBPA,NVFADQE,NVFAFAI, 
                               NVFCTRM
 NA5A773  PROBLEM  - ON A BUSY MACHINE, A REQUEST STARTABLE APPL
                     MAY TAKE MORE THAN ONE MINUTE TO START UP.  IF 
                     THIS HAPPENS MORE THAN 3 TIMES FOR AN APPL, THE
                     APPL IS DISABLED BY NVF. 
          SOLUTION - CHANGE THE TIME LIMIT FROM ONE MINUTE TO FIVE
                     MINUTES FOR STARTING UP AN APPLICATION.  ALSO, 
                     DO NOT DISABLE THE APPL IF IT EXCEEDS THREE
                     TIMEOUTS.
          PAM     84/10/01     NVFSTIM,TXTANVF,NVFIAST,NVFSNON,TEXTNVF
 NA5A920   NIP WILL RETURN TO NVF CR/IAP/R WITH RC = 35X IF 
           IT COULD NOT FIND CONNECTION NUMBER FOR THE REQUEST. 
           LTN      84/09/05       HVLLCB 
  
 NA5B008  1- THIS MOD WILL HONOR INITR IF INITR ARRIVES BEFORE ICN/AP/N.
          PROTOCOL FLOW WILL BE AS FOLLOWS: 
                 3/1                       0/2
                                    ----- 
                         INITR -----
                         ------ 
           ULINIT    <--
         <------ 3/3
                     --- INITN
                        ------- 
                                ----- 
                                     ---->      DLINIT
                       ICN/AP/N            0/4 ---------> 
                    <---------------------
                 0/3
                    ---  INITR
                        ------- 
                                ----
                                     ---->       ULINIT 
                                           0/0 ---------> 
                                     -----
                         INITN  ----
                        --------
           DLINIT   <-- 
         <------ 0/0
  
          2- SENDING ICN/AP/A WITH REASON CODE 9 TO INFORM THE OTHER
          HOST THAT CONNECTION ALREADY EXISTED. (HCSTTP STATE TABLE ERROR 
          DUES TO ILLEGAL EXTERNAL TRIGGER) 
  
          LTN    94/09/18    XSTTP
  
 NA5B022  PROBLEM  - NVF ABORTED WITH CPU ERROR EXIT AFTER K.ST,AP=QTFS.
          ANALYSIS - A REQUEST STARTABLE APPLICATION DID NOT NETON
                     PROPERLY, AND NVF THOUGHT THAT SEVERAL COPIES OF 
                     THE APPL EXISTED WHEN IN REALITY, NONE EXISTED.
                     WHEN NVF TRIED TO PROCESS THE K.ST COMMAND, IT 
                     LOCATED THE APPL IN THE "AST" TABLE AND FOUND THAT 
                     THREE COPIES SUPPOSEDLY EXISTED.  THEN IT SEARCHED 
                     THE "AST" TABLE LOOKING FOR THE MATCHING COPIES. 
                     IT DID NOT STOP AT THE END OF THE TABLE, BUT 
                     CONTINUED TO SEARCH UNTIL IT FOUND A MATCH.
                     THIS CAUSED THE CPU ERROR EXIT.
          SOLUTION - CHANGE NVF TO STOP SEARCHING WHEN IT GETS TO THE 
                     END OF THE TABLE.  IF IT HAS NOT FOUND ALL OF THE
                     APPL COPIES, IT WILL SEND THE "READY.." MESSAGE. 
          PAM     84/10/01     NVFOPAC
 NA5B018   NIP SHOULD REJECT CR/IAP/N FROM NVF WHEN LLCB HAS
           LLCBWOF FLAG TURNED ON.
  
           LTN      84/09/27       HVLLCB 
 NA50238  DT12 IS NEW REPLACING DT7 AS A VALID
          USER DEFINED TIPTYPE WITH INTERNAL VALUE 12.
          YCY     84/08/13     NDLPSS1,NDLNFCM,NDLLIST
 NA50166  NIP STOPS DURING INITIALIZATION WITH NIP MAXIMUM FL REACHED 
  
          PROBLEM - NIP DOES NOT SET THE HOST REGULATION LEVEL DURING 
                    INITIALIZATION, UNLESS THE ROUTINE MGETS REQUESTS 
                    ADDITIONAL FIELD LENGTH, SO THE HOST REGULATION 
                    LEVEL CAN BE LEFT UNSET.  IF THE HOST REGULATION
                    LEVEL AND THE PREVIOUS REGULATION LEVEL ARE NOT 
                    EQUAL, AND THE HOST REGULATION LEVEL IS ZERO, NIP 
                    WILL DISPLAY THE MESSAGE "NIP MAXIMUM FL REACHED".
  
          SOLUTION- SET THE HOST REGULATION LEVEL AND THE PREVIOUS
                    HOST REGULATION LEVEL TO NO REGULATION WHEN 
                    THE MEMORY CONTROL TABLE IS INITIALIZED.
  
          OUR THANKS TO TIM ROBERTS OF CONTROL DATA, LOS ANGELES, FOR 
          HIS DETAILED ANALYSIS OF THE PROBLEM. 
  
          EMH/RMF            84/10/04              INIP,ITABS 
  
 NA50177  PSR NA50034 WAS SUPPOSE TO ALLOW THE RECOGNITION OF X.25
          TERMINAL NAMES FOR CS COMMANDS.  THE MODSET DOES NOT WORK 
          ENTIRELY. 
  
          THIS MOD SET CORRECTS NA50034 WHEN CONVERTING HEXIDECIMAL 
          NUMBERS TO INTEGERS.
  
          NA50034 NEEDS TO BE APPLIED BEFORE THIS ONE CAN BE INSTALLED. 
          DKE     84/10/09     CSSRCA 
 NA5B032  COLLECT JOB SHOULD NOT REQUEST TAPE(S) IF NO FILES
          TO COPY.
  
          THE COLLECT JOB REQUESTS TWO TAPES IRRESPECTIVE OF
          WHETHER OR NOT ANY FILES EXIST TO BE COPIED TO TAPE.
          THIS IS UNACCEPTABLE FOR THE SUPER-MINI SYSTEM. 
  
          THE COLLECT JOB HAS BEEN CHANGED TO - 
          1.  REQUEST TAPE(S) ONLY IF THERE ARE FILES TO BE COPIED, 
          2.  REQUEST ONLY ONE TAPE IF IN THE PARAMETER RECORD THERE
              EXISTS *PARAM(ONETAPE=YES)*.
          ALL PARAMETER RECORDS HAVE BEEN CHANGED TO INCLUDE THE
          PARAMETER *ONETAPE=YES*.
  
          RWH            10/07/84       NWINIT,NWRESTRT,NWRECOVR, 
                                        NWMULTI,NWMINIT,NWMRECOV, 
                                        JOBCOL
  
 NA5A974  THIS IDENT CHANGES THE DECK NAMES AND THE NAMES OF THE
          ENTRY POINTS OF THE DECK INVOLVED TO BEGIN WITH NP$.
          THE DECKS TO BE CHANGED ARE CALLSYS, CMMINT AND CSET63. 
          THESE DECKS ARE NOW CALLED NP$CSYS, NP$CMIT AND NP$CS63.
          CALLS TO THE ENTRY POINTS OF THESE DECKS ARE ALSO 
          CHANGED ACCORDINGLY.
          YCY     84/10/05     NP$CIO,NETXFR,NP$S63,NP$CMIT,NP$CSYS.
 NA5A930  PROBLEM  - CS ABORTED WHEN IT RECEIVED SUP/MSG THAT IT
                     DID NOT KNOW HOW TO PROCESS. 
          ANALYSIS - THE SUP MSG WAS A NPI/DD SUP WHICH IS SUPPOSED TO
                     BE PROCESSED BY NIP.  NIP ROUTED IT TO CS INSTEAD. 
          SOLUTION - NEIB1 IN NIP HAS BEEN CORRECTED TO RECOGNIZE THE 
                     NPI/DD SUP MSG AS ONE FOR NIP TO PROCESS.  PIP HAS 
                     BEEN CORRECTED TO USE THE CORRECT PFC/SFC VALUE
                     FOR THE NPI/DD SUP MSG.
          EG     08/28/84    NEIB1, SMPFC, NPNIPSM
 NA5B034  PROBLEM -  NVF REJECTS CONNECTION REQUESTS FOR PTFS AND QTFS. 
                     THIS MAKES IT IMPOSSIBLE TO INITIATE FILE TRANSFERS
                     TO THAT HOST.
          ANALYSIS - NVF KEEPS A COUNT OF THE NUMBER OF COPIES OF A 
                     REQUEST-STARTABLE APPLICATION THAT ARE ACTIVE. 
                     THIS COUNT IS DECREMENTED WHEN NVF TIMES OUT ON
                     STARTING UP A REQUEST-STARTABLE APPLICATION. 
                     HOWEVER, THE COUNT WAS NEVER INCREMENTED WHEN
                     NVF INITIATED THE JOB FOR THE REQUEST-STARTABLE
                     APPLICATION.  SINCE THE COUNT IS SAVED IN AN 
                     UNSIGNED FIELD, THE COUNT WENT FROM ZERO TO THE
                     LARGEST NUMBER THAT COULD FIT IN THE FIELD MINUS 
                     ONE.  WHEN THIS HAPPENED, NVF BEGAN REJECTING
                     THE CONNECTION REQUEST FOR THE REQUEST-STARTABLE 
                     APPLICATION, SINCE THE MAXIMUM NO OF COPIES OF 
                     THE REQUEST-STARTABLE APPLICATION WERE ALREADY 
                     ACTIVE.
          SOLUTION - ROUTINE NVFSTIM IN NVF HAS BEEN CORRECTED TO NOT 
                     DECREMENT THE COUNT OF ACTIVE OR PENDING REQUEST-
                     STARTABLE APPLICATIONS.
          EG     10/10/84    NVFSTIM
 NA5B023  WHEN USER DOES CONTROL/T AT TERMINAL DURING MFLINK SESSION, 
          THE FILE DOES NOT GET RETURNED BACK TO TERMINAL AND STAYS AT
          THE NIP CONTROL POINT UNTIL NIP GOES DOWN.
          SOLUTION FOR THIS PROBLEM IS TO DELAY THE SCP REQUEST TO TERM 
          SHORT AND LONG TERM CONNECTIONS UNTIL NVF RETURNS THE 
          NET/OFF/N OR FAIL/APPL/N TO NIP.
          (FILE IS SWITCHED BACK TO APPLICATION WHEN PIP
          RESPONDS TO PRU TERMINATE REQUEST WORKLIST).
          LTN    84/10/10    HAPFAIL,HPNOFF,HPNOFFN,HPPUT,NPPCT,NPPSM 
  
 *L630*    ************************************************ 
 NA5B043  PIP IN FAULT PROCESSING OF ERRORS DURING A READ FROM DI 
  
          PIP SHOULD NOT ISSUE A READ ERROR FUNCTION FOR A CHANNEL
          ERROR IN A READ FROM DI IF GENERAL STATUS SHOWS THAT AN ERROR 
          WAS DETECTED BY DI. 
  
          PCH/SW 84/10/17    PIP
 NA5B045  2.4.1. PIP CAN NOT SEND OUT COLON CHARACTER TO NETWORK. 
  
          PIP HAS A PROBLEM IN PROCESSING DISPLAY CODE TO ASCII 
          CONVERSION AND CAN NOT OUTPUT COLON CHARACTER TO NETWORK. 
  
          SW     84/10/17    PIP
 NA5B046  PROBLEM  - NVF ALLOWED MULTIPLE COPIES OF A REQUEST STARTABLE 
                     APPLICATION TO NETON, EVEN THOUGH THE APPLICATION
                     WAS SUPPOSED TO ONLY HAVE ONE ACTIVE COPY AT A TIME. 
          ANALYSIS - IN NET/ON PROCESSING, NVF WOULD ALWAYS INCREMENT THE 
                     NUMBER OF CURRENT COPIES FIELD IN THE *AST* WHEN AN
                     APPLICATION NETTED ON.  THE ONLY CASE NVF WOULD NOT
                     SET THIS FIELD WAS IF THE APPLICATION ALLOWED ONLY 
                     ONE COPY TO BE ACTIVE.  IN THE CASE OF A REQUEST 
                     STARTABLE APPLICATION WITH A MXCOPY OF 1, NVF COULD
                     ROUTE SEVERAL JOBS TO START UP THE APPL, AND THEY
                     WOULD ALL NETON USING THE SAME *AST* ENTRY.
          SOLUTION - CHANGE NVF TO SET THE CURRENT COPIES FIELD IN THE
                     *AST* TO 1 IF AN APPLICATION WITH A MXCOPY = 1 
                     NETS ON. 
          PAM     84/10/29     NVFSNON
 NA5B047  THIS FIXES THE PROBLEM OF BUFFER MANAGEMENT IN NIP, 
          AND ALSO APPLICATION HANGS IN AUTO RECALL.
          LTN       84/10/25       HPNOFF,HPNOFFN 
  
 NA5B048  PROBLEM  - WHEN AN A-A CONNECTION REQUEST TRIED TO CONNECT
                     TO AN APPLICATION, CR/IAP/A WAS SENT BY NVF WITH 
                     RC=22, EVEN THOUGH THE CALLED APPLICATION WAS
                     AVAILABLE. 
          ANALYSIS - THE CALLED APPLICATION WAS NOT REQUEST STARTABLE,
                     BUT COULD HAVE MORE THAN ONE COPY.  THIS MEANS THAT
                     WHEN THE APPLICATION NETS ON, THE APPL NUMBER WILL 
                     BE APPENDED TO THE "BASE" APPL NAME TO FORM THE NAME 
                     OF THE NETTED ON APPL.  IN THE CR/IAP/R, THE 
                     CALLED APPL NAME WAS "TERM1" INSTEAD OF "TERM107". 
                     NVF LOCATED "TERM1" IN THE *AST* AND FOUND IT WAS
                     NOT REQUEST STARTABLE AND NOT NETTED ON, AND SO
                     SENT BACK A CR/IAP/A WITH RC=22. 
          SOLUTION - WHEN NVF CHECKS IF THE CALLED APPL IS NETTED ON, 
                     CHECK IF THE APPL IS REQUEST STARTABLE OR IF THE 
                     APPL CAN HAVE MORE THAN ONE ACTIVE COPY. 
          PAM     84/12/05     NVFARAP
 NA5B052  PIP MAY HANG IN PROCESSING OF BLOCK PROTOCOL ERROR
  
          PIP MAY HANG IN PROCESSING OF BLOCK PROTOCOL ERROR IF 
          OPTION FOR HALTING NPU AT ERROR IS SELECTED.
  
          FOUR OTHER MINOR BUG FIXES ARE INCLUDED.
  
          SW     84/10/24    PIP
 NA5B054   INCREASE NIP TABLES SPACE BY 11000B FOR PIP USAGE. 
           LTN      84/10/26       ITABS
  
 NA5B063  NIP RELEASES FL BUFFER ATFER O.S. PROCESSES SCP REQUEST WITH
          NO ERROR CODE RETURNED. 
          LTN       84/11/05       HPNOFFN
  
 NA5B067  PIP HUNG WITH MDI CHANNEL FULL ON OUTPUT
  
          DURING MDI OUTPUT IN PROGRESS PIP HUNG AT AN OUTPUT 
          INSTRUCTION.
          PIP SHOULD CHECK FOR CHANNEL EMPTY BEFORE EXECUTING 
          THE OUTPUT INSTRUCTION. 
  
          SW     84/11/13    PIP
 NA5B070  PRU MODE INTERFACE WILL NOT WORK FOR MDI
  
          CHECK FOR VALID BLOCK HEADER FOR MDI IS NOT CORRECT 
          IN COMPARING DN IN INCOMING MESSAGE WITH TARGET HN
          WHEN THE INTERFACE IS IN PRU MODE.
          IT RESULTS IN BLOCK HEADER FORMAT ERROR.
  
          SW     84/11/12    PIP
 NA5B073  PIP IS NOT PAUSING FOR STORAGE MOVE.
  
          IF PIP OVERLAYS ARE STORED IN ECS OR 819 DISK, LOADER DRIVER
          6DE DOES NOT ISSUE DRIVER-SEEK-WAIT MONITOR FUNCTION FOR
          MASS STORAGE ACCESS DELAY AS OTHER DRIVERS DO, INSTEAD, IT
          ISSUES PAUSE-FOR-STORAGE-MOVE WHEN NECESSARY. 
          PIP WAITS FOR DRIVER-SEEK-WAIT FUNCTION AS A TRIGGER FOR ITS
          PAUSE-FOR-STORAGE-MOVE THAT NEVER HAPPENS.
  
          PIP WILL CHECK FOR EITHER DRIVER-SEEK-WAIT OR PAUSE-FOR-
          STORAGE-MOVE AS A TRIGGER FOR ITS PAUSE-FOR-STORAGE-MOVE. 
  
          SW     84/11/28    PIP
 NA5B077  COLLECT FAILS TO PICK UP FILES. 
  
          DUE TO AN ERROR IN THE ALGORITHM USED TO OBTAIN THE NAMES 
          OF ALL FILES IN THE CATALOG, *COLLECT* WILL NOT SEE FROM
          1 TO 4 FILES EACH TIME IT RUNS.  THESE MAY OR MAY NOT BE
          NETWORK FILES.
  
          THIS MODSET CORRECTS THE ERROR. 
  
          RWH            11/21/84       COLLECT 
  
 NA5B079  PIP DOES NOT MAKE UPLINE IVT BACK AS A THREE-WORD BLOCK.
  
          NIP NEEDS THREE-WORD BUFFER TO PROCESS AN INCOMING BACK.
          IF PIP SENDS A BACK AS A THREE-WORD BLOCK IN THE INBOUND
          BUFFER, NIP WILL USE THE BLOCK FOR THE PROCESSING.
  
          THIS CODE CORRESPONDS TO NA5A526 OF NOS 2.3.
  
          SW     84/11/26    PIP
 NA5B082  PIP INCORRECTLY ISSUES MDI READ ERROR FUNCTION. 
  
          PIP SHOULD NOT ISSUE MDI READ ERROR FUNCTION IF THE FUNCTION
          COULD NOT BE ISSUED FOR THE CHANNEL ACTIVE BEFORE FUNCTION. 
  
          PIP IS CHANGED TO ISSUE THE READ ERROR FUNCTION IF THE ERROR
          CODE IS NOT FOR CHANNEL ACTIVE BEFORE FUNCTION AND THE LAST 
          FUNCTION IS FOR READ. 
  
          SW     84/12/05    PIP
 NA5B091  PRU INPUT ORDER CODE IS SET UP INCORRECTLY IN PIP FOR MDI.
  
          MDI GENERAL STATUS IS INTERPRETED INCORRECTLY IN PIP RESULTING
          IN AN INVALID INTERNAL CODE FOR A PRU MODE INPUT. 
  
          RMK    84/12/03    PIP
 NA5B093  TROUBLES WHEN FILE TRANSFER IS TERMINATED BY RECEIVER.
  
          BREAK-RECEIVED FLAG IS NOT SET IN PCNB WHEN FILE TRANSFER 
          IS TERMINATED BY THE RECEIVER.
  
          WHEN PRU MODE OFF COMMAND IS SENT TO THE FRONT END BY THE 
          RECEIVING PIP TO END THE FILE TRANSFER, PIP MUST BE READY 
          TO RECEIVE IVT MODE INPUT FROM THE FRONT END BEFORE THE 
          NIP-PIP INTERFACE CHANGES TO THE IVT MODE.
  
          WHEN THE SENDING PIP IS WAITING FOR NO OUTPUT ACTIVITY TO 
          REQUEST THE END OF THE FILE TRANSFER, PIP MUST WAIT FOR THE 
          PROCESSING OF BACK PIP MAY BE REQUIRED TO SEND FOR THE LAST 
          RECEIVED BLOCK. 
  
          SW     84/12/03    PIP
 NA5B095  PP DIRECT CELL CONFLICTS IN MDI INTERFACE 
  
          T6/T7 THAT ARE TEMPORARILY USED IN TAKING MDI GENERAL STATUS
          SHOULD BE KEPT INTACT THERE.
  
          T16/T17 ARE NOW USED IN PLACES OF THEM AFTER SOME INTERFACE 
          MODIFICATIONS.
  
          SW     84/12/04    PIP
 NA5B100  NO PRU BUFFERS RESERVED FOR INPUT.
  
          NUMBER OF PRU BUFFERS RESERVED FOR INPUT IS AN ITEM OF
          SITE DEFINED PIP ASSEMBLY VARIABLES.
          DEFAULT VALUE OF THIS VARIABLE IS ZERO. 
  
          TO AVOID THE CCP DEADLOCK SITUATION WHEN PRU TRAFFICS 
          ARE BUSY THE DEFAULT VALUE IS CHANGED TO ONE. 
  
          SW     84/12/05    PIP
 NA5B129  PROBLEM  - PIP MASTER CLEARED SAM WHILE SAM WAS TALKING TO
                     A DIFFERENT PIP IN A DIFFERENT HOST. 
          ANALYSIS - PIP HAS CODE TO TIME OUT SAM IF SAM DOES NOT 
                     COMMUNICATE WITH IT.  IF SAM IS TALKING TO 
                     A DIFFERENT PIP, THIS SITUATION WILL ALWAYS
                     OCCUR.  PIP WILL MASTER CLEAR SAM THEN.
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT TIME OUT WAITING 
                     FOR SAM TO COMMUNICATE WITH IT.
          EG     12/19/84    PIP
 NA5B131  THIS IDENT FIXES THE PROBLEM THAT NVF CLOBBERS
          THE APPLICATION NAME IN THE PAC ENTRY FOR EVERY OTHER 
          CRRAP IF THEY REACH THE HOST ABOUT THE SAME TIME. IT
          ALSO CAUSES SOME TIME OUT ON MFLINK SINCE THE SERVER
          NEVER NETS ON.
  
          YCY     85/01/03     NVFTICR,TXTANVF,NVFASPC
 NA5B134  PROBLEM  - TERMINAL SENT 249 CHARACTER BLOCK UPLINE WHICH 
                     RESULTED IN A COUPLER ERROR 91.
          ANALYSIS - PIP RAN OUT OF INBOUND BUFFER SPACE WHEN IT WAS
                     TRANSFERRING THE DATA TO NIP'S FIELD LENGTH. 
                     PIP ASSUMED THIS WAS DUE TO CCP NOT TELLING PIP
                     WHAT THE CORRECT SIZE OF THE MESSAGE WAS AND 
                     GENERATED A COUPLER ERROR 91.  THE MESSAGE WAS 
                     254 CHARACTERS LONG INCLUDING THE NETWORK HEADER.
                     CCP TOLD PIP THE MESSAGE WAS LESS THAN OR EQUAL TO 
                     256 CHARACTERS LONG SO CCP DID NOT DO ANYTHING 
                     WRONG.  WHEN PIP CHECKED TO SEE IF THE INBOUND 
                     BUFFER SPACE WAS AVAILABLE, IT CHECKED FOR A 
                     SMALLER SIZE BUFFER THAN IT NEEDED.  THIS RESULTED 
                     IN PIP RUNNING OUT OF INBOUND BUFFER SPACE.
          SOLUTION - PIP HAS BEEN CORRECTED TO CHECK FOR THE CORRECT
                     INBOUND BUFFER SPACE.  THIS SOLUTION IS FOR NOS
                     2.4.1 AND LATER SYSTEMS. 
          EG     12/27/84    PIP
 NA5B138  CORRECTIONS FOR NA5B095 (PIP DIRECT CELL USE CONFLICTS) 
  
          AFTER NA5B095 DISPLAY-CODED IVT DOWNLINE MESSAGES THAT CONTAIN
          COLONS AND ARE LONGER THAN 640 CHARACTERS CAUSE TROUBLES IN 
          PIP AND IN FRONT END. 
  
          SW     85/01/04    PIP
 NA5B147  PROBLEM  - MFLINK HUNG BEFORE FILE TRANSFER STARTED.
          ANALYSIS - NAM K-DISPLAY SHOWED ONE SUPERVISORY MESSAGE 
                     QUEUED FOR THE APPLICATION THAT WAS NOT BEING
                     RECEIVED BY THE APPLICATION.  OBSERVATION OF 
                     THE APPLICATION SHOWED IT WAS IN A LOOP CONSTANTLY 
                     ISSUING NETWAIT CALLS.  ANALYSIS OF AIP-S MEMORY 
                     SHOWED THE DATA AVAILABLE WORD IN AIP HAD NOT BEEN 
                     UPDATED BY NIP YET.  ANALYSIS OF NIP PRODUCED A
                     CASE WHEN NIP WILL NOT UPDATE AIP-S DATA AVAILABLE 
                     WORD WHEN IT SHOULD. 
          SOLUTION - XSACB HAS BEEN CORRECTED TO PROCESS ALL
                     APPLICATIONS IN LTHE AT TABLE. 
          EG     01/09/85    XSACB
 NA5B151  PROBLEM  - PRU BUFFERS ALLOCATED BY NIP ARE GETTING LOST. 
          ANALYSIS - AFTER NIP ALLOCATED THE BUFFERS, NIP DID NOT 
                     LINK THE BUFFERS UP CORRECTLY.  ALSO THE COUNT 
                     OF BUFFERS IN THE SYSTEM CHAIN IS INCORRECT. 
          SOLUTION - NIP HAS BEEN CORRECTED TO LINK THE BUFFERS UP
                     CORRECTLY AND TO UPDATE THE COUNT OF BUFFERS 
                     IN THE SYSTEM CHAIN CORRECTLY. 
          EG     01/11/85    XCHKABC, NPRLB 
 NA5B156  PROBLEM  - MINIMUM PRU BUFFER COUNT FIELD IS SET TO ZERO IN 
                     PIP ENTRY. 
          ANALYSIS - AT INITIALIZATION TIME, NIP ROUTINE ITABS STORED 
                     THE MINIMUM PRU BUFFER COUNTS IN THE PIT ENTRIES.
                     HOWEVER, NIP ROUTINE XCHKCET ZEROED OUT THE ENTIRE 
                     PIT ENTRY BEFORE IT SET UP A NEW PIP ENTRY.
          SOLUTION - THE MINIMUM PRU BUFFER COUNT FIELDS WILL BE SET UP 
                     BY XCHKCET INSTEAD OF ITABS. 
          EG     01/15/85    ITABS, XCHKCET 
 NA5B157  PIP MAY REQUEST TOO MANY PRU BUFFERS FROM THE SYSTEM POOL 
  
          IF REQUEST FROM PIP FOR MORE PRU BUFFERS IS NOT SATISFIED FOR 
          SYSTEM PRU POINTER WORD BEING BUSY, THE REQUIRED PRU BUFFER 
          COUNT IS CARRIED ON TO THE NEXT CYCLE RESULTING IN A NUMBER OF
          REQUIRED PRU BUFFERS TOO HIGH.
  
          REQUIRED PRU BUFFER COUNT MUST BE RESET AND ACCUMULATED FOR 
          EACH CYCLE. 
  
          SW     85/01/11    PIP
 NA5B161  UPDATE THE COPYRIGHT INFORMATION IN THE NVF BANNER AND ON 
          THE NAM PL TO 1985. 
          PAM     85/01/22     TMSGNVF,CRCOM
 NA5B172  PROBLEM  - WHEN RUNNING WITH MULTIPLE PIPS, IT IS POSSIBLE FOR
                     ONE OF THE PIPS TO GRAB ALL THE PRU BUFFERS.  THIS 
                     FORCES THE OTHER PIPS TO WAIT FOR THIS PIP TO FREE 
                     UP A BUFFER.  THIS CAN RESULT IN ALL UPLINE DATA 
                     TRAFFIC FROM A NPU TO BE SUSPENDED UNTIL THE BUFFER
                     IS FREED UP. 
          ANALYSIS - THERE SHOULD BE A MAXIMUM NUMBER OF BUFFERS THAT 
                     EACH PIP CAN RESERVE.  THIS MAXIMUM NUMBER OF
                     BUFFERS MUST BE SELECTABLE BY EACH INSTALLATION. 
                     PIP MUST BE MODIFIED TO NOT EVER REQUEST MORE
                     BUFFERS THAN THE MAXIMUM VALUE.
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT REQUEST MORE BUFFERS 
                     THEN THIS MAXIMUM.  NIP HAS BEEN CORRECTED TO
                     PROCESS THE N1PRUB, N2PRUB, AND N3PRUB CONTROL 
                     CARD AS THE MAXIMUM NUMBER OF BUFFERS TO ALLOCATE
                     FOR EACH PIP.
          EG     01/21/85    INIP, MSETPTR, NPRLB, PIT, XCHKCET, XEXEC
          SW     01/21/85    PIP
 NA50339  THE APPLICATION NAME WAS MISSING FROM THE ABAP AND AEAP 
          ACCOUNT MESSAGES.  THIS CODE CHANGES NVF TO CORRECTLY EXTRACT 
          THE APPLICATION NAME FROM ITS *PTAC* TABLE, STORE THE APPL
          NAME IN THE FIRST SEVEN CHARACTERS OF A TEMPORARY ITEM, AND 
          MOVE THE APPL NAME FROM THE TEMPORARY ITEM TO THE ACCOUNT 
          MESSAGE.
          PAM     84/11/13     NVFTIAM
 NA50347   NP$GSM USES LOCAL FLAG TO SET IBU, THEN UPDATE ABH BEFORE
           GIVING TO APPLICATION. 
           LTN      85/01/04       NP$GSM 
  
 *L642*    ************************************************ 
 FN2406   THIS IDENT IMPLEMENTS A NEW PARAMETER RTS=Y/N FOR 
          THE DEVICE OR TERMDEV STATEMENT. WHEN SPECIFIED FOR ASYNC 
          AND NON 2741 DEVICES, IT PASSES A FN/FV PAIR TO THE DEVICE
          CONFIGURATION RECORD. THE FN VALUE IS 145 FOR RTS. CCP HAS
          A RTS FLAG INITIALIZED TO FALSE AND SET WHEN A RTS FN/FV IS 
          MET.
          YCY     84/10/19     DATANDL,NDLSDAT,NDLPSS1,NDLNFCM,NDLLIST
 FA6469   TO IMPLEMENT NAM/CCP TERMINAL DELAY 
          ATTRIBUTES COMPATIBILITY, TWO NEW PARAMETERS
          MCI AND MLI ARE IMPLEMENTED FOR DEVICE AND TERMDEV
          STATEMENTS. EACH OF THEM HAS RANGE 0 TO 250. THE
          FN VALUS FOR MCI AND MLI ARE 146 AND 147
          RESPECTIVELY. 
          YCY     84/11/26     DATANDL,NDLSDAT,NDLCKRG,NDLPSS1,NDLNFCM, 
                               NDLLIST
 FN2425   THIS IDENT IMPROVES THE USE OF HOST AND NPU MEMORY. 
          IT ADJUSTS THE ABL AND DBZ DEFAULTS FOR ASYNC DEVICES BASED 
          ON THE LINE SPEED SPECIFIED. THE DIFFERENCE BETWEEN DBL AND 
          ABL IS ALSO ADJUSTED SUCH THAT IT IS ONE FOR LSPEED GREATER 
          THAN OR EQUAL TO 600 AND ZERO OTHERWISE.
          YCY     84/10/25     NDLNFCM
 FN2409   THIS MODSET ALLOWS PL PARAMETER FOR REMOTE
          BATCH LINE PRINTERS. IF PL IS NOT SPECIFIED THEN
          NDLP DEFAULTS PL TO 64 FOR LINE PRINTERS. 
          YCY     84/11/08     NDLNFCM
 FN2417   THIS FEATURE INTRODUCES THE INACT PARAM ON NIP CONTROL CARD.
          IT IS THE VALUE OF INACTIVE TIME OF CONNECTION IN MINUTES.
          THIS CODE IMPLEMENTS PROBLEM LOG ENTRY 17 FOR THE 2.4.1 SYSTEM. 
          IF INPUT PARAM IS ZERO, NO FC/INACT WILL BE SENT. 
          LTN       84/10/23       INPARUT,INIP,XCHKPCR 
  
 FN2420   THIS IDENT REMOVES AUTOLOG PARAMETER FROM DEVICE
          AND TERMDEV STATEMENTS. THE NDLLIST IS ALSO MODIFIED TO 
          REFLECT THIS CHANGE. THE FN VALUE FOR AUTOLOG IS 21.
          YCY     84/10/26     DATANDL,NDLSDAT,NDLNFCM,NDLLIST,NDLPSS1
 FN2423A  FEATURE CODE TO COLLECT CDCNET FILES.  CODE WILL BE ACTIVE
          ONLY IF *CDCNET* IS DEFINED DURING THE UPDATE RUN.
  
          THE FOLLOWING ADDITIONAL *HOST TYPE* FILES WILL BE COLLECTED. 
            FS - FILE SERVER
            OS - OPERATOR SERVER
            LS - LOG SERVER 
            IN - INITMDI
  
          IN ADDITION, MDI DUMP FILES WILL BE COLLECTED IN THE
          FOLLOWING RANGES OF NAMES.
            DI_AA_NIN ... DI_99_NIN 
             .             .
             .             .
             .             .
            DR_AA_NIN ... DR_99_NIN 
  
            DS_AA_NIN ... DS_99_NIN 
             .             .
             .             .
             .             .
            D9_AA_NIN ... D9_99_NIN 
  
          RELATED MODSET - FN2423B, TO *COLLECT* STARTUP JOB. 
  
          RWH            12/11/84       CLT=INI, COLLECT, CLT=IO2 
  
 FN2423B  FEATURE CODE TO COLLECT CDCNET FILES.  THIS CODE CHANGES
          THE *COLLECT* STARTUP JOB TO COPY TO TAPE MDI DUMP FILES
          IF THEY WERE PICKED UP BY *COLLECT*.  THIS CAN OCCUR
          ONLY IF *COLLECT* IS BUILT WITH *CDCNET* DEFINED. 
          SEE...
  
          RELATED MODSET - FN2423A, TO *COLLECT* AND FRIENDS. 
  
          RWH            12/11/84       JOBCOL
  
 FN2424   FEATURE: PROBLEM LOG ENTRY 24.
          THIS FEATURE INCLUDES CODE FOR NIP, AIP, AND NVF. 
  
          NIP WILL IGNORE DATA ON CONNECTIONS THAT ARE LISTED OFF WHEN
          DETERMING IF AN APPLICATION PROGRAM SHOULD BE ROLLED IN AFTER 
          NETWAIT.
  
          AIP WILL INCLUDE A NEW ROUTINE, *NETFUNC*.
  
          NVF WILL CALL THE NEW AIP ROUTINE, *NETFUNC*, DURING
          INITIALIZATION.  ALSO, SERVICES AND SCHEDULER WILL CHECK A
          NEW "DATA DELIVERABLE" BIT IN THE NSUP WORD, WHEN DETERMINING 
          IF INCOMING DATA BLOCKS ARE DELIVERABLE.
  
          LTN     84/11/29     BLINK,BDELINK,HPGET,HSWACNB,RELACNB
          YCY                  NP$NWL,NP$MODE,NETGET,NETWAIT
                               NP$ERR,NETFUNC,NP$USI
          PAM                  NVFICTN,SSACNI,TEXTSS
 FA6028   QTRM HAS BEEN ENHANCED WITH THE FOLLOWING NEW FEATURES: 
  
           1. DEVICE CONNECTION LENDING INCLUDING PASSING OF DATA 
              BETWEEN APPLICATIONS. 
           2. SUPPORT FOR ISSUING ASYNCHRONOUS SUPERVISORY MESSAGES 
              INCLUDING APPLICATION INTERRUPTS AND FLOW CONTROL 
              BREAKS. 
           3. MANIPULATION OF AIP DEBUG LOG FILE AND AIP STATISTICS 
              FILE. 
           4. USE OF DIFFERENT CHARACTER TYPES FOR INPUT ON THE SAME
              CONNECTION OR DIFFERENT CONNECTIONS.
           5. NOTIFICATION OF INACTIVE CONNECTIONS. 
           6. TRANSPARENT MODE INPUT. 
           7. SUPPORT FOR NAM K-DISPLAY.
           8. APPLICATION SUPPLIED OUTCALL PARAMETERS.
           9. SENDING QUALIFIED DATA ON APPLICATION-TO-APPLICATION
              CONNECTIONS.
          10. LOGICAL IDENTIFIERS IN THE ESTABLISHMENT OF APPLICATION-
              TO-APPLICATION CONNECTIONS. 
  
          12. APPLICATION NOTIFICATION OF USER INTERRUPTS.
          13. USE OF CHARACTER TYPE 3 FOR SYNCHRONOUS SUPERVISORY 
              MESSAGES. 
          14. SUPPORT FOR CHARACTER TYPE 4 FOR APPLICATION-TO-
             APPLICATION CONNECTIONS. 
  
          EG     12/06/84    QTRMCOM,QTRMBUF,QTRMNIT,SMAPDEF,NETDBG,
                             NETDMB,NETLGS,NETLOG,NETSTC,NETREL,NETSETF,
                             NP$ERR,QTENDT,QTGET,QTLINK,QTOPEN,QTPUT, 
                             QTCMD(NEW),QTSUP(NEW)
 FN2432   THIS FEATURE WILL ADD TO DAYFILE OF APPLICATION THE MESSAGE 
          "NETON WITH NIN = XXX" TO INFORM THE APPLICATION OWNER
          WHICH NIN OF THE NETWORK THE APPLICATION HAS NETTED ON WITH.
          THIS IMPLEMENTED BY PROBLEM LOG ENTRY NUMBER 32, 2.4.1 LEVEL. 
          LTN       84/10/22       NIP:  HPNONVF,AWLNTRY
                                   AIP: NP$ON,NP$NWL
  
 FN24CS   THIS MODSET ADDS CODE TO CS TO ACCEPT ACCOUNTING MESSAGES 
          COMING FROM THE DI.  TWO NEW SERVICE MESSAGES ARE INTRODUCED: 
          STI/AP/U AND STI/TE/U.  CS MERELY FORMATS THE INFORMATION IN
          THE MESSAGES AND SENDS IT TO THE ACCOUNT DAYFILE.  TWO NEW
          ACCOUNT MESSAGES (SCAP AND SCTE) ARE ALSO INTRODUCED. 
  
          THIS MOD CAN BE INSTALLED WITHOUT THE CORRESPONDING DI CODE.
  
          DKE     84/11/20     SMCS,SMPFC,SMCSDEF,TEXTCS,CSDDNT,
                               CSEDEQ,CSESDA
 FS4201B  THIS FEATURE IDENT INTRODUCES CHECKMARKING AND INTRAHOST
          BINARY FILE TRANSFER. 
          YCY     84/11/26     NX$ADEF,NX$ACBX,AIPSTDF,AIPDEF,
                               NP$SENF,NP$RECV,NP$DATA,NP$STPR
                               NP$STTP,NP$RLOC,NP$SHRK,NP$INT8
                               NP$XCLH,NP$UPRU
 FS4563A   INTRODUCING SWITCHING APPLICATIONS CAPABILITY INTO NIP.
           PROBLEM DESCRIBED IN DAP NUMBER S4563 BY AMATZIA-BEN-ARTZE.
           LTN      84/11/15       SMPFC,SMAPDEF,SMAPPL,HCSTTP
                                   HCONEND,NCSTTP.
  
 FS4563B  FEATURE CODE TO INTRODUCE THE ENHANCED APPLICATION SWITCHING
          FEATURE TO NVF. 
          PAM     84/11/16     SUPMSG,SMNVF,SMPFC,TEXTNVF,TXTANVF,
                               NVFTRCN,NVFTRVD,NVFTACC,NVFTPSV,NVFTDSP, 
                               NVFTVAA,NVFTPUV,NVFCCPA,NVFUMQE,NVFTRLC
 FN2404   CS WILL PROCESS CNF/RC/R FROM CCP GENERATED BY ESCAPE RC
          FROM TERMINAL BY USER. ALL ORIGINAL CHARACTERISTICS OF
          TERMINAL SHOULD BE RESET (ACCORDING TO NCF ). 
  
          LTN       85/01/07       SMPFC,TEXTCS,CS
  
 NA5A932  PROBLEM  - IN THE NAMPL, THE DECKS ST$XXX AND ND$XXX MUST SURROUND
                     THE DECKS OF EACH PRODUCT (NIP, NVF, ETC.).  SOME OF 
                     THESE DECKS ARE MISSING.  ALSO, THE ND$TVF DECK IS IN THE
                     WRONG PLACE. 
          SOLUTION - ADD ST$XXX AND ND$XXX DECKS FOR NIP, AIP, AND DLFP.
                     CHANGE THE ND$TVF DECK TO BE AFTER THE CWEOR INSTEAD OF
                     BEFORE IT. 
          PAM    1/2/85      NIPDEF,AIPDEF,DLFPDEF,PIP,ND$TVF 
 NA5A938  CS ABORTS AT INITIALIZATION TIME WITH THE MESSAGE --
          BAD NCF READ.  A RECORD WAS READ THAT CS WAS NOT
          EXPECTING.
  
          CODE WAS GENERATED TO DO ALL CIO READS WITH RECALL. 
          ALSO DEBUG CODE WAS ADDED TO SAVE THE RELATIVE PRU
          ADDRESS BEFORE INVOKING THE CIO RANDOM READ REQUEST.
  
          THIS CODE ASSUMES THAT PSR IDENT NA5A079 IS ALREADY 
          INSTALLED.
  
          DKE     84/10/25     CSIBXT 
 NA5B050  PROBLEM  - WHEN NVF PROMPTS FOR A USER'S PASSWORD, IT DOES
                     NOT OVERSTRIKE THE INPUT FIELD ON A TEKTRONIX 4014 
                     TERMINAL.
          ANALYSIS - NVF ONLY OVERSTRIKES THE INPUT FIELD FOR HARDCOPY
                     TERMINALS -- M33 AND 2741 TERMINAL CLASSES.
                     ALTHOUGH THE TEKTRONIX 4014 IS NOT A HARDCOPY
                     TERMINAL, IT BEHAVES THE SAME WAY AS A HARDCOPY
                     TERMINAL IF THE INPUT FIELD CONTAINS OVERSTRIKES,
                     I.E. IT DOES NOT LET YOU SEE THE PASSWORD BEING
                     TYPED IN.
          SOLUTION - CHANGE NVF TO OVERSTRIKE THE INPUT FIELD FOR A 
                     TEKTRONIX 4014 TERMINAL. 
          PAM     84/10/24     MISCOM,NVFTILP 
 NA5B068  SHOST PARAMETER SHOULD ACCEPT UP TO A 
          MAXIMUM OF 6 HEX DIGITS. FIXED BY CHANGING
          THE SIZE OF THE RANGE CHECK ARRAY FROM 65 TO 66 
          IN NDLCKRG. 
          YCY     84/11/27     NDLCKRG
 NA5B071  NDLP NOW DEFAULTS THE DUMP FLAG IN THE NPU
          CROSS REFERENCE TABLE TO BE TRUE, SO THAT A DUMP IS 
          ALWAYS TAKEN IF AN NPU IS GETTING RELOADED. 
          YCY     84/11/14     NDLNFNT
 NA5B072   THIS MOD PREVENTS NIP FROM ABORTING WITH BUFFER MANAGEMENT 
           ERROR WHEN APPLICATION SENDS CON/END/R THAT IS 1 WORD LONG.
           ERR/LGL/SM WITH RC=14 WILL BE SENT TO APPLICATION IF 
           CON/END/R TEXT IS LESS THAN 2. 
  
           SET REASON CODE OF CON/END/N TO 0 OR 1 OR 2 ACCORDINGLY. 
           0 - NORMAL LENDING CONFIRMATION. 
           1 - NO FORWARDING INDICATION. SECONDARY LOANED A LOANED CONN.
           2 - APPL. TRIED TO LEND AN A-A CONNECTION. NORMALLY
               TERMINATE THE CONNECTION.
           LTN      84/11/21       HCRRCNR,HPPUT,SMAPDEF
  
 NA5B074  PROBLEM  - NVF ABORTED WITH THE MESSAGE, "NVFTDSP - CANNOT
                     FIND AST ENTRY FOR APPL".
          ANALYSIS - IF NVF COULD NOT FIND THE APPL NAME IN THE AST TABLE,
                     THIS WAS CONSIDERED AN INTERNAL ERROR, AND NVF WOULD 
                     ABORT.  THE FEATURE CODE FOR ENHANCED APPL SWITCH
                     ERRONEOUSLY CHANGED THIS LOGIC TO HAVE NVF ABORT NOT 
                     ONLY IF THE APPL NAME WAS NOT FOUND, BUT ALSO IF 
                     THE APPL HAD NOT YET NETTED ON.  THIS LATTER 
                     CONDITION IS NOT AN INTERNAL ERROR, AND IN FACT, 
                     CAN HAPPEN QUITE FREQUENTLY. 
          SOLUTION - CHANGE NVF TO ONLY ABORT IF THE APPL NAME IS NOT 
                     FOUND IN THE AST TABLE (THE WAY IT USED TO BE).
          PAM     84/11/26     NVFTDSP
 NA5B076  NIP SHOULD NOT SET BLOCK TYPE TO NULL WHEN IBU IS SET.
          LTN       85/01/08       HPGET
  
 NA5B089  NIP WILL COPY FROM WORD 2 OF TEXT BUFFER OF CON/END/R 
          TO WORD 3 OF CR/RCN/R BUFFER. 
          LTN       84/12/03       HCRRCNR
  
 NA5B114  PROBLEM  - A QTGET CALL CHANGED THE VALUE OF THE CHARACTER-SET
                     FIELD IN THE NETWORK INFORMATION TABLE.  ALTHOUGH
                     THE DOCUMENTATION DOES NOT STATE THAT QTRM WILL NOT
                     OVERWRITE THIS FIELD, TEST APPLICATIONS HAVE BEEN
                     WRITTEN ASSUMING QTRM WILL NEVER CHANGE THE VALUE
                     STORED IN THIS FIELD.
          ANALYSIS - QTGET WAS CHANGED IN THE LATEST SYSTEM TO CALL 
                     QTTIP TO SEND SYNCHRONOUS SUPERVISORY MESSAGES.
                     THIS REQUIRED QTGET TO STORE THE CHARACTER SET 
                     TYPE FOR SYNCHRONOUS SUPERVISORY MESSAGE IN THE
                     CHARACTER-SET FIELD OF THE NETWORK INFORMATION 
                     TABLE. 
          SOLUTION - QTGET HAS BEEN CORRECTED TO SAVE THE VALUE IN THE
                     CHARACTER-SET FIELD BEFORE IT OVERWRITES IT AND
                     RESTORE THE FIELD AFTER THE QTTIP CALL.
          EG     12/17/84    QTGET
 NA5B115  CHECKMARK RESTART FOR PRU MODE FILE TRANSFER DOES NOT WORK. 
  
          FOR CHECKMARK RESTART CAPABILITY PIP MUST BE ABLE TO CONTROL
          THE MASS STORAGE WRITE ACCESS BY PRU POSITION AS THE PRU
          MODE READ ACCESS CURRENTLY IS.
  
          FOR THIS PURPOSE PIP SETS RANDOM PROCESSING FLAG IN FET WHEN
          A PRU FOR THE FILE TRANSFER IS RECEIVED FROM THE REMOTE.
          WHEN CIO MONITOR FUNCTION IS SENT FOR PRU MODE I/O, PIP PLACES
          CURRENT PRU POSITION IN FET FROM PCNB ALONG WITH RANDOM RE- 
          WRITE REQUEST FLAG. (NOTE: THIS FLAG IS EFECTIVE ONLY FOR 
          WRITE ACCESS AND WHEN RANDOM PROCESSING FLAG IS SET.) 
          ALSO NOTE, THAT PRU POSITION FOR MASS STORAGE READ ACCESS IS
          PLACED THERE NOW. 
          THAT THE NEXT PRU POSITION IS SAVED IN PCNB WHEN A PRU BUFFER 
          IS RELEASED IS NOW APPLICABLE TO WRITE ACCESS AS WELL AS TO 
          READ ACCESS.
  
          WHEN A CHECKMARK IS RECEIVED FROM THE REMOTE AND ALL THE
          OUTSTANDING PRUS ARE WRITTEN TO THE MASS STORAGE, THE CURRENT 
          PRU POSITION IS SAVED IN PCNB AS PENDING POSITION.
          WHEN A CHECKMARK REPLY IS SENT TO THE REMOTE, THE PENDING PRU 
          POSITION IS SAVED IN PCNB AS THE PRU CORRESPONDING TO THE 
          ACKNOWLEDGED CHECKMARK. 
  
          AT RESTART OUTPUT WORKLIST PROCESSING THE GIVEN NEW PRU 
          POSITION IS SAVED IN PCNB AS THE PRU POSITION FOR THE FIRST 
          (ACKNOWLEDGED) CHECKMARK. 
  
          SW     84/12/03    PIP
 NA5B119  PROBLEM  - WHEN A LOANED CONNECTION IS BROKEN, QTRM IS NOT
                     RETURNING A REASON CODE 20 TO THE PRIMARY
                     APPLICATION.  INSTEAD IT IS GETTING A REASON CODE
                     6. 
          ANALYSIS - QTGET IS NOT SETTING THE CORRECT STATE WHEN IT 
                     IS PROCESSING THE CON/END/N SUPERVISORY MESSAGE
                     FOR A CONNECTION IT HAS JUST LOANED.  THIS CAUSES
                     IT TO GENERATE THE WRONG REASON CODE WHEN IT 
                     RECEIVES THE CON/CB SUPERVISORY MESSAGE. 
          SOLUTION - QTGET HAS BEEN CORRECTED TO CHANGE THE CONNECTION
                     STATE TO 'LENT' WHEN IT PROCESSES THE CON/END/N
                     SUPERVISORY MESSAGE FOR A CONNECTION IT HAS JUST 
                     LOANED.
          EG     12/17/84    QTGET
 NA5B122  THIS IDENT ALLOWS AIP TO RETRY SENDING THE NETON
          WORKLIST IF NIP RETURNS REASON CODE ONE IN THE NETON
          STATUS WORD WHILE NAM IS STILL AVAILABLE. 
          YCY     85/01/14     NETON
 NA5B126  PROBLEM  - QTENDT DID NOT REJECT A CALL FOR A CONNECTION THAT 
                     HAD ALREADY BEEN TERMINATED.  ALSO QTENDT DOES NOT 
                     PASS DATA IF IT IS AN SECONDARY APPLICATION. 
          ANALYSIS - QTENDT DID NOT CHECK FOR THE STATE "WAITING FOR
                     CON/END/N" WHEN IT WAS CHECKING THE CONNECTION 
                     STATE.  QTENDT PASSES DATA ONLY IF THE NEXT
                     APPLICATION FIELD WAS NONZERO. 
          SOLUTION - QTENDT HAS BEEN CORRECTED TO CHECK FOR THAT STATE. 
                     QTENDT HAS ALSO BEEN CORRECTED TO NOT REQUIRE THE
                     NEXT APPLICATION FIELD TO BE NONZERO IF IT IS A
                     SECONDARY APPLICATION. 
          EG     12/19/84    QTENDT 
 NA5B132  REG/CP PROCESSOR SHOULD CHECK FOR LOGICAL FAILED FLAG 
          BEFORE RELAESING CONNECTIONS. 
          ALOW CON/END/R TO BE AT LEAST ONE WORD IN TEXT. 
          LTN       84/12/21       NPREGCP,HPPUT
  
 NA5B136  CHANGE NVF TO SEND A CR/RCN/A WITH REASON CODE 26 INSTEAD OF
          REASON CODE 27. 
          PAM     85/01/02     NVFTRLC
 NA5B137   CORRECTLY SEND REASON CODE IN CR/CB/U TO NVF AND CON/CB/U
           TO APPLICATION WHEN LOGICAL LINK HAS FAILED. 
           WHEN ALLOCATING ACNT ENTRY FOR NEW CONNECTION, NIP CHECKS
           THE WHOLE WORD OF ENTRY INSTEAD OF ACNB ADDRESS FIELD TO 
           TO MAKE SURE THIS ENTRY IS AVAILABLE.
           LTN      85/01/15       NPREGLL,NPREGCP,HCSTTP,HALLOCN 
  
 NA5B143  NDLP SHOULD ENABLE USE OF RC PARAMETER
          ON THE LINE STATEMENT. ALSO IT SHOULD PROVIDE 
          LISTINGS SUPPORT FOR THE RC PARAMETER IN THE
          SUMMARY LISITNGS. 
          YCY     85/01/07     NDLSDAT,NDLLIST
 NA50305  THIS IDENT FIXES THE PROBLEM THAT A TRUNK 
          STATEMENT DEFINED AFTER A GROUP STATEMENT MAY 
          GET ERROR 31. THE PROBLEM WAS CAUSED BY THE GROUP 
          INFORMATION NOT CLEARED AFTER THE GROUP STATEMENT.
          BUT SINCE THE TRUNK STATEMENT MAY APPEAR ANYWHERE 
          IN THE NCF, THE GROUP INFORMATION IS NOW CLEARED
          IN STERM FOR A TRUNK STATEMENT AND RESTORED AFTER 
          PROCESSING OF STERM FOR THE TRUNK STATEMENT. THE
          ACTUAL CLEARING OF THE REPEAT INFORMATION OCCURS
          WHERE NDLPSS1 SEES A LINE OR NPU STATEMENT. 
          YCY     84/11/27     NDLPSS1
  
 NA50336  THIS MODSET CORRECTS THE ACCOUNT DAYFILE MESSAGE FORMATS, 
          AND UPDATES THE DOCUMENTATION IN CS TO INCLUDE THE X.25 
          STATISTICS ADDED AT LEVEL 2.3.  WITH THIS MODSET, THE 
          LINE, TRUNK, AND NPU STATISTICS MESSAGES IN THE ACCOUNT 
          DAYFILE AND ERROR LOG HAVE THE FOLLOWING FORMAT:  
  
                 SCLI, NODE, C1, PORT, TTTTTTLLLLLL.
                 SCLI, NODE, C2, SSSSSSCCCCCC.
                 SCLI, NODE, C3, BBBBBBPPPPPPAAAAAA.
  
                 SCTU, NODE, C1, PORT, TTTTTTLLLLLL.
                 SCTU, NODE, C2, SSSSSSCCCCCC.
                 SCTU, NODE, C3, BBBBBB.
  
                 SCNQ, NODE, C1, CCCCCCDDDDDDLLLLLL.
                 SCNQ, NODE, C2, GGGGGGRRRRRRSSSSSS.
                 SCNQ, NODE, C3, PPPPPPIIIIIINNNNNN.
                 SCNQ, NODE, C4, WWWWWW.
  
          DEPENDENCIES:  NA5A394 (INCLUDED IN 2.3) AND NA5A291
          (INCLUDED IN 2.2).  SINCE THIS MODSET AFFECTS THE FORMAT OF 
          THE ERROR LOG MESSAGES ISSUED BY CS, THE CORRESPONDING HPA
          MODSET MUST BE INSTALLED WHEN THIS MODSET IS INSTALLED. 
  
          EMH    10/29/84    CSESES 
  
 FN2430A  MODIFY NS K-DISPLAY PROCESSING TO SEND HELP DISPLAY TO RIGHT
          K-DISPLAY SCREEN WHENEVER K-DISPLAY IS ASSIGNED TO
          APPLICATION.
          EG     12/12/84    NS$STR 
 NA5B121  PROBLEM  - NAM K-DISPLAY CODE FOR HANDLING RIGHT SCREEN HAS 
                     BUGS IN IT.
          ANALYSIS - 1. NIP ROUTINE KHOPDIS RETURNED ERR/LGL TO APP FOR 
                        HOP/DIS THAT WAS CORRECTLY FORMATTED. 
                     2. NIP ROUTINE KHOPDIS FREED UP RIGHT SCREEN BUFFER
                        RIGHT AFTER COMPLETING PROCESSING OF WORKLIST 
                        FROM APPLICATION. 
                     3. NIP ROUTINE KHOPDIS DOES NOT RETURN K-DISPLAY 
                        RIGHT SCREEN BUFFERS. 
                     4. NIP ROUTINE KHOPDIS SETS DISPLAY ADDRESS TO 
                        FIRST WORD OF SUPERVISORY MESSAGE INSTEAD OF
                        FIRST WORD OF DISPLAY TEXT. 
          SOLUTION - 1. NIP ROUTINE KHOPDIS HAS BEEN CORRECTED TO CHECK 
                        FORMAT OF RIGHT DISPLAY DATA CORRECTLY. 
                     2. NIP ROUTINE KHOPDIS HAS BEEN CORRECTED TO 
                        RELEASE THE PARTIAL WORKLIST AFTER PROCESSING 
                        THE RIGHT SCREEN DISPLAY DATA.
                     3. NIP ROUTINE KHOPDIS HAS BEEN CORRECTED TO RETURN
                        THE PREVIOUS RIGHT SCREEN BUFFER BEFORE 
                        RESETTING THE POINTERS. 
                     4. NIP ROUTINE KHOPDIS HAS BEEN CORRECTED TO SET 
                        THE DISPLAY ADDRESS TO THE FIRST WORD OF DISPLAY
                        TEXT. 
          EG     01/15/85    KHOPDIS
 NA5B144  PROBLEM  - QTRM DID NOT BUILD CORRECT THE CORRECT HOP/DIS 
                     SUPERVISORY MESSAGE. 
          ANALYSIS - QTRM CREATED A HOP/DIS SUPERVISORY MESSAGE THAT
                     WAS ONE WORD SHORTER THAN IT SHOULD BE.  THE SIZE
                     OF THE FRAGMENT BUFFER WAS ALSO TOO LONG.
          SOLUTION - QTSUP HAS BEEN CORRECTED TO BUILD A CORRECT HOP/DIS
                     SUPERVISORY MESSAGE. 
          EG     01/04/85    QTSUP
 NA5B158  PROBLEM  - NIP ALLOCATES MORE PRU BUFFERS THAN IT ACTUALLY
                     NEEDS. 
          ANALYSIS - WHEN NIP CONVERTS A NETWORK CONNECTION INTO A PRU
                     CONNECTION, IT CHECKS IF ANY PRU BUFFERS HAVE BEEN 
                     ALLOCATED YET FOR THE PRU SIZE THAT THE CONNECTION 
                     WILL BE USING FOR TRANSFERRING PRU DATA.  IF NONE
                     HAVE BEEN ALLOCATED, NIP WILL ALLOCATE THE MAXIMUM 
                     ALLOWED FOR THAT BUFFER SIZE.
          SOLUTION - NIP HAS BEEN CORRECTED TO ALLOCATE THE MINIMUM 
                     ALLOWED FOR THAT BUFFER SIZE.
          EG     01/15/85    HPRUON 
 NA5B160  PROBLEM  - QTGET TERMINATED AN A-A CONNECTION WHEN THE OTHER
                     APPLICATION SENT DATA TO THIS APPLICATION. 
          ANALYSIS - QTPUT DID NOT CONVERT THE TEXT LENGTH FROM ACT=4 TO
                     ACT=2 FOR THE A-A DATA.
          SOLUTION - QTPUT HAS BEEN CORRECTED TO CONVERT THE TEXT LENGTH
                     FROM ACT=4 TO ACT=2 FOR A-A DATA.
          EG     01/16/85    QTPUT
 NA5B162  PROBLEM  - HOP/CMD TEXT WAS NOT RETURNED TO QTRM APP. 
          ANALYSIS - QTGET CODE TO COPY TEXT WAS COPYING FROM UNSIGNED
                     INTEGER WORD INTO CHARACTER WORD.
          SOLUTION - QTGET CODE HAS BEEN CORRECTED TO COPY FROM UNSIGNED
                     WORD INTO UNSIGNED WORD. 
          EG     01/16/85    QTGET
 NA5B165  PROBLEM  - THE 2.3 QTRM INITIALIZED THE XSLEEP FIELD IN THE 
                     NETWORK INFORMATION TABLE TO ZERO.  THE 2.4.2
                     QTRM DOES NOT. 
          ANALYSIS - THE CODE TO ZERO OUT THE XSLEEP FIELD IN QTOPEN
                     WAS ACCIDENTALLY REMOVED.
          SOLUTION - QTOPEN HAS BEEN CORRECTED TO ZERO OUT THE FIELD
                     AGAIN. 
          EG     01/16/85    QTOPEN 
 NA5B166  PROBLEM  - QTRM DID NOT SEND THE RO/MARK SYNCHRONOUS SUP MSG. 
          ANALYSIS - THE APPLICATION HAD CURRENT ABL SET TO ZERO WHEN 
                     THE USER BREAK OCCURRED.  THE RO/MARK SUP MSG
                     IS SENT WHEN A FC/ACK SUP MSG IS RECEIVED BY QTRM. 
                     WHEN THE FC/ACK WAS RECEIVED BY QTGET, QTGET CALLED
                     QTTIP TO SEND THE RO/MARK SUP MSG BUT FORGOT TO
                     STORE THE CONNECTION NUMBER IN THE NIT.  QTTIP 
                     REJECTED THE CALL THEN.
          SOLUTION - QTGET HAS BEEN CORRECTED TO STORE THE CONNECTION 
                     NUMBER IN THE NIT BEFORE CALLING QTTIP.
          EG     01/17/85    QTGET
 NA5B173   NIP WILL SEND "(" AND ")" IN HOP/PAGE INSTEAD OF HOP/CMD.
           LTN      85/01/21       KAPPMOD
  
 NA5B180  THIS IDENT ALLOWS NETIO OR NETXIOD TO SAVE THE CURRENT
          FILE TRANSFER TRIGGER IN THE COMMON NX$ACBX.
          WHEN NAM INTERFACE ERROR OCCUR, EVEN FOR A NON-DEBUG
          MFLINK, THE ANALYST CAN TELL WHAT THE LAST PROBLEM
          CAUSING TRIGGER IS. 
          YCY     85/01/23     NX$ACBX, NP$STPR 
 NA50311 THIS FEATURE MOVE BUILD PARAMETER MAXNIP TO NIP
         CONTROL CARD CALL PARAMETER. 
         CYC 11/12/84  DECK INIP
 NA5B171  THIS IDENT ALLOWS USERS TO SPECIFY IMDISC 
          ON A X25 LINE STATEMENT.
          YCY     85/01/25     NDLNFCM
 NA5B182  PROBLEM  - QTRM DOES NOT SET SCT FIELD IN CON/REQ/N 
                     SUPERVISORY MESSAGE. 
          ANALYSIS - NONE NEEDED. 
          SOLUTION = QTGET HAS BEEN CORRECTED TO CLEAR SCT FIELD IN 
                     CON/REQ/N SUPERVISORY MESSAGE. 
          EG     01/25/85    QTGET
 FN2430B  THIS CODE ADDS THE HELP TEXT TO THE RIGHT K-DISPLAY OF NVF. 
          PAM     85/02/04     NVFCPHT,NVFCUHS,NVF,HMSGNVF
 FN2430C  THIS PORTION OF CODE BRINGS IN THE CAPABILITY OF RIGHT HELP 
          K-DISPLAY FOR CS. 
          LTN       85/02/04       TEXTCS,CSCPHT,CSCUHS,CSSROC,SSRRCS 
  
 FN2428    THIS MOD WAS IMPLEMENTED ACCORDING TO PROBLEM LOG ENTRY
           NUMBER 28. MESSAGES DO NOT REQUIRE ANY OPERATOR ACTION WILL
           BE REPORTED TO AUDIENCE GROUP 3; AND INITIAL DEFAULT 
           REPORTING STATUS OF THE HOP IS CHANGED TO OFF. 
           LTN      85/02/11       CSESSM,CSSSNO
  
 NA5B167  SET COUNT VARIABLE COUNTING FROM 1 TO 255 WHEN ALOCATING
          NCNTNCNB ENTRY FOR NEW CONNECTION.
          LTN       85/02/07       HVLLCB 
  
 NA5B187  NDLP SUMMARY LIST PROCESSOR IS NOT INTERPRETING 
          USER STIP PROPERLY. IT ALSO LEAVES AN EXTRA CARRIAGE
          RETURN WHEN IT PRINTS THE OPTIONAL PAD PARAMETER FOR
          THE TERMINAL STATEMENT LIST.
          YCY     85/02/19     NDLLIST,NDLNFCM
 NA5B188  PIP IS NOT PROTECTED FROM A KIND OF BLOCK PROTOCOL ERROR. 
  
          IF NPU STATUS OR MDI GENERAL STATUS STATES THAT AN IVT INPUT
          BLOCK IS AVAILABLE FOR A PRU TYPE INPUT, PIP IS CONFUSED AND
          ABORTS AS A PIP'S FAULT.
  
          PIP SHOULD DETECT THIS SITUATION AND PROCESS IT AS AN INPUT 
          FORMAT ERROR. 
  
          SW     85/02/15      PIP
 NA5B190  APPL NAME STAYED IN K-DISPLAY AFTER APPL
          WAS OVERRIDDEN. THIS TURNED OUT TO BE A NDL 
          PROBLEM THAT APPL NAMES ARE NOT CHECKED 
          AND ERRORED ACCORDINGLY IF THEY EXCEED
          5 CHARACTERS LONG WHEN MXCOPYS SPECIFIED IS 
          GREATER THAN ONE. 
          YCY     85/02/12     ATLCF,ER2CNDL,NDLP2LF
 NA5B194  PROBLEM  - QTLINK REJECTED A BAD QTLINK CALL AND THEN DID 
                     NOT ALLOW ANY FURTHER QTLINK REQUESTS. 
          ANALYSIS - QTLINK DID NOT CLEAR THE A-A REQUEST OUTSTANDING 
                     FLAG WHEN IT REJECTED THE QTLINK REQUEST.
          SOLUTION - QTLINK HAS BEEN CORRECTED TO NOT SET THE A-A 
                     REQUEST OUTSTANDING FLAG UNLESS IT ACCEPTS THE 
                     REQUEST. 
          EG     02/07/85    QTLINK 
 NA5B196  BACKS FOR PRU INPUT BLOCKS NOT SENT WHILE INPUTS OUTSTANDING. 
  
          BACKS FOR PRU INPUT BLOCKS ARE NOT SENT WHILE INPUT BLOCK 
          QUEUE IS NOT EMPTY. 
  
          PIP IS CHANGED TO SEND OUTSTANDING BACKS REGARDLESS OF THE
          INPUT BLOCK QUEUE.
  
          SW     85/02/18    PIP
 NA5B200  PROBLEM  - NIP FAILED WITH A MONITOR CALL ERROR AFTER AN A-A
                     FILE TRANSFER TERMINATED.
          ANALYSIS - NIP ROUTINE NPPCT HAD BEEN CALLED TO PROCESS THE 
                     TERMINATION OF AN A-A FILE TRANSFER CONNECTION.
                     WHEN NPPCT TRIED TO RETURN THE FILE BACK TO THE
                     APPLICATION, IT GOT A SST RC=2.  IN RESPONSE TO
                     THIS, NPPCT DISCONTINUED PROCESSING THE
                     TERMINATION.  UNFORTUNATELY NPPCT HAS SET THE
                     PIP INTERLOCK FOR ONE OF THE TWO PIPS THAT WAS 
                     RUNNING AND EXITED WITHOUT CLEARING THAT INTERLOCK.
                     THE NEXT TIME NIP WANTED TO SET THE INTERLOCK, IT
                     WAS FOR GARBAGE COLLECTION SO NIP NEEDED TO SET
                     THE INTERLOCK FOR ALL PIPS.  WHEN THE NIP ROUTINE
                     MSETIL SAW THAT THE INTERLOCK WAS ALREADY SET FOR
                     THE FIRST PIP, IT ASSUMED THE INTERLOCK WAS ALREADY
                     SET FOR ALL PIPS AND EXITED.  THE GARBAGE
                     COLLECTION ROUTINE THEN MOVED THE PRU BUFFERS
                     EVEN THOUGH THE SECOND PIP WAS NOT INTERLOCKED.
                     THIS RESULTED IN THE PIT TABLE ENTRY FOR THE SECOND
                     PIP TO CONTAIN SOME BAD POINTERS, WHICH THEN CAUSED
                     NIP TO OVERWRITE RA+0 AND RA+1, WHICH CAUSES A 
                     MONITOR CALL ERROR.
          SOLUTION - NIP ROUTINE NPPCT HAS BEEN CORRECTED TO RELEASE THE
                     PIP INTERLOCK IF IT GETS A SST RC=2 FROM THE 
                     OPERATING SYSTEM WHEN IT TRIES TO RETURN THE FILE
                     TO THE APPLICATION.
          EG     02/12/85    NPPCT
 NA5B201  PROBLEM  - CDCNET APPLICATION NETFS WAS RECEIVING NULL BLOCKS 
                     IN RESPONSE TO NETGETL CALLS EVEN THOUGH NIP HAD 
                     DATA QUEUED FOR IT.
          ANALYSIS - NIP HAD NOT UPDATED THE DELIVERABLE DATA BIT IN
                     AIP'S FIELD LENGTH.  THIS WAS DUE TO NIP ROUTINE 
                     HSWACNB CALLING HUPDTDB TO UPDATE THE DELIVERABLE
                     DATA BIT WHILE THE ACNB FLAGS FOR LIST PROCESSING
                     HAD NOT BEEN UPDATED.  THIS RESULTED IN HUPDTDB
                     DECIDING THAT THE DELIVERABLE DATA BIT DID NOT NEED
                     TO BE UPDATED WHEN IT FACT IT SHOULD HAVE BEEN.
          SOLUTION - HSWACNB HAS BEEN CORRECTED TO CALL HUPDTDB AFTER 
                     THE ACNB FLAGS HAVE BEEN UPDATED.
                     HUPDTDB IS DOING IT ANYWAY.
          EG     02/14/85    HSWACNB
 NA5B204  FOR USER DEFINED TERMINALS, W, CTYP AND NCIR
          MAY BE LEFT OUT WITHOUT GETTING WARNING MESSAGES FROM 
          NDLP SO THAT THE USER WILL NOT BE FORCED TO SPECIFY 
          THESE PARAMETERS, WHICH SOMETIMES CAUSES CONFIGURATION
          ERRORS WITH THE REVERSE HASP TIP. 
          YCY     85/02/15     NDLNFCM
 NA5B206  PRU FILE TRANSFER RESTART REQUEST FROM RECEIVER NOT ACCEPTED. 
  
          RESTART REQUEST FROM RECEIVER FOR PRU MODE FILE TANSFER IS NOT
          ACCEPTED BY THE SENDING PIP.
  
          PIP IS MODIFIED TO ACCEPT THE RESTART REQUEST AFTER A CHECK 
          FOR THE VALID RESTART POINT.
  
          SW     85/02/12    PIP
 NA50353  FOR HASP DEVICES, THE VALUE OF UBL SPECIFIED
          CAN BE BETWEEN 1 AND 31 DECIMAL FOR CONSOLE DEVICES,
          AND CAN BE BETWEEN 1 AND 7 FOR BATCH DEVICES RESPECTIVELY.
          YCY     85/02/15     NDLNFCM,NDLLIST
 FN2418   THIS CODE IMPLEMENTS THE LD PARAMETER FOR EN/DI TRUNKS
          ACCORDING TO PROBLEM LOG ENTRY 18.
          LTN       85/02/14       CSSM,CSSROC,CSSADI,CSSAEN
  
 NA5B185  PROBLEM  - NIP SWAPPED OUT APPLICATION EVEN THOUGH IT HAD DATA
                     QUEUED FOR IT. 
          ANALYSIS - NIP ROUTINE HPWAIT WILL SWAP OUT AN APPLICATION ON 
                     A NETWAIT REQUEST IF IT HAS NO SUPERVISORY MESSAGES
                     QUEUED.  HAVING DATA MESSAGES QUEUED DOES NOT MAKE 
                     ANY DIFFERENCES. 
          SOLUTION - NIP ROUTINE HPWAIT HAS BEEN CORRECTED TO NOT SWAP
                     THE APPLICATION IF IT HAS DATA QUEUED. 
          EG     02/22/85    HPWAIT 
 NA5B207  PROBLEM  - WHEN A USER ATTEMPTED TO SWITCH TO IAF FROM ANOTHER
                     APPLICATION, THE MESSAGE "ILLEGAL APPLICATION" WAS 
                     RETURNED.
          ANALYSIS - NVF WAS SETTING THE LOAN STATUS FIELD IN THE CR/SWH
                     TO THE VALUE OF THE REASON CODE FROM THE CR/RCN, 
                     EVEN IF IT WAS NOT A LOAN CONNECTION.  IAF WAS 
                     THEN REJECTING THE CON/REQ BECAUSE OF THE ILLEGAL
                     VALUE IN THE LOAN STATUS FIELD.
          SOLUTION - NVF WILL ONLY SET THE LOAN STATUS FIELD IF IT IS 
                     INDEED A LOAN CONNECTION.
          PAM     85/02/25     NVFTDSP
 NA5B214  THIS MODSET UPDATES THE IMS FOR AIP FROM 2.3 TO 2.4.2 
          LEVEL.
          YCY     85/02/22     NP$DATA,NP$SENF,NP$RECV
                               NP$SMSG,NP$STPR,NP$BTO8
 NA50358  DEFINE ADDITIONAL 4 WORDS TO NPUCB ARRAY, AND ZERO THESE
          WORDS IN INITIALIZATION ROUTINE.
          LTN       85/02/26       TEXTCS,CSIBXT
  
 NA50366  SELF LOADING NPU'S DO NOT USE CCP SO CS DOES NOT NEED TO CHECK
          FOR CCP VERSION BEFORE GRANTING SUPERVISION.
          LTN       85/02/26       CSSANS 
  
 NA50370  THIS IDENT CHANGES THE FV VALUE FOR OP
          ON THE DEVICE STATEMENT SUCH THAT IT IS 0 FOR 
          PRINTER AND 1 FOR DISPLAY.
          YCY     85/02/22     NDLNFCM,NDLLIST,NDLPSS1
 FC24N02  PROVIDE INCOMING CALL DATA FOR PAD SUBTIP TYPE CONNECTIONS
  
          THIS MODSET IS THE NAM PORTION OF THE FEATURE THAT PROVIDES 
          INCOMING CALL DATA FOR PAD SUBTIP TYPE CONNECTIONS.  NIP WILL 
          RECEIVE THE CALLING AND CALLED DTE ADDRESS, FACILITIES CODES, 
          AND CALL USER DATA FROM CCP IN THE ICN/TE SM AND PASS IT
          TO NVF IN THE CR/ITE SM.
  
          LAE            01/15/85           SMDEF, SMNIP, SMNVF.
                                            HCRITER.
  
 NA5B085  PRU MODE FILE TRANSFER GETS LEVEL 7 HEADER FORMAT ERROR.
  
          SOMETIMES CIO REQUEST TO READ CONTROL WORD IS COMPLETED 
          WITH NO DATA IN THE BUFFER EVEN WHEN FILE POSITION IS NOT 
          AT EOI. 
          PIP FAILS TO PROCESS THIS SITUATION AND SENDS TWO BLOCKS
          WITH SAME BLOCK NUBMER. 
  
          PIP IS MODIFIED TO INCREMENT BLOCK NUMBER EVEN AFTER IT 
          SENT A NULL BLOCK.
  
          SW     85/02/28    PIP
 NA5B153  THIS IDENT FIXES THE PROBLEM THAT SOMETIMES 
          WHEN CONNECTION IS REJECTED BY A T-A APPLICATION, 
          NVF GENERATES "ILLEGAL APPLICATION" MESSAGE RATHER
          THAN "USER ACCESS NOT POSSIBLE - CONTACT NETWORK
          ADDMINSTRATION.". 
          YCY     85/02/27     NVFTDAD
 NA5B212  PRU MODE FILE TRANSFER GETS NETXFER ERROR 21. 
  
          IF THE PRU MODE FILE TRANSFER REACHES EOI WITH AN EXACT 
          MULTIPLE OF 64 CM WORDS IN THE BUFFER AND MORE THAN 66
          CM WORDS STILL REMAINING AVAILABLE, PIP MISSES THE EOI
          CONDITION AND RESULTS IN NETXFER ERROR 21.
  
          CHECKING FOR FULL PRUS IN THE BUFFER BY PIP IS NOT VALID
          AND SHOULD BE REMOVED.
  
          SW     85/03/1     PIP
 NA50365  THIS IDENT FIXES THE PROBLEM THAT FOR 
          ACCOUNT MESSAGE ABER, THE PASSWORD IS MISSING.
          YCY     85/02/27     NVFTIAM
 NA5B159  WHEN NVF FORMATS THE VCB FOR THE PASSIVE
          DEVICES, IT DID NOT PASS THE APPLICATION NUMBER TO
          THEM CORRECTLY. HENCE PASSIVE DEVICES DID NOT SHOW
          UP ON THE K DISPLAY WHEN USER PERFORMS A
          K.ST,TES,AP=ANAME.  GARBAGE APPLIATION NAMES
          ARE ALSO CAUSED BY THIS PROBLEM.
          THIS PSR ALSO CONTAINS CODE FOR FIXING NA5A514
          WHERE DEVICES TYPES FOR CR AND LP WERE REVERSELY
          DISPLAYED.
          YCY     85/03/19     NVFTDSP,NVFOFVD
 NA5B169  THIS IDENT FIXES THE SLOW REPONSE TIME WHEN 
          NVF SWITCHES A CONNECTION TO A NEW APPLICATION. 
          INSTEAD OF DOING AN UNFORCED NETWAIT WHEN THERE 
          IS NOTHING FOR NVF TO DO. NVF CHECKS IF MSG OF BLKS 
          HAVE BEEN NETPUT, AND IF SO A DELAY FOR 700 MILLISECONDS
          IS PERFORMED. WHEN THE TIMER EXPIRES AND NVF HAS NOTHING
          TO DO, IT WILL THEN DO AN UNFORCED NETWAIT. 
          YCY     85/03/13     TEXTSS,SSACNI,SSSWNR 
 NA5B202  STARTUP FILE SUPPORT FOR NEW NETLS FLUSH COUNT PARAMETER. 
  
          RWH            03/06/85       NWINIT,NWRESTRT,NWRECOVR, 
                                        NWMULTI,NWMINIT,NWMRECOV
  
 NA5B205  PROBLEM  - PIP ERROR 91 OCCURS WHEN PIP GETS CONFUSED FILLING 
                     THE PRU BUFFERS. 
          ANALYSIS - BECAUSE OF THE SIZE OF THE PRU BUFFERS, PIP ROUTINE
                     IPD GETS CONFUSED WHEN IT RECEIVES A BLOCK THAT
                     EXACTLY FITS THE BUFFER SIZE.
          SOLUTION - NIP HAS BEEN CORRECTED TO ALLOCATE PRU BUFFERS THAT
                     ARE ONE WORD SMALLER.
          EG     03/04/85    HPRUON, XCHKABC
 NA5B211  STARTUP FILE SUPPORT FOR NEW NIP *INACT* PARAMETER. 
  
          RWH            03/06/85       NWINIT,NWRESTRT,NWRECOVR, 
                                        NWMULTI,NWMINIT,NWMRECOV, 
                                        JOBNIP
  
 NA5B220  PROBLEM  - NIP FAILED WITH FREE CHAIN ERROR MESSAGE.
          ANALYSIS - THE TOTOL NUMBER OF FREE WORDS DID NOT MATCH THE 
                     TOTAL NUMBER OF FREE BUFFER SPACE.  THIS WAS DUE 
                     TO ONE OF THE FREE BUFFERS HAVING ITS SIZE 
                     DECREMENTED BY ONE.  THIS OCCURRED WHEN XSACB WAS
                     CALLED TO PROCESS THE NETON OF AN APPLICATION THAT 
                     WAS REJECTED BY NVF.  THE PROCESSING THAT RESULTED 
                     CAUSED THE AT TABLE TO BE SHRUNK.  HOWEVER, AFTER
                     THE TABLE WAS SHRUNK, XSACB CONTINUED PROCESSING 
                     AS IF THE TABLE WAS STILL THE SAME SIZE AND
                     OVERWROTE THE SIZE FIELD OF THE FREE BUFFER. 
          SOLUTION - NIP ROUTINE XSACB HAS BEEN CORRECTED TO DISCONTINUE
                     PROCESSING AFTER THE AT TABLE IS SHRUNK. 
          EG     03/16/85    XSACB
 NA5B221  PROBLEM  - NAM FAILED WITH CPU ERROR EXIT.
          ANALYSIS - NAM HAD LEFT 10 BUFFERS LYING AROUND THAT HAD ZERO 
                     SIZE AND BELONGED TO NO ONE.  ONE OF THESE BUFFERS 
                     HAD THE WORD IN FRONT OF IT USED AS THE FIRST WORD 
                     OF A USED BUFFER.  THIS RESULTED IN A NIP GARBAGE
                     COLLECTION ROUTINE MOVING MOST OF NIP'S MEMORY TILL
                     IT WENT BEYOND NIP'S FIELD LENGTH WHICH RESULTED 
                     IN THE FAILURE.
          SOLUTION - NIP ROUTINE HPNON HAS BEEN CORRECTED TO RESTORE
                     THE NWL BLOCK SIZE VALUE IN THE NWL IF IT
                     TERMINATES ABNORMALLY AND NIP ROUTINE XABTAPP IS 
                     CALLED.
          EG     03/04/85    HPNON
 NA5B223  PROBLEM  - NVF ABORTED WITH THE MESSAGE "NVFDDNT - SM NOT 
                     ROUTED.  THIS HAPPENED BECAUSE NVF RECEIVED AN 
                     ERR/LGL FROM NIP.
          ANALYSIS - NVF RECEIVED AN ERR/LGL BECAUSE AFTER RECEIVING
                     A CR/RCN FOR A LOAN-TYPE CONNECTION, IT SENT OUT 
                     A CR/RCN/N AND A CR/RCN/A.  THE CR/RCN THAT NVF
                     RECEIVED WAS IN LIMBO STATE.  AFTER NVF SENT OUT 
                     THE CR/RCN/N IT SHOULD HAVE SENT OUT A CR/SWH TO 
                     SWITCH THE CONNECTION BACK TO THE PRIMARY APPL.
                     NVF WAS CHECKING THE WRONG FIELD TO DETERMINE IF 
                     THE SWITCH SHOULD BE SENT, SO INSTEAD OF A 
                     CR/SWH, NVF SENT OUT AN ERRONEOUS CR/RCN/A.
          SOLUTION - CHANGE NVF TO CHECK FOR A LOAN-TYPE CONNECTION 
                     BY CHECKING THE REASON CODE ON THE CR/RCN INSTEAD
                     OF CHECKING THE PTA$LCF FLAG.
          PAM     85/03/18     NVFTRCN
 NA5B233  PRU MODE FILE TRANSFER SOMETIMES LOSES EOF PRU. 
  
          PRU MODE FILE TRANSFER SOMETIMES GETS NETXFER ERROR 25, OR
          LOSES EOF PRUS IF NA5B085 IS INSTALLED. 
          CIO REQUEST CODE FOR READ CONTROL WORD FROM PIP IS UNDER A
          CERTAIN CIRCUMSTANCE SENT WITH LEVEL NUMBER OF 17B INCLUDED 
          IN THE REQUEST CODE THAT CAUSES EOF PRU READ WITH NO DATA 
          IN THE CIO BUFFER.
  
          READ CONTROL WORD CIO REQUEST MUST BE SENT WITH NO LEVEL
          NUMBER IN IT TO GET PRU CONTROL WORDS REGARDLESS OF THE 
          PRU LEVEL.
  
          SW     85/03/06    PIP
 NS5B245  PROBLEM  - NS ABORTED WHEN IT DETECTED A BAD DIRECTORY FOR THE
                     NLF. 
          ANALYSIS - NS THOUGHT IT HAD READ UP THE DIRECTORY FOR THE NLF
                     WHEN IT FACT IT WAS PART OF THE NCF DIRECTORY.  NS 
                     ASSUMED THAT READW WOULD RETURN CONTROL TO THE 
                     PROGRAM ONLY AFTER ALL THE NCF DATA HAD BEEN READ
                     INTO THE WORKING STORAGE AREA. 
          SOLUTION - NS HAS BEEN CORRECTED TO DOUBLE THE SIZE OF THE CIO
                     BUFFER SO THAT THE READW WILL COMPLETE BEFORE
                     CONTROL IS RETURNED TO NS. 
          EG     03/18/85    NS$NSI 
 NA5B246  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT.
          ANALYSIS - NIP ROUTINE MGETS HAD BEEN CALLED TO ALLOCATE A
                     LARGE BUFFER (5560B WORDS LONG).  SINCE NONE OF
                     THE EXISTING BUFFERS WERE LARGE ENOUGH, MORE 
                     MEMORY WAS REQUESTED.  THE CODE ASSUMES THAT 
                     IF MORE MEMORY IS REQUESTED, THEN AFTER THE MEMORY 
                     IS ALLOCATED, THERE IS ENOUGH BUFFER SPACE TO
                     SATISFY THE REQUEST.  IT WAS NOT, AND THIS CAUSED
                     NIP ROUTINE MSEIZE TO REFERENCE AN ADDRESS OUTSIDE 
                     THE FIELD LENGTH OF THE PROGRAM. 
          SOLUTION - NIP SHOULD NEVER BE REQUESTING A BUFFER 5560 WORDS 
                     LONG.  THE BUFFER WAS TO BE USED FOR THE ACNT TABLE
                     FOR NVF.  THE ACNT TABLE WAS LARGE BECAUSE NIP WAS 
                     NOT INCREMENTING THE NUMBER OF FREE ENTRIES IN THE 
                     TABLE WHENEVER IT RELEASED AN CONNECTION NUMBER. 
                     NIP ROUTINE HBSTTP HAS BEEN CORRECTED TO INFORM
                     NIP ROUTINE RELACNB TO DO THAT.
          EG     03/18/85    HBSTTP 
 NA5B231  PROBLEM  - AIP RETURNED NETON REJECT RC=1 TO APPLICATION EVEN 
                     THOUGH NAM WAS AVAILABLE.
          ANALYSIS - IF NAM DOES NOT HAVE A BUFFER AVAILABLE FOR AN 
                     INCOMING WORKLIST WHEN THE APPLICATION TRIES TO
                     NETON, AIP WILL CLEAR THE NAM AVAILABLE FLAG.
                     THIS CAUSES AIP TO NOT RETRY THE NETON BUT RATHER
                     TO RETURN A NETON REJECT RC=1 TO THE APPLICATION.
          SOLUTION - AIP ROUTINE NP$XFER HAS BEEN CORRECTED TO NOT CLEAR
                     THE NAM AVAILABLE FLAG UNLESS NAM IS REALLY NOT
                     THERE. 
          EG     03/04/85    NP$XFER
 NA5B249  PROBLEM  - WHEN USERS LOG IN WITH A BLK BLOCK AND A MSG BLOCK 
                     (INSTEAD OF JUST A MSG BLOCK), THE USER WILL 
                     SOMETIMES GET CONNECTED UNDER THE WRONG USER NUMBER. 
          ANALYSIS - IF A USER SENDS THE BLK BLOCK PART OF THE LOGIN AND
                     THEN GETS TIMED OUT OR DISCONNECTED BEFORE THE MSG 
                     BLOCK COMES IN, THE BLK BLOCK WILL REMAIN IN THE 
                     <IWBQ>.  THEN IF ANOTHER USER TRIES TO LOGIN WITH
                     THE SAME CONNECTION NUMBER, THE FIRST USER'S LOGIN 
                     BLK BLOCK WILL BE USED.
          SOLUTION - WHEN NVF ISSUES A CR/TRM, CHECK IF THE ACN$BLKF FLAG 
                     IS SET (INDICATING THAT A BLK BLOCK IS WAITING IN
                     THE <IWBQ>), AND IF SO, FIND AND DELETE THE BLK
                     BLOCK.  THIS CODE IS FOR 2.3/2.4 COUNTERPART TO
                     NA50345. 
          PAM     85/03/20     NVFCTRM
 NA5B251  THIS IDENT FIXES ONE OCCASION WHEN THE FILE TRANSFER PROCESS
          ERRORS EXIT WITH "NAM INTERFACE ERROR". 
  
          PROBLEM: WHEN THE REMOTE HOST WAS TAKEN DOWN, THE REMOTE PIP
                   SENT FT/OFF TO THE RECEIVING PIP WHEN THE RECEIVING
                   AIP WAS STILL IN DATA PHASE. 
  
          SOLUTION: DEFINE FT/OFF TRIGGERS IN THE DATA STATE OF PRU 
                    SENDER AND DO THE SAME OF ALL THE STATES THAT 
                    MIGHT HAVE BEEN TRANSFERRED TO FROM THE 
                    DATA STATE DUE TO AN ERROR CONDITION INFORMED 
                    XFTIER (PIP TO AIP) 
          YCY     85/03/22     NP$STTP
 NA5B142  PROBLEM  - SOMETIMES BEFORE NVF PUTS OUT THE BANNER, A
                     MESSAGE LEFT OVER FROM A PREVIOUS CONNECTION 
                     WOULD APPEAR.
          ANALYSIS - IF A CONNECTION WAS BEING TERMINATED BY NVF AND
                     THEN GOT HUNG BEFORE THE TERMINATION WAS COMPLETE, 
                     ANY MESSAGES FROM NVF FOR THAT CONNECTION WOULD
                     STILL BE IN NVF'S TABLES.  THEN, AFTER THE 
                     CONNECTION WAS TIMED OUT, IF ANOTHER CONNECTION
                     COMES IN WITH THE SAME CONNECTION NUMBER, THE
                     LEFTOVER MESSAGES WOULD BE SENT TO THAT CONNECTION.
          SOLUTION - WHEN A CONNECTION TIMES OUT, IF IT IS IN A 
                     "TERMINATE PENDING" STATE, NVF WILL DELETE ANY 
                     DATA MESSAGES FOR THAT CONNECTION. 
          PAM     85/04/02     NVFCUFS
 NA5B222  PROBLEM  - NVF IS ABORTED BY NOS WHEN NAM IS BROUGHT DOWN 
                     WITH THE ID,HOST COMMAND.
          ANALYSIS - WHEN NVF NETS OFF, NIP GOES AWAY WITHOUT CLEARING
                     THE LONG AND SHORT TERM CONNECTIONS IT HAS WITH
                     NVF.  THIS CAUSES NVF TO GET ABORTED BY NOS. 
          SOLUTION - NIP ROUTINE HPNOFF HAS BEEN CORRECTED TO CLEAR 
                     THE LONG AND SHORT TERM CONNECTIONS IT HAS WITH
                     NVF BEFORE GOING AWAY. 
          EG     03/29/85    HPNOFF 
 NA5B224  PROBLEM  - NVF ABORTED WHEN IT RECEIVED A CR/CB WITH THE WRONG
                     VCB ORDINAL. 
          ANALYSIS - NIP HAD CALLED GARBAGE COLLECTION AND A OLD ACNB 
                     THAT SHOULD NOT HAVE EXISTED WAS RECONNECTED TO
                     THE ACNT TABLE.  THE BAD ACNB HAD AN OLD VCB 
                     ORDINAL THAT WAS NOT THE SAME AS THE VCB ORDINAL 
                     OF THE REAL ACNB FOR THAT CONNECTION.  WHEN THE
                     REAL CONNECTION WAS TERMINATED, NIP USED THE OLD 
                     VCB ORDINAL FROM THE OLD ACNB. 
                     THE OLD ACNB WAS SUPPOSED TO HAVE BEEN RELEASED. 
                     IT WAS NOT BECAUSE AN APPLICATION WITH THE SAME
                     APPLICATION NUMBER HAD PREVIOUSLY NETTED OFF AND 
                     WHEN IT DID, ITS TERMINAL CONNECTION WAS NOT 
                     RECONNECTED TO NVF.  INSTEAD, THE APPLICATION'S
                     CONNECTION WAS LEFT IN LIMBO ALONG WITH ITS
                     CORRESPONDING ACNB.  THIS WAS DUE TO THE HIGHEST 
                     CONNECTION NUMBER FIELD IN THE ACNT BEING
                     INCORRECT.  THIS WAS DUE TO THE CONNECTION TABLE 
                     NOT INCLUDING A ENTRY FOR THE LOANED CONNECTION. 
          SOLUTION - NIP ROUTINE RELACNB HAS BEEN CORRECTED TO CHECK
                     FOR LOANED CONNECTIONS IN DETERMINING HOW MUCH OF
                     THE ACNT TABLE CAN BE SHRUNK.
          EG     04/18/85    RELACNB
 NA5B225  ADD *CDCNET* PARAMETER TO STARTUP FILE AND *COLLECT*
          TO ALLOW TWO *COLLECT* BINARIES IN SYSTEM OR LIBRARY. 
  
          RWH            03/18/85       JOBCOL,COLLECT
  
 NA5B227  PROBLEM  - NIP ABORTED WITH THE ERROR MESSAGE - MGETC/MAXFL 
                     REACHED. 
          ANALYSIS - NIP ROUTINE MGETS WAS UNABLE TO SATISFY A BUFFER 
                     REQUEST.  THIS WAS BECAUSE NIP WAS ALREADY AT ITS
                     MAXIMUM FIELD LENGTH AND NONE OF THE EXISTING
                     FREE BUFFERS WERE BIG ENOUGH.  THE CONDITION SHOULD
                     NEVER HAVE OCCURRED BECAUSE NIP SHOULD HAVE GONE 
                     INTO REGULATION LEVEL 0.  THE NIP DAYFILE SHOWED 
                     NIP HAD GONE INTO REGULATION LEVEL 0 AND THEN INTO 
                     REGULATION LEVEL 1.  IT SHOULD HAVE GONE BACK TO 
                     REGULATION LEVEL 0 BUT DID NOT DUE TO MGETS NOT
                     CALLING NIP ROUTINE MSTAVF.
          SOLUTION - THE CODE IN NIP ROUTINE MSTAVF TO SET THE
                     REGULATION LEVEL HAS BEEN MOVED TO NIP ROUTINE 
                     MSEIZE.
          EG     03/29/85    MGETC,MSEIZE,MGBGCLT 
 NA5B235  PROBLEM  - NIP DOES NOT UPDATE THE DELIVERABLE DATA BIT WHEN
                     THE TEMPORARY LIST OFF FLAG IS CLEARED FOR A 
                     CONNECTION THAT HAS DATA QUEUED FOR IT.
          ANALYSIS - NIP ROUTINE HPPUT DID NOT CHECK IF THE DELIVERABLE 
                     DATA BIT SHOULD BE SET WHEN IT CLEARED THE 
                     TEMPORARY LIST OFF FLAG. 
          SOLUTION - NIP ROUTINE HPPUT HAS BEEN CORRECTED TO SET THE
                     DELIVERABLE DATA BIT WHEN IT CLEARS THE TEMPORARY
                     LIST OFF FLAG IF DATA IS QUEUED ON THAT CONNECTION.
          EG     03/28/85    HPPUT
 NA5B247  PROBLEM  - PIP IGNORES REGULATION LEVEL 1 AND 2 MESSAGES WHEN 
                     TRANSFERRING PRU DATA. 
          ANALYSIS - NIP ROUTINE NPREGCN IS NOT SETTING THE REGULATION
                     FLAG IN THE PCNB WHEN IT IS PROCESSING THE REG/LL
                     SUPERVISORY MESSAGE.  THIS MEANS THAT PIP DOES NOT 
                     KNOW THAT THE LOGICAL LINK IS IN REGULATION. 
          SOLUTION - NIP ROUTINE NPREGCN HAS BEEN CORRECTED TO SET THE
                     REGULATION FLAG IN THE PCNB WHEN APPROPRIATE.
          EG     03/29/85    NPREGCN
 NA5B252  NIP SHOULD NOT ALLOW DOWNLINE BLOCK WITH ACT = 4 ON A TO A
          CONNECTION. 
          LTN       85/02/29       HPPUT
  
 NA5B257  PROBLEM  - FILE TRANSFER HUNG.
          ANALYSIS - NIP IS SETTING THE LIMIT POINTER IN THE PRU BUFFER 
                     ONE WORD SHORTER THAN IT SHOULD.  THIS IS CAUSING
                     PIP TO NOT BE ABLE TO GET A PRU BUFFER OF THE RIGHT
                     SIZE AND THEREBY IS CAUSING THE FILE TRANSFER TO 
                     HANG.
          SOLUTION - NIP ROUTINE XCHKABC HAS BEEN CHANGED TO SET THE
                     CORRECT ADDRESS FOR THE LIMIT POINTER IN THE FET.
          EG     03/26/85    XCHKABC
 FN2450   SUPPORT OF 8-BIT COUPLER NODE NUMBER (PIP CODE) 
  
          MODIFY NIP CODE TO HANDLE 8 BIT COUPLER NODE NUMBER.
          PIP RECEIVES 8-BIT COUPLER NODE NUMBER FROM EST IN THE REVISED
          FORMAT AND SETS UP CET ENTRIES FOR NIP IN THE REVISED FORMAT. 
          DEDICATED PIPS RECEIVE 8-BIT NODE NUMBERS FROM NIP IN NBT-S 
          IN THE REVISED FORMAT.
  
          EG     03/29/85    CET,NBT, 
          SW     85/04/08    PIP
 NA5B148  WHEN A PRIMARY APPLICATION NETTED OFF AFTER LOANING A 
          T-A CONNECTION THEN NETTED ON AGAIN, IN THE CASE OF THE SECOND
          VERSION OF APPLICATION HAVING THE SAME APPLICATION NUMBER, THE
          LOANED CONNECTION SHOULD NOT BE RETURNED TO THE SECOND VERSION
          AS THE PRIMARY APPLICATION. 
          LTN       85/04/08       HCSTTP 
  
 NA5B155   SET PRIACB VALUE TO ACB ADDRESS WHEN SENDING CON/CB/U TO 
           PRIMARY APPLICATION ONLY.
           LTN      85/04/09       HCONCBU
  
 NA5B239  NVF DOES NOT VALIDATE COLLECT FACILITIES
          CORRECTLY. THE TEMPORARY CODE IN NVF DISALLOWING
          COLLECT IS REMOVED. ALSO, THERE WAS A PROBLEM THAT
          THE VALUE OF FACPARAM WAS NOT STORED CORRECTLY, 
          ASSUMING THAT ALL FACPARAM VALUES SHOULD BE 
          STORED LEFT JUSTIFIED IN THE FACPRAM BUFFER FOR 
          VERIFICATION PURPOSES. ALSO, FAST SELECT AND
          COLLECT FACILITIES ARE SHARING A SINGLE FAC CODE. 
          THIS IS ADJUSTED BY THIS MODSET TOO.
          YCY     85/04/05     NVFARAP
 NA5B272  PROBLEM  - NIP DOES NOT UPDATE THE DELIVERABLE DATA BIT WHEN
                     THE TEMPORARY LIST OFF FLAG IS SET FOR A 
                     CONNECTION THAT HAS DATA QUEUED FOR IT.
          ANALYSIS - NIP ROUTINE HPGET DID NOT CHECK IF THE DELIVERABLE 
                     DATA BIT SHOULD BE CLEARED WHEN IT SET THE 
                     TEMPORARY LIST OFF FLAG. 
          SOLUTION - NIP ROUTINE HPGET HAS BEEN CORRECTED TO CLEAR THE
                     DELIVERABLE DATA BIT WHEN IT SETS THE TEMPORARY
                     LIST OFF FLAG IF DATA IS QUEUED ON THAT CONNECTION.
          EG     03/28/85    HPGET
 NA5B276  THIS IDENT ALLOWS COUPLER NODE NUMBERS
          TO HAVE MAXIMUM VALUE OF 255 DECIMAL. SINCE THE 
          EST ENTRY FOR COUPLER NODE NUMBER IS EXPANDED 
          FROM A 6 BIT TO AN 8 BIT FIELD, THE MAXIMUM 
          VALUE FOR COUPLER NODE NUMBER ON THE COUPLER
          STATEMENT, THE HOST NODE NUMBER ON THE DEVICE 
          AND TERMDEV STATEMENT, THE SOURCE NODE ON THE 
          OUTCALL STATEMENT AND THE DNODE ON THE
          INCALL STATEMENT SHOULD BE ALLOWED A MAXIMUM
          VALUE OF 255. 
          YCY     85/04/05     NDLCKRG,NDLNFNT
 NA5B213  MDI READ ERROR IS NOT CORRECTLY RECOVERED 
  
          AFTER MDI READ ERROR, FUNCTION TO GET MDI GENERAL STATUS
          IS TRIED WITH CHANNEL ACTIVE THAT CAUSES COUPLER ERROR 01.
  
          AT A BLOCK PROTOCOL ERROR FROM MDI, RE-READ IS TRIED BY READ
          ERROR FUNCTION FROM PIP OR AUTOMATICALLY BY MDI.
          AS THE BLOCK SEQUENCE NUMBER IS NOT RESTORED, BLOCK SEQUENCE
          ERROR WILL RESULT AT THE NEXT TRIAL.
  
          AT A BLOCK PROTOCOL ERROR DETECTED IN THE BLOCK HEADER, 
          THE CHANNEL ERROR PROCESSOR IS CALLED TO PROCESS THE ERROR. 
          IF THIS IS A REAL PROTOCOL ERROR, READ ERROR FUNCTION WILL BE 
          REPEATEDLY ISSUED UNTIL THE MAXIMUM RETRY COUNT IS REACHED. 
  
          IF THE FRONT END IS TURNED OFF AFTER A BLOCK PROTOCOL ERROR,
          PIP WILL ABORT NAM.  ERROR CODE MUST BE RESET AFTER THE 
          BLOCK PROTOCOL ERROR MESSAGE IS SENT TO NAM.
  
          SW     85/03/19    PIP
 NA5B269  USING INTEGER INSTRUCTION TO INCREMENT THE NUMBER OF SCP CALL 
          IN OSCCALL
          LTN       85/04/09       OSCCALL
  
 NA5B275  PROBLEM  - IF A USER LOANED A CONNECTION TO A SECONDARY 
                     APPLICATION, THEN THE PRIMARY APPL FAILED, 
                     WHEN THE CONNECTION WAS RETURNED TO THE PRIMARY, 
                     THE USER WOULD BE SENT AN APPLICATION PROMPT.
                     IF THE USER ENTERED "IAF" IN RESPONSE TO THE 
                     APPLICATION PROMPT, IAF WOULD GET AN ERROR.
          ANALYSIS - WHEN NVF TRIED TO SWITCH THE USER TO IAF, IT 
                     PASSED THE LOAN REASON CODE FROM THE CR/RCN TO 
                     IAF IN THE CR/SWH.  IAF DID NOT UNDERSTAND WHY 
                     IT WAS GETTING A LOAN REASON CODE BECAUSE THIS 
                     WAS NO LONGER A LOANED CONNECTION. 
          SOLUTION - IN THE CASE WHERE THE LOAN CONNECTION NO LONGER
                     EXISTS, AS WHEN THE PRIMARY APPL FAILS OR THE
                     SECONDARY APPL ABORTS THE CONNECTION, NVF WILL 
                     NOT PASS ALONG THE LOAN REASON CODE IN THE CR/SWH. 
          PAM     85/04/16     NVFTRVD
 NA5B278  THIS CODE FIXES SOME BUGS IN NA50311. 
          CYC 04/03/85  INIP,ITABS
 NA5B293  PROBLEM  - NVF ABORTED WITH THE MESSAGE "NVFTDSP -- 
                     CANNOT FIND AST ENTRY FOR MAILSRV".
          ANALYSIS - WHENEVER THE LAST APPLICATION IN THE AST TABLE 
                     WAS SELECTED, BECAUSE OF AN ERROR IN THE WAY 
                     NVF SEARCHED THE TABLE, NVF WOULD ABORT BECAUS 
                     IT THOUGHT IT COULD NOT FIND THE APPLICATION IN
                     THE TABLE. 
          SOLUTION - CHANGE THE WAY THAT NVF CHECKS IF THE APPLICATION
                     EXISTS IN THE AST TABLE. 
          PAM     85/04/16     NVFTDSP
 NA5B298  PROBLEM  - QTRM DOES NOT CLEAR THE CURRENT BLOCK LIMIT FIELD
                     IN THE NIT WHEN THE APPLICATION SENDS A DOWNLINE 
                     FC/BRK SUPERVISORY MESSAGE.
          SOLUTION - QTRM HAS BEEN CORRECTED TO CLEAR THE CURRENT BLOCK 
                     LIMIT FIELD. 
          EG     04/23/85    QTGET
 NA5B177  WHEN SECONDARY RETURN LOANED CONNECTION, RESERVED ACN SHOULD
          BE USED.
          LTN       85/04/14       HCSTTP 
  
 NA5B268  AIP HUNG ON NETWAIT.
          THE CONDITION OF THE HANG IS THAT  ATASBI FLAG WAS NOT SET
          AND THE ATASBS FLAG WAS SET.
          HWRAVAL WILL NOT UPDATE THE DATA AVAILABILITY WORD
          OR CALL OSCHAPP TO ISSUE A SWAPIN REQUEST.
          CAUSE:  
          A SHORT NETWAIT CAUSES THE ATASBF FLAG GET SET. 
          A SUPERVISORY MESSAGE (IN THIS CASE, A CONACRA) IS
          LINKED TO THE THE ACB OF THE APPLICATION CONCERNED. 
          THE FIRST UPDATE OF THE DATA-AVALABILITY WORD FAILS.
          OSCHAPP DOES NOT ISSUE A SWAPIN REQUEST BECAUSE 
          ATASBF FLAG IS SET. 
          THE NEXT CALL OF XSACB GOES TO STATE 1, BUT BECAUSE 
          OF THE TIMING, ATASBF, AND ATASBW DO NOT GET CLEARED
          IN STATE 1. THE SECOND UPDATE OF THE DATA-AVAILABILITY
          WORD FAILS TOO. BECAUSE IT IS ONLY CHECKING FOR 
          ATASBR FLAG, IT SETS THE ATASBS FLAG. THIS GENERATES
          THE NECESSARY HANG CONDITIONS.
  
         SOLUTION:  
  
           IN SECTION ENDPROC1 OF XSACB, AFTER THE UPDATE 
           OF THE DATA-AVALABILITY WORD FAILS, IT SHOULD
           CHECK FOR BOTH ATASBR AND ATASBW FLAG NOT SET
           BEFORE IT SETS THE ATASBS FLAG. NOTE, THAT 
           WHEN ATASBF FLAG IS SET, ATASBW FLAG IS ALSO SET.
          YCY     85/04/29     XSACB
 NA5B308  OUTGOING FILE TRANSFER YIELDS PRU BUFFERS TO INCOMING TRANSFER
  
          WHEN FILE TRANSFERS IN BOTH DIRECTIONS ARE ACTIVE IN A PIP, AS
          THE LAST FREE BUFFER IS ONLY ASSIGNED TO THE INBOUND TRANSFER,
          OUTGOING FILE TRNSFERS MAY BE HALTED UNTIL INBOUND TRANSFERS
          END.
          CORRECTIONS ARE MADE NOT TO KEEP ONE LIMBO BUFFER FOR INBOUND 
          TRANSFER WHEN A BUFFER IS ALREADY ASSIGNED FOR AN INBOUND 
          TRANSFER. 
  
          SW     85/04/26    PIP
 NA5B097  PROBLEM  - WHEN DATA WAS PASSED ON A LOANED CONNECTION, 
                     THE DATA WOULD NOT GET TO THE SECONDARY APPL.
          ANALYSIS - NVF WAS NOT MOVING THE DATA PROPERLY FROM THE
                     CR/RCN TO THE TEMPORARY HOLDING AREA TO THE
                     CR/SWH.  ALSO, NIP WAS NOT COPYING THE DATA
                     BUFFER FROM THE CON/END TO THE CR/RCN. 
          SOLUTION - NVF WILL MOVE THE DATA PROPERLY.  NIP WILL COPY
                     THE DATA BUFFER PROPERLY.
          PAM     85/05/07     NVFTRCN,NVFTDSP,TEXTNVF
          LTN                  HCRRCNR
 NA5B108  WHEN LINE GETS DISCONNECTED, FOR LOANED CONNECTION, PRIMARY 
          APPLICATION WILL RECEIVE CON/CB/U WITH RC = 1 AND LOAN INDICATOR
          TURNED ON.
          LTN       85/04/16       HCSTTP,HCONCBU 
  
 NA5B290  PROBLEM  - IF A PRIMARY APPL LOANED A CONNECTION TO A 
                     SECONDARY APPL, THEN THE PRIMARY APPL FAILED,
                     WHEN THE SECONDARY APPL RETURNED THE CONNECTION
                     TO THE PRIMARY APPL, THE USER WOULD GET AN 
                     APPLICATION PROMPT, BUT NO APPLICATION FAILED
                     MESSAGE. 
          ANALYSIS - IN THE CASE WHERE THE PRIMARY APPL FAILS, NVF
                     WAS NOT SENDING THE "APPLICATION FAILED" MESSAGE.
          SOLUTION - WHEN THE PRIMARY APPL FAILS, AND THE CONNECTION
                     IS RETURNED TO THE PRIMARY APPL, NVF WILL SEND 
                     THE "APPLICATION FAILED" MESSAGE.  THIS CODE 
                     ALSO DELETES SOME DEBUG MESSAGES THAT WERE 
                     TEMPORARILY PUT IN NVF.
          PAM     85/05/07     NVFTRVD,NVFTVAA,NVFTRCN
 NA5B295  TIMER MDIDLY IN MDI/GMS SHOULD BE INCREASED.
  
          TIMER MDIDLY IS QUADRUPLED TO WAIT FOR MCI WRITE LENGTH 
          ERROR PROCESSING AND TO COMPLY WITH THE PROCESSING TIMING OF
          FASTER PP-S.
  
          SW     85/05/09    PIP
 NA5B299  NVF FAILURE CAUSED BY NIP ABORTING THE WRONG APPLICATION. 
          WHEN NIP TRIED TO FORMAT A SCP CALL TO END AN APPLICATION 
          WHICH WAS AT STATE 6, IT DID NOT EXECUTE THE XABTAPP
          IMMEDIATELY IF THE NETONA FROM NVF HAS A FATAL ERROR CODE 
          AND THE UPDATE ATHAN IS SMALLER THAN THE LOOP INDEX.
          THIS WILL CAUSE NIP TO ABORT THE WRONG APPLICATION AND
          GENERATE VARIOUS MEMORY MANAGEMENT PROBLEMS.
          CODE IS CUT SO THAT UNDER THE ABOVE MENTIONED SITUATION,
          XABTAPP IS EXECUTED IMMEDIATELY.
          THIS IDENT ALSO FIXES THE PROBLEMS ADDRESSED BY NA5B312 
          NA5B305.
          YCY     85/05/13     XSACB
 NA5B323  PROBLEM  - NIP DID NOT INFORM AIP THAT TWO DATA BLOCKS WERE 
                     AVAILABLE FOR DELIVERY.  THIS RESULTED IN THE
                     APPLICATION NOT RESPONDING TO TERMINAL TYPEINS.
          ANALYSIS - THE APPLICATION HAD ISSUED A LST/OFF SUPERVISORY 
                     MESSAGE FOLLOWED BY A LST/ON SUPERVISORY MESSAGE.
                     IN PROCESSING THE LST/ON SUPERVISORY MESSAGE, NIP
                     DID NOT UPDATE THE DELIVERABLE DATA BIT IN THE 
                     ACB. 
          SOLUTION - NIP ROUTINE HLONOFF HAS BEEN CORRECTED TO CLEAR
                     THE LST-OFF FLAG IN THE ACB BEFORE CALLING NIP 
                     ROUTINE HUPDTDB TO UPDATE THE DELIVERABLE DATA 
                     BIT. 
          EG     05/20/85    HLONOFF
 NA5B338  NIP FAILED WHEN SECONDARY TRIED TO NETOFF.
          WHEN AN APPLICATION TRIED TO LOAN A CONNECTION TO 
          ITSELF, IT MAY HAVE THE SITUATION THAT THE PRIMARY
          INFORMATION ENTRY WITHIN THE ACNT IS AFTER THE
          SECONDARY ENTRY. IN THIS CASE, NIP SHOULD 
          UPDATE ACTION 5 OF THE HCSTTP SUCH THAT THE 
          APPLICATION NUMBER AND ACN IN ACNTPRID OF THE 
          THE PRIMARY APPLICATION NOW REFER TO NVF APPLICATION
          NUMBER AND THE ACN OWNED BY NVF.
          YCY     85/05/20     HCSTTP 
 FA6467   FEATURE - MODIFY NIP TO SUPPORT DOWNLINE BREAKS ON DEVICE 
                    CONNECTIONS.
          EG     11/20/84    NBSTTP,STATTBL 
 NA5B178  PROBLEM  - NVF SENT OUT THE WRONG REASON CODE ON A CR/RCN/A 
                     IF THE SECONDARY APPL WAS AT MAXACN. 
          ANALYSIS - THE REASON CODE FOR THE CR/RCN/A WAS HARD CODED
                     TO BE 22 (SECONDARY NOT AVAILABLE).
          SOLUTION - USE THE REASON CODE VALUE PASSED AS A PARAMETER
                     TO NVFTRLC WHEN SETTING THE RC IN THE CR/RCN/A.
          PAM     85/06/04     NVFTDSP,NVFTRLC
 NA5B311  PRIMARY FILES CANNOT BE TRANSFERRED BY NETXFR.
          PIP WHICH PERFORMS RANDOM READ CAN NOT OPERATE
          ON PRIMARY FILES. 
          NETXFR WILL GENERATE ILLEGAL FILE TYPE MESSAGE
          FOR PRIMARY FILE XFR. 
          YCY        85/05/22        NP$INFO
 NA5B352  NIP SHOULD ISSUE SST CALL TO RETURN OWNERSHIP OF
          THE FILE TO THE APPLICATION ONLY IF THE APPLICATION IS
          SWAPPED IN. 
          PROBELM: NIP ISSUES SST CALL (RETURN FILE OWNERSHIP) EVEN 
            WHEN THE APPLICATION IS SWAPPED OUT.
          SOLUTION: BEFORE NIP ISSUES THE SST CALL FOR RETURNING FILE 
            OWNERSHIP FROM THE OS TO THE APPLICATION, IT
            CHECKS IF THE ATASBSO FLAG IS SET. IF THE FLAG IS 
            SET, IT FAKES THE REASON CODE TO BE THE ONE FOR 
            UCP-SWAPPED-OUT. THIS WILL FORCE NIP TO PROCESS 
            THE CHAINED REQUEST LATER. ALSO, IN THE SECTION 
            THAT ISSUES THE SST DAYFILE MESSAGE WITH THE
            REASON CODE, IT CHECKS IF THE ATASBSO IS NOT SET BEFORE 
            IT DOES SO. THIS WAY, IF INDEED THE SST CALL IS 
            REJECTED EVEN IF THE APPLICATION IS SWAPPED IN, NIP 
            WILL STILL DAYFILE THE REASON CODE. 
          YCY     85/05/30     NRCSSTP
 NA5B263  REDUCE NIP-S CPU USAGE, FIELD LENGTH, AND THE INTERACTIVE 
          RESPONSE TIME BY MAKING THE FOLLOWING CHANGES.
          1. USE PRESET WORDS WERE POSSIBLE.
          2. USE SPECIAL DOWNLINE BUFFER FOR BACKS TO REDUCE USAGE OF 
             BUFFER MANAGEMENT ROUTINES.
          3. USE GLOBAL BASED ARRAY FOR AT, PIT, CET, AND TNT.
          4. REPLACE USE OF LIST RING WITH CONNECTION DATA QUEUE RING.
          5. USE BASED ARRAYS FOR PASSING PARAMETERS WHERE APPLICABLE.
          6. REMOVE USE OF INTERLOCK TABLE AND SIMPLIFY INTERFACE 
             BETWEEN PIP AND NIP. 
          7. MISCELLANEOUS CHANGES TO VARIOUS ROUTINES TO REDUCE THEIR
             CPU USAGE AND THEREBY ALSO IMPROVE RESPONSE TIME.
          8. ADD NEW FEATURE TO ALLOW APPLICATION TO RECEIVE MULTIPLE 
             UPLINE DATA MESSAGES IN SINGLE WORKLIST TRANSFER.
          EG     04/22/85    MOST OF NIP AND AIP, PIP 
 NA5B335  THIS MODSET ALLOWS A CODED FILE TRANSFER OF 1920
          CHARACTERS. 
          YCY     85/06/10     NX$ADEF
 NA5B354  PROBLEM: APPLICATION ABORTS ON BAD REASON CODE
                   RETURNED TO BY NIP DURING CONNECTION REQUEST.
          SOLUTION: 
            CASE (1)
            WHEN A REGLL OCCURS, NIP SENDS CRCB WITH REASON CODE 17B
            TO NVF. WHEN CRTRM IS RECEIVED, NIP SHOULD MAP 17B TO 
            43B, MEANING LOGICAL LINK FAILURE FOR THE APPLICATION 
            TO UNDERSTAND THE RC2 FIELD.
  
            CASE (2)
            WHEN NIP SENDS TCNTA TO CCP, IT SHOULD SET THE REASON CODE
            ACCORDING TO THE VALUE OF RCBRK.
            IN NTCNTAR, NIP SHOULD ALSO SET THE VALUE OF TCNRC TO 
            THE VALUE OF RCBRK. 
  
  
          YCY     85/06/10     HCACRQA,NCSTTP,NTCNTAR 
 NA5B357  PROBLEM: WHEN THE CHARACTER MODE SENDER RETURNS 
          AFTER RECEIVING A ER(E), IT SETS THE RC FIELD TO 25 
          ARBITRARILY.
  
          SOLUTION: 
          THE REASON CODE THAT THE NETXFR RETURNS TO THE APPLICATION
          FOR A ER(E) SHOULD BE THE ONE SET WHEN THE CHARACTER MODE 
          SENDER SENDS THE ES(E). 
          YCY     85/06/05     NP$STTP
 NA50376  PROBLEM -  NIP FAILS WHEN TWO APPLICATIONS WHICH INITIATE 
                     INTRAHOST APPLICATION-TO-APPLICATIONS ARE RUN. 
          ANALYSIS - NIP ROUTINE HVLLCB IS OVERWRITING THE ADDRESS OF 
                     THE FIRST LLCB POINTED TO BY THE TERMINAL NODE 
                     TABLE WITH THE ADDRESS OF THE NEW LLCB THAT WAS
                     JUST ADDED.  WITH THE BAD ADDRESS IN THE TERMINAL
                     NODE TABLE, NIP NO LONGER KNOWS ABOUT ANY OF THE 
                     PREVIOUS LOGICAL LINKS WITH TERMINAL NODE 1. 
                     WHEN THE HOST-TO-HOST LOGICAL LINK IS TERMINATED,
                     THE LLCB IS RELEASED BUT THE TERMINAL NODE TABLE 
                     WILL STILL POINT TO IT.  THIS CAUSED NIP TO FAIL 
                     WITH A CPU ERROR EXITS AND MRELS BUFFER MANAGEMENT 
                     ERRORS.
          SOLUTION - HVLLCB HAS BEEN CORRECTED TO NOT OVERWRITE THE 
                     ADDRESS IN THE TERMINAL NODE TABLE UNLESS IT IS
                     CREATING THE FIRST LLLCB FOR THAT TERMINAL NODE
                     NUMBER.
          EG     05/12/85    HVLLCB 
 NA50392  PROBLEM - WHEN NAMI IS CALLED WITH RS=RCRDNAME, AND 
                    RCRDNAME IS NOT FOUND IN THE MASTER FILE, 
                    NAMI FAILS TO INCLUDE THE RCRDNAME IN THE 
                    DAYFILE ERROR MESSAGE.
  
          SOLUTION - ROUTINE LOAD$JOB HAS BEEN MODIFIED 
                     SO THAT THE ERROR MESSAGE WILL INCLUDE 
                     THE NON_EXISTING RECORD NAME.
          TET     85/06/10     NAMI 
 NA5B300  GARBARGE FOUND IN AIP STATISTICS FILE HEADER. 
          IN NETSTC ST$MSG1 SHOULD BE DEFINED AS
          35 CHARACTERS RATHER THAN 25 CHARACTERS LONG. 
          YCY    06/13/85    NETSTC 
 NA5B361  PROBLEM  - NIP ABORTED WITH MRELS BUFFER MANAGEMENT ERROR.
          ANALYSIS - NIP HAD RECEIVED A HE/CP SUPERVISORY MESSAGE 
                     FROM PIP AND CALLED NIP OVERLAY NPHECP TO PROCESS
                     THE MESSAGE. NHPECP CALLS MRELS TO RELEASE ALL 
                     THE QUEUED DOWNLINE MESSAGES.  ONE OF THE DOWNLINE 
                     MESSAGES QUEUED WAS A BACK WHICH RESIDED IN THE
                     DOWNLINE BACK BUFFER INSTEAD OF THE DYNAMIC BUFFER 
                     AREA.  WHEN MRELS TRIED TO RELEASE THIS BUFFER, IT 
                     ABORTED NIP BECAUSE THE BUFFER WAS OUTSIDE THE 
                     DYNAMIC BUFFER AREA. 
                     NIP CAN ALSO ABORT WITH THIS ERROR IF NIP PROCESSES
                     NVF-S NETOFF REQUEST AND GETS A SWAPPED OUT REASON 
                     FROM THE OPERATING SYSTEM. 
          SOLUTION - NIP OVERLAYS NPHECP AND NPESTOF HAVE BEEN CORRECTED
                     TO CHECK FOR THE SPECIAL BACK BUFFERS AND NOT CALL 
                     MRELS TO RELEASE THEM. 
                     NIP OVERLAY HPNOFF HAS BEEN CORRECTED TO ADJUST THE
                     DRHDRWD BASED ARRAY ADDRESS BEYOND THE END OF THE
                     SCP FUNCTION LISTS.
          EG     06/12/85    NPESTOF, NPHECP, HPNOFF
NA5B362   PROBLEM - TVF HAS GROWN SO ITS SPECIFIED FL IN THE
                    NAMI STARTUP RECORD (10K) IS NOW INSUFFICIENT.
                    THIS CAUSES TVF TO FAIL.
  
          SOLUTION - INCREASE TVF'S FL FROM 10K TO 15K. 
          TET     85/06/17     JOBTVF 
 NA5B369  PROBLEM  - AIP IS NOT DELIVERING DATA MESSAGES TO NVF.
          ANALYSIS - AIP ROUTINE NETGET DID NOT SET THE LIST FLAG IF STAT IS
                     NOT DEFINED.  THIS CAUSED AIP TO NOT GET THE DATA MESSAGES 
                     FROM NIP.
          SOLUTION - AIP ROUTINE NETGET HAS BEEN CORRECTED TO SET THE LIST FLAG 
                     IRREGARDLESS OF HOW IT WAS BUILT.
          EG     06/15/85    NETGET 
 NA5B370  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT AT ADDRESS 34610. 
          ANALYSIS - NIP OVERLAY KDEL USES A FORWARD POINTER IN THE 
                     LLCB WITHOUT FIRST VERIFYING THAT THE LLCB BASED 
                     ARRAY IS ASSIGNED TO A LLCB. 
          SOLUTION - NIP OVERLAY KDEL HAS BEEN CORRECTED TO ONLY LOOK 
                     AT THE FORWARD POINTER IF THE BASED ARRAY IS 
                     ASSIGNED TO A LLCB.
          EG     06/14/85    KDEL 
 NA5B371  PROBLEM  - NAM WAS NOT TALKING WITH ONE OF THE NPUS.
          ANALYSIS - PIP WAS WAITING FOR NIP TO ALLOCATE A INBOUND
                     BUFFER FOR THIS NPU.  NIP WAS NOT ALLOCATING ONE 
                     ONE BECAUSE THE CURRENT INBOUND BUFFER INDEX WAS 
                     POINTING TO THE WRONG PSEUDO FET.
          SOLUTION - NIP ROUTINE NEIB HAS BEEN CORRECTED TO SET THE 
                     CURRENT INBOUND BUFFER INDEX TO THE RIGHT VALUE. 
          EG     06/14/85    NEIB 
 NA5B372  PROBLEM  - PTFS ABORTED WITH MESSAGE - BLOCK TOO LARGE. 
          ANALYSIS - PTFS HAD RECEIVED A QMSG BLOCK WITH THE IBU BIT
                     SET.  THE IBU BIT WAS SET BECAUSE NIP COULD NOT
                     DELIVER THE QMSG BLOCK DUE TO THE CONNECTION NOT 
                     HAVING BEEN INITIALIZE FOR DATA TRAFFIC (I.E.
                     THE FC/INIT SUP MSG HAD NOT BEEN EXCHANGED YET 
                     WITH THE APPLICATION).  PTFS IS NOT CHECKING 
                     THE IBU BIT SO IT ASSUMED IT WAS RECEIVING DATA
                     WITHOUT HAVING RECEIVED A FC/INIT SUP MSG AND
                     ABORTED. 
          SOLUTION - NIP ROUTINE HGETDA HAS BEEN CHANGED TO RETURN
                     A NULL BLOCK TO THE APPLICATION IS THE 
                     CONNECTION IS IN THIS STATE. 
          EG     06/14/85    HGETDA 
 NA5B373  PROBLEM  - EXCEPT FOR THE HEADER LINE OF THE NAM STATUS 
                     DISPLAY, THERE IS NO INDICATION WHEN NIP GOES
                     INTO REGULATION.  THIS MAKES IT VERY CONFUSING 
                     FOR THE OPERATOR SINCE HE WILL NOT KNOW WHAT THE 
                     PROBLEM IS WHEN TERMINAL USERS CALL UP TO COMPLAIN 
                     ABOUT GETTING WAIT.. AT THEIR TERMINALS UNLESS HE
                     IS THOROUGHLY FAMILIAR WITH THE NAM K-DISPLAY. 
          SOLUTION - NIP OVERLAY XNBRLC HAS BEEN CORRECTED TO ISSUE 
                     INFORMATIVE DAYFILE MESSAGES WHEN NIP GOES INTO
                     REGULATION.
          EG     06/17/85    XNBRLC 
 NA5B296  PIP ISSUES BLOCK PROTOCOL WORKLIST TO NON-EXISTENT CONNECTION.
  
          WHEN CONNECTION IS NOT EXISTENT, PIP SHOULD NOT SEND BLOCK
          PROTOCOL WORKLIST ENTRY.
  
          PIP IS CHANGED TO ISSUE DAYFILE WORKLIST ENTRY WHEN IT CAN
          NOT FIND A CONNECTION.
  
          SW     85/06/25    PIP
 NA5B351  DELAY TIMER FOR MDI RESET IS TOO SHORT
  
          DELAY TIMER FOR MDI RECOVERY FROM RESET AND FOR FUNCTION
          RESPONSE IS TOO SHORT.
  
          THIS MODIFICATION MAKES THE DELAY 500 MILLISECONDS LONG 
          BASED ON SYSTEM REAL-TIME CLOCK.
  
          SW     85/06/25    PIP
 NA5B355  FILE TRANSFER USING DD=US RETURNS EXTRA EMPTY RECORD. 
  
          PIP CREATS AN EMPTY RECORD AT EOI WHEN THE FILE TRANSFER
          IS USING DD=US. 
  
          CIO CODE FOR EOI WRITE IS IMPLEMENTED FOR FILE TRANSFER.
  
          SW     85/06/25    PIP
 NA5B359  THIS MODSET UPDATES PIP TO USE THE CORRECT *REQM* 
          SUBFUNCTION WHEN REQUESTING AN EST ENTRY.  THESE ARE NEW
          SUBFUNCTIONS DEFINED BY THE RMS RAM ENHANCEMENT PROJECT.
          CRL.   85/06/15    PIP
 NA5B363  PROBLEM  - NAM ABORTED WITH PIP ERROR 67. 
          ANALYSIS - NIP ROUTINE XCHKABC HAD INCREMENTED THE NUMBER OF
                     AVAILABLE PRU BUFFERS WITHOUT ACTUALLY ALLOCATING
                     THE PRU BUFFER.
          SOLUTION - NIP SHOULD NOT INCREMENT THE NUMBER OF AVAILABLE 
                     PRU BUFFERS IF IT DOES NOT ACTUALLY ALLOCATE THE 
                     BUFFER.
          EG     06/18/85    XCHKABC
 NA5B374  THIS CODE CONTAINS THE NVF PORTION OF THE FIX FOR THIS
          PSR.  THIS CODE DEPENDS ON SOME NIP CHANGES ALSO. 
          IF NVF RECEIVES A CR/RCN FROM A SECONDARY APPL RETURNING
          TO THE PRIMARY APPL, AND IF THE APPLICATION NAME FIELD IN 
          THE SUPERVISORY MESSAGE IS ZERO, NVF WILL ASSUME THAT THE 
          PRIMARY APPL HAS FAILED, AND WILL CLEAR THE LOAN STATUS 
          FROM THE PTAC ENTRY.
          PAM     85/06/21     NVFTRVD
 NA5B375  PROBLEM  - THE APPLICATION TAPPL4 WAS DROPPED, BUT STAYED 
                     IN THE NIP K-DISPLAY.
          ANALYSIS - NVF THOUGHT THAT TAPPL4 HAD AN OUTSTANDING T-A 
                     CONNECTION.  THIS WAS BECAUSE NVF RECEIVED A 
                     CR/RCN WITH A REASON CODE OF "PRIMARY LOANING
                     CONNECTION TO SECONDARY".  THE SECONDARY APPL
                     NAME IN THE SUPERVISORY MESSAGE WAS "BYE". 
                     FOR THIS SPECIAL LOAN REASON CODE, NVF DOES NOT
                     DECREMENT THE NUMBER OF CONNECTIONS FOR THE
                     PRIMARY APPLICATION UNTIL JUST BEFORE THE
                     CONNECTION IS SWITCHED TO THE PRIMARY APPL.
                     BUT SINCE THE APPL NAME WAS "BYE", THE CONNECTION
                     WAS SIMPLY TERMINATED AND NEVER SWITCHED SO THE
                     PRIMARY APPL CONNECTION COUNT WAS NEVER DECREMENTED. 
          SOLUTION - IF NVF RECEIVES A CR/RCN WITH A REASON CODE OF 
                     "PRIMARY LOANING CONNECTION TO SECONDARY", AND IF
                     THE SECONDARY APPL NAME IS ONE OF THE RESERVED 
                     WORDS OF "BYE", "HELLO", "LOGOUT", OR "LOGIN", 
                     NVF WILL DECREMENT THE CONNECTION COUNT OF THE 
                     PRIMARY APPL BEFORE TERMINATING THE CONNECTION.
          PAM     85/06/21     NVFTCRN
 NA5B377  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT AT 25054. 
          ANALYSIS - NIP WAS PROCESSING A GETL WORKLIST REQUEST TO
                     GET A DATA BLOCK THAT WAS 10 CHARACTERS LONG.
                     THE INPUT CHARACTER TYPE WAS 3 AND THE APPLICATION 
                     HAD SPECIFIED DATA TRUNCATION FOR THE CONNECTION.
                     BECAUSE THE APPLICATION HAD SPECIFIED A SMALLER
                     BUFFER THAN THE DATA, NIP ALLOCATED A BUFFER FOR 
                     THE DATA THAT COULD NOT HOLD THE ENTIRE DATA 
                     MESSAGE.  HOWEVER, NIP ROUTINE BCONV CONVERTED THE 
                     ENTIRE MESSAGE TO ACT 3.  THIS RESULTED IN THE 
                     WORD AFTER THE BUFFER BEING OVERWRITTEN AND THE
                     RESULTING CPU ERROR EXIT.
          SOLUTION - NIP ROUTINE HGETDA HAS BEEN CORRECTED TO UPDATE
                     THE TEXT LENGTH OF THE DATA WHEN IT IS GOING TO
                     TRUNCATE THE DATA. 
          EG     06/19/85    HGETDA 
 NA5B378  CS IS NOT INTERPRETING THE STI/AP AND STITE MESSAGES
          PROPERLY. 
  
          CHANGE FIELD DEFINITIONS TO THE PROPER ALIGNMENT.  ADD
          NEW CODE FOR ADDITION OF DEVICE TYPE FIELD.  CHANGE 
          CONNECT TIME TO BE INTEGER AND NOT AN ASCII STRING. 
  
          THIS MODSET IS DEPENDENT ON FEATURE IDENT FN24CS WHICH
          ADDS SUPPORT OF ACCEPTING NEW ACCOUNTING MESSAGES FROM
          DI-S. 
  
          DKE     85/06/28     SMCS,CSESDA
 NA5B383  PROBLEM  - NIP REACHED 200K FIELD LENGTH. 
          ANALYSIS - NIP WAS NOT RELEASING NONMOVABLE BUFFERS TO THE
                     FREE CHAIN.
          SOLUTION - NIP ROUTINE HPGET HAS BEEN CORRECTED TO CALL 
                     MRELS TO RETURN BUFFERS FOR DATA MESSAGES THAT 
                     CONTAIN NO TEXT. 
          EG     06/27/85    HPGET
 NA5B384  PROBLEM  - NIP DID NOT ZERO OUT THE APPLICATION FIELD IN THE
                     CR/RCN SUPERVISORY MESSAGE WHEN IT RETURNED A
                     SECONDARY APPLICATION CONNECTION TO NVF AND THE
                     PRIMARY APPLICATION HAD FAILED.
          ANALYSIS - NIP OVERLAY HPNOFF DID NOT UPDATE THE CORRECT
                     ENTRY IN THE CONNECTION TABLE FOR THE SECONDARY
                     APPLICATION WHEN THE PRIMARY APPLICATION NETTED
                     OFF. 
          SOLUTION - NIP ROUTINE HPNOFF HAS BEEN CORRECTED TO UPDATE
                     THE CORRECT ENTRY IN THE CONNECTION TABLE OF THE 
                     SECONDARY APPLICATION. 
          EG     06/25/85    HPNOFF 
 NA5B385  PROBLEM  - NIP IS CALLING A NEW PIP EVERY TEN SECONDS TO
                     PERFORM AN EST SCAN EVEN THOUGH THERE IS A 
                     DEDICATED PIP RUNNING. 
          ANALYSIS - NIP OVERLAY XCHKCET IS NOT CHECKING CORRECTLY
                     FOR A DEDICATED PIP WHEN IT IS DETERMINING 
                     IF PIP NEEDS TO BE CALLED TO PERFORM AN EST
                     SCAN.
          SOLUTION - NIP OVERLAY XCHKCET HAS BEEN CORRECTED TO
                     CHECK CORRECTLY FOR A DEDICATED PIP. 
          EG     06/21/85    XCHKCET
 NA5B386  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT BECAUSE NIP ROUTINE 
                       XSTTP JUMPED TO BAD LOCATION.
                   - ADD GARBAGE COLLECTION FLAG TO INDICATE WHEN 
                     GARBAGE COLLECTION IS BEING PERFORMED. 
          SOLUTION - NIP ROUTINE XSTTP HAS BEEN CORRECTED TO EXECUTE A
                       RETURN JUMP INSTEAD OF A DIRECT JUMP TO THE ABORT
                       ROUTINE. 
          EG     06/19/85     XSTTP, PT, XEXEC, ITABS 
 NA5B388  PROBLEM  - PIP ABORTED  NIP WITH PIP ERROR 040. 
          ANALYSIS - THE PRU BUFFER POINTER IN THE PIT ENTRY WAS BAD. 
                     BETWEEN THE TIME THAT MSETPTR SET THE BACKWARD 
                     POINTERS IN THE PRU FREE CHAIN AND THE TIME THE
                     GARBAGE COLLECTION ROUTINE EXECUTED, PIP MODIFIED
                     THE PRU BUFFER POINTERS. 
          SOLUTION - NIP ROUTINE MSETPTR HAS BEEN CORRECTED TO NOT
                     CLEAR THE NIP/PIP INTERLOCK. 
          EG     05/30/85    MSETPTR
 NA5B389  PROBLEM  - PIP ABORTED NIP WITH PIP ERROR 067.
          ANALYSIS - NIP HAD OVERWRITTEN WORD ONE OF A NCNT TABLE WITH
                     CONNECTION DATA RING POINTERS.  THIS WAS MOST
                     LIKELY DONE BY GARBAGE COLLECTION.  NIP HAD AN ACNB
                     WITH CONNECTION DATA RING POINTERS WHICH SHOULD
                     HAVE POINTED TO ITSELF BUT DID NOT.  THE PROBLEM 
                     MAY HAVE BEEN CAUSED BY NIP ROUTINE INSCDR BEING 
                     CALLED TWICE TO INSERT THE SAME ACNB IN THE
                     CONNECTION DATA RING.  THIS COULD ONLY OCCUR IF
                     DURING A CONNECTION SWITCH, DATA IS QUEUED FOR THE 
                     ACNB.
          SOLUTION - NIP OVERLAY HSWACNB HAS BEEN CORRECTED TO CALL 
                     NIP ROUTINE INSCDR TO INSERT THE ACNB IN THE 
                     CONNECTION DATA RING IF THERE IS DATA QUEUED ON
                     IT.  NIP ROUTINE UPACNB3 AND NIP OVERLAY UPACNB4 
                     HAVE BEEN CORRECTED TO NOT CALL NIP ROUTINE
                     INSCDR.  NIP OVERLAYS HSWACNB AND RELACNB HAVE 
                     BEEN CORRECTED TO NOT CALL NIP ROUTINE DELCDR
                     UNLESS THE ACNB IS ALREADY IN THE CONNECTION 
                     DATA RING. 
          EG     06/30/85    HSWACNB, RELACNB, UPACNB3, UPACNB4,
                             SKENIP 
 NA5B353  THIS IDENT CORRECTS THE PROBLEM THAT
          SOMETIMES WHEN AN APPLICATION SENDS A HOP/ALT 
          MESAGE TO NAM IN IGNORED STATE, NAM DOES NOT
          REPOND TO THE APPLICATION WITH A HOP/IG.
  
  
          YCY     85/07/09     HPNOFF 
 NA5B360  WHEN NIP GETS A NOINTERLOCK REPONSE FROM PIP, NIP 
          SHOULD ABORT BECAUSE THE RESULT OF THE MEMEORY MOVE IS
          UNPREDITABLE. 
          IN THIS CASE, WE GOT A MREL PROBLEM IN GARBAGE COLLECTION 
          BUT MEMORY COULD BE ALTERED WHEN THERE WAS A NOINTERLOCK
          REPOSNSE FROM PIP.
          YCY     85/07/02     MSETIL 
 NA5B387  PIP DOES NOT RESPOND TO NAM INTERLOCK REQUEST.
  
          PIP HUNG WITHOUT PAUSING OR RESPONDING TO NAM INTERLOCK 
          REQUEST WHEN ACTIVE FRONT END COUNT OR ACTIVE PRU COUNT IS
          GARBLED.
  
          CHECK FOR NAM INTERLOCK REQUEST AND PAUSE ARE ADDED AT THE
          END OF ONE PIP CYCLE WHEN THERE MAY BE NO ACTIVE NBT NETRY. 
  
          SW     85/07/01    PIP
 NA50398  PROBLEM: NIP DOES NOT HANDLE CONDITIONAL CODE 
                   CODE FOR TRACE AND DEBUG CONSISTENTLY. 
  
          ANALYSIS: IN INIDP AND THE CALL TO INIDP, TRACE 
                    OPTION,ZZDN SHOULD BE TESTED RATHER 
                    THAN DEBUG, SINCE TRACE SHOULD BE 
                    ENABLED BY SETTING ZZDN TO 1 ONLY.
                    IN KNAMCOM, WHEN LB IS USED, ZZDN 
                    INSTEAD OF DEBUG SHOULD BE TESTED.
          SOLUTION: CHANGES FROM TESTING DEBUG TO TESTING 
                    ZZDN SHOULD BE APPLIED TO THE CODE
                    SECTIONS MENTIONED ABOVE. 
          YCY     85/07/02     NIP,INIPD,KNAMCOM
 NA5B368  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT WHEN K-DISPLAY
                      TYPEIN WAS MADE.
          ANALYSIS - NIP OVERLAY KPTYPIN CAN ONLY HANDLE 8 TOKENS, I.E. 
                     8 PARAMETERS.  THE OPERATOR ENTERED A TYPEIN WITH
                     12 PARAMETERS. 
          SOLUTION - NIP OVERLAY KPTYPIN HAS BEEN CORRECTED TO HANDLE 
                     UP TO 25 PARAMETERS. 
          EG     07/17/85    KPTYPIN
 NA5B403  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT WHEN PLATO INTERFACE
                     CODE WAS INCORPORATED INTO IAF.
          ANALYSIS - NIP ROUTINE OMOVE HAD BEEN CALLED TO MOVE ZERO 
                     WORDS.  IT CANNOT HANDLE THIS. 
                   - NIP ALSO DID NOT RELEASE THE UPDATE DATA QUEUE 
                     BUFFER WHEN NO DATA MESSAGES WERE DELIVERABLE. 
          SOLUTION - NIP ROUTINE OMOVE HAS BEEN CORRECTED TO HANDLE 
                     MOVING ZERO WORDS. 
                   - NIP ROUTINE HPGETMM HAS BEEN CORRECTED TO RELEASE
                     THE BUFFER IF NOT DATA MESSAGES ARE DELIVERABLE. 
          EG     07/03/85    OMOVE, HPGETMM 
 NA5B407  PIP WOULD NOT DROP ON NAM IDLE DOWN.
  
          PIP-S INTERNAL COUNTER FOR ACTIVE PRU STREAMS MAY NOT GO TO 
          ZERO WHEN ALL STREAMS ARE TERMINATED.  INSTEAD, IT MAY BECOME 
          NEGATIVE.  THIS CONDITION PREVENTS PIP FROM DROPPING ITSELF 
          WHEN NAM IS IDLED.
  
          THIS CORRECTIVE CODE REMOVES CHECK FOR COUNT OF ACTIVE PRU
          STREAMS.  PIP-S ACTIVITY IS CHECKED ONLY BY COUNT OF ACTIVE 
          FRONT END PROCESSORS AND THAT SHOULD BE SUFFICIENT. 
  
          SW     85/07/19    PIP
 NA5B408  PROBLEM  - NVF HUNG WITH 65 SUPERVISORY MESSAGES QUEUED FOR 
                     IT.
          ANALYSIS - THE NVF TRACE SHOWED THE LAST SUPERVISORY MESSAGE
                     THAT NVF RECEIVED WAS A CR/CB SUPERVISORY MESSAGE
                     FOR A CONNECTION THAT NVF HAD JUST SEND A CR/IAP/A 
                     SUPERVISORY MESSAGE.  IT IS BELIEVED THAT NVF GOT
                     CONFUSED WHEN IT RECEIVED THIS SUPERVISORY MESSAGE 
                     SINCE IT HAD NO RECORD OF THE CONNECTION ANY MORE. 
          SOLUTION - NIP COMMON DECK STATTBL HAS BEEN CORRECTED TO NOT
                     SEND NVF A CR/CB SUPERVISORY MESSAGE WHILE IT IS 
                     WAITING FOR A RESPONSE TO A CR/IAP/R SUPERVISORY 
                     MESSAGE. 
          EG     07/12/85    STATTBL
 NA5B415  PROBLEM  - AIP ABORTED APPLICATION WITH DAYFILE MESSAGE:  
                     NWL HAS OVERFLOWED.
          ANALYSIS - THE APPLICATION ISSUED A NETPUT CALL WITH A
                     BAD APPLICATION BLOCK HEADER WORD.  AIP USED 
                     THE BAD ABH WORD TO COMPUTE THE SIZE OF THE
                     MESSAGE AND COMPUTED A NEGATIVE SIZE.  THIS
                     CAUSED BAD VALUES TO BE STORED IN THE NWL
                     HEADER AND THE RESULTING ERROR.
          SOLUTION - AIP ROUTINE NP$PUT HAS BEEN CORRECTED TO 
                     CHECK FOR CORRECT ACT TYPE WHILE PROCESSING
                     THE ABH WORD.
          EG     07/17/85    NP$PUT 
 NA5B415  PROBLEM  - NAM DID NOT RETURN ERR/LGL SUP MSG TO APP WHEN 
                     IT ISSUED FRAGMENTED GETL CALL WITH ZERO LENGTH
                     TEXT ARRAY.
          ANALYSIS - THE FRAGMENTED GETL CALL ON LIST ZERO WAS CONVERTED
                     INTO A GETSM WORKLIST BY AIP SINCE NIP HAD 
                     SUPERVISORY MESSAGES QUEUED FOR THE APPLICATION. 
                     AFTER THE SUPERVISORY MESSAGES WERE DELIVERED TO 
                     NIP, AIP HAD NOT CHOICE BUT TO RETURN A BLOCK
                     HEADER WITH THE IBU BIT SET TO THE APPLICATION 
                     SINCE AIP DOES NOT GENERATE ERR/LGL SUP MSGS.
          SOLUTION - THE NAM REFERENCE MANUAL IS BEING UPDATED TO ALLOW 
                     ZERO LENGTH TEXT ARRAY AND AIP ROUTINE NETGETF 
                     IS ALSO BEING MODIFIED TO ALLOW ZERO LENGTH TEXT 
                     ARRAY. 
          EG     07/19/85    NETGETF
 NA5B421  PROBLEM  - PIP ABORTED NIP WITH MESSAGE - PIP ERROR 067.
          ANALYSIS - NIP OVERLAY XCHKABC HAD ALLOCATED ADDITIONAL PRU 
                     BUFFER AT THE SAME TIME THAT PIP WAS ADDING AN 
                     PRU BUFFER TO THE FREE CHAIN.  SINCE BOTH NIP AND
                     PIP UPDATED THE SAME WORD, THIS CAUSED THE NIP 
                     POINTER TO THE NEW BUFFER TO GET OVERWRITTEN.
                     WHEN PIP TRIED TO USE THE NEW BUFFER AND COULD 
                     NOT FIND IT, IT ABORTED NIP WITH THE ABOVE ERROR 
                     CODE.
          SOLUTION - NIP OVERLAY XCHKABC HAS BEEN CORRECTED TO LINK 
                     NEWLY ALLOCATED BUFFERS TO THE PIT TABLE INSTEAD 
                     OF THE FIRST PRU BUFFER IN THE CHAIN.
          EG     07/22/85    XCHKABC
 FS4848   PERMIT PARAMETERS EP, IC AND OC FOR TERMINALS ON X.25 LINES,
          TO BE CONSISTENT WITH ASYNC.  CCP MODSET FCX25IVT SUPPORTS
          THESE PARAMETERS IN CCP FOR X.25. 
  
          DMR    85/05/02    NDLNFCM
          EMH 
  
 NA5B332  PROBLEM  - SOMETIMES, DATA ON THE CON/END WOULD NOT GET 
                     PASSED TO THE NEXT APPLICATION.
          ANALYSIS - THE DATA WOULD GET PASSED ONLY IF THE APPL 
                     WAS LOANING THE CONNECTION TO A SECONDARY APPL.
                     THIS WAS BECAUSE IN ALL OTHER CASES, NVF WOULD 
                     SEND OUT A CR/RCN/N RIGHT AWAY AND WRITE OVER
                     THE SIZE OF THE SUPERVISORY MESSAGE.  THEN, WHEN 
                     NVF CHECKED THE SIZE OF THE CR/RCN/R, THE SIZE 
                     VARIABLE DID NOT REFLECT THE TRUE SIZE.
          SOLUTION - BEFORE NVF SENDS THE CR/RCN/N MESSAGE, IT WILL 
                     SAVE THE SIZE OF THE CR/RCN/R MESSAGE. 
          PAM     85/07/30     NVFTRCN
 NA5B404  PROBLEM: PIP DOES NOT DROP EST ENTRY. 
  
          ANALYSIS: WHEN HECP IS RECEIVED FROM PIP, IT
                    CLEARS NBTOUT FOR THE OUTBOUND
                    BUFFER. IF THAT OUTBOUND BUFFER HAS 
                    A SPECIAL PRUID BUFFER WAITING TO BE
                    CONVERTED TO A REGULAR PCNB, IT WILL
                    NEVER BE CONVERTED. THE SECOND HECP 
                    WILL RELEASE ALL OUTBOUND BUFFERS 
                    INCLUDING THE SPECIAL PRUID BUFFERS.
  
  
  
           SOLUTION: IN NPHECP, CONVERTS THE TEMPORARY
                     PCNB ID TO A REGULAR PCNB ID (14B).
                     THEN RELEASE THE SPECIAL PRUID BUFFER. 
  
          YCY     85/07/25     NPHECP 
 NA5B411  PROBLEM  - A-A TELENET WOULD NOT WORK.
          ANALYSIS - TELENET APPENDS FACILITIES TO THE CR/RAP THAT NVF
                     RECIEVES.  IN ORDER TO INDICATE THE TELENET
                     FACILITIES TO NVF, THE FIRST FACILITY CODE/PARAM 
                     PAIR THAT TELENET APPENDS IS OF THE FORM "00 27".
                     THIS COMBINATION OF FACILITY CODE/PARAMETER
                     INDICATES THAT THE REMAINING FACILITIES ARE
                     TELENET FACILITIES.  WHEN NVF SAW THE FACILITY CODE
                     OF "00", IT THOUGHT IT WAS AN ILLEGAL CODE AND 
                     DISALLOWED THE CONNECTION. 
          SOLUTION - NVF WILL CORRECTLY INTERPRET THE "00 27" TELENET 
                     FACILITY AS WELL AS THE TELENET WINDOW SIZE AND
                     PACKET SIZE FACILITIES.
          PAM     85/07/24     NVFARAP
 NA5B424  PROBLEM  - NIP FAILED WITH MONITOR CALL ERROR.
          ANALYSIS - NIP HAD CHANGED THE BUFFER ID OF A NCNB INTO A 
                     PCNB WITHOUT ACTUALLY CREATING A PCNB.  THIS 
                     CAUSED GARBAGE COLLECTION TO ADJUST NONEXISTENT
                     POINTERS IN A PCNB WHICH WAS ACTUALLY A NCNB.
                     THE RESULT WAS THAT RA+1 WAS OVERWRITTEN.  THE 
                     NCNB BUFFER ID WAS CHANGED BECAUSE A MALICIOUS 
                     APPLICATION SENT A PRU/ON SUPERVISORY MESSAGE
                     THAT WAS REJECTED BY HBSTTP.  HBSTTP DID NOT 
                     SET PARAMP1 TO A NONZERO VALUE SO ITS CALLER,
                     HPPUT THOUGHT THE PRU/ON SUPERVIORY MESSAGE WAS
                     ACCEPTED AND CREATED A SPECIAL BUFFER FOR THE
                     PIP OUTBOUND CHAIN.  WHEN THIS BUFFER WAS
                     PROCESSED BY XEXEC, THE NCNB ID WAS CHANGED INTO 
                     A PCNB ID. 
          SOLUTION - NIP ROUTINE HBSTTP HAS BEEN CORRECTED TO SET 
                     PARAMP1 NONZERO IF IT REJECTS A PRU/ON SUPERVISORY 
                     MESSAGE.  NIP ROUTINE HPPUT HAS BEEN CORRECTED TO
                     NOT CALL HBSTTP TO RESTORE THE IVT CONNECTION STATE
                     IF THE PRU/ON SUPERVISORY MESSAGE WAS REJECTED.
          EG     07/24/85    HBSTTP, HPPUT
 NA5B430  PROBLEM  - NIP FAILED WITH MONITOR CALL ERROR AFTER ID,HO WAS 
                     ENTERED. 
          ANALYSIS - NIP HAD RECEIVED THE NETOFF WORKLIST FROM NVF AND
                     ZEROED OUT THE ENTRY IN THE AT TABLE FOR NVF.  IN
                     RESPONSE TO THE SCP FUNCTION, NIP GOT A RETURN CODE
                     44B, WHICH REQUIRED NIP TO ISSUE A SWAPIN FUNCTION.
                     WHILE NIP WAS WAITING FOR THE SWAPIN TO COMPLETE,
                     GARBAGE COLLECTION GOT CALLED AND GARBAGE
                     COLLECTION MOVED NVF-S ACNT WHICH REQUIRED UPDATING
                     THE ADDRESS OF THE ACNT IN NVF-S ACB.  THE ACB 
                     ADDRESS WAS EXTRACTED FROM THE AT TABLE ENTRY FOR
                     NVF, WHICH HAD THE VALUE ZERO.  THUS RA+1 WAS
                     OVERWRITTEN. 
          SOLUTION - NIP ROUTINE XEXEC HAS BEEN CORRECTED TO NOT CALL 
                     GARBAGE COLLECTION IF THIS CONDITION EXISTS.  ALSO 
                     NIP ROUTINE HPNOFF HAS BEEN CORRECTED NOT TO DUMP
                     ITS FIELD LENGTH IF A RETURN CODE ZERO IS RETURNED.
          EG     07/26/85    XEXEC, HPNOFF
 NA5B433  NAM CPU ERROR EXIT CAUSED BY PIP WLE. 
  
          PIP ISSUES BLOCK PROTOCOL ERROR WLE ON IVT INPUTS.
  
          AT A BLOCK PROTOCOL ERROR IN AN IVT TYPE INPUT ON A CONNECTION
          THAT IS NOT IN PRU STREAM STATE PIP IS TO ISSUE A DAYFILE 
          WORKLIST ENTRY. 
  
          SW     85/07/30    PIP
 NA5B333  PROBLEM  - NVF ALLOWS CONNECTIONS BEYOND MAXACN IF A
                     CONNECTION IS LOANED OUT.
          ANALYSIS - WHEN A CONNECTION WAS LOANED FROM A PRIMARY TO 
                     A SECONDARY APPLICATION, NVF WOULD DECREMENT THE 
                     T-A CONNECTION COUNT FOR THE PRIMARY APPLICATION.
          SOLUTION - WHEN A CONNECTION IS LOANED, NVF WILL NOT
                     DECREMENT THE T-A CONNECTION COUNT FOR THE 
                     PRIMARY APPLICATION.  WHEN THE CONNECTION IS 
                     RETURNED TO THE PRIMARY APPL, THE CONNECTION 
                     COUNT IS NOT INCREMENTED.
          PAM     85/08/06     NVFTCB,NVFTDSP,NVFTRCN,NVFUPRP,NVFTRVD,
                               NVFTURT,NVFTVVD,TEXTNVF,TXTANVF,NVFTACC, 
                               NVFTRLC
 NA5B344  CHANGE THE X.25 A-A SUBTIP FROM *X25* TO *XAA* TO ELIMINATE 
          CONFUSION.  THE VALUE *X25* WILL ALSO BE RETAINED TEMPORARILY,
          FOR COMPATIBILITY.
  
          EMH                 85/07/25       NDLLIST,NDLNFCM,NDLPSS1
 NA5B348  PROBLEM  - NIP ABORTED WITH BAD BSN MESSAGE.
          ANALYSIS - NIP HAD RECEIVED A BACK BLOCK FROM THE MDI WITH
                     BSN = 3.  IT SHOULD HAVE BEEN 7.  BECAUSE NIP WAS
                     BUILT WITH DEBUG DEFINED, IT ABORTED.
          SOLUTION - NIP ROUTINE NBADBSN HAS BEEN CORRECTED TO ABORT
                     NIP ONLY IF THE OPERATOR HAD ENTERED THE K-DISPLAY 
                     COMMAND TO TURN ON NAM DEBUG CODE. 
          EG     08/02/85    NBADBSN
 NA5B416  PROBLEM  - NIP DID NOT INFORM AIP THAT DATA WAS AVAILABLE.
          ANALYSIS - NIP ROUTINE HUPDTDB DID NOT CALL HWRAVAL TO UPDATE 
                     AIP-S DATA AVAILABLE WORD WHEN DATA WAS QUEUED FOR 
                     THE APPLICATION.  THIS WAS BECAUSE THE D BIT IN
                     THE AIP DATA AVAILABLE WORD DID NOT NEED TO BE 
                     UPDATED. 
          SOLUTION - NIP ROUTINE HUPDTDB HAS BEEN REWRITTEN AND ALL 
                     ROUTINES WHICH CALL IT HAVE BEEN CORRECTED TO PASS 
                     THE NUMBER OF DATA MESSAGES ADDED/DELETED FROM THE 
                     QUEUE. 
          EG     07/22/85    BDELINK, BLINK, HGETDA, HLONOFF, HLSTDX, 
                             HPPUT, HSFCBRK, HSWACNB, HUPDDAW (ADDED),
                             HUPDTDB (PURGED), RELACNB
 NA5B451  PROBLEM  - LOGOUT TERMINAL MESSAGE DID NOT GET DELIVERED TO 
                     IAF. 
          ANALYSIS - NIP ROUTINE HSWACNB DID NOT UPDATE THE COUNT OF
                     DATA BLOCKS QUEUED TO THE ACNB WHEN THE ACNB WAS 
                     SWITCHED FROM ONE APPLICATION TO ANOTHER.  THIS
                     CAUSED THE COUNT FIELDS TO BE OFF, SO IAF THOUGHT
                     THERE WAS NOT DATA QUEUED FOR IT.
          SOLUTION - NIP ROUTINE HSWACNB HAS BEEN CORRECTED TO UPDATE 
                     THE COUNT CORRECTLY. 
          EG     08/09/85    HSWACNB
 NA5B453  PROBLEM  - CS FAILED WITH CPU ERROR EXIT. 
          ANALYSIS - CS ROUTINE CSTRCT CALLED CS ROUTINE CSTITR WHICH 
                     CALLED SERVICE AND SCHEDULER ROUTINE SSTAQE WHICH
                     MOVED THE NDQ ENTRY.  THIS CAUSED THE BASE ARRAYS
                     THAT CS ROUTINE CSTRCT SET UP TO BE OFF BY 3 WORDS.
                     THE RESULT WAS A CPU ERROR EXIT. 
          SOLUTION - CS ROUTINE CSTRCT HAS BEEN CORRECTED TO RESET THE
                     BASE ARRAY POINTERS AFTER CALLING CS ROUTINE 
                     CSTITR.
          EG     08/14/85    CSTRCT 
 NA5B455  PROBLEM  - IF A CONNECTION WAS LOANED TO A SECONDARY APPL,
                     AND IF THE PRIMARY APPL FAILED OR NETTED OFF,
                     NVF WOULD NOT SEND OUT THE FAI/APP/N OR NET/OFF/N
                     UNTIL THE SECONDARY APPL RETURNED THE LOANED 
                     CONNECTION.
          ANALYSIS - WHEN THE CONNECTION WAS LOANED, NVF RESERVED THE 
                     CONNECTION WITH THE PRIMARY APPL.  SO WHEN THE 
                     PRIMARY APPL NETTED OFF OR FAILED, NVF THOUGHT 
                     THAT THE APPL STILL HAD AN OUTSTANDING T-A 
                     CONNECTION.
          SOLUTION - NVF WILL KEEP TRACK OF REGULAR CONNECTIONS AND 
                     "RESERVED" CONNECTIONS SEPARATELY.  THEN, IF 
                     AN APPL FAILS OR NETS OFF, NVF WILL CHECK FOR
                     ANY OUTSTANDING T-A OR A-A CONNECTIONS ONLY, AND 
                     WILL NOT CHECK FOR RESERVED CONNECTIONS.  IF 
                     THERE ARE NO T-A OR A-A CONNECTIONS OUTSTANDING, 
                     NVF WILL SEND OUT THE FAI/APP/N OR NET/OFF/N.
          PAM     85/08/13     TEXTNVF,NVFTCB,NVFTDSP,NVFTRVD,NVFTVVD,
                               NVFAIAP,NVFARAP,NVFOFAD,NVFSCAD,NVFSNON, 
                               NVFUCRS
 NA5B456  PROBLEM  - AIP USES LOCAL VARIABLE WITHOUT HAVING STORED
                     ANYTHING IN IT.
          SOLUTION - AIP ROUTINE NETGETQ HAS BEEN CORRECTED TO
                     USER INPUT VARIABLE ADR INSTEAD OF LOCAL 
                     VARIABLE ACLN. 
          EG     08/09/85    NETGETQ
 NA5B457  PROBLEM  - PIP ABORTED NIP WITH ERROR MESSAGE PIP ERROR 067.
          ANALYSIS - NIP HAD UPDATED THE COUNT OF PRU BUFFERS BEFORE
                     UPDATING THE POINTER FOR THE PRU BUFFERS.
          SOLUTION - NIP ROUTINE XCHKABC HAS BEEN CORRECTED TO UPDATE 
                     THE POINTER FIRST BEFORE UPDATING THE COUNT OF 
                     PRU BUFFERS. 
          EG     08/13/85    XCHKABC
 NA5B464  PROBLEM  - IF A CONNECTION WAS LOANED FROM A PRIMARY TO A 
                     SECONDARY APPL, BUT THE LOAN GETS REJECTED WITH
                     A CR/RCN/A, THE PRIMARY APPL MAY HANG IN THE 
                     K-DISPLAY (OR NIP MAY ABORT WITH CPU ERROR EXIT).
          ANALYSIS - AFTER NVF ISSUED THE CR/RCN/A, NIP SENT NVF A
                     CR/RCN TO RECONNECT TO THE PRIMARY APPL.  THE
                     PRIMARY APPL HAD A TACN = 1 AND RACN = 0.  NVF 
                     ERRONEOUSLY DECREMENTED RACN, SO IT HAD A VALUE
                     OF -1.  WHEN THE APPL WAS DROPPED, NVF DID NOT 
                     CLEAN UP THE APPLICATION TABLE BECAUSE IT THOUGHT
                     IT HAD OUTSTANDING CONNECTIONS.
          SOLUTION - WHEN AN INITIAL LOAN IS ATTEMPTED, THE TACN WILL 
                     BE DECREMENTED AND THE RACN WILL BE INCREMENTED. 
                     THIS WILL BE DONE FIRST INSTEAD OF LAST, TO TAKE 
                     CARE OF THE CASE WHERE THE LOAN NEVER COMPLETES
                     AND RESULTS IN A CR/RCN/A. 
          PAM     85/08/15     NVFTCB,NVFTDSP,NVFTRVD,NVFTVVD,NVFTRCN 
 NA5B465  PROBLEM  - NIP FAILED WITH ERROR MESSAGE -
                     NIP/HBSTTP ERR AN=  8,CN=1,17,13 
          ANALYSIS - A MALICIOUS APPLICATION HAD SENT A PRU/ON
                     SUPERVISORY MESSAGE TO NIP.  NIP REJECTED THE
                     PRU/ON SUPERVISORY MESSAGE BUT HAD MISTAKENLY
                     CHANGED THE STATE OF THE CONNECTION.  THIS CAUSED
                     NIP TO ABORT LATER WITH THE HOST SIDE BLOCK
                     PROTOCOL STATE TABLE ERROR.
          SOLUTION - NIP ROUTINE HPPUT HAS BEEN CORRECTED TO CALL NIP 
                     ROUTINE HBSTTP TO CHANGE THE STATE BACK TO NORMAL
                     AFTER A PRU/ON SUPERVISORY MESSAGE IS REJECTED.
          EG     08/15/85    HPPUT
 NA5B469  PROBLEM  - IF A USER TRIES TO LOAN A CONNECTION AND THE 
                     NAME OF THE SECONDARY APPL IS ONE OF THE 
                     RESERVED APPLICATION NAMES, SUCH AS "BYE" OR 
                     "LOGOUT", NVF WOULD SEND A CR/RCN/N INSTEAD OF 
                     CR/RCN/A.
          SOLUTION - CHANGE NVF TO SEND A CR/RCN/A WHEN A RESERVED
                     APPLICATION NAME IS SPECIFIED ON A LEND. 
          PAM     85/08/19     NVFTRVD,NVFTCRN,NVFTVAA
 NA5B470  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT AT 25503. 
          ANALYSIS - THE COUNT OF DELIVERABLE DATA BLOCKS HAD GONE
                     NEGATIVE.  SINCE THE COUNT IS STORED IN AN UNSIGNED
                     FIELD, THIS MEANT IT WAS TREATED AS A VERY LARGE 
                     POSITIVE NUMBER.  THIS CAUSED NIP TO THINK THAT
                     THERE WAS DELIVERABLE DATA QUEUED WHEN THERE WAS 
                     NOT.  BECAUSE THERE WAS NO DATA QUEUED, NIP FAILED 
                     WITH A CPU ERROR EXIT WHEN NIP ROUTINE HSCAND
                     PASSED A ZERO ACNB ADDRESS TO HGETDA.
          SOLUTION - THE FOLLOWING PLACES HAVE BEEN FOUND WHERE THE 
                     COUNT OF DELIVERABLE BLOCKS WAS NOT UPDATED
                     WHEN IT SHOULD HAVE BEEN.
  
                     - HBSTTP CLEARS TEMPORARY LIST OFF FLAG WHEN IT
                       PROCESSES A DOWNLINE MSG/QMSG BLOCK. 
                     - HLONOFF CLEARS TEMPORARY LIST OFF FLAG WHEN IT 
                       PROCESSES A LST/ON SUPERVISORY MESSAGE.
                     - HLSTDX CLEARS TEMPORARY LIST OFF FLAG WHEN IT
                       PROCESSES A LST/FDX SUPERVISORY MESSAGE. 
                     - HPPUT CLEARS LIST OFF FLAG WHEN IT PROCESSES A 
                       LST/SWH SUPERVISORY MESSAGE. 
                     - RELACNB RELEASES ALL DATA BLOCKS QUEUED FOR
                       CONNECTION.
          EG     08/17/85    HBSTTP, HLONOFF, HLSTDX, HPPUT, RELACNB
 NA5B473  PROBLEM  - NVF ABORTED WITH "ILLEGAL VCB ORDINAL".
          ANALYSIS - THE VCB ORDINAL WAS ILLEGAL BECAUSE A NEW
                     ORDINAL WAS ASSIGNED TO A CONNECTION, BUT THE
                     NEW ORDINAL HAD VALID DATA ASSOCIATED WITH IT. 
                     THIS MEANS THAT THE DATA IS STILL IN USE BY
                     ANOTHER CONNECTION.
                     WHEN NVF ENDS A CONNECTION, IT READS THE VCB 
                     DATA INTO THE PTAC TABLE AND THEN MARKS THE VCB
                     DATA AS INVALID.  IF A PTAC ENTRY EXISTS, THE
                     VCB DATA SHOULD BE INVALID.  IF A PTAC ENTRY 
                     DOESN'T EXIST FOR A CONNECTION, THE VCB DATA 
                     SHOULD BE VALID (AS THE VCB CONTAINS THE DATA
                     NORMALLY CONTAINED IN THE PTAC). 
                     IN THIS CASE, AN INITIAL LOAN WAS RETURNED TO
                     NVF IN LIMBO STATE.  NVF SENT A CR/SWH TO THE
                     PRIMARY APPL AND ERRONEOUSLY WROTE THE PTAC
                     INFO TO THE VCB FILE (THUS MAKING THE VCB DATA 
                     VALID).  FOR SOME REASON, THE SWITCH NEVER 
                     COMPLETED AND THE CONNECTION WAS BROKEN.  SINCE
                     NVF STILL HAD A PTAC ENTRY FOR THE CONNECTION, 
                     IT DID NOT BOTHER TO READ IN THE VCB DATA -- IT
                     JUST TERMINATED THE CONNECTION, LEAVING THE VCB
                     DATA MARKED AS VALID.  WHEN A NEW CONNECTION 
                     WAS ASSIGNED THE SAME VCB ORDINAL, THE ERROR 
                     OCCURRED AND NVF ABORTED.
          SOLUTION - NVF WILL NOT WRITE TO THE VCB FILE WHEN IT SENDS 
                     THE CR/SWH.  THE WRITING TO THE VCB FILE WILL
                     TAKE PLACE WHEN IT NORMALLY DOES -- UPON RECEIPT 
                     OF THE CR/ACC SM.
          PAM     85/08/19     NVFTRLC,NVFTRCN
 *L647*    ************************************************ 
 FPA6694  MODIFICATIONS TO PIP BASED ON DAP ARH6694.
  
          PIP CODE TO SUPPORT IEEE 802.3 HEADER SPECIFICATIONS. 
  
          SW     85/06/11    PIP
 FS4952   IMPLEMENTING CTRCTD COMMAND FOR CDCNET
          PROBLEM: NEED A CTRCTD COMMAND SUPPORT FROM 
                   THE HOST.
          ANALYSIS: THE APPLICATION NEEDS A FLAG IN 
                    CONREQ TO TELL THE APPLICATION IF 
                    IT IS GOING THROUGH MDI OR CCP. 
                    SUPPORT OF THE CTRCTDD COMMAND IS ALSO
                    NEEDED. 
  
          SOLUTION: WHEN ICNTE IS SENT FROM THE MDI TO THE
                    APPLICATION, NIP WILL SET A BIT IN CRITE
                    TO TELL NVF THAT IT IS FROM THE MDI.
                    NVF WILL SET A BIT IN THE CRSWH AND SENDS IT
                    TO NIP. NIP WILL THEN COPY IT TO BE A CONREQ. 
                    CTRCTD WILL BE SENT AS SYNCHRONOUS DATA.
          PAM $ YCY 85/08/19    NIP & NVF 
 NA5B186  PROBLEM  - NS LOOPING AND ISSUING MESSAGE - SM ABH ERROR. 
          ANALYSIS - SAM SENT NS A SUPERVISORY MESSAGE THAT WAS 69
                     WORDS LONG.  NIP CANNOT DELIVER SUPERVISORY
                     MESSAGES LARGER THAN 63 WORDS LONG TO THE
                     APPLICATION. 
          SOLUTION - NIP HAS BEEN CORRECTED TO DISCARD SUPERVISORY
                     MESSAGES FROM CCP LARGER THAN 63 WORDS LONG WHICH
                     ARE DESTINED FOR NS OR CS. 
          EG     09/23/85    NEIB1
 NA5B232  PROBLEM  - CS DISPLAYS WRONG TERMINAL CLASS FOR 3270 TERMINALS
                     IN TERMINAL STATUS MESSAGE.
          ANALYSIS - CS ROUTINE CSESTS WAS NEVER UPDATED TO SUPPORT 
                     3270 TERMINAL CLASS. 
          SOLUTION - CS ROUTINE CSESTS HAD BEEN CORRECTED TO SUPPORT
                     3270 TERMINAL CLASS. 
          EG     10/09/85    CSESTS 
 NA5B343  PROCESSING MDI SOFT ERROR 
          PROBLEM: NAM HANG WITH MESSAGES OUTSTANDING.
  
          ANALYSIS: WHEN PIP SENDS HECP MESSAGES TO NIP 
                    FOR MDI TROUBLES, IF THE MDI TROUBLE
                    IS RECOVERABLE, THEN IT WILL NOT
                    SEND REGCP TO CLEAN UP THE CONNECTIONS. 
                    FOR THESE KINDS OF THE ERRORS, NIP STILL
                    GOES AHEAD TO RELEASE THE DOWNLINE MSGS.
                    HENCE, RESULTING IN NAM HANGS.
  
          SOLUTION: A BIT HEMDI IS USED ON BIT 35 OF THE
                    HECP MESSAGE. IT IS ONLY SET FOR RECOVERABLE
                    MDI TROUBLE. WHEN NIP SEES THIS BIT SET, IT 
                    WILL JUST DAYFILE THE ERROR AND DOES NOT
                    RELEASE THE DOWNLINE MSGS.
  
          SW & YCY  85/08/19    PIP & NIP 
 NA5B418  PROBLEM  - THE PARAM CARD 
                         PARAM(ZZFC=500)
                     IN THE PARAM RECORDS INIT, RESTRT, RECOVR, MULTI,
                     MINIT, AND MRECOV IS TO BE REPLACED BY THE FOLLOWING@D 
                         PARAM(ZZFC=500)
                         PARAM(CDCNET=YES)
                         PARAM(FSSTART=NO)
                         PARAM(LSSTART=NO)
                         PARAM(OSSTART=NO)
                     TO SUPPORT CDCNET PROPERLY.
  
          SOLUTION - THE RECORDS ARE CHANGED AS REQUESTED.
  
          TET   07/17/85    INIT,RESTRT,RECOVR,MULTI,MINIT,MRECOV 
 NA5B423  ROUTINE NBADBSN IS NOT LISTED WHEN NIP IS BUILT 
  
          PROBLEM - THE LISTING OF ROUTINE NBADBSN IS SUPPRESSED
                    BECAUSE A STOPIMS CONTROL IS ABSENT.
  
          SOLUTION- ADD A STOPIMS CONTROL TO THE NBADBSN DECK.
  
          RMF            85/07/20       NBADBSN 
  
 NA5B428  FILE TRANSFERS BETWEEN CYBERS WITH DD=UU WRITES EXTRA WORD. 
  
          DESTINATION FILES FROM FILE TRANSFERS BETWEEN CYBERS WITH 
          DD=UU OR US ARE ALWAYS MADE EVEN CM WORDS LONG.  IF THE 
          SOURCE FILE IS ODD CM WORDS LONG, A PADDING OF A WHOLE CM 
          WORD IS APPENDED AT THE END OF THE DESTINATION FILE.
  
          IF A FILE TRANSFER ENDS AT THE BEGINNING OF AN EVEN NUMBERED
          CM WORD WITH UNUSED FOUR BITS, THIS CM WORD IS DISCARDED AS 
          IT IS NOT A PART OF THE SOURCE FILE.
  
          SW     85/10/03    PIP
 NA5B435  THIS FEATURE INTRODUCES NETWTQ IN AIP.
          ALSO, IN NIP CODE IS CUT TO HANDLE NETWTQ.
          YCY     85/07/19     NETXFR,NETWAIT,NETWTQ,AT,XSACB,XEXEC 
                               HWRAVAL,SYSTIME,NX$ACBX
 NA5B439  PROBLEM  - SAM NPU LOAD IS NOT VERY EFFICIENT BECAUSE EACH
                     WORKLIST FROM NS CONTAINS ONLY 1 SUPERVISORY 
                     MESSAGE WHEN IT COULD CONTAIN MANY.
          ANALYSIS - AIP FLUSHES THE WORKLIST IF THE BLOCK TYPE IS 4. 
          SOLUTION - AIP HAS BEEN CORRECTED TO NOT FLUSH THE WORKLIST 
                     IF THE BLOCK TYPE IS 4.
                     EG     09/06/85    NP$PUT, NP$PUTF 
 NA5B448  PIP MAY HANG DEPENDENT UPON SITE DEFINED PARAMETERS.
  
          IF MAXIMUM COUNT OF PIPS IN SYSTEM AND MAXIMUM COUNT OF 
          FRONT-END PROCESSORS FOR A PIP ARE DEFINED DIFFERENTLY
          AT A SITE, PIP MAY HANG IN THE TERMINATION PROCESSING 
          FOR ERRORS IN RELEASING ASSIGNED CHANNELS.
  
          MIXED USES OF MAXDRV AND MAXFE IN THE PIP CODE SHOULD 
          BE CORRECTED. 
  
          A MINOR CORRECTION FOR PIP LISTING IS INCLUDED. 
  
          SW     85/08/07    PIP
 NA5B454  PROBLEM  - NIP IS USING A LOT OF CPU TIME AND NO APPLICATION
                     CAN NETON. 
          ANALYSIS - THE NAM DAYFILE AND DUMP SHOWS EVERYTHING IS NORMAL
                     EXCEPT NVF HAS NOT NETTED ON YET.  NIP IS BEING
                     SATURATED WITH NETON WORKLIST FROM MANY OTHER
                     APPLICATIONS SO IT WAS NEVER ABLE TO PROCESS NVF-S 
                     NETON WORKLIST.
          SOLUTION - SINCE AIP WAS CONTINUALLY REISSUING THE NETON
                     WORKLIST FOR ALL THE APPLICATION, NIP WAS BUSY 
                     CONTINUALLY REJECTING NETON WORKLISTS.  AIP SHOULD 
                     DELAY BEFORE REISSUEING THE NETON WORKLIST.
          EG     09/10/85    NETON
 NA5B480  CHANGING DEFAULT VALUES FOR ABL AND DBL 
          FOR INTRAHOST A-A.
          PROBLEM: INTRAHOST DATA TRANSFER RATE IS POOR.
  
          ANALYSIS: THE CURRENT SETTINGS OF ABL AND DBL 
                    IS 2 AND 7 RESPECTIVELY FOR INTRAHOST 
                    A-A CONNECTIONS.
                    THIS WILL UNDERUTILISE THE DBL AND ABL
                    VALUES TO EFFECT A BETTER TURNAROUND
                    TIME FOR DATA TRANSFER. 
  
          SOLUTION: THE RECOMMENDED SETTINGS ARE ABL 7 AND DBL 5, 
                    RESPECTIVELY. 
  
          YCY  85/08/19    TEXTNVF
 NA5B481  PROBLEM: NIP DOESNOT LOGS THE CSR STATUS WORD FROM A COUPLER
          ERROR INTO THE ERRLOG FILE AS A NW01 MESSAGE. 
  
          SOLUTION: CODE IN NPHECP IS NOW CHANGED SUCH THAT THE TWELVE BIT CSR
           IS ALSO PART OF THE NW01 MESSAGE.
          YCY     85/09/12     SMNIP,NPHECP 
 NA5B482  PROBLEM  - CS ISSUES INCORRECTLY FORMATTED ACCOUTING FILE 
                     MESSAGES FOR CDCNET. 
          SOLUTION - CS ROUTINE CSESDA HAS BEEN CORRECTED TO ISSUE
                     THE ACCOUNTING MESSAGES IN THE CORRECT FORMAT. 
          EG     10/01/85    CSESDA 
 NA5B486  PROBLEM  - AIP DOES NOT TRUNCATE DATA FROM AIP-S UPLINE DATA
                     QUEUE IF THE APPLICATION HAS REQUESTED TRUNCATION. 
          ANALYSIS - AIP ROUTINE NP$EXTQ DID NOT UPDATE THE ABH WORD
                     WITH THE TRUNCATED SIZE. 
          SOLUTION - AIP ROUTINE NP$EXTQ HAS BEEN CORRECTED TO UPDATE 
                     THE ABH WORD WHEN IT TRUNCATES THE DATA SIZE.
          EG     09/03/85    NP$GETQ
 NA5B488  PROBLEM  - NIP FAILED WHEN A MASS STORAGE ERROR OCCURRED ON A 
                     FILE BEING TRANSFERRED TO ANOTHER HOST.
          ANALYSIS - NIP IS NOT SETTING THE ERROR PROCESSING FLAG IN THE
                     FET, SO CIO IS NOT GIVING CONTROL TO PIP WHEN IT 
                     ENCOUNTERS A MASS STORAGE ERROR.  INSTEAD, CIO IS
                     ABORTING NAM.
          SOLUTION - NIP HAS BEEN CORRECTED TO SET BOTH THE USER
                     PROCESSING AND ERROR PROCESSING FLAGS IN THE 
                     FET WHEN IT CREATES IT IN THE PRU BUFFER.
          EG     09/09/85    PRUBUFF, XCHKABC, HPRUON 
 NA5B491  PIP STAYS SERVICING BREAKPOINTED MDI TOO LONG.
  
          PIP IS CHANGED NOT TO TRY TO GET MDI GENERAL STATUS REPEATEDLY
          WHEN STATUS IS BUSY.
  
          SW     85/09/12    PIP
 NA5B493  PROBLEM  - THE FOLLOWING MISCELLANEOUS PROBLEMS HAVE BEEN 
                     FOUND IN NIP.
                     1. TWO PIPS WERE FOUND TO BE PERFORMING THE EST
                        SCAN. 
                     2. NBT INBOUND BUFFERS WERE FOUND THAT SHOULD HAVE 
                        BEEN RELEASED.
                     3. NIP DOES NOT SAVE SYS= AND RCL= ADDRESSES.
          ANALYSIS - 1. WHEN AN EST ENTRY IS TURNED OFF WHICH RESULTS 
                        IN THE PIP THAT IS PERFORMING THE EST SCAN TO 
                        DROP OUT AND LATER THE SAME EST ENTRY IS
                        TURNED ON WHICH RESULTS IN A NEW PIP BEING
                        CALLED INTO A PP, THAT PIP WILL PERFORM THE 
                        EST SCAN EVEN IF ANOTHER PIP IS PERFORMING
                        THE EST SCAN. 
                     2. WHEN NEIB SWITCHES INBOUND FET PROCESSING, IT 
                        IS NOT CHECKING IF THE NBT ENTRY HAS BEEN 
                        CLEARED DUE TO NIP PROCESSING AN EST/OFF
                        SUPERVISORY MESSAGE.  THIS CAN RESULT IN
                        NIP ALLOCATING A INBOUND BUFFER FOR A FREE
                        NBT ENTRY.
          SOLUTION - 1. NIP ROUTINE XCHKCET HAS BEEN CORRECTED TO CLEAR 
                        THE EST SCAN FLAG WHEN IT SETS UP A UNUSED PIT
                        ENTRY.
                     2. NIP ROUTINE NEIB HAS BEEN CORRECTED TO CHECK FOR
                        NBT ENTRY IN USE BEFORE PROCESSING THE INBOUND
                        BUFFER AFTER A SWITCH.
                     3. NIP ROUTINE IRECVR HAS BEEN CORRECTED TO SAVE 
                        THE RETURN ADDRESS OF SYS= AND RCL=.
          EG     09/09/85    NEIB, XCHKCET, IRECVR
 NA5B501  PROBLEM  - AIP DID NOT DISCARD DATA IN THE UPLINE DATA QUEUE
                     CORRECTLY. 
          ANALYSIS - AIP ROUTINE NP$GETQ DID NOT ADJUST ITS POINTERS
                     CORRECTLY WHEN IT WAS DISCARDING THE DATA MESSAGES 
                     IN THE UPLINE DATA QUEUE.  ALSO AIP ROUTINE NP$SEND
                     WAS CHECKING CORRECTLY FOR THE BUFFER LENGTH.
          SOLUTION - AIP ROUTINE NP$GETQ HAS BEEN CORRECTED TO UPDATE 
                     THE DATA QUEUE POINTERS CORRECTLY AND AIP ROUTINE
                     NP$SEND HAS BEEN CORRECTED TO CHECK THE BUFFER 
                     POINTERS CORRECTLY.
          EG     09/12/85    NP$GETQ, NP$SEND 
 NA5B507  PROBLEM  - NIP FAILED WITH MRELS BUFFER MANAGEMENT ERROR. 
                   - NIP DID NOT SEND DATA BLOCKS TO THE APPLICATION IN 
                     THE EXACT ORDER THE DATA BLOCK WERE RECEIVED BY
                     NIP. 
          ANALYSIS - AN APPLICATION WAS TESTING THE PLATO INTERFACE AND 
                     RECEIVED DATA BLOCKS THAT FILLED UP THE AIP BUFFER.
                     THIS CAUSED NIP ROUTINE HPGETMM TO OVERWRITE THE 
                     WORD IMMEDIATELY AFTER THE END OF THE BUFFER.
                   - NIP ROUTINES HGETDA AND DELCDR HAD BOTH UPDATED
                     THE POINTER IN THE ACB OF THE LAST ACNB THAT NIP 
                     DELINKED DATA FROM.
          SOLUTION - NIP ROUTINE HPGETMM HAS BEEN CORRECTED TO ALLOCATE 
                     A BUFFER TWO WORDS LARGER THAN THE AVAILABLE SPACE 
                     IN AIP-S BUFFER. 
                   - NIP HAS BEEN CORRECTED TO USE THE POINTER IN THE 
                     ACB TO POINT TO THE NEXT ACNB TO EXTRACT DATA FROM 
                     INSTEAD OF THE LAST ACNB IT EXTRACTED DATA FROM. 
          EG     09/19/85    BDELINK, HGETDA, HPGETMM, HSCAND 
 NA5B508  PROBLEM  - AIP RETURNED NULL BLOCK TO APPLICATION WHEN IT HAD 
                     DATA QUEUED IN ITS UPLINE DATA BUFFER. 
          ANALYSIS - AIP ROUTINE NETGETQ DID NOT CHECK CORRECTLY FOR
                     DATA AVAILABLE IN THE BUFFER IF THE LIST NUMBER WAS
                     ZERO.
          SOLUTION - AIP ROUTINE NETGETQ HAS BEEN CORRECTED TO CHECK
                     CORRECTLY. 
          EG     09/19/85    NETGETQ
 NA5B509  PROBLEM  - THE PARAM CARDS
                         PARAM(ZZFC=500), 
                         PARAM(CDCNET=YES), 
                         PARAM(FSSTART=NO), 
                         PARAM(LSSTART=NO), AND 
                         PARAM(OSSTART=NO)
                     ARE TO BE DELETED FROM THE FOLLOWING PARAMETER 
                     RECORDS, INIT, RESTRT, RECOVR, MULTI, MINIT, 
                     AND MRECOV.
  
                     THESE PARAM CARDS WILL BE ADDED TO CDCNET NAMSTRT
                     IN THE CHA1 BUILD STEP.
  
          SOLUTION - THE PARAM CARDS ARE DELETED AS DESCRIBED.
  
          TET   10/03/85    INIT,RESTRT,RECOVR,MULTI,MINIT,MRECOV 
 NA5B511  PROBLEM - NAMSTRT RECORDS DO NOT ATTACH NCFFILE, LCFFILE, AND 
                    NLFFILE FROM THE CORRECT USERNAME NOW THAT THE
                    CDCNET INSTALLATION PICTURE HAS BEEN FINALIZED. 
                    THE USERNAME FOR THESE FILES IS NOW *NETADMN*.
          SOLUTION - ADD A *PARAM* STATEMENT TO EACH OF THE PARAMETER 
                    RECORDS TO INDICATE THE USERNAME WHERE THE FILES
                    ARE STORED. 
          JAH     85/09/23     NWINIT,NWRESTRT,NWRECOVR,NWMULTI,NWMINIT,
                               NWMRECOV,JOBCS,JOBNS,JOBNVF
 NA5B514  CORRECTING MACRO EXPANSION IN BUILDING
          SYMBOL TABLE IN AIP.
          PROBLEM: NFETCH AND NSTORE ABORTED APPLICATIONS.
  
          ANALYSIS: THE SYMBOL TABLE ENTRY AFTER CONNET 
                    WAS CLOBBERED AND ALL ENTRIES AFTER 
                    THAT WERE SHIFTED BY ONE WORD.
                    THE MACRO EXPANSION CANNOT HANDLE A 
                    B DECLARATION.
  
          SOLUTION: CONNET WHICH WAS DECLARED AS
                    B(00,43,01) IS NOW DECLARED AS U(00,43,01). 
  
          YCY  85/08/19    SMAPPL 
 NA5B515  PIP MAY HANG AFTER NPU OR MDI ON CHANNEL ZERO IS TURNED OFF.
  
          PIP KEEPS CHANNEL RESERVATION TABLE INTERNALLY TO KNOW WHEN 
          TO RELEASE A CHANNEL TO SYSTEM. 
          WHEN NPU/MDI ON CHANNEL ZERO IS NOT THE FIRST ONE ASSIGNED TO 
          THE PIP AND SOME OF THE PRECEDING NPU/MDI IS ALREADY SET OFF, 
          PIP HAS TROUBLES IN HANDLING THE TABLE TO TURN OFF THE NPU/MDI
          ON CHANNEL ZERO THAT CAUSES PIP TO HANG LATER WHEN MORE 
          NPU/MDI IS TURNED ON OR WHEN NAM IS TURNED DOWN.
  
          INTERPRETATION OF EMPTY ENTRY IN THE TABLE IS CORRECTED.
  
          SW     85/09/25    PIP
 NA5B518  PROBLEM  - NIP ABORTED ON INTERNAL ERROR IN PROC HSCAND.
          ANALYSIS - NIP HAD AN ACNB QUEUED IN THE CONNECTION DATA
                     RING THAT HAD NO DATA QUEUED FOR IT.  THE
                     ACNB HAD DATA QUEUED BUT THAT DATA WAS THROWN
                     AWAY WHEN THE APPLICATION RECEIVED A FC/BRK SUP
                     MSG.  HOWEVER, THE ACNB WAS NOT TAKEN OUT OF THE 
                     CONNECTION DATA RING.
          SOLUTION - NIP ROUTINE HSFCBRK HAS BEEN CORRECTED TO CALL 
                     DELCDR WHEN IT RELEASES ALL THE DATA BLOCK QUEUED
                     TO THE ACNB. 
          EG     09/27/85   HSFCBRK 
 NA5B519  PROBLEM  - WHILE A CONNECTION IS LOANED TO A SECONDARY APPL,
                     IF THE PRIMARY APPL SHOULD FAIL AND THEN NET BACK
                     ON AND RECEIVE THE SAME APPL NUMBER THAT IT HAD
                     BEFORE, AFTER THE LOANED CONNECTION IS RETURNED, 
                     ANYONE TRYING TO CONNECT TO THE (ONCE) PRIMARY 
                     APPL WILL RECEIVE THE MESSAGE "APPLICATION BUSY".
          ANALYSIS - WHEN THE LOANED CONNECTION IS RETURNED WITH
                     REASON CODE 9 (PRIMARY APPL FAILED), NVF TRIES TO
                     LOCATE THE PRIMARY AND DECREMENT THE RESERVED
                     CONNECTION COUNT.  SINCE NVF FOUND AN APPL WITH
                     THE SAME APPL NUMBER AS THE PRIMARY APPL, NVF
                     DECREMENTED THE RESERVED CONNECTION COUNT.  THIS 
                     PUT THE COUNT FOR THAT APPL AT -1 (777776).  THEN, 
                     WHENEVER ANYONE TRIED TO CONNECT TO THAT APPL, NVF 
                     THOUGHT IT HAD TOO MANY CONNECTIONS ALREADY AND
                     SENT THE "APPL BUSY" MESSAGE.
          SOLUTION - IF A LOANED CONNECTION IS RETURNED TO NVF WITH 
                     REASON CODE 9, NVF WILL NOT DECREMENT THE RESERVED 
                     CONNECTION COUNT OF THE PRIMARY APPL, SINCE THE
                     PRIMARY APPL HAS ALREADY GONE AWAY.
          PAM     85/10/04     NVFTRVD
 NA5B522  CORRECTING OVERLAPPING DEFINTIONS THAT CAUSE IAF
          HANG. 
          PROBLEM: IAF APPLICATION BUSY.
  
          ANALYSIS: THE PTA$NET OVERLAPS WITH ANOTHER COUNT 
                    FIELD IN TEXTNVF SUCH THAT WHEN 
                    A CONNETION IS ABOUT TO BE ESTABLISHED
                    THE COUNT GOES UP BY ERROR. 
  
          SOLUTION: PTA$NET IS REDEFINED AS BIT 42 INSTEAD OF 
                    AS BIT 43.
          PAM       85/10/03    NVF 
 NA5B527  PROBLEM  - THE FORMAT OF THE CDCNET ACCOUNTING MESSAGE HAS
                     CHANGED. 
          SOLUTION - CS ROUTINE CSESDA HAS BEEN CORRECTED TO HANDLE 
                     THE NEW FORMAT.
          EG     10/04/85    SMCS, CSESDA 
 NA5B528  PROBLEM  - THE FEATURE CODE FOR CDCNET TERMINAL CHARACTERISTICS 
                     DOES NOT WORK. 
          ANALYSIS - THE BIT INDICATING WHETHER THE TERMINAL WAS USING
                     CDCNET OR CCP WAS NOT IN THE SAME PLACE IN THE 
                     CR/SWH AND THE CON/REQ.
          SOLUTION - CHANGE THE ITEM DESCRIPTION OF THE *CRSWNET* ITEM
                     IN THE CR/SWH TO MATCH THE CORRESPONDING ITEM IN 
                     THE CON/REQ. 
          PAM     85/10/08     SMNVF
 NA5B531  PIP STAYS IN A LOOP MORE THAN 30 SEC AT CHANNEL ACCESS ERRORS.
  
          IF PIP GETS CHANNEL ACCESS ERRORS LIKE CHANNEL ACTIVE AFTER 
          FUNCTION, PIP STAYS IN A LOOP RETRYING CHANNEL ACCESSES FOR 
          63 TIMES BEFORE MDI INOPERATIVE IS REPORTED.
  
          THE CODE IS CHANGED TO REPORT CHANNEL ACCESS ERROR AND LEAVE
          THE LOOP EACH TIME PIP FINDS THIS KIND OF ERRORS AND MDI
          INOPERATIVE IS REPORTED AFTER 8 ERRORS. 
  
          SW     85/10/28    PIP
 NA5B535  MDI INPUT BLOCK PROTOCOL ERROR RECOVERY TRIAL NEVER ENDS. 
  
          MDI INPUT BLOCK PROTOCOL ERROR IS TO BE TERMINATED AFTER
          EIGHT SUCCESSIVE FAILURES BUT THE TRY IS REPEATED UNTIL 
          SUCCESSFUL RECOVERY.
  
          CODE IS CORRECTED.
  
          SW     85/10/11    PIP
 NA5B537  PROBLEM  - CDCNET BIT IS NOT SET ON CONNECTION SWITCH.
          ANALYSIS - NVF WAS STORING THE CDCNET BIT IN THE VCB TABLE, 
                     BUT WHEN THE INFORMATION WAS COPIED FROM THE VCB 
                     TO THE PTAC ON A RECONNECT, NVF DID NOT COPY THE 
                     THE CDCNET BIT TO THE PTAC.
          SOLUTION - HAVE NVF COPY THE CDCNET BIT FROM THE VCB TO THE 
                     PTAC DURING A RECONNECT. 
          PAM     85/10/17     NVFTRVD
 NA5B543  PROBLEM  - INITMDI HAS WRONG CPU PRIORITY.  IT SHOULD HAVE
                     CPU PRIORITY FOR NETWORK SERVICE CLASS INSTEAD 
                     OF SYSTEM ORIGIN SERVICE CLASS.
          ANALYSIS - INITMDI IS BEING RUN AS A SYSTEM ORIGIN SERVICE
                     CLASS JOB. 
          SOLUTION - NIP ROUTINE NPININD HAS BEEN CORRECTED TO FORCE
                     THE SERVICE CLASS OF THE INITMDI JOB TO NETWORK
                     WHEN IT CALLS DSP TO ROUTE THE JOB IN. 
          EG     10/18/85    NPININD
 NA5B544  IGNORING SECOND NCBRKPC TRIGGER.
          PROBLEM: NAM FAILED WITH NCSTATE = 16, TRIGGER
                   IS NCBRKPC (13). 
          ANALYSIS: WHEN PIP DETECTS A BLOCK SEQUENCE 
                    ERROR, PIP SENDS NIP WORKLIST WITH
                    OP CODE = 6. NIP THEN CHANGES STATE 
                    TO STATE 16 WAITING ON A PIPR FROM PIP. 
                    IN THIS STATE, IF PIP SEES ANOTHER BLOCK
                    SEQUENCE ERROR, IT CAN SEND NIP ANOTHER 
                    PRU WORKLIST WITH OPCODE = 6 BEFORE IT
                    FINALLY SENDS NIP A WORKLIST WITH OPCODE
                    3 ( PRU TERMINATION WORKLIST).
  
          SOLUTION: STATTBL CODE IS CHANGED SUCH THAT IN
                    STATE 16, NIP CAN STILL ACCEPT TRIGGER
                    NCBRKPC AND IGNORE IT.
  
          YCY  85/10/21    STATTBL
 NA5B546  PIP ERROR 76 - BLOCK PROTOCOL ERROR AFTER LEVEL SEVEN ERROR.
  
          IF A BLOCK PROTOCOL ERROR IS FOUND BEFORE THE LEVEL SEVEN 
          ERROR FOUND IN A PREVIOUS PRU INPUT IS NOT YET REPORTED TO
          NIP,  PIP TREATS IT AS AN ILLOGICAL ACTION.  IT SHOULD BE 
          ALLOWED.
  
          PIP STREAM STATE RESPONSE TABLE IS CHANGED TO ALLOW THE 
          SITUATION.
  
          SW     85/10/22    PIP
 NA5B548  PROBLEM: NAM DIED WITH MRELS BUFFER 
          MANAGEMENT ERROR. 
  
          ANALYSIS: AN APPLICATION SENT A 
          CONACRQ WITH TLC = 1. 
  
          SOLUTION: NIP SHOULD PROTECT ITSELF 
                    FROM AN APPLICATION 
                    SPECIFYING A TLC LESS THAN
                    THE MINIMUN REQUIRED SIZE 
                    OF THE SUPERVISORY MESSAGE. 
  
          YCY     85/10/24     HPPUT
 NA5B557  PROBLEM  - NETWORK APPLICATIONS THAT USE THE NAM K-DISPLAY
                     FEATURE SHOULD HAVE THE CAPABILITY TO TURN ON/OFF
                     LOGGING OF K-DISPLAY TYPEINS IN THE NAM/SYSTEM 
                     DAYFILE. 
          SOLUTION - A NEW HOP/DAY SUPERVISORY MESSAGE HAS BEEN 
                     DEFINED.  IT IS SENT FROM THE APPLICATION TO NAM 
                     WHEN THE APPLICATION EITHER WANTS TO TURN ON OR
                     OFF THE LOGGING OF K-DISPLAY TYPEINS.
          EG     10/28/85    SMAPDEF, SMAPPFC, SMAPPL, KDIS, HPPUT, 
                             KPTYPIN, KPCLNUP, HPKDISP, SKENIP
 NA5B573  DELAYS FOR MDI CHANNEL ERROR BY PIP IS TOO SHORT. 
  
          MDI CHANNEL ERROR RETRY DELAY LOOP COUNT IS INCREASED TO 4000.
  
          SW     85/11/19    PIP
  
 NA50340  PROBLEM  - NOP MESSAGE FROM CS TO ALL NPUS HAD CHARACTER
                     CHANGED. 
          ANALYSIS - SERVICE AND SCHEDULER ROUTINE SSRRCS CALLED SERVICE
                     AND SCHEDULER ROUTINE SSBEBF TO EXTRACT 60 BITS
                     FROM THE CHARACTER STRING.  THE BIT POSITION FOR 
                     THE BEGINNING OF THE EXTRACTION WAS 60.  THIS
                     CAUSED ROUTINE SSBEBF TO EXTRACT AN EXTRA BIT FROM 
                     THE PREVIOUS WORD IN THE STRING AND MODIFY A 
                     CHARACTER IN THE NEWLY CREATED COPY OF THE STRING. 
          SOLUTION - SERVICE AND SCHEDULER ROUTINE SSRRCS HAS BEEN
                     CORRECTED TO CHECK FOR BIT POSITION OF 60 AND
                     CONVERT IT TO ZERO.
          EG     10/09/85    SSRRCS 
 NA50382  IMPLEMENTING PRIVILEGED APPLICATION OUTCALLS. 
          PROBLEM: PRIVILEGED APPLICATION OUTCALL IS
                   NOT HONOURED.
  
          METHOD:  IF AN APPLICATION SPECIFIES ANY NUMBER OF
                   WORDS GREATER THAN THE EXISTING TWO WORDS
                   FOR THE CONACRQ CALL, THE EXCESS WORDS WILL
                   BE CARRIED OVER TO THE CRIAPR CALL.
                   THIS WILL NOT BE DONE ON SUBSEQUENT RETRYS.
  
                   IN NVF, SOME FIXES IN T
                   CHECKS THE PRIVILEGED APPLICATION OUTCALLS.
  
          PAM $ YCY 85/10/07    NIP & NVF 
 NA50420  CORRECTING CA VALUES FOR 3270 TERMINALS.
          PROBLEM: A 3270 TERMINAL DOES NOT HAVE THE
                   CORRECT CA VALUES OTHER THAN 0.
          ANALYSIS: IN MTRMPRM, THE ERROR STATUS FLAG 
                    IN THE RANGE CHECKING WAS NOT SET 
                    CORRECTLY.
  
          SOLUTION: IN MTRMPRM, THE ERROR FLAG IS NOW SET 
                    CORRECTLY.
          YCY 85/09/25    NDLNFCM 
 *L664*    ************************************************ 
 FN25QT1  THE FOLLOWING FEATURES HAVE BEEN ADDED TO QTRM FOR
          NOS 2.5.1 RELEASE.
  
          1. INCORPORATE QTRM CODE GENERATED BY ISD TO SUPPORT
             POLLING SINGLE CONNECTIONS FOR DATA. 
          2. PROVIDE CAPABILITY FOR QTRM APPLICATION TO SUPPRESS
             LOGGING OF NAM K-DISPLAY TYPEINS.
          3. PROVIDE CAPABILITY FOR QTRM APPLICATIONS TO CHANGE 
             INACTIVITY TIMER.
  
          EG     12/04/85    QTRMCON, QTCMD, QTGET, QTOPEN, QTSUP 
 FN6865  IMPLEMENT INPUT TIMEOUT DAP ARH6865. 
  
         NEW SUPERVISORY MESSAGE FROM APPLICATION TO NIP HAS BEEN 
         CREATED - DC/STMR WITH PFC/SFC VALUE C202.  NEW NIP OVERLAY
         HDCSTMR HAS BEEN CREATED TO PROCESS THIS SUPERVISORY MESSAGE.
         NIP ROUTINES HSFCINA AND XCHKPCR HAVE BEEN MODIFIED TO SUPPORT 
         THE NEW FEATURE. 
  
         EG     11/20/85
 FN6991   IMPLEMENT COMPUTER ACCESS SECURITY FEATURES IN NOS 2.5.1
  
          THIS MODSET IMPLEMENTS THE NAM PORTION OF THE COMPUTER
          ACCESS SECURITY FEATURES.  NVF WAS MODIFIED TO IMPLEMENT THE
          *PERSONAL IDENTIFIER VALIDATION*,  *RESTRICT MULTIPLE 
          CONCURRENT LOGINS*, *PASSWORD EXPIRATION* FEATURES, AND THE 
          PASSWORD OVERMASKING FEATURE. 
  
          DEPENDENCIES -
  
          SRN - HQD4137      SCR - 2561 
  
          GAH            02/17/86           TMSGNVF,TEXTNVF,TXTANVF 
                                            NVFCTRM,NVFISUE,NVFTACC 
                                            NVFTCRN,NVFTDAD,NVFTDSP 
                                            NVFTETC,NVFTETI,NVFTIAM 
                                            NVFTILP,NVFTPSV,NVFTPUV 
                                            NVFTPVR,NVFTRLC,NVFTRVD 
                                            NVFTVVD 
  
 NA5B013  FIXING HOP/ALT RESPONSE IN IGNORED STATE. 
          PROBLEM: HOP/ALT WAS NOT  RESPONDED WITH
                   HOP/IG IN IGNORED STATE. 
          ANALYSIS: WHEN AN APPLICATION IS IN IGNORED 
                    STATE, A HOP/ALT SHOULD GET A 
                    HOP/ALT RESPONSE. 
  
          SOLUTION: IN HPKDISP, THE THE APPLICATION NUMBER
                    WAS SET TO ZERO TO LOOK UP THE THE ATI
                    BIT. IT IS NOW CHANGED SUCH THAT THE
                    CORRECT AN VALUE IS USED TO INDEX INTO
                    THE AT TABLE FOR THE ATI FLAG.
         YCY 85/11/04    NIP
NA5B475   PROBLEM  - TERMINAL HANG DURING LENDING BECAUSE NVF DOES NOT
                     SEND OUT CR/SWH
          ANALYSIS - WHILE FORMING THE CR/SWH SM, NVF MISSPELLED A FIELD
                     NAME, CRSLST INSTEAD OF CRSWLST. THE MISSPELLED
                     FIELD NAME, CRCLST, HAPPENED TO BE A THAT OF AN
                     EXISTING FIELD, WHICH SHARED MEMORY LOCATION WHICH 
                     THE CRNACN FIELD. AS A RESULT, THE ACN WAS OVER
                     WRITTEN, AND THE CR/SWH SM WENT TO A DIFFERENT 
                     CONNECTION.
          SOLUTION - THE MISSPELLING ,IN NVFTRLC, HAS BEEN CORRECTED
          TET     85/11/21     NVFTRLC
 NA5B510  PROBLEM  - NAM DID NOT RELEASE THE EST ENTRY AFTER THE EST
                     ENTRY WAS TURNED OFF.
          ANALYSIS - PIP NEVER RELEASED THE EST ENTRY BECAUSE IT WAS
                     WAITING FOR A REG/CP/N SUPERVISORY MESSAGE FROM
                     NIP.  NIP DID NOT SEND THE REG/CP/N SUPERVISORY
                     MESSAGE BECAUSE IT WAS WAITING FOR A TERMINATE 
                     PRU CONNECTION WORKLIST FROM PIP.  PIP HAD SENT
                     THIS WORKLIST, SO NIP MUST HAVE LOST IT.  TWO
                     CASES WERE FOUND IN NIP WHERE IT WOULD LOSE
                     TRACK OF THE TERMINATE PRU CONNECTION WORKLIST.
                     THE FIRST CASE WAS IF THERE WERE 2 ENTRIES IN
                     THE ACB PWL RING AND NIP RECEIVED A REASON CODE
                     OF 44 IN RESPONSE TO THE SWAPIN OF THE APPLICATION.
                     NIP WOULD RELINK THE FIRST PWL ENTRY IN THE RING 
                     EVEN THOUGH IT WAS ALREADY LINKED.  THE RESULT 
                     WOULD BE THE SECOND PWL ENTRY WOULD GET LOST AND 
                     NEVER BE PROCESSED.  THE SECOND CASE WAS IF THE
                     APPLICATION HAD TWO CONNECTIONS AND THESE TWO
                     CONNECTIONS HAD THE SAME NETWORK CONNECTION
                     NUMBER ON DIFFERENT LOGICAL LINKS.  WHEN NIP 
                     PROCESSED THE PWL ENTRY IN THE ACB PWL RING FOR
                     THE FIRST CONNECTION, IT WOULD ALSO RELEASE THE
                     ENTRY IN THE ACB PWL RING FOR THE SECOND 
                     CONNECTION WITHOUT EVER PROCESSING IT. 
          SOLUTION - NIP ROUTINE XSACB HAS BEEN CORRECTED TO NOT CALL 
                     NPPWL TO PROCESS THE PWL RING IF THE APPLICATION 
                     IS STILL SWAPPED OUT.  NIP ROUTINE NPPCT HAS BEEN
                     CORRECTED TO CHECK THE WHOLE NETWORK ADDRESS 
                     RATHER THAN JUST THE CONNECTION NUMBER WHEN IT 
                     CHECKS FOR ENTRIES IN THE ACB PWL RING TO RELEASE. 
          EG     10/18/85    PWL, NPPCT, XSACB
 NA5B532  PROBLEM  - NVF HUNG IN OUTCALL LIST BECAUSE OF BAD OUTCALL
                     ENTRY. 
  
          ANALYSIS - THIS HAS HAPPENED BECAUSE THE SIZE OF THE OUTCALL
                     RECORD IN THE LCF WAS AN EXACT MULTIPLE OF PRU.
                     DURING INITIALIZATION TIME, NVFIAST COPIES THE LCF 
                     INTO NVF'S INTERNAL TABLES. SINCE THE SIZE OF THE
                     OUTCALL RECORD WAS AN EXACT MULTIPLE OF PRU, THE 
                     READ MACRO HAS COMPLETELY TRANSFERED THE WHOLE 
                     OUTCALL RECORD INTO NVF WITHOUT DETECTING THE EOR. 
                     IN THE NEXT ITERATION, THE READ ENCOUNTERED AN EOR 
                     WHILE IT WAS TRYING TO READ THE INCALL RECORD. THIS
                     HAS BEEN MISINTERPRETED BY NVFIAST, AND THE RESULT 
                     WAS THE SIZE THE OUTCALL LIST BEING DOUBLED WITH 
                     UNDEFINED  ENTRIES IN THE SECOND HALF. 
  
          SOLUTION - MODIFY NVFIAST SO THAT IT WILL NOW SAVE THE RECORD 
                     NAME FOR THE CURRENT ITERATION, AND ASSURE THAT IT 
                     IS NOT THE SAME WHEN THE NEXT RECORD IS READ. IF 
                     THE RECORD NAME DOES NOT CHANGE AFTER A READ, THE
                     READ HAS SIMPLY READ AN EOR INSTEAD OF NEXT RECORD.
                     IN THIS CASE, ANOTHER READ WILL BE ISSUE TO READ 
                     THE NEXT RECORD. 
  
          TET   03/13/86    NVFIAST 
 NA5B547  PROBLEM  - NIP REACHED MAXIMUM FIELD LENGTH DUE TO MALICIOUS
                     APPLICATION. 
          ANALYSIS - MALICIOUS APPLICATION SENT 10000 PRU/ON/R
                     SUPERVISORY MESSAGES AND 1000 CON/ACRQ SUPERVISORY 
                     MESSAGES.  THIS CAUSED NIP TO GENERATE AND QUEUE 
                     10000 PRU/ON/A SUPERVISORY MESSAGES AND 1000 
                     CON/ACRQ/A SUPERVISORY MESSAGES WHICH WAS MORE 
                     THAN ENOUGH TO CAUSE NIP TO REACH ITS MAXIMUM
                     FIELD LENGTH.
          SOLUTION - NIP HAS BEEN CORRECTED TO RETURN AN ERR/LGL
                     SUPERVISORY MESSAGE TO THE APPLICATION IF THE
                     APPLICATION SENDS A PRU/ON/R OR CON/ACRQ/R 
                     SUPERVISORY MESSAGE WHICH RESULTS IN AN ABNORMAL 
                     RESPONSE AND NIP HAS 100 CON/ACRQ/A, 
                     PRU/ON/A, OR ERR/LGL SUPERVISORY MESSAGES QUEUED 
                     FOR THE APPLICATION.  IF NIP HAS MORE
                     THAN 100 CON/ACRQ/A, PRU/ON/A, OR ERR/LGL
                     SUPERVISORY MESSAGES QUEUED FOR THE APPLICATION, 
                     THEN NO ABNORMAL RESPONSE (I.E. NO SUPERVISORY 
                     MESSAGE IS GENERATED) IS SENT TO THE APPLICATION 
                     IF THE PRU/ON/R OR CON/ACRQ/R IS REJECTED. 
         EG     11/07/85    ACB, AWLDEFS, HBSTTP, HCACRQA, HCSTTP,
                            HPRUON, HPRUONX 
 NA5B569  PROBLEM  - NVF ABORTS WITH "NVFTURT - CANNOT FIND PTAC ENTRY".
          ANALYSIS - IF A USER ENDS A CONNECTION BY TYPING "BYE" AT 
                     THE SAME TIME THAT ANOTHER USER IS TRYING TO LOAN
                     A CONNECTION, NVF CAN DELETE THE PTAC ENTRY OF 
                     BOTH CONNECTIONS.  FOR THE USER THAT TYPES "BYE",
                     NVF CALLS NVFTCRN, WHICH CALLS NVFTETC TO DELETE 
                     THE PTAC ENTRY.  ON RETURN FROM NVFTCRN, THE PTAC
                     ENTRY HAS BEEN DELETED, BUT NVF STILL CHECKS AN
                     ENTRY IN THE PTAC TO SEE IF THIS IS A LOANED 
                     CONNECTION.  IN THIS CASE, IT IS ACTUALLY CHECKING 
                     THE WRONG PTAC -- THAT OF THE LOANED CONNECTION. 
                     NVF THINKS THAT THIS LOANED CONNECTION HAS 
                     SPECIFIED "BYE" AS THE SECONDARY APPLICATION, AND
                     IT PROCEEDS TO SEND OUT A CR/RCN/A AND DELETE THE
                     PTAC OF THE LOANED CONNECTION.  WHEN NVF GETS
                     AROUND TO ACTUALLY PROCESSING THE REAL LOANED
                     CONNECTION, THE PTAC ENTRY IS GONE, AND NVF ABORTS.
          SOLUTION - ON RETURN FROM NVFTCRN, NVF WILL ONLY CHECK THE
                     PTAC TABLE IF THE USER HAD TYPED IN "HELLO" OR 
                     "LOGIN", AS THE PTAC WILL STILL BE AROUND.  IF 
                     THE USER TYPED IN "BYE" OR "LOGOUT", NVF WILL NOT
                     CHECK THE PTAC BECAUSE IT WILL HAVE ALREADY BEEN 
                     DELETED. 
          PAM     85/11/18     TEXTNVF,NVFTCRN,NVFTRVD,NVFTVAA
 NA5B570  FOR A DEBUG NAM SYSTEM, DBGSTOP SHOULD
          CAUSE A NAM  FAILURE. 
  
          ANALYSIS: IN KNAMCOM, WHEN DEBUG WAS TURNED 
                    ON, KNAMDB WAS IGNORED BECAUSE
                    THE CODE WAS THERE ONLY FOR A 
                    NONDEBUG SYSTEM.
  
          SOLUTION: IN KNAMCOM, THE CODE SHOULD BE THERE
                    FOR A DEBUG SYSTEM AND HENCE KNAMDB 
                    IS SET TO TRUE. WHEN DBGSTOP IS 
                    RECEIVED, IT WILL CAUSE A NAM ABORT.
          YCY       86/01/06    NIP 
 NA5B572  NAM STILL ALLOW FILE TRANSFER EVEN IN REGULATION
          LEVEL 2.
  
          ANALYSIS: WHEN THE DI WAS SET AT REGULATION 
                    LEVEL 2, NAM ONLY SET THE REGULATION
                    FLAG FOR ALL CONNECTIONS EXISTING 
                    IN THE NCNT OF THE LLCB CONCERNED.
                    IF THE REGULATION LEVEL STAYS AT
                    THE SAME LEVEL 2, THEN THE CONNECTION 
                    ENTRIES DID NOT GET UPDATED WITH
                    THEIR REGULATION LEVELS.
  
          SOLUTION: IN BLDNCNB, CODE IS CUT SUCH THAT 
                    A CHECK IN LLCBNRL IS DONE AND
                    THE REGULATION LEVELS OF THE
                    NEW CONNECTIONS UPDATED. BUT, 
                    THE RECEIVER DOES NOT GET ITS 
                    CONNECTION PRIORITY UNTIL A 
                    CRRAPN IS RECEIVED, AND THEREFORE 
                    A SIMILAR CHECK HAS TO BE DONE. 
  
          YCY 11/22/85  BLDNCNB,NICAPNX 
  
 NA5B574  PIP SENDS STOP REGULATION FUNCTION TO MCI NOT IN REGULATION.
  
          PIP SENDS STOP REGULATION FUNCTION TO MCI WHEN IT RECEIVES
          CHANGE REGULATION MESSAGE FROM NIP.  MCI IS NOT EXPECTING TO
          RECEIVE STOP REGULATION WHEN IT IS ALREADY NOT IN REGUALTION
          BY A PREVIOUS STOP REGULATION FUNCTION. 
          PIP MUST REMEMBER WHEN IT SENDS START/STOP REGULATION SO THAT 
          IT WILL NOT SEND STOP REGULATION FUNCTION WHEN REGULATION IS
          NOT IN EFFECT.
  
          PIP TRIES TO ISSUE A REGULATION FUNCTION TO MCI WITHOUT 
          CHECKING MCI GENERAL STATUS.
          PIP IS CHANGED TO GET MCI GENERAL STATUS TO KNOW IT IS NOT
          BUSY BEFORE IT ISSUES A TRANSPARENT FUNCTION. 
  
          SW     85/11/12    PIP
  
 NA5B575  CHANGING DEFAULT NAM FIELD LENGTH 
          PROBLEM: NEED TO INCREASE DEFAULT NAM FIELD 
                   LENGTH.
  
          ANALYSIS: THE FOLLOWING FORMULA IS USED TO
                    COMPUTE NAM FIELD LENGTH. 
  
          MAXFL = 11096 + 700H + 6560A + 30(C + D) + 30E + M
                  + 20(K1*W1+ ... KN*WN) + 22Y + 13Z
                  + 78B1 + 142B2 + 206B3
  
          WHERE H = MAX HOST NODE = 5 
                A = 0 
                C = MAX HOST = 3
                D = MAX NPU + MDI NODES 
                M  = MAXIMUM NODE NUMBER
                E = MAX APPLICATIONS = 15 
                KI*WI = WORDS PER TERMINAL
                KI = 1
                WI = 940/7.5 = 125.3
                Y = MAX BATCH TERMINAL DEVICES = 20 
                Z = NO OF CONNECTED INTERACTIVE DEVICES = 250 
                B1 = 8
                B2 = 16 
                B3 = 8
                YCY 85/11/19    NIP 
  
 NA5B576  REMOVING SUPPORT OF STIP=X25 IN NDL TERMDEF.
  
          PROBLEM: IN 2.4.1 AND 2.4.2 STIP=XAA WAS
                   IMPLEMENTED BUT STIP=X25 WAS LEFT
                   AND MAPPED INTERNALLY TO XAA FOR 
                   COMPATIBILITY PURPOSES.
                   AFTER 2.4.3, WE ARE GOING TO REMOVE
                   STIP=X25 FOR GOOD. 
  
          ANALYSIS: IN NDLPSS1, A MAPPING WAS DONE
                    SUCH THAT X25 WAS CHANGED TO XAA
                    IF SPECIFIED AS THE STIP VALUE IN THE 
                    X.25 TERMDEF STATEMENT. 
                    NOW, THIS CODE IS REMOVED AND SEARCHES
                    FOR X.25 AS A VALID STIP VALUE WILL 
                    RESULT IN INVALID VALUE ERROR MESSAGE.
          YCY       85/12/19    NDL 
 NA5B583  NAM RETURNED BAD REASON CODE TO APPLICATION.
          PROBLEM: AN A-A APPLICATION OBTAINED A CONACRQA 
                   WITH REASON CODE 09. 
  
          ANALYSIS: THE X.25 A-A APPLICATION OBTAINED 
                    REASON CODE 09 FIRST FROM TCNTA,
                    AND THEN FROM CRCB AND FINALLY FROM 
                    CRTRMN. REASONC 
                    REFERS TO A VALID REASON CODE 
                    MEANING X.25 CONFIGURATION PROBLEM. 
  
          SOLUTION: ROUTIEN HCACRQ HAS TO MAP 09 TO 
                    A DOCUMENTED REASON CODE IN NAM.
                    A CHOICE IS HEX D6, MEANING 
                    REMOTE NOT RESPONDING 
          YCY 11/22/85  HCACRQA 
 NA5B585  PROBLEM  - NIP CAN REACHED MAXIMUM FIELD LENGTH WITH TOO MANY 
                     ASYNCHRONOUS SUPERVISORY MESSAGES QUEUED FOR THE 
                     APPLICATION. 
          SOLUTION - NIP HAS BEEN CORRECTED TO ABORT APPLICATIONS THAT
                     HAVE MORE THAN 500 ASYNCHRONOUS SUPERVISORY
                     MESSAGES QUEUED FOR THEM ON THE ASSUMPTION THAT
                     THE APPLICATION IS MISBEHAVING AND NOT PICKING UP
                     ITS SUPERVISORY MESSAGES.
          EG     11/13/85  AWLDEFS, APPSTAT, HWLP, XABTAPP
 NA5B588  PROBLEM  - NIP FAILED WITH ERROR MESSAGE - NIP/NCSTTP ERR 
                     HN=22,TN= 43,CN=  1, 7,16
          ANALYSIS - PIP HAD SENT A TERMINATE PRU CONNECTION WORKLIST.
                     THIS CAUSED THE NETWORK CONNECTION STATE TO CHANGE 
                     TO 16.  THIS WAS IMMEDIATELY FOLLOWED BY A 
                     IFT/OFF/R SUPERVISORY MESSAGE FROM THE APPLICATION 
                     TO TERMINATE PRU PROCESSING ON THE CONNECTION. 
                     THE SUPERVISORY MESSAGE FROM THE APPLICATION 
                     GENERATED A NXTOFR TRIGGER (VALUE 7) FOR THE 
                     NETWORK CONNECTION STATE TABLE.  THE STATE TABLE 
                     CONSIDERED THIS TO BE A SITUATION THAT SHOULD NOT
                     OCCUR AND ABORTED. 
          SOLUTION - THE NETWORK CONNECTION STATE TABLE HAS BEEN
                     TO ALLOW THE NXTOFR TRIGGER AFTER NIP PROCESSES
                     A TERMINATE PRU CONNECTION WORKLIST FROM PIP.
                     NO ACTION WILL OCCUR WHEN THE TRIGGER IS RECEIVED. 
          EG     12/03/85    STATTBL
 NA5B589  MAXIMUM BLOCK SIZE CHECK FOR UPLINE MDI BLOCK IS NOT CORRECT. 
  
          MAXIMUM UPLINE BLOCK SIZE CURRENTLY ALLOWED FOR MDI IS 2043.
          IT MUST BE CHANGED TO 2048. 
  
          SW     PIP         85/12/02 
 NA5B590  PROBLEM  - PERIODICALLY THE NAM CONTROL POINT ON THE B DISPLAY
                     CONTAINS A FLASHING *REQUEST K-DISPLAY* MESSAGE. 
                     ASSIGNMENT OF THE K-DISPLAY TO NAM DOES NOT SHOW 
                     ANY REASON FOR THE FLASHING MESSAGE. 
          ANALYSIS - THE CONSOLE MACRO IS BEING CALLED EVERY TIME NIP 
                     CLEANS UP ITS K-DISPLAY BUFFERS.  CALLING THE
                     CONSOLE MACRO IS GENERATING THE REQUEST K-DISPLAY
                     MESSAGE ON THE B DISPLAY.
          SOLUTION - NIP OVERLAY KPCLNUP HAS BEEN CORRECTED TO CALL THE 
                     CONSOLE MACRO ONLY IF THE K-DISPLAY TYPEIN DAYFILE 
                     FLAG NEEDS TO BE CLEARED.
          EG     12/03/85    KPCLNUP
 NA5B592  NIP CPU ERROR EXIT AT 3365. 
          PROBLEM: NAM FAILED WHILE LOANING FROM PRIMARY
                   TO SECONDARY.
  
          ANALYSIS: WHEN THE PRIMARY STARTED LOANING TO 
                    SECONDARY. AFTER A CRSWH WITH STATUS
                    O.K. (8) WAS RECEIVED, HCSTTP TRIED 
                    TO SAVE THE SECONDARY AN AND ACN IN 
                    THE ACNT OF THE PRIMARY APPLICATION 
                    WHICH NO LONGER EXISTED. THAT CAUSED
                    THE CPU ERROR EXIT. 
  
          SOLUTION: THE CONNECTION SHOULD STILL BE ALLOWED
                    TO BE LOANED TO THE SECONDARY, EXCEPT ON
                    RETURN, HCSTTO ACTION 13 ACNB1 SHOULD 
                    CHECK FOR ACNBPRAF (PRIMARY FAILED FLAG) BEFORE 
                    SAVING THE SECONDARY ACN AND AN UNDER THE PRIMARY 
                    ACNT. 
  
         YCY 12/10/1985 NIP 
 NA5B594  NO APPL NAME ON ALERT LINE IN K-DISPLAY 
          ON SECOND/SUBSEQUENT HOP/ALERTS.
          PROBLEM: SECOND/SUBSEQUENT HOP/ALERTS WERE
                   IGNORED BY NAM.
  
          ANALYSIS: IN KAPIGP, THE UPDATING OF APPL 
                    NUMBERS IN THE ALERT LINE WAS NOT 
                    CORRECT WHEN THE OPERATOR ASSIGNED
                    THE K-DISPLAY TO THE APPLICATION. 
                    NEEDED. WHEN THE SECOND HOP/ALERT 
                    CAME, IT WAS IGNORED BECAUSE THE
                    OLD APPLICATION NUMBER WAS NOT
                    WIPED OUT WHEN THE K-DISPLAY WAS
                    ASSIGNED TO THE APPLICATION.
  
          SOLUTION: IN KAPIGP, THE APPLICATION NUMBER OF THE
                    APPLICATION SENDING THE HOP/ALERT IS
                    CLEARED WHEN THE OPERATOR  ASSIGNS THE
                    THE K-DISPLAY TO THE APPLICATION CONCERNED. 
  
          YCY       85/12/13    NIP 
  
 NA5B595  PROBLEM  - NIP ABORTED WITH ERROR MESSAGE - HPNOFF, NIP 
                     INTERNAL ERROR.
          ANALYSIS - AN APPLICATION WHICH HAD LOANED ITS TERMINAL 
                     CONNECTION TO ANOTHER APPLICATION NETTED OFF.
                     THE SECONDARY APPLICATION (NVF) DID NOT HAVE 
                     THE CONNECTION SO NIP ABORTED.  DURING THE 
                     LOANING OF A TERMINAL CONNECTION FROM ONE
                     APPLICATION TO ANOTHER, IF THE NETWORK 
                     TERMINATES THE CONNECTION WHILE NVF HAS THE
                     CONNECTION, THE PRIMARY APPLICATION IS NOT 
                     INFORMED THAT THE CONNECTION IS GONE NOR DOES
                     NIP CLEAN UP ITS TABLE FOR THE PRIMARY 
                     APPLICATION TO INDICATE THAT THE LOANED
                     CONNECTION NO LONGER EXISTS. 
          SOLUTION - NIP HAS BEEN CORRECTED TO INFORM THE PRIMARY 
                     APPLICATION AND CLEAN UP ITS TABLES IF THE 
                     NETWORK TERMINATES A LOANED CONNECTION WHILE 
                     THAT CONNECTION IS CONNECTED TO NVF. 
          EG     12/19/85    HCSTTP, HCONCBU, STBLDEF, STATTBL
 NA5B596  PROBLEM  - DEGRADATION IN COUPLER TO COUPLER FILE TRANSFER
                     BETWEEN 2.4.1 AND 2.4.2. 
                     NAM IS NOT KEEPING TRACK OF NUMBER OF NPU REJECTS
                     OF DOWNLINE DATA AND PIP REJECTS OF UPLINE DATA. 
          ANALYSIS - PIP WAS CHANGED AT NOS 2.4.2 RELEASE TO PERFORM
                     RANDOM WRITES INSTEAD OF SEQUENTIAL WRITES.  FOR 
                     HIGH SPEED DISK DEVICES UTILIZING UEM, THIS
                     CHANGE WOULD CAUSE A PERFORMANCE DEGRADATION.
                     THIS MAY HAVE CAUSED THE PERFORMANCE DEGRADATION.
                     NIP IS NOT ALLOCATING PRU BUFFERS AS FAST AS IN
                     2.4.1.  THIS MAY ALSO HAVE CAUSED A PERFORMANCE
                     DEGRADATION. 
          SOLUTION - PIP HAS BEEN CORRECTED TO PERFORM SEQUENTIAL WRITES
                     EXCEPT FOR THE ABNORMAL CASE WHEN A RANDOM WRITE 
                     IS NEEDED.  NIP HAS BEEN CORRECTED TO ALLOCATE 
                     PRU BUFFERS AS SOON AS PIP REQUESTS THEM.
                     PIP HAS BEEN CORRECTED TO MAINTAIN A COUNTER IN
                     THE NBT OF THE NUMBER OF NPU AND PIP REJECTS AND 
                     NIP HAS BEEN CORRECTED TO DAYFILE THESE COUNTERS 
                     WHEN IT DAYFILES THE REST OF ITS STATISTICS
                     COUNTERS.
          EG     10/14/85    NBT, NEIB, PIP, PIT, PT, XCHKABC, XEXEC, 
                             XENDRPV, XTERMST, SKENIP, KDISLN, KSTTUPD
NA5B598   PROBLEM  - NVF WAS PROCESSING THE CR/IAP/R WHEN THE HOP 
                     TYPE IN  "DI,HO".  AS A RESULT, A CR/IAP/A WAS 
                     GENERATED AND PUT IN CTQ. NVF ALSO SENT A CR/TRM/R 
                     TO TERMINATE THE CONNECTION. BECAUSE OF THE DELAY
                     IN QUEUE PROCESSING, THE CR/AIP/A ACTUALLY LEFT
                     NVF LATER THAN THE CR/TRM/R DID. AS A RESULT, NIP
                     RETURNED A ERRLGL WITH REASON CODE 04 TO NVF BECAUSE,
                     TO NIP, THE CONNECTION NO LONGER EXISTED AFTER 
                     AFTER THE CR/TRM/R WAS RECEIVED. 
          SOLUTION - PROCEDURE NVFCCPA IS MODIFIED SO THAT IT WILL
                     CHECK THE STATE OF THE ACN BEFORE IT ACTUALLY
                     SENDS OUT THE CR/IAP/A. THE CR/IAP/A WILL BE 
                     SENT ONLY IF THE CR/TRM/R HAS NOT YET BEEN SENT
                     (ACN$STATE IS NOT "ENDED").
          TET     86/01/10     NVFCCPA
 NA5B600  NVF SHOULD ACCEPT CONACRQ WITH MORE THAN 2
          WORDS FOR NONPRIVELEGED APPLICATION.
  
          PROBLEM: NVF REJECTED CONACRQ WITH MORE THAN
                   TWO WORDS. 
  
          ANALYSIS: FOR UPWARD COMPATIBILITY, NVF SHOULD
                    LOOK INTO THE EXTRA WORDS IN THE
                    CONACRQ ONLY IF THE APPLICATION IS
                    PRIVELEGED, ELSE, IT SHOULD IGNORE
                    THE EXTRA WORDS.
  
          SOLUTION: NVFAIAP WAS CHANGED SUCH THAT 
                    THE PAC$OUTSPEC IS SET TO TRUE ONLY 
                    IF THERE ARE EXTRA WORDS IN THE CONACRQ 
                    MESSAGE AND IF THE APPLICATION IS 
                    PRIVELEGED. 
  
                YCY 01/31/86    NVF 
  
 NA5B602  CHANGING THE FN VALUES FOR MCI AND MLI. 
  
          PROBLEM: THE FN VALUES FOR MCI AND MLI ARE
                   NO LONER 146 AND 147 RESPECTIVELY, 
                   BUT SHOULD BE 147 AND 148 RESPECTIVELY,
  
          ANALYSIS: AN ERROR IN DOCUMENTATION IN THE
                    ORIGINAL DAP ARH6469 CAUSED THIS
                    PROBLEM.
  
          SOLUTION: THE STATUS LIST IN NDLNFCM FOR FN 
                    SHOULD BE CHANGED. ALSO, THE NDLLIST
                    ROUTINES AFFECTED SHOULD BE CHANGED 
                    TOO.
          YCY       86/01/03    NDL 
 NA5B603  PROBLEM  - QTRM IS NOT INFORMING THE APPLICATION PROGRAM OF 
                     THE CONNECTION NUMBER THAT IT RECEIVED THE FC/RST
                     SUPERVISORY MESSAGE ON.
          SOLUTION - QTRM ROUTINE HAS BEEN CORRECTED TO STORE THE 
                     CONNECTION NUMBER IN THE NIT CONNECTION-NUMBER 
                     FIELD WHEN IT PROCESSES A FC/RST SUPERVISORY 
                     MESSAGE FROM NIP.
          EG     01/06/85    QTGET
NA5B604    PROBLEM  - AN APPLICATION REQUESTED TERMINAL CHARACTERISTICS 
                      AND NETTED OFF BEFORE IT RECEIVED RTC/A FROM
                      CPP. AS A RESULT, NVF RECEIVED A CTR/RTC/A AND
                      ABORTED.
           SOLUTION - PROCEDURE NVFDDNT HAS BEEN MODIFIED TO SKIP 
                      THE CTR/RCT/A.
                      NOTE : THIS IS JUST A TEMPORARY SOLUTION. 
                             THE PROBLEM IS ACTUALLY A DESIGN ISSUE,
                             AND THEREFORE, HAS BEEN SUBMITTED TO 
                             BOB FARRELL. 
  
          TET     86/01/14     SMAPPFC,NVFDDNT
 NA5B608  CLEANING UP DEFINITIONS FOR NAM FIELD LENGTH
  
          PROBLEM: NAM FIELD LENGTH DEFS ARE INCONSISTENT 
  
          ANALYSIS: THE CURRENT MAXNIP (DEFAULT FIELD 
                    LENGTH VALUE) IS 170000B, BUT THE 
                    MAXXXFL (MAXIMUM FIELD LENGTH) IS 
                    150000B. ANOTHER INCONSISTENT 
                    DEFINITION IS THE K-DISPLAY 
                    MAXIMUM FIELD LENGTH SET AT 200000B.
  
          SOLUTION: THE FIELD LENGTH DEFINITION FOR 
                    DEFAULT FIELD LENGTH IS SET AT
                    3000000B. THE MAXIMUM FIELD LENGTH
                    IS SET AT 360000B.
  
                YCY 01/31/86    NIP 
  
 NA5B609  PIP COMSUMES TOO MUCH TIME TO TEST DEAD MCI INTERFACES. 
  
          SW     85/12/17    PIP
 NA5B610  PIP ERROR 75 WHEN MDI IS TURNED OFF.
  
  
          ERROR, PIP TRIES TO SEND TO IT REGULATION LEVEL ZERO (OR STARTVICE
          REGULATION) COMMAND.  SOME OF THE ACTIONS THAT FOLLOW CAUSE 
          PIP ERROR 75 IF THE COMMAND COULD NOT BE SENT BECAUSE OF
          A DEVICE ERROR. 
  
          PIP IS CHANGED NOT TO SEND A REGULATION COMMAND WHEN A DEVICE 
          IS TURNED OFF.
  
          SW     86/01/13    PIP
 NA5B611  PIP ERROR 76 AT LEVEL SEVEN INPUT ERROR.
  
          PIP ERROR 76 MAY HAPPEN IF INPUT Q-MESSAGES ARE RECEIVED AFTER
          LEVEL SEVEN INPUT ERROR IS DETECTED BEFORE PIP RECEIVES 
          SUPERVISORY MESSAGE FROM THE APPLICATION. 
  
          RESPONSE ACTION FOR THE Q-MESSAGE IS CHANGED TO IGNORE THE
          MESSAGE.
  
          SW     86/01/16    PIP
 NA5B612  PROBLEM  - UPLINE IVT DATA THROUGHPUT CAN BE IMPROVED.
  
                   - GARBAGE COLLECTION GETS CALLED TOO OFTEN IF
                     THERE ARE MANY FRONT ENDS. 
  
          SOLUTION - THE UPLINE DATA BUFFER ALLOCATION SCHEME HAS BEEN
                     REDESIGNED TO MAKE THE UPLINE BUFFERS VARIABLE IN
                     SIZE AND THE CONDITIONS FOR ALLOCATING AN UPLINE 
                     BUFFER HAS BEEN MADE MORE FLEXIBLE.
  
                   - THE CONDITIONS UNDER WHICH GARBAGE COLLECTION WILL 
                     BE CALLED HAVE BEEN MADE MORE STRICT.
  
          EG     01/07/86    INPARU, NBT, NEIB, XCHKCET, XEXEC
 NA5B613  DISALLOWINNG QTSUP FROM SENDING SUPERVISORY 
          MESSAGES THAT ARE GENERATED BY QTRM.
  
          PROBLEM: QTRM IS SOMETIMES CONFUSED IF QTSUP
                   SENDS ASYNCHRONOUS SUPERVIOSRY 
                   MESSAGES THAT ARE GENERATED BY 
                   QTRM ITSELF. 
  
          ANALYSIS: QTRM GENERATES A SET OF ASYNC 
                    SUPERVISORY MESSAGES WHEREAS CALLING
                    QTSUP WITH OPCODE 0 SENDS THE SUPERVISORY 
                    MESSAGE POINTED TO BY WSA (2ND PARAMETER
                    OF THE QTSUP). SOME OF THE SUPERVISORY
                    MESSAGES GENERATED BY QTRM ITSELF REGISTERS 
                    A STATE CHANGE IN NIT$STATE SUCH THAT 
                    THESE STATES WILL BE CHECKED AGAINST
                    THE RESPONSE MESSAGES TO THESE SELF 
                    GENERATED ASYNC SUPERVISORY MESSAGES. 
                    SENDING THESE MESSAGES THROUGH QTSUP WITH 
                    WORK CODE 0 REGISTERS NO STATE CHANGE 
                    AND HENCE CAUSE INCONSISTENT RESULTS
                    WHEN RECEIVING THE RESPONSE MESSAGES. 
  
          SOLUTION: IN QTSUP, CODE IS CUT TO CHECK IF THE 
                    ASYNC SUPERVISORY MESSAGE THAT QTSUP
                    IS CALLED TO SEND WITH OPCODE 0 MATCHES 
                    WITH ANY OF THE SUPERVISORY MESSAGES CAUSING
                    STATE CHANGES IF THEY ARE GENERATED BY
                    QTRM ITSELF. IF A MATCH IS FOUND THEN 
                    QTRM SHOULD ABORT.
          YCY 86/02/28          AIP 
 NA5B614  SPECIAL STATISTICS GATHERING CODE FOR NIP TO CHECK IF NIP 
          IS LOSING THE CPU FOR A LONG PERIOD OF TIME WHEN IT ISSUES
          A SCP SWAPIN, UPDATES THE DATA AVAILABLE BIT, OR WRITES 
          DATA BACK TO THE APPLICATION-S FIELD LENGTH.
          EG     04/24/85    STATTAB,HWRAVAL,BWLBLK,OSWAPIN 
          ADDITIONAL STATISTICS GATHERING CODE FOR NIP TO DETERMINE 
          WHERE NIP IS SPENDING MOST OF ITS REAL TIME.
          EG     06/20/85    HWLP,XEXEC,OSCHAPP,HPAWL,BRLBLK,HRDPUT,
                             OSCCALL,OVLCALL,MSETIL,MGBGCLT,XTERMST,
                             OCFL,OSWAPIN,SKENIP,HHIR,XCHKPCR,NEIB
 NA5B616  PROBLEM  - QTRM APPLICATION HAS NO OPTION TO NOT ABORT WHEN IT
                     RECEIVES AN ERR/LGL SUPERVISORY MESSAGE OR IF ITS
                     NETON REQUEST IS REJECTED. 
          SOLUTION - QTCMD HAS BEEN ENHANCED WITH NEW COMMAND CODES 
                     9 AND 10.  IF QTCMD IS CALLED WITH COMMAND CODE 9, 
                     QTOPEN WILL NOT ABORT WHEN THE NETON IS REJECTED.
                     INSTEAD CONTROL WILL RETURN TO THE APPLICATION 
                     WITH THE APPROPRIATE RETURN CODE STORED IN THE NIT.
                     IF QTCMD IS CALLED WITH COMMAND CODE 10, QTGET WILL
                     NOT ABORT WHEN THE APPLICATION RECEIVES AN ERR/LGL 
                     SUPERVISORY MESSAGE. 
          EG     03/25/86    QTCMD, QTGET, QTOPEN, QTRMCOM, QTRMNIT 
 NA5B619  PROBLEM  - AIP WAS HUNG IN CPU LOOP.
          ANALYSIS - NP$GETQ HUNG IN CPU LOOP WHEN IT WAS CALLED TO 
                     DISCARD DATA FOR A SPECIFIC CONNECTION AND GMBHEAD 
                     WAS EQUAL TO 1, GMBFOOT WAS EQUAL TO 101, AND
                     GMBLAST WAS EQUAL TO 100.
          SOLUTION - NP$GETQ HAS BEEN CORRECTED TO NOT SET NOWHEAD TO 
                     ONE IF NOWHEAD IS EQUAL TO GMBFOOT.
          EG     01/31/86    NP$GETQ, NP$SEND 
 NA5B621  PROBLEM  - THE JOB RECORD NAME OF NETOS HAS BEEN CHANGED TO 
                     NETOU. THE COLLECTOR DID NOT COLLECT DUMP FILES
                     FOR NETOU BECAUSE IT DOES NOT RECOGNIZE THOSE
                     FILE NAMES.
          SOLUTION - THE COLLECTOR HAS BEEN MODIFIED TO RECOGNIZE AND 
                     COLLECT DUMP FILES FOR NETOU.
  
          TET   02/04/86    CLT=INI 
 NA5B622  REMOVING THE EFFECT OF NA5B582 THAT 
          HARD CODED THE VALUE OF THE NIP DEFAULT 
          FIELD LENGTH ON THE CONTROL CARD. 
  
          ANALYSIS: NA5B608 IS A PERMANENT FIX FOR
                    THE PROBLEM, HENCE NA5B582 IS NO
                    LONGER NEEDED.
  
                YCY 86/02/07    JOBNIP
  
 NA5B626  PIP ABORTED WITH PIP ERROR 47.
          PROBLEM: ANM ABORTED WITH PIP ERROR 47. 
  
          ANALYSIS: THERE WAS A BAD TERMINAL NODE 
                    CONFIGURED IN THE MDI EST ENTRY.
                    THIS CAUSED PIP TO ABORT LATER. 
  
          SOLUTION: NIP NOW VERIFY EVERY REGLL TO SEE THAT
                    IF THE SN[0] FROM THE REGLL MATCHES ANY 
                    OF THE CET COUPLER NODE NUMBER. IF, IT
                    DOES, NIP WILL THEN DISCARD THE REGLL.
                    DAYFILE MESSAGE DISCARDED WILL BE BAD 
                    NETWORK BLOCK DISCARDED.
          YCY 86/02/26    NIP 
 NA5B628  PROBLEM  - THE DI DEVELOPMENT GROUP HAS DEFINED NEW SYN. SM 
                     "C1OC". THIS SM WILL BE SENT UPLINE WHEN A USER
                     CHANGES SOME TERMINAL CHARACTERISTICS. THE 
                     DEBUGGED VERSION OF NVF ABORTED ITSELF BECAUSE 
                     IT DID NOT RECOGNIZE THE SM. 
  
          SOLUTION - THE DECK NVFDDNT IS MODIFIED SO THAT THE DEBUGGED
                     VERSION WILL NOT ABORT ITSELF WHEN IT RECEIVES AN
                     UNKNOWN SM. INSTEAD NVF WILL IGNORE THE SM AFTER 
                     IT GENERATE A DAYFILE MESSAGE AND ALERT THE
                     OPERATOR.
          TET     02/28/86     SMAPPFC,NVFDDNT
 NA5B629  NIP QUEUES ICNEX/N WITH ONE EXCESS OCTET. 
          PROBLEM: INCEX/N QUEUED BY NIP CONTAINS 
                   ONE EXCESS OCTET.
          ANALYSIS: WHEN NIP FORMATS THE ICNEX/N FROM 
                    CRAP/N FROM NVF, IT CONVERTS THE
                    WORD COUNT FROM ABHTLC OF CRRAP/N 
                    TO ASCII CHARACTER TO THE NEAREST 
                    OCTET. BUT THAT RESULTS TO ONE
                    MORE OCTET THEN NEEDED. 
  
          SOLUTION: THE TLC COUNT SHOULD  BE ADJUSTED BY
                    SPECIAL CASING ICNEX/NA.
  
          YCY 86/02/21    NIP 
  
 NA5B630  CPU ERROR EXIT IN CHARACTER MODE FILE TRANSFER
          PROBLEM: MFLINK CPU ERROR EXIT. 
  
          ANALYSIS: THE LAST BLOCK THAT MFLINK RECEIVED 
                    WAS A 400 CHARACTER BLOCK. WHEN GOING 
                    THROUGH X.25, CCP SPLITS THE BLOCKS 
                    INTO A BLK OF 200 CHARACTERS,ANOTHER
                    BLK OF 200 CHARACTERS AND A FINAL 
                    ZERO TLC MSG BLOCK. THE TRANSLATION 
                    SERVICE CANNOT HANDLE MSG BLOCK WITH
                    ZERO CHARACTER LENGTH.
  
          SOLUTION: IN NP$DATA, AIP SHOULD CHECK ON ZERO
                    LENGTH MSG BLOCK AND NOT COPY THE HEADER
                    AS PART OF THE NETWORK BUFFER.
          YCY       86/03/06    AIP 
 NA5B631  PROBLEM  - NIP ABORTED WITH THE FOLLOWING STATE TABLE ERROR 
                     MESSAGE - NIP/NCSTTP ERR HN= 0,TN=  0,CN  1, 0,62
          ANALYSIS - THE NETWORK CONNECTION STATE TABLE PROCESSOR HAD 
                     BEEN CALLED TO PROCESS A CR/ITE/N RESPONSE FROM
                     NVF.  UNFORTUNATELY THE LLCB SHOWED THAT NO SUCH 
                     CONNECTION EXISTED SO NIP ABORTED DUE TO AN
                     INTERNAL ERROR.  THE REMNANTS OF THE NIP UPLINE
                     BUFFER SHOWED THE FOLLOWING SITUATION OCCURRED.
                     NIP RECEIVED A REG/LL RL=0, FOLLOWED BY 2 RELEASE
                     PWL WORKLISTS, FOLLOWED BY A REG/LL RL=3, FOLLOWED 
                     BY A ICN/TE/R, FOLLOWED BY 2 PRU CONNECTION
                     TERMINATION RESPONSE WORKLIST, FOLLOWED BY A REG/LL
                     RL=17B.  WHEN NIP PROCESSED THE REG/LL RL=0, THERE 
                     MUST HAVE BEEN 2 PRU CONNECTIONS OUTSTANDING.  NIP 
                     COULD NOT COMPLETE PROCESSING THE REG/LL RL=0 UNTIL
                     PIP ACKNOWLEDGED THE TERMINATION OF THE 2 PRU
                     CONNECTIONS.  BEFORE THAT OCCURRED, THE LOGICAL
                     LINK CAME BACK UP AND CCP REQUESTED A NEW TERMINAL 
                     CONNECTION.  NIP WOULD HAVE CREATED THE APPROPRIATE
                     DATA STRUCTURES AND QUEUES A CR/ITE/R SUP MSG FOR
                     NVF.  WHEN PIP FINALLY SENT THE PRU CONNECTION 
                     TERMINATION ACKNOWLEDGEMENT WORKLISTS, THE LLCB WAS
                     RELEASED EVEN THOUGH A NEW TERMINAL CONNECTION HAD 
                     BEEN ESTABLISHED.
          SOLUTION - NIP HAS BEEN CORRECTED TO NOT RELEASE THE LLCB IF
                     THERE OUTSTANDING IVT CONNECTIONS ON THE LOGICAL 
                     LINK.
          EG     03/14/86    NPPCT
 NA5B635  PROBLEM  - PIP IS STILL REFERENCING ON/OFF BIT IN EST ENTRY 
                     TO DETERMINE IF DEVICE IS ON OR OFF.  IN THE NOS 
                     2.5.2 RELEASE, THIS BIT WILL NO LONGER EXIST.
          SOLUTION - PIP HAS BEEN CORRECTED TO LOOK AT THE EQUIPMENT
                     STATUS FIELD TO DETERMINE IF THE EQUIPMENT IS ON 
                     OR OFF.
          EG     86/03/13    PIP
 NA5B638  PROBLEM  - CS ABORTED WITH ERROR MESSAGE CSDDNT - SM NOT
                     ROUTED.
          ANALYSIS - CS RECEIVED A CTRL/CHAR/N SUPERVISORY MESSAGE.  CS 
                     DID NOT HAVE ANY CODE TO HANDLE THIS SUPERVISORY 
                     MESSAGE SO IT ABORTED. 
          SOLUTION - CS HAS BEEN CORRECTED TO IGNORE THE CTRL/CHAR/N, 
                     CTRL/CHAR/A, CTRL/TCD, CTRL/CCD, CTRL/CTD/N, 
                     CTRL/CTD/A, CTRL/RTC/A, AND CTRL/RCC/A.
                     SUPERVISORY MESSAGES.
          EG     03/21/86    TEXTCS, CSDDNT 
 NA5B639  PROBLEM  - THE INSTALLATION OF THE SECURITY-ACCESS CODE HAS CAUSED
                     CCP TO GENERATE EXTRA "OVER..".
  
          ANALYSIS - NVF USED TO SEND A "CLEAR SCREEN" TO THE TERMINAL
                     TO HIDE THE PASSWORD AFTER A SUCCESSFUL VALIDATION.
                     THE SECURITY CODE OUTPUTS A MASK TO THE TERMINAL TO
                     OVERSTRIKE THE TYPED-IN PASSWORD BEFORE IT SENDS THE 
                     "CLEAR SCREEN". THIS CAUSES CCP TO GENERATE AN "OVER.."
                     AND THE SCREEN IS CLEARED ONLY AFTER THE USER HAS HIT
                     A <CR>.
  
          SOLUTION - CHANGE NVF NOT TO SEND THE "CLEAR SCREEN" ANYMORE
                     BECAUSE IT IS NO LONGER NEEDED. THE TYPED-IN PASS- 
                     WORD IS NOW CLEARED BY THE OVERMASK. 
  
          TET   03/25/86    NVFTPSV 
 NA5B641  PROBLEM  - QTRM DID NOT STORE THE CORRECT TERMINAL CLASS
                     IN THE NIT CONNECTION ENTRY. 
          ANALYSIS - QTGET OVERWROTE THE TERMINAL CLASS FIELD IN THE
                     CON/REQ SUPERVISORY MESSAGE BEFORE IT PICKED UP
                     THE CONTENTS OF THE TERMINAL CLASS FIELD TO STORE
                     IN THE NIT CONNECTION ENTRY. 
          SOLUTION - QTGET HAS BEEN CORRECTED TO NOT OVERWRITE THE
                     CON/REQ SUPERVISORY MESSAGE UNTIL AFTER ALL
                     INFORMATION NEEDED FROM IT IS EXTRACTED. 
          EG     03/27/86    QTGET
 NA5B644  PROBLEM  - SEVERAL NVF DAYFILE MESSAGES DO NOT FOLLOW 
                     CORPORATE GUIDELINES FOR ERROR MESSAGES. 
  
          SOLUTION - REPLACE ALL OCCURENCES OF "CARD" WITH "STATEMENT", 
                     "ILLEGAL" WITH "INVALID", AND "PARA" WITH
                     "PARAMETER". 
  
          NOTE     - RETRANSMITTED TO CORRECT A TYPO. 
  
          TET   04/03/86    NVFCSC, NVFLIST, TMSGNVF, NVFOPAC, NVFTDAD
 NA5B648  CN DIRECTIVE REJECTED BY DLFP.
  
          PROBLEM: WHEN PROCESSING NIP TRACE AND CN USED
                   AS A DIRECTIVE, DLFP REJECTS IT. 
                   ALSO, A BAD REFERENCE IS MADE TO 
                   ABH WHICH IS A BASED ARRAY BUT NOT 
                   IN THE COMMON AREA.
  
          ANALYSIS: IN DLNBH, THE ROUTINE PROCESSING
                    DIRECTIVE FOR NIP/PIP TRACE, THE
                    CN DIRECTIVE WAS MISPLACED. IT IS 
                    OFF BY 1. 
  
          SOLUTION: THE STATUS LIST IS ADJUSTED FOR CN AND
                    ALL OTHERS FOLLOWING IT.
                    A TEMPORARY ABH IS SET UP AND THEN SET
                    ABH TO TEMP ABH.
  
          YCY 86/04/10    DLFP
  
 NA5B652  PROBLEM  - IF A USER ENTERED "APPSW,HELLO" OR 
                     "APPSW,LOGIN" FROM AIF, NVF COULD BE ABORTED 
                     BECAUSE IT TRIED TO REFER TO A NON EXISTING
                     PTAC ENTRY.
  
          ANALYSIS - MANY NVF PROCEDURES CALL ONE ANOTHER, PASSING
                     THE  PERAMETER "PT", WHICH IS AN INDEX TO THE
                     ENTRY IN THE PTAC TABLE FOR THE CONNECTION 
                     BEING PROCESSED. MOST OF THE PROCEDURES DO NOT 
                     MODIFIED "PT". HOWEVER, A FEW OF THEM, LIKE
                     NVFTETC AND NVFTRLC DO MODIFY IT IF THE CONNEC-
                     TION IS TERMINATED. NVFTRVD, WHEN PROCESSING AN
                     "APPSW,HELLO", CALLED NVFTRLC AND UPON RETURN
                     FROM THE CALL, USED "PT", ASSUMING ITS OLD VALUE,
                     AND HENCE RAN INTO TROUBLE.
  
          SOLUTION - NVFTRLC HAS BEEN CORRECTED NOT TO USE "PT" AFTER 
                     CALLING NVFTRLC. 
  
          TET   04/11/86    NVFTRVD 
 NA5B653  PROBLEM  - CDCNET DEVELOPMENT HAS DEFINED SOME NEW SUPERVI- 
                     SORY MESSAGES THAT NVF HAS TO BE AWARE OF. 
  
          SOLUTION - THE NEW SUPPERVISORY MESSAGES ARE DEFINED IN 
                     SMAPPFC, AND NVF IS MODIFIED TO IGNORE THEM. 
  
          TET   04/11/86    SMAPPFC, NVFDDNT
 NA5B659  PROBLEM  - NVF GENERATED INCONSISTENT TLC FOR CR/RAP/N'S, 
                     THE TLC IS SOMETIMES 3, SOMETIMES 4, DEPEND ON 
                     WHETHER THE CR/RAP/N WAS GENERATED BY NVFARAP, 
                     OR BY NVFAVVD AND NVFASPC. THIS INCONSISTENCY
                     HAS CAUSED THE CDCNET GATEWAY TO FAIL ON MULTI-
                     HOST FILE TRANSFER.
  
          SOLUTION - NVF HAS BEEN MODIFIED TO GENERATE CONSISTENT 
                     TLC FOR ALL CR/RAP/N'S.
  
          TET   04/24/86    SMDEF,NVFARAP,NVFAVVD,NVFASPC 
 NA5B661  PROBLEM  - NVF REFUSED USER LOGIN WITH MESSAGE ** MULTIPLE
                     CONCURRENT LOGINS PROHIBITED ** ALTHOUGH THE USER
                     HAS NO OTHER CONCURRENT LOGINS ON GOING. 
  
          ANALYSIS - WHEN A USER FIRST LOGIN TO THE SYSTEM, NVF CREATES 
                     AN ENTRY IN THE RML TABLE TO RESTRICT THE USER IF
                     HE IS NOT ALLOWED MULTIPLE CONCURRENT LOGINS. IN 
                     SOME CASES, NVF HAS FAILED TO DELETE THE ENTRY WHEN
                     THE USER LOGED OUT. TO IDENTIFY AN USER, NVF USED
                     THE COMBINATION OF THE USER INDEX AND THE FAMILY 
                     ORDINAL. THE NVF DUMP SHOWED THAT THE TWO FAMLILY
                     ORDINALS THAT NVF RECEIVED FROM THE TWO CPM56
                     REQUESTS (ONE WHEN THE USER FIRST LOGED IN AND ONE 
                     WHEN THE USER SWITCHED FROM THE PRIMARY TO AN
                     SECONDARY APPLICATION. THIS CHANGE IN FAMILY OR- 
                     DINAL HAD MADE NVF FAIL TO LOCATE, AND HENCE FAIL
                     TO DELETE, THE ENTRY IN THE RML TABLE. SINCE THE 
                     ENTRY WAS NOT DELETED, NVF REJECTED ANY FURTHER
                     ATTEMPS TO LOGIN BY THAT USER BECAUSE NVF THOUGHT
                     THAT THE USER WAS STILL ON THE SYSTEM THROUGH A
                     DIFFERENT TERMINAL.
  
          SOLUTION - NVF IS CHANGED TO USE THE COMBINATION OF FAMILY
                     NAME AND USER INDEX TO IDENTIFY AN USER (INSTEAD 
                     OF USING THE COMBINATION OF FAMILY ORDINAL AN
                     USER INDEX). 
  
          TET    04/28/86    TEXTNVF,NVFTURL,NVFTPSV
 NA5B664 PROBLEM  - NVF ABORTED BECAUSE IT COULD NOT FIND PAAC ENTRY
                    FOR A CONNECTION. 
  
         ANALYSIS - NVF RECIEVED A CR/RAP/R WITH ANAME=QTSF. NVF
                    GENERATED THE CR/RAP/N AND CR/SWH/R, PUTTING THEM 
                    IN THE CTQ. RIGHT AFTER THIS NVF RECEIVED A 
                    NET/OFF/R FOR QTSF. AS A RESULT, NVF SENT A CR/TRM/R
                    TO TERMINATE THE CONNECTION, FOLLWED BY THE 
                    NET/OFF/N. THE CR/TRM/R REACHED NIP BEFORE CR/RAP/N 
                    DID. NIP REJECTED THE CR/TRM/R BECAUSE IT WAS 
                    EXPECTING THE CR/RAP/N. AT THAT TIME THE NET/OFF/N
                    REACHED NIP AND QTSF COMPLETELY NETED OFF. A DIFFE- 
                    RENT APLLICATION NETTED ON, REUSING THE APPLICATION 
                    NUMBER. SINCE NVF DID NOT RECEIVED THE CR/TRM/N, IT 
                    WENT AHEAD SEND OUT THE CR/SWH/R, AND THE CONNECTION
                    WAS SWITHED TO THE WRONG APPLICATION. NVF RECEIVED
                    THE CR/ACC AND TRIED TO PROCESS IT. NVF THEN ABORTED
                    BECAUSE THE PAAC ENTRY FOR THIS CONNECTION HAD BEEN 
                    DELETED AT THE TIME IT SENT OUT THE CR/TRM/R. 
  
         SOLUTION - MODIFY NVFAFAI SO THAT IT WILL CHECKED THE ACN$STATE
                    FOR A CONNECTION BEFORE IT CALL NVFCTRM TO TERMINATE
                    A CONNECTION. IF THE ACN$STATE IS "CREATE" (MEAMING 
                    THE CR/RAP/N HAS NOT ACTUALLY GONE OUT), DO NOT SEND
                    THE CR/TRM/R AS NIP WOULD REJECT IT ANYWAY. INSTEAD,
                    LET THE PROTOCOL ACTIONS CONTINUE. NVF WILL SEND OUT
                    CR/RAP/N AND THEN CR/SWH/R. SINCE THE APLLICATION IS
                    IN NET/OFF PENDING STATE, NVF WILL EVENTUALLY 
                    RECEIVE A CR/RCN/R. AT THIS TIME NVF WILL DECREMENT 
                    THE A-A CONNECTION COUNT AND SEND THE NET/OFF/N IF
                    THE COUNT EQUALS ZERO.
  
         TET    06/06/86    NVFAFAI 
 NA5B666  NAM DIED WITH NCSTTP ERROR. 
  
          PROBLEM: NAM DIED WITH TRIGGER 13 AT STATE 15 
                   OF THE NCSTTP TABLE. 
  
          ANALYSIS: WHEN THE PRU APPLICATION FAILED OR
                    ISSUED CONEND, A TRIGGER PRUOFFR
                    WAS GENERATED AND NCSTTP CHANGED ITS
                    STATE TO STATE 15. BUT PIP GENERATED
                    A PRU WORKLIST OF OPCODE 6 AS WELL. 
                    THIS CAUSED A STATE TABLE ERROR.
  
          SOLUTION: IN STATE 15 OF THE NCSTTP TABLE, THE
                    NCKRKPC TRIGGER SHOULD BE IGNORED. SO WHEN
                    THE PIPR TRIGGER COMES, THE STATE IS CHANGED
                    TO STATE 0 AND THEN WHEN HSTC COMES, IT WILL
                    FINISH UP THE CONNECTION BY SENDING WTERM.
  
          YCY       86/05/01    NIP 
 NA5B667  PROBLEM  - WHEN THE USER SWITCHED FROM THE PRIMARY APPL (IAF) 
                     TO THE SECONDARY APPL (NETFS) AND THE SECONDARY
                     REFUSED THE CONNECTION, THE CONNECTION WAS 
                     SWITCHED BACK TO IAF BUT IAF ALWAYS REJECTED THE 
                     SECOND CON/REQ/R.
  
          ANALYSIS - IAF REJECTED THE CON/REQ/R BECAUSE THE FAMILY
                     AND THE USER FIELD IN THE CON/REQ/R WERE BLANKED.
                     THIS IN TURN WAS DUE TO THE CR/SWH/R THAT NIP
                     RECEIVED FROM NVF CONTAINED BLANKS IN THESE FIELDS.
                     THESE TWO FIELDS HAD BLANKS IN THERE BECAUSE THE 
                     XREF DECLARATION OF FUNC XSFW IN NVFTRLC DID NOT 
                     INCLUDE A LENGH FIELD AND HENCE THE DEFAULT ZERO 
                     WAS USED. IN THAT CASE, XSFW BLANKED OUT EVERYTHING
                     EACH TIME IT WAS CALLED. 
  
          SOLUTION - NVF HAS BEEN MODIFY TO SEND NIP CR/SWH/R WITH
                     CORRECT CONTENTS IN THESE TWO FIELDS.
  
          TET    05/16/86    NVFTRLC
 NA5B668  PROBLEM  - THE ACCESS SECURITY CODE SENT THE PASSWORD MASK TO 
                     THE TERMINAL AS A MSG BLOCK.  THIS CAUSED SOME PACER 
                     SCRIPTS TO BE OUT OF SYN BECAUSE THE SCRIPTS HAVE
                     BEEN DESIGNED TO SEND MESSAGES BASED ON THE EOT
                     GENERATED BY CCP EACH TIME CCP RECEIVES A MSG BLOCK
                     FROM THE HOST. 
  
          SOLUTION - CHANGE THE BLOCK TYPE OF THE PASSWORD MASK TO BLK
                     INSTEAD OF MSG.
  
          TET   05/07/86    NVFTVVD 
 NA5B669  CHANGING THE FILE TRANSFER STATE TABLES 
          TO ACCEPT BLOCKS IN STATES WAITING FOR
          FCACKS. 
  
          PROBLEM: THERE WAS A PROBLEM THAT PUTTING THE 
                   DI IN REGULATION AND HENCE, HOLDING
                   UP THE BACK BLOCKS MOMENTARILY WOULD 
                   CAUSE A STATE TABLE ERROR IN THE 
                   NETXFR STATE TABLES. 
  
          ANALYSIS: IN THOSE STATES WAITING FOR FCACKS, 
                    ADDITIONAL STATES SHOULD BE ADDED TO
                    ALLOW AIP TO ACCEPT BLOCKS, AND YET 
                    WAIT FOR THE FCACKS TO BE CLEANED UP
                    AND CHANGING INTERFACES IN THE SAME 
                    APPLICATION LAYER.
  
          SOLUTION: TWO MORE STATES NSPWAC1 AND NSPWAC2 ARE 
                    ADDED TO PRU SENDER TABLES AND ADDITIONAL 
                    CHANGES ARE MADE TO THE PRU RECEIVER. 
                    ALSO, IN THOSE STATES WAITING FOR FCACK 
                    TO RETURN, FOR BOTH PRU AND CHARACTER 
                    MODE, A LSTOFF IS MADE TO THE NETXFR
                    CONNECTION, AND WHEN THE FCACK COMES, 
                    A LSTON IS ISSUED BEFORE IT EXIT FROM 
                    THE NETXFR ROUTINE. THIS IS TO AVOID
                    MOVING OTHER FILE TRANSFER PROTOCOL 
                    DATA ELEMENTS LIKE LEVEL SEVEN MESSAGES 
                    INTO THE NETXFR INTERFACE WHILE WAITING 
                    FOR THE FCACK TO RETURN.
          YCY 86/05/12    AIP 
 NA5B671  PROBLEM  - COPYRIGHT MESSAGES HAVE TO BE UPDATED. 
  
          SOLUTION - UPDATE THEM. 
  
          TET    05/13/86   CRCOM, TMSGNVF
 NA5B673  PROBLEM  - NVF ABORTS WITH MESSAGE "NVFTVVD - CAN NOT FIND
                     PTAC ENTRY". 
  
          ANALYSIS - THIS HAPPENED WHEN THE USER DID A LOT OF TYPE- 
                     AHEADS EXTREMELY FAST DURING THE TIME HE ANSWERED
                     TO A LOGIN PROMPT.  AFTER NVF HAD COLLECTED THE
                     FIRST THREE TYPEINS, IT ISSUED A CPM56 REQUEST TO
                     NOS. IF NVF RECEIVED ANY TYPEIN DATA FOR THIS CON- 
                     NECTION DURING THE TIME IT WAITED FOR RESPONSE FROM
                     NOS, NVF WOULD ERRONEOUSLY ISSUED ANOTHER CPM56
                     REQUEST. IF THIS HAPPENED DURING THE FOURTH UNSUC- 
                     CESSFUL ATTEMP, THE REGULAR CPM56 RESPONSE FROM NOS
                     WOULD CAUSE NVF TO TERMINATE THE CONNECTION (USER
                     RETRY LIMIT). WHEN THE RESPONSE FOR THE EXTRA CPM56
                     REQUEST CAME LATER, NVF TRIED TO PROCESS IT, AND 
                     NVF ABORTED ITSELF BECAUSE IT COULD NOT FIND THE 
                     PTAC ENTRY FOR THIS (TERMINATED) CONNECTION. 
  
          SOLUTION - MODIFY NVF TO PROCESS TYPEIN DATA ONLY WHEN IT IS
                     ACTUALLY EXPECTING THEM. IF NVF IS IN A STATE
                     WHERE IT DOES NOT EXPECTING ANY DATUM, SUCH AS 
                     WAITING FOR CPM RESPONSE, IT WILL IGNORE INPUT.
  
          TET    05/23/86    NVFTETI
 NA5B676  THIS MODSET ADDRESSES THE PROBLEM OF
          FIELD LENGTH AND CPU USAGE DEGRADATION FOR
          NAM BETWEEN 17T AND 19N.
  
          NA5B612 TRANSMITTED IN 19E IMPROVED THE 
          RESPONSE TIME FOR HIGHER IBL RUNS (200+)
          BUT DEGRADED BOTH THE NAM FIELD LENGTH
          AND THE CPU USAGE FOR LOWER IBL RUNS (150 
          AND 50). THIS MODSET ADJUSTED THE PARAMETERS
          FOR CALLING GARBAGE COLLECTION SUCH THAT
          IT USED THE 17T VALUES FOR LOWER IBL RUNS,
          AND THE 19E VALUES FOR HIGHER IBL RUNS. 
          THE PARAMETERS, TBUF, AND NFSIZE ARE CONTROLLED 
          BY A COUNT, NAMELY, CONCOUNT IN TEXT PT.
          WHEN THIS COUNT GOES BEYOND 65, THE 19E PARAMETER 
          VALUES ARE USED , BUT WHEN IT IS BELOW 65, THE
          17T VALUES ARE USED.
  
          RUNNING WITH THIS MODSET, THE FIELD LENGTH
          FOR 19N IBL 50 RUN SHOULD SHOW A SMALLER
          FIELD LENGTH AND BETTER CPU USAGE. HOWEVER, THE 
          RESPONSE TIME FOR HIGHER IBL 150+ SHOULD SHOW 
          IMPROVEMENT. THE PRICE IS THAT THE FIELD LENGTH 
          FOR HIGHER IBL SHOULD SHOW A DEGRADATION. IN TERMS
          OF PRIORITY, CPU RESPONSE TIME IMPROVEMENT HAS A HIGHER 
          PRIORITY THAN FIELD LENGTH DEGRADATION. 
          YCY     86/07/15     PT,INPARU,BLDNCNB,RELNCNB
 NA5B677  NVF FAILED WITH "PTAC ENTRY NOT FOUND". 
          PROBLEM: WHEN A CRRCN FOR A T-A CONNECTION
                   WAS SENT FROM NIP TO NVF, NVF COULD
                   NOT FIND ITS PTAC ENTRY AND IT ABORTED 
                   IN DEBUG MODE. 
  
          ANALYSIS: THE FLOW OF THIS PROBLEMATIC CONNECTION 
                    IS AS FOLLOWS:  
                    THE APPLICATION CONCERNED IS VEIAF. 
                    A) A CRITEN WITH A VCB ORDINAL 15 WAS RECEIVED
                       BY NIP AND NIP SAVED IT IN THE ACNBVCBO. 
                    B) AFTER A CRSWH WAS ISSUED BY NVF, THE HOST
                       CONNECTION STATE CHANGED FROM 4 TO 5.
                    C) A CHANGE TERMINAL CHARACTERISTICS MESSAGE WAS
                       RECEIVED AND THAT TRIGGER A "TCC" TRIGGER
                       TO MOVE THE HOST CONNECTION STATE FROM STATE 5 TO
                       STATE 12.
                    D) NO CONREQN WAS RECEIVED YET. 
                    E) 10 MINUTES LATER A TIMEOUT TRIGGER WAS RECEIVED, 
                       AND BY MISTAKE, THE STATE TABLE GENERATED A CRCB 
                       INSTEAD OF A FCINACT MESSAGE. WHEN NVF RECEIVED
                       THE CRCB IT RELEASED AND REUSED ITS VCB ORDINAL 15.
                       THIS TIME THIS VCB ORDINAL WENT TO IAF.
                    F) THE APPLICATION  VEIAF NETOFFED. NOW, NIP SENT CRRCN 
                       WITH THEIR VCB ORDINALS TO ALL CONNECTIONS INCLUDING 
                       THE ONE WITH VCB ORDINAL 15. THIS CAUSED NVF TO SEACH
                       THE PTAC ENTRY USING VCB ORDINAL 15 AS THE KEY AND IT
                       FAILED BECAUSE IT DELETED THAT PTAC ENTRY WHEN THE CRCB
                       WAS RECEIVED.
          SOLUTION:    IN STATE 12 OF THE HOST CONNECTION STATE TABLE, INSTEAD
                       OF SENDING CRCB, NIP SHOULD SEND FCINACT. THEN WHEN
                       CRRCNN COME, IT GOES BACK TO STATE 4 AND WAITS FOR CRTERM
                       CLEAN UP THIS CONNECTION.
 NA5B682 PROBLEM  - 1. THE COLLECTOR DID NOT COLLECT DI DUMP IF 
                       NETFM FAILED TO ATTACH (OR GET) IT.
                    2. THE COLLECTOR STOPPED AT A HOLE. IN OTHER
                       WORDS, WHEN THE FILE NAMES ARE DISCONTINUOUS,
                       IT STOPPED.
  
         SOLUTION - MODIFY COLLECT SO THAT IT WILL
                    1. TRY TO COLLECT (AND/OR) PURGE A DI DUMP
                       DIRECTLY IF IT HAS FAILED TO DO SO THROUGH 
                       NETFM CALLS. 
                    2. IT NO LONGER STOPS ON A HOLE. IE. IT WILL
                       SEARCH FOR ALL POSSIBLE DI DUMP FILES. 
  
         TET    06/06/86    COLLECT 
 NA5B684  PROBLEM -  I CANNOT ESTABLISH AN INTERHOST LOGICAL LINK TO
                     THE SAME HOST. 
          ANALYSIS - BLDLLCB IS REJECTING THE REG/LL SUPERVISORY MESSAGE
                     FROM CCP TO ESTABLISH THE INTERHOST LOGICAL LINK 
                     BECAUSE THE TERMINAL NODE MATCHES ONE OF ITS OWN 
                     COUPLER NODE NUMBER. 
          SOLUTION - BLDLLCB HAS BEEN CORRECTED TO NOT REJECT THE REG/LL
                     SUPERVISORY MESSAGE TO ESTABLISH THE INTERHOST 
                     LOGICAL LINK IF IT IS A HOST TO HOST LOGICAL LINK
                     THAT IS BEING ESTABLISHED. 
          EG     06/09/86    BLDLLCB, NPREGLL 
 NA50213  PROBLEM  - NS LOADS WRONG LOAD FILE INTO NPU. 
          ANALYSIS - NS STORED THE NPU NODE NUMBER IN THE NCT (NS$BNCT).
                     IT THEN USED THIS FIELD AS A KEY FOR BUILDING
                     THE NPT AND OVERWROTE THIS FIELD WITH THE OFFSET 
                     INTO NPT (NS$BNPT).  THIS RESULTED IN NCT$NTORD
                     POINTING TO THE WRONG NPT ORDINAL. 
          SOLUTION - NS COMMON DECK NCT$NS HAS BEEN CHANGED TO USE
                     SEPARATE FIELDS FOR THE NPT ORDINAL AND NCT OFFSET.
          EG     10/10/85    NCT$NS 
 NA50393  NDL NOW PASSES EXACT VALUE FOR THE LENGTH OF
           THE DTEA ADDRESS.
          PROBLEM: SOME PUBLIC DATA NETWORK REQUIRES
                   EXACT VALUE OF THE LENGTH OF THE 
                   DTEA ADDRESS TO BE PASSED. 
  
          ANALYSIS: THIS CHANGE AFFECTS BOTH NDL AND
                    AND NVF. NVF HAS TO SKIP ACCORDING
                    TO THE ROUNDED VALUE OF THE CALLED
                    DTEA ADDRESS LENGTH ALTHOUGH NDL DOES 
                    NOT ROUND IT TO AN EVEN VALUE.
  
          SOLUTION: IN NDLP2LF, NDL ASSIGNS EXACT LENGTH OF 
                    THE DTEA TO THE LCF OUTCALL AND INCALL RECORD.
                    IN NVFAIAP, NVF ROUNDS UP THE VALUE OF
                    THE CALLED DTEA ADDRESS LENGTH TO LOCATE THE
                    START BIT POSITION OF THE FACILITY. SIMILARLY,IN
                    NVFARAP, NVF ROUNDS UP THE VALUE OF THE CALLED
                    DTEA ADDRESS LENGTH. THE CALLING DTEA ADDRESS 
                    LENGTH IS ASSIGNED BY THE NETWORK AND HENCE 
                    IT DOES NOT HAVE TO BE CHANGED. 
  
          YCY 03/11/86   NDL AND NVF
  
 NA50404  NAM DIED WITH STATE TABLE ERROR.
          PROBLEM: A STATE TABLE ERROR OCCURRED WITH
                   THE NBSTTP PROCESS WITH TRIGGER 7
                   AT STATE 7.
  
          ANALYSIS: A PTFS APPLICATION RECEIVED A 
                    SINTR TRIGGER WHEN IT WAS AT
                    STATE 7 OF THE NETWORK BLOCK
                    STATE TABLE.  PRIOR TO THAT 
                    A BREAK BLOCK WAS RECEIVED FROM 
                    THE X.25 SOFTWARE DURING CONNECTION 
                    ESTABLISHMENT.
  
          SOLUTION: SINCE APPLICATION DID NOT SENT ANY
                    FCRST TO CLEAR THE BREAK CONDITION
                    IN THE NETWORK SIDE, A SINTR TRIGGER
                    IN STATE 7 OF THE NETWORK BLOCK 
                    STATE TABLE SHOULD BE ACCEPTED AND
                    A INTR BLOCK SENT TO CCP TO CLEAR THE 
                    BREAK CONDITION AND STATE CHANGED TO
                    STATE 3.
  
                    YCY 85/10/30    NIP 
 NA50448  PROBLEM  - NVF LEAVES TERMINALS IN TRANSPARENT MODE IF THE
                     USER HAS BEEN IN FSE WHEN IAF OR NAM IS DROPPED. 
          ANALYSIS - CCP DOES NOT RESET THE TERMINAL CHARACTERISTICS
                     WHEN THIS HAPPENS. 
          SOLUTION - WHEN NVF SENDS OUT THE BANNER, IT WILL ALSO SEND 
                     A CTR/CHAR SM TO CCP TO SET THE INPUT MODE TO
                     NON-TRANSPARENT. 
          PAM     85/12/06     NVFTITE,TEXTNVF,TXTANVF,NVFUMQE,NVFTDAD, 
                               NVFTINA,NVFTCRN,NVFTPUV,NVFTRVD
 NA50456  FOR XAUTO LINES, THE DEFAULT ABL SHOULD BE
          2.
  
          PROBLEM: CURRENTLY, THE DEFAULT ABL FOR 
                   XAUTO DEVICES IS 1.
  
          SOLUTION: WHEN NDLNFCM ASSIGNS THE VALUE OF THE 
                    DEFAULT TO ABL, IT SHOULD CHECK IF
                    XAUTO$REC IS SET. IF XAUTO IS SET, THEN 
                    ABL IS 2 ELSE ABL SHOULD BE 1 BY DEFAULT. 
          YCY  85/16/1985       NDL 
 NA50463  ALLOWING NDL USERS TO SPECIFY NONE FOR
          UDATA ON THE OUTCALL STATEMENTS.
  
          PROBLEM: NEED TO GENERATE NULL ENTRY FOR
                   UDATA. 
  
          ANALYSIS: CHANGE NDLP SUCH THAT UDATA = NONE
                    IS ACCEPTED.
  
          SOLUTION: WHEN UDATA = NONE IS SPECIFIED, NDL 
                    PASS1 FORMATS A UDATA ENTRY WITH
                    KEYWORD ID AND A ZERO LENGTH ENTRY IN 
                    THE STATEMENT TABLE. IN PASS2, WHEN IT SEES 
                    THAT THE ENTRY LENGTH IS ZERO, IT DOES NOT
                    FORMAT ANY UDATA ENTRY FOLLOWING THE PRID.
                    BUT IF UDATA= NONE IS NOT SPECIFIED, AND
                    NO OTHER VALID UDATA VALUE IS SPECIFIED, THE
                    DEFAULT 24 SEMIOCTETS WILL STILL BE FORMATTED 
                    AFTER PRID. 
          YCY  85/16/1985       NDL 
 NA50469  THE MAXIMUM LENGTH OF DTEA SHOULD BE 15 
          INSTEAD OF 14.
  
          PROBLEM: BY CCITT STANDARD, THE LENGTH OF 
                   THE DTEA SHOULD BE 15 INSTEAD OF 
                   14.
  
          ANALYSIS: NDLP NEEDS TO BE CHANGED TO ACCEPT
                    A LONGER DTEA ADDRESS.
  
          SOLUTION: IN NDLPSS1, ENTVAL SHOUDL BE CHANGED TO 
                    ACCEPT ONE MORE ST$ENTRY IN ORDER TO
                    PROCESS TWO 7 CHARACTER LONG STVALNAM 
                    AND ONE 1 CHARACTER LONG STVALNAM.
                    IN NDLP2LF, THE MXDTEA DEF NEEDS TO BE
                    CHANGED TO 15. ALSO, NDLP2LF, NEEDS TO PROCESS
                    A THREE WORD ENTRY STVALNAM.
  
          YCY 03/11/1986 NDL
  
 NA50476  PROBLEM  - WHEN IT ISSUED THE PASSWORD PROMT, NVF DID NOT 
                     SET THE EP (ECHO FLAG) IN THE DOWN LINE BLOCK
                     HEADER FOR TERMINAL CLASES 1, 4, AND 8. AS A 
                     RESULT, THE PASSWORD WAS SHOWING (SUPPOSED TO
                     BE HIDDEN) FOR SOME TEKTRONIX TERMINALS. 
  
          SOLUTION - MODIFY NVFTILP SO THAT IT WILL TURN THE ECHO FLAG
                     OFF FOR ALL TERMINAL CLASSES WHEN IT ISSUES THE
                     PASSWORD PROMT.
  
          TET   03/07/86    NVFTILP 
 NA50509  NAM DID NOT RELEASE ACB FOR RBF AFTER IT
          NETOFFED. 
  
          PROBLEM: AFTER RBF NETOFFED, IT STAYED IN THE 
                   K-DISPLAY AND SUBSEQUENT NETON ATTEMPTD
                   FROM A FRESH COPY OF RBF WAS REJECTED.S
  
          ANALYSIS: IN THE ACB THERE IS A SIX BIT FIELD 
                    FOR STORING THE NUMBER OF PRU CONNECTIONS.
                    IN THE ACNT, THE COUNT OF INACTIVE ENTRIES
                    FOR RBF IS 132 OCTAL. BUT THE SIX BIT FIELD 
                    CALLED ACBNPRU CAN ONLY REPRESENT 63 PRU
                    CONNECTIONS. HENCE, WHEN RBF NETOFFED, NPPCT
                    STARTED DECREMENTING A COUNT WHICH WAS ALREADY
                    OVERFLOWED AND HENCE IT NEVER WENT TO ZERO AND
                    NAM WOULD ONLY RELEASE THE ACB AND THE AT ENTRY 
                    AFTER THE ACBNPRU COUNT GOES TO ZERO. 
  
          SOLUTION: THE ACBNPRU FIELD IS CHANGED TO A 12 BIT
                    FIELD AND SINCE THE CURRENT ACB DOES NOT
                    HAVE ANY MORE ROOM FOR THAT, ONE MORE WORD
                    IS ADDED SO THAT THE SIZE OF THE ACB IS NOW 
                    20 DECIMAL. 
  
          YCY 86/05/09    NIP 
  
 NA50510  NAM DIED WITH NCSTTP ERROR STATE 11 TRIGGER 13. 
  
          PROBLEM: NCSTTP COULD NOT HANDLE PIP TERMINATION
                   WORKLIST WITH OPCODE 6 AT STATE 11.
  
          ANALYSIS: WHEN THE NETWORK RECEIVED A TCNTA 
                    FROM CCP, IT STARTS TERMINATING  THE
                    PRU CONNECTIONS. FIRST, IT SENDS TERMINATE
                    PRU CONNECTIONS AND GOES TO STATE 11, WAITING 
                    FOR PIP TO RESPONSE TO THE TERMINATION WORKLIST.
                    HOWEVER, PIP DETECTED ANOTHER BLOCK PROTOCOL
                    ERROR AT THAT POINT, SO IT SENT A "BREAK AND
                    DAYFILE" PRU TERMINATION WORKLIST WITH OPCODE 
                    6 TO THE THE CONNECTION WHICH CAUSED THE
                    NCSTTP STATE TABLE ERROR. 
  
          SOLUTION: WHEN THE NETWORK RECEIVED THE NCKRKPC TRIGGER 
                    IN STATE 11,IT SHOULD IGNORE IT AND WAIT
                    FOR THE PIPR TRIGGER TO COME TO CLEAN UP
                    THE CONNECTION. SIMILAR CHANGE IS MADE TO STATE 
                    6 WHILE WAITING FOR TERM BLOCKS FROM CCP. 
  
          YCY 86/05/12    NIP 
  
 *L678*    ************************************************ 
 FN25AP1  FEATURE  - ENHANCE AIP TO RECOVER FROM RMS I/O ERRORS WHICH 
                     MAY OCCUR ON THE AIP TRACE OR STATISTICS FILES.
          EG     01/20/86    NP$DB, NETDBG, NP$RETN(NEW), NP$PIOE(NEW), 
                             NETREL, NP$STAT, NP$ON,
 FN25NP1  ENHANCE NIP TO RECOVER FROM RMS I/O ERRORS ON ANY OF THE DISK 
          FILES THAT IT PROCESSES.
          EG     01/31/86    RDUMP, NPPCT, TWRITE, XCLOST, OPEN, WRITER,
                             WRITEO, ROUTE, REWIND, READ, ITRACE, NPPCT,
                             NEIB, XENDNAM, XENDRPV, NEIB, NXBLINK, 
                             INIPD, NNETREL, RELFILE
 FN25QT2  ENHANCE QTRM TO SUPPORT DOWNLINE PRU INTERFACE FOR QTRM 
          APPLICATION PROGRAM PSU.  THIS INTERFACE IS NOT SUPPORTED FOR 
          ANY OTHER NAM APPLICATION PROGRAMS.  THE FOLLOWING INTERFACE
          CHANGES HAVE BEEN MADE TO QTRM. 
  
          THREE NEW COMMAND CODES HAVE BEEN ADDED TO QTCMD. 
  
              11:  DEVICE TYPES SUPPORTED.
  
                   QTRM NORMALLY SUPPORTS ONLY CONNECTIONS TO CONSOLE 
                   DEVICE TYPES.  IF THE A-TO-A FIELD IS SET IN THE 
                   NIT, THEN QTRM WILL ALSO SUPPORT CONNECTIONS TO
                   OTHER APPLICATIONS.
  
                   IF THIS COMMAND CODE IS SPECIFIED, QTRM PROCESSING 
                   CHANGES TO ACCEPT CONNECTIONS TO ONLY THOSE DEVICE 
                   TYPES SPECIFIED BY THE APPLICATION PROGRAM WHICH CAN 
                   INCLUDE BATCH DEVICES.  THE SECOND PARAMETER WSA IS
                   A WORD CONTAINING SINGLE BIT FLAGS TO INDICATE THE 
                   DEVICE TYPES SUPPORTED.  THE BIT POSITION OF A FLAG
                   (BIT 0 = RIGHTMOST BIT) CORRESPONDS TO THE DEVICE
                   TYPE VALUE; E.G.  BIT 0 REFERS TO DEVICE TYPE 0.  IF 
                   THE BIT IS NONZERO, THEN THE APPLICATION PROGRAM 
                   SUPPORTS THAT DEVICE TYPE.  THIS QTCMD CALL CAN BE 
                   CALLED ANYTIME AFTER QTOPEN AND CAN BE CALLED
                   MULTIPLE TIMES TO CHANGE THE DEVICE TYPES SUPPORTED. 
                   THIS QTCMD CALL WILL ALSO OVERRIDE THE A-A FLAG IN 
                   THE NIT. 
  
              12:  AUTOMATIC PROCESSING OF PRU/ON SUPERVISORY MESSAGE.
  
                   QTRM NORMALLY INFORMS THE APPLICATION PROGRAM WHEN A 
                   NEW CONNECTION IS FULLY ESTABLISHED WITH THE 
                   APPLICATION PROGRAM.  IF THE PRU INTERFACE IS TO BE
                   USED ON THIS CONNECTION, THE APPLICATION PROGRAM 
                   WILL HAVE TO SEND A PRU/ON SUPERVISORY MESSAGE AND 
                   WAIT FOR A NORMAL RESPONSE BEFORE THE PRU INTERFACE
                   CAN BE USED. 
  
                   IF THIS COMMAND CODE IS SPECIFIED, QTRM PROCESSING 
                   CHANGES TO AUTOMATICALLY SEND THE PRU/ON SUPERVISORY 
                   MESSAGE FOR THE DEVICE TYPES SPECIFIED BY THE
                   APPLICATION PROGRAM.  THE APPLICATION PROGRAM IS NOT 
                   INFORMED ABOUT THE NEW CONNECTION UNTIL A NORMAL 
                   RESPONSE IS RECEIVED FOR THE PRU/ON SUPERVISORY
                   MESSAGE.  IF AN ABNORMAL RESPONSE IS RECEIVED, THE 
                   CONNECTION IS AUTOMATICALLY TERMINATED AND THE 
                   APPLICATION PROGRAM IS NEVER INFORMED THAT A 
                   CONNECTION HAD BEEN ESTABLISHED.  THE SECOND 
                   PARAMETER WSA IS A WORD CONTAINING SINGLE BIT FLAGS
                   TO INDICATE THE DEVICE TYPES FOR WHICH PRU/ON
                   SUPERVISORY MESSAGE PROCESSING IS TO BE PERFORMED. 
                   THE BIT POSITION OF A FLAG (BIT 0 = RIGHTMOST BIT) 
                   CORRESPONDS TO THE DEVICE TYPE VALUE; E.G.  BIT 1
                   REFERS TO DEVICE TYPE 1.  IF THE BIT IS NONZERO, 
                   THEN QTRM WILL PERFORM PRU/ON PROCESSING FOR THAT
                   DEVICE TYPE.  THIS QTCMD CALL CAN BE CALLED ANYTIME
                   AFTER QTOPEN AND CAN BE CALLED MULTIPLE TIMES TO 
                   CHANGE THE DEVICE TYPES FOR WHICH PRU/ON SUPERVISORY 
                   MESSAGE PROCESSING IS PERFORMED.  SINCE PRU
                   INTERFACE IS NOT SUPPORTED FOR DEVICE TYPES 0 AND 5, 
                   THE SETTING OF THOSE BITS IN THE WSA WILL BE 
                   IGNORED; I.E.  NO PRU/ON SUPERVISORY MESSAGE 
                   PROCESSING WILL BE PERFORMED FOR THOSE DEVICE TYPES. 
  
              13:  CONVERT PM MESSAGES. 
  
                   QTRM NORMALLY DELIVERS PM MESSAGES UNALTERED TO THE
                   APPLICATION PROGRAM.  THIS MEANS THE PM MESSAGE WILL 
                   BE IN 8/12 ASCII.
  
                   IF THIS COMMAND CODE IS SPECIFIED, QTRM PROCESSING 
                   CHANGES TO DELIVER PM MESSAGES ACCORDING TO THE
                   CONVERSION CODE STORED IN THE WORD POINTED TO BY 
                   THE SECOND PARAMETER (WSA).  THIS QTCMD CALL CAN BE
                   CALLED ANYTIME AFTER QTOPEN AND CAN BE CALLED AS 
                   OFTEN AS NECESSARY TO CHANGE THE CHARACTER SET FOR 
                   PM MESSAGES. 
  
                   THE FOLLOWING CONVERSION CODES HAVE BEEN DEFINED:  
  
                   0:  PM MESSAGES ARE DELIVERED UNCHANGED, WHICH IS
                       APPLICATION CHARACTER TYPE 3 (12 BIT ASCII). 
  
                   1:  PM MESSAGES ARE DELIVERED IN 6 BIT DISPLAY CODE. 
                       LOWER CASE LETTERS WILL BE CONVERTED TO UPPER
                       CASE.  SPECIAL CHARACTERS FOR WHICH THERE IS NO
                       CORRESPONDING DISPLAY CODE CHARACTER WILL BE 
                       CONVERTED TO BLANKS. 
  
                   2:  PM MESSAGES ARE DELIVERED IN CYBER CONSOLE 
                       DISPLAY CODE.  THIS IS ESSENTIALLY THE SAME AS 
                       6 BIT DISPLAY CODE EXCEPT ADDITIONAL SPECIAL 
                       CHARACTERS THAT CANNOT BE DISPLAYED ON THE 
                       CYBER CONSOLE ARE CONVERTED TO BLANKS. 
  
          EIGHT NEW SUPERVISORY MESSAGE CODES HAVE BEEN ADDED TO QTSUP. 
          APPLICATION PROGRAMS THAT WANT TO SEND THESE SUPERVISORY
          MESSAGES SHOULD CALL QTSUP WITH THE APPROPRIATE SUPERVISORY 
          MESSAGE CODE RATHER THAN GENERATE THE SUPERVISORY MESSAGES
          THEMSELVES AND CALLING QTSUP WITH SUPERVISORY MESSAGE CODE 0. 
  
              14:  SEND PRU/ON/R SUPERVISORY MESSAGE TO NAM.
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE CONNECTION-
                   NUMBER FIELD OF THE NIT AND STORE THE PRU SIZE IN
                   THE PARM-FLAG1 FIELD OF THE NIT.  THE CONNECTION 
                   SPECIFIED IN THE CALL MUST BE IN THE NORMAL STATE
                   (STATE 2), HAVE NO BLOCKS OUTSTANDING, AND NOT BE A
                   CONNECTION TO DEVICE TYPES 0 OR 5.  THE PARM-FLAG1 
                   FIELD SPECIFIES THE SIZE OF THE PRU BUFFERS TO BE
                   USED BY NAM AND CAN HAVE THE VALUES 1, 2, OR 3.  THE 
                   SECOND PARAMETER WSA IS NOT REQUIRED FOR THIS CALL 
                   AND CAN BE OMITTED.  THE STATE OF THE CONNECTION IS
                   CHANGED TO THE APPLICATION-WAITING-FOR-PRU-
                   CONNECTION STATE (STATE 16). 
  
              15:  SEND SET/DEV SUPERVISORY MESSAGE TO NAM. 
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE
                   CONNECTION-NUMBER FIELD OF THE NIT, STORE THE NO OF
                   WORDS CONTAINING SET/DEV FN/FV PAIRS IN THE
                   CURRENT-TRANS-SIZE FIELD OF THE NIT, AND STORE THE 
                   FN/FV PAIRS IN THE WSA BUFFER.  THE CONNECTION 
                   SPECIFIED IN THE CALL MUST BE ESTABLISHED AS A PRU 
                   CONNECTION (STATES 17 - 24).  THE CURRENT-TRANS-SIZE 
                   FIELD MUST HAVE A MINIMUM SIZE OF ONE WORD.
  
              16:  SEND SET/FILE SUPERVISORY MESSAGE TO NAM.
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE
                   CONNECTION-NUMBER FIELD OF THE NIT, STORE THE NO OF
                   WORDS CONTAINING SET/FILE FN/FV PAIRS IN THE 
                   CURRENT-TRANS-SIZE FIELD OF THE NIT, AND STORE THE 
                   FN/FV PAIRS IN THE WSA BUFFER.  THE CONNECTION 
                   SPECIFIED IN THE CALL MUST BE ESTABLISHED AS A PRU 
                   CONNECTION (STATES 17 - 24).  THE CURRENT-TRANS-SIZE 
                   FIELD MUST HAVE A MINIMUM SIZE OF ONE WORD.
  
              17:  SEND OFC/DATA/R SUPERVISORY MESSAGE TO NAM.
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE
                   CONNECTION-NUMBER FIELD OF THE NIT, STORE THE NO OF
                   WORDS CONTAINING OFC/DATA TEXT IN THE
                   CURRENT-TRANS-SIZE FIELD OF THE NIT, STORE THE 
                   OFC/DATA TEXT IN THE WSA BUFFER, AND SET THE 
                   PARM-FLAG1 FIELD OF THE NIT TO THE REQUIRED VALUE
                   FOR THE EOJ FLAG (0 = DO NOT SET EOJ FLAG; 1 = SET 
                   EOJ FLAG).  THE CONNECTION SPECIFIED IN THE CALL 
                   MUST BE ESTABLISHED AS A PRU CONNECTION (STATES
                   17 - 24).  THE CURRENT-TRANS-SIZE FIELD MUST HAVE
                   A MINIMUM SIZE OF ONE WORD.
  
              18:  SEND OFC/STRT SUPERVISORY MESSAGE TO NAM.
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE
                   CONNECTION-NUMBER FIELD OF THE NIT, THE PRU POSITION 
                   MUST BE STORED IN THE FIRST WORD OF THE WSA BUFFER,
                   AND THE LOCAL FILE NAME AND FNT ORDINAL MUST BE
                   STORED IN THE SECOND WORD OF THE WSA BUFFER.  THE
                   CONNECTION SPECIFIED IN THE CALL MUST BE IN THE
                   INITIAL-PRU-CONNECTION STATE (STATE 17).  THE LOCAL
                   FILE NAME MUST BE STORED IN THE LEFTMOST 42 BITS OF
                   THE SECOND WORD OF THE WSA BUFFER.  THE FNT ORDINAL
                   MUST BE STORED IN THE RIGHTMOST 18 BITS OF THIS SAME 
                   WORD.  THE STATE OF THE CONNECTION IS CHANGED TO THE 
                   ACTIVE-PRU-CONNECTION STATE (STATE 18).
  
              19:  RESTART PRU OUTPUT.
  
                   QTRM WILL SEND AN OFC/RSM OR OFC/RSTR SUPERVISORY
                   MESSAGE TO NAM.  BEFORE MAKING THIS CALL, THE
                   APPLICATION PROGRAM MUST STORE THE CONNECTION NUMBER 
                   IN THE CONNECTION-NUMBER FIELD OF THE NIT AND THE
                   PRU POSITION MUST BE STORED IN THE FIRST WORD OF THE 
                   WSA BUFFER.  THE CONNECTION SPECIFIED IN THE CALL
                   MUST BE IN ONE OF THE PRU-CONNECTION-STOPPED  STATES 
                   (STATES 21 - 23).  THE STATE OF THE CONNECTION IS
                   CHANGED BACK TO THE ACTIVE-PRU-CONNECTION STATE
                   (STATE 18).
  
              20:  SEND OFC/STP/R SUPERVISORY MESSAGE TO NAM. 
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE
                   CONNECTION-NUMBER FIELD OF THE NIT.  THE CONNECTION
                   SPECIFIED IN THE CALL MUST BE IN THE ACTIVE-PRU- 
                   CONNECTION STATE (STATE 18).  THE SECOND PARAMETER 
                   WSA IS NOT REQUIRED FOR THIS CALL AND CAN BE 
                   OMITTED.  THE STATE OF THE CONNECTION IS CHANGED 
                   TO THE APPLICATION-STOPPING-PRU-TRANSFER STATE 
                   (STATE 19).
  
              21:  SEND OFC/ABT/R SUPERVISORY MESSAGE TO NAM. 
  
                   BEFORE MAKING THIS CALL, THE APPLICATION PROGRAM 
                   MUST STORE THE CONNECTION NUMBER IN THE
                   CONNECTION-NUMBER FIELD OF THE NIT.  THE CONNECTION
                   SPECIFIED IN THE CALL MUST BE AN ACTIVE PRU
                   CONNECTION (STATES 18 - 24) THAT IS NOT IN THE 
                   PRU-ABORT STATE (STATE 20).  THE SECOND PARAMETER
                   WSA IS NOT REQUIRED FOR THIS CALL AND CAN BE 
                   OMITTED.  THE STATE OF THE CONNECTION IS CHANGED TO
                   THE PRU-ABORT STATE (STATE 20).
  
  
          TWO NEW FIELDS HAVE BEEN ADDED TO THE CONNECTION ENTRY OF THE 
          NIT.  THEY ARE THE UPLINE-BLOCK-SIZE FIELD AND THE
          DOWNLINE-BLOCK-SIZE FIELD.
  
             UPLINE-BLOCK-SIZE     WORD 5 BITS 59-48 (BIT 0 = RIGHTMOST 
                                   BIT) OF CONNECTION ENTRY.
  
                                   QTGET WILL STORE A VALUE IN THIS 
                                   FIELD WHEN IT ACCEPTS A CONNECTION 
                                   REQUEST.  THE VALUE WILL COME FROM 
                                   THE UBZ FIELD OF THE CON/REQ/R 
                                   SUPERVISORY MESSAGE. 
  
             DOWNLLINE-BLOCK-SIZE  WORD 5 BITS 47-36 (BIT 0 = RIGHTMOST 
                                   BIT) OF CONNECTION ENTRY.
  
                                   QTGET WILL STORE A VALUE IN THIS 
                                   FIELD WHEN IT ACCEPTS A CONNECTION 
                                   REQUEST.  THE VALUE WILL COME FROM 
                                   THE DBZ FIELD OF THE CON/REQ/R 
                                   SUPERVISORY MESSAGE. 
  
          TEN NEW NIT RETURN CODES HAVE BEEN ADDED.  ALL ARE IN 
          RESPONSE TO QTGET CALLS.
  
              45:  PRU CONNECTION ESTABLISHED.
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED A PRU/ON/N SUPERVISORY
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   OF THE NEW PRU CONNECTION.  THE STATE OF THE 
                   CONNECTION WILL HAVE BEEN SET TO THE INITIAL-PRU-
                   CONNECTION STATE (STATE 16).  TO GET THIS RETURN 
                   CODE, THE APPLICATION PROGRAM MUST HAD PREVIOUSLY
                   EITHER CALLED QTSUP WITH SMC = 14 OR CALLED QTCMD
                   WITH CC = 12 AND RECEIVED A NEW CONNECTION THAT
                   NEEDED TO BE ESTABLISHED AS A PRU CONNECTION.
  
              46:  UNABLE TO ESTABLISH PRU CONNECTION.
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED A PRU/ON/A SUPERVISORY
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   THAT COULD NOT BE CONVERTED INTO A PRU CONNECTION. 
                   THE STATE OF THE CONNECTION WILL HAVE BEEN RESET TO
                   THE NORMAL STATE (STATE 2).  THE SUB-RETURN-CODE 
                   FIELD OF THE NIT WILL CONTAIN THE RETURN CODE FROM 
                   THE PRU/ON/A SUPERVISORY MESSAGE.  TO GET THIS 
                   RETURN CODE, THE APPLICATION PROGRAM MUST HAD
                   PREVIOUSLY CALLED QTSUP WITH SMC = 14. 
  
              47:  RECEIVED OFC/DATA/N SUPERVISORY MESSAGE. 
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED AN OFC/DATA/N SUPERVISORY 
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   ASSOCIATED WITH THE SUPERVISORY MESSAGE.  TO GET 
                   THIS RETURN CODE, THE APPLICATION PROGRAM MUST HAD 
                   PREVIOUSLY CALLED QTSUP WITH SMC = 17. 
  
              48:  PRU OUTPUT TRANSFER STOPPED BY PIP OR THE NETWORK. 
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED AN OFC/STPD SUPERVISORY 
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   OF THE CONNECTION IN WHICH PRU TRAFFIC HAS STOPPED.
                   THE STATE OF THE CONNECTION WILL HAVE BEEN CHANGED 
                   TO THE PRU-OUTPUT-STOPPED-BY-NETWORK STATE (STATE
                   22) OR PRU-OUTPUT-STOPPED-BY-PIP STATE (STATE 23). 
                   THE SUB-RETURN-CODE FIELD OF THE NIT WILL CONTAIN
                   THE RETURN CODE FROM THE OFC/STPD SUPERVISORY
                   MESSAGE.  TO GET THIS RETURN CODE, THE APPLICATION 
                   PROGRAM MUST HAVE AN ACTIVE PRU CONNECTION.  THE 
                   FIRST WORD OF THE WSA BUFFER WILL CONTAIN THE
                   CURRENT PRU POSITION OF THE FILE.  IF THE OFC/STPD 
                   WAS CAUSED BY A PM MESSAGE, THEN THE PM MESSAGE WILL 
                   HAVE BEEN COPIED TO THE WSA BUFFER BEGINNING WITH
                   THE SECOND WORD.  THE SIZE OF THE PM MESSAGE (NO OF
                   CHARACTERS) WILL BE IN THE CURRENT-TRANS-SIZE FIELD
                   OF THE NIT.  THE PM MESSAGE WILL BE IN 8/12 ASCII, 
                   OR DISPLAY CODE (IF QTCMD WAS CALLED WITH CC=13).
                   IF THE PM MESSAGE IS TOO LARGE FOR THE BUFFER, IT
                   WILL AUTOMATICALLY BE TRUNCATED AND THE TRUNC FIELD
                   WILL BE SET TO 1 IN THE NIT. 
  
              49:  PRU OUTPUT TRANSFER STOPPED BY APPLICATION.
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED AN OFC/STP/N SUPERVISORY
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   OF THE CONNECTION IN WHICH PRU TRAFFIC HAS STOPPED.
                   THE STATE OF THE CONNECTION WILL HAVE BEEN CHANGED 
                   TO THE PRU-OUTPUT-STOPPED-BY-APPLICATION STATE 
                   (STATE 20).  TO GET THIS RETURN CODE, THE
                   APPLICATION PROGRAM MUST HAD PREVIOUSLY CALLED QTSUP 
                   WITH SMC = 20.  THE FIRST WORD OF THE WSA BUFFER 
                   WILL CONTAIN THE CURRENT PRU POSITION OF THE FILE. 
  
              50:  PRU OUTPUT ABORTED.
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED AN OFC/ABT/N SUPERVISORY
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   OF THE CONNECTION IN WHICH PRU TRAFFIC HAS BEEN
                   ABORTED.  THE STATE OF THE CONNECTION WILL HAVE BEEN 
                   CHANGED TO THE WAITING-FOR-END-OF-OUTPUT-JOB STATE 
                   (STATE 24).  TO GET THIS RETURN CODE, THE
                   APPLICATION PROGRAM MUST HAD PREVIOUSLY CALLED QTSUP 
                   WITH SMC = 21.  THE FIRST WORD OF THE WSA BUFFER 
                   WILL CONTAIN THE ACCOUNTING DATA FOR THE FILE.  THE
                   SECOND WORD OF THE WSA BUFFER WILL CONTAIN THE LFN 
                   AND FNT ORDINAL OF THE FILE WHOSE OUTPUT WAS 
                   ABORTED.  THE LFN WILL BE IN THE LEFTMOST 42 BITS OF 
                   THE WORD AND THE FNT ORDINAL WILL BE IN THE
                   RIGHTMOST 18 BITS. 
  
              51:  PRU OUTPUT TRANSFER ENDED. 
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED AN OFC/EOO SUPERVISORY
                   MESSAGE FROM THE NETWORK.  THE CONNECTION-NUMBER 
                   FIELD IN THE NIT WILL CONTAIN THE CONNECTION NUMBER
                   OF THE CONNECTION IN WHICH PRU TRAFFIC HAS ENDED.
                   THE STATE OF THE CONNECTION WILL HAVE BEEN CHANGED 
                   TO THE WAITING-FOR-END-OF-OUTPUT-JOB STATE (STATE
                   23) THE FIRST WORD OF THE WSA BUFFER WILL CONTAIN
                   THE ACCOUNTING DATA FOR THE FILE.  THE SECOND WORD 
                   OF THE WSA BUFFER WILL CONTAIN THE LFN AND FNT 
                   ORDINAL OF THE FILE WHOSE OUTPUT HAS ENDED.  THE LFN 
                   WILL BE IN THE LEFTMOST 42 BITS OF THE WORD AND THE
                   FNT ORDINAL WILL BE IN THE RIGHTMOST 18 BITS.
  
              52:  PRU OUTPUT JOB FINISHED. 
  
                   THIS RETURN CODE IS GENERATED IN RESPONSE TO A QTGET 
                   CALL.  QTRM HAS RECEIVED AN OFC/EOO OR OFC/DATA/N
                   SUPERVISORY MESSAGE FROM THE NETWORK.  THE 
                   CONNECTION-NUMBER FIELD IN THE NIT WILL CONTAIN THE
                   CONNECTION NUMBER OF THE CONNECTION IN WHICH THE PRU 
                   OUTPUT JOB HAS FINISHED.  THE STATE OF THE 
                   CONNECTION WILL HAVE BEEN CHANGED TO THE 
                   INITIAL-PRU-CONNECTION STATE (STATE 17). 
  
          THREE NEW SECONDARY RETURN CODES HAVE BEEN ADDED TO THE NIT.
          THE FIRST TWO ARE ERROR RESPONSES TO QTSUP SMC = 14 CALLS.
          THE THIRD ONE IS AN ERROR RESPONSE TO QTCMD CC = 13 CALL. 
  
              27:  QTSUP REJECTED THE CALL BECAUSE PRU INTERFACE IS 
                   NOT SUPPORTED ON THE CONNECTION THAT WAS SPECIFIED;
                   I.E. THE DEVICE TYPE FOR THE SPECIFIED CONNECTION
                   WAS EITHER 0 OR 5. 
  
              28:  QTSUP REJECTED THE CALL BECAUSE AN INVALID PRU BUFFER
                   SIZE WAS SPECIFIED IN THE PARM-FLAG1 FIELD OF THE
                   NIT; I.E. THE VALUE SPECIFIED WAS NOT 1, 2, OR 3.
  
              29:  QTCMD REJECTED THE CALL BECAUSE AN UNKNOWN CONVERSION
                   CODE WAS SPECIFIED IN THE QTCMD CALL.
  
          EIGHT NEW CONNECTION STATES HAVE BEEN ADDED TO THE NIT. 
          THEY ARE AS FOLLOWS:  
  
              15:  THIS CONNECTION IS CURRENTLY IN A TRANSITION STATE 
                   WHILE A NEW CONNECTION IS BEING CONVERTED INTO A 
                   PRU CONNECTION.  QTRM IS WAITING FOR THE NORMAL
                   RESPONSE TO THE PRU/ON SUPERVISORY MESSAGE.  NO
                   OTHER INFORMATION IN THE ASSOCIATED 10-WORD ENTRY
                   FOR THIS CONNECTION SHOULD BE CONSIDERED ACCURATE. 
  
              16:  THIS CONNECTION IS CURRENTLY IN A TRANSITION STATE 
                   WHILE IT IS BEING CONVERTED INTO A PRU CONNECTION. 
                   QTRM IS WAITING FOR THE NORMAL RESPONSE TO A PRU/ON
                   SUPERVISORY MESSAGE. 
  
              17:  THIS CONNECTION IS IN THE INITIAL PRU CONNECTION 
                   STATE.  NO OUTPUT TRANSFER IS OCCURING AT THIS 
                   TIME.
  
              18:  THIS CONNECTION IS IN THE ACTIVE PRU CONNECTION
                   STATE.  AN OUTPUT FILE IS CURRENTLY BEING TRANSFERRED
                   BY PIP TO THE NETWORK. 
  
              19:  THIS CONNECTION IS IN THE PROCESS OF STOPPING THE
                   TRANSFER OF THE OUTPUT FILE.  THE APPLICATION PROGRAM
                   HAS REQUESTED THE SUSPENSION OF THE OUTPUT FILE
                   TRANSFER AND IS WAITING FOR THE RESPONSE.
  
              20:  THIS CONNECTION IS IN THE PROCESS OF ABORTING THE
                   TRANSFER OF THE OUTPUT FILE.  THE APPLICATION PROGRAM
                   HAS REQUESTED THE TERMINATION OF THE OUTPUT FILE 
                   TRANSFER AND IS WAITING FOR THE RESPONSE.
  
              21:  THIS CONNECTION IS IN THE PRU-TRANSFER-STOPPED-BY- 
                   APPLICATION STATE. 
  
              22:  THIS CONNECTION IS IN THE PRU-TRANSFER-STOPPED-BY- 
                   NETWORK STATE. 
  
              23:  THIS CONNECTION IS IN THE PRU-TRANSFER-STOPPED-BY- 
                   PIP STATE. 
  
              24:  THIS CONNECTION IS IN THE WAITING-FOR-END-OF-JOB 
                   STATE.  THE OUTPUT FILE TRANSFER HAS TERMINATED
                   AND THE APPLICATION PROGRAM IS WAITING FOR THE 
                   END OF OUTPUT JOB INDICATION.
  
          EG     09/06/86    AIPDEF, QTRMBUF, QTRMCOM, QTRMNIT, 
                             QTCMD, QTGET, QTLINK, QTOPEN, QTPUT, QTSUP 
 FN5222  THIS CODE IMPLEMENTS THE NECCESSARY CHANGES IN NVF, AS DES-
         CRIBED IN DAP S5222, TO SUPPORT THE 585 PRINTER CONNECTED
         THRU CDCNET. 
  
         NOTE : THIS CODE CAN BE TRANSMITTED WITH NO DEPENDENCY.
  
         TET    09/25/86    MISCOM, TXTANVF, NVFTACC, NVFTDSP,
                            NVFTITE, NVFTSPC, NVFIAST, NVFTETC, 
                            NVFTRCN, NVFTURL, NVFTDAD.
 FN5222A  MODIFY NIP TO SUPPORT HIGH SPEED PSU PRINTERS ON CDCNET AS
          DOCUMENTED IN DAP S5222.
  
          NAM HAS BEEN MODIFIED TO SUPPORT NEW DEVICE TYPE 7 AND NEW
          OS/NVFU SUPERVISORY MESSAGE.
          EG     10/14/86    NPPCT, PIP, SMDEF, SMPFC 
 FN607C    THIS IS THE NECESSARY COLLECT CODE TO SUPPORT FEATURE
           FN607 WHICH CHANGES ALL CDCNET APPLICATIONS TO ACCESS
           THE NETDIR FROM THE ACCOUNT THEY ARE RUNNING.
  
           TET    10/06/86     COLLECT
 FS21001  IMPLEMENTING LINE SPEED OF UP TO 38400 KPS. 
  
          PROBLEM: NDLP SHOULD PROCESS UP TO 38400 KPS
                   LINE SPEED AND TERMINAL SPEED. 
  
          SOLUTION: APPROPRIATE ENTRIES ARE ADDED TO
                    PROCESS 19200 AND 38400 LINES SPEED 
                    AND TERMINAL SPEED. NDLLIST WAS ALSO
                    MODIFIED TO PRINT THOSE NEW LINESPEEDS AND
                    TERMINAL SPEEDS.
  
          YCY 86/09/02    NDL 
  
 FS5200    THIS IS THE NVF CODE TO IMPLEMENT THE "NO CURSOR POSITIONING"
           FEATURE AS DESCLIBED IN DAP S5200. 
  
           DEPENDENCIES:  
              THIS CODE NEED ACCOMPANIED CODE IN BOTH CCP AND CDCNET. 
           THE CCP CODE IS TRANSMITTED WITH THE SAME ID (FS5200). 
           THE CDCNET CODE IS TRANSMITTED UNDER PSR AC1D937.
  
           TET    27/01/87    HEADER, TEXTNVF, TXTANVF, NVFCPUT,
                              NVFTILP, NVFTETI, NVFTVVD, TMSGNVF. 
 NA5B021 PROBLEM  - WHEN NAMI PROCESSED RN PARAMETER, IT DID NOT
                    CHECK TO SEE IF THE PARAMETER RECORD NAME ENTERED 
                    IS AN EXISTING PARAM RECORD NAME. THEREFORE WHEN
                    THE OPERATOR TYPED IN A NON-EXISTING NAME FOR RN, 
                    NAMI UPDATED THE MEMORY FILE WITH THE BAD NAME. 
                    THIS DISALLOWED NAMI TO DO ANY FURTHER NORMAL 
                    OPERATION UNTIL THE RN NAME WAS CORRECTED.
  
         SOLUTION - CHANGED NAMI TO CHECK FOR THE EXISTENCE OF THE
                    PARAM RECORD NAME ENTERED. THE MEMORY FILE IS 
                    CHANGED ONLY WHEN NAMI GETS AN EXISTING PARAM 
                    RECORD NAME FOR RN. 
  
         TET    07/22/86    NAMI
 NA5B618  DUPLICATE APPLICATION NAMES APPEAR
          ON THE NAM ALERT LINE.
  
          PROBLEM: TWO CS NAMES WERE FOUND TO APPEAR
                   ON THE NAM ALERT LINE. 
  
          ANALYSIS: CS PREVIOUSLY FAILED BUT NIP DID NOT
                    CLEAR THE ALERT LINE BUFFER FOR THE 
                    APPLICATION NAME THAT FAILED. 
  
          SOLUTION: CODE IS ADDED TO HAPFAIL SUCH THAT
                    IT CLEARS THE NAME OF THE APPLICATION 
                    THAT FAILED FROM THE ALERT BUFFER.
  
          YCY     86/08/05     HAPFAIL
 NA5B643 PROBLEM  - NVFARAP REJECTED X.25 A-A CONNECTION BECAUSE
                    THE PSN (TELENET) HAD INSERTED "THROUGHPUT
                    NEGOTIATION" IN THE FACILITY FIELD. 
  
         ANALYSIS - WHEN NVF RECEIVES A CR/RAP/R WITH SOME NON- 
                    RESERVED FACILITIES, IT COMPARES THEM WITH
                    THOSE DECLARED IN INCALL STATEMENTS. WHEN 
                    NDLP PROCESSES A INCALL STATEMENT, IT PLACES
                    THE PARAMETER VALUES STARTING AT BIT POSITION 
                    16 OR 24 OF THE CORRESPONDING WORD OF THE COR-
                    RESPONDING INCALL BLOCK. THE STARTING BIT PO- 
                    SITION DEPENDS ON WHETHER THE PARAMETER FIELD 
                    HAS FIXED, OR VARIABLE LENGTH.
                    FOR FIXED LENGTH PARAMETER, THE STARTING POSITION IS
                    16; FOR VARIABLE LENGTH, IT IS 24. THE OLD NVF CODE 
                    ALWAYS ASSUMED THE PARAMETER AT POSTION 24, AND 
                    THEREFORE, IN CASE OF FIXED LENGTH PARAMETERS, IT 
                    DID NOT PICK UP THE RIGHT VALUE.
  
         SOLUTION - CHANGE NVFARAP TO PICK UP VALUE AT LOCATION 
                    16 OR 24, DEPENDING ON WHETHER IT IS FIXED
                    OR VARIABLE LENGTH. 
         TET    06/23/86    NVFARAP 
 NA5B651  PROBLEM  - WHEN THE USER EXECUTED THE APPSW COMMAND WITH
                     A NON-EXISTING SECONDARY APPLICATION NAME, NVF 
                     RETURNS A CR/RCN/A WITH RC=20.  REASON CODE 20 
                     IS ALSO USED IN THE CASE WHEN THE SECONDARY
                     APPLICATION DOES EXIST BUT THE USER IS NOT 
                     VALIDATED TO USE IT.  THIS CAUSES IAF TO ISSUE 
                     THE MESSAGE **USER NOT VALID FOR 2ND APPLICATION** 
                     WHEN THE USER SPECIFY AN NON-EXISTING APPLICATION. 
  
          SOLUTION - CREATE A NEW REASON CODE RC=23B FOR CR/CRN/A.
                     RC=20B MEANS *USER NOT VALID FOR SECONDARY APPL.*
                     AS USUAL, WHILE RC=23B MEANS *SECONDARY APPLICATION
                     NAME INVALID*
  
          TET    05/02/86    SMDEF, NVFTVAA 
 NA5B672  DLFP LOOPS ON BAD INPUT FILE. 
  
          PROBLEM: WHEN THE OUTPUT OF DLFP IS USED AS THE 
                   INPUT TO THE SAME DLFP PROCESS, DLFP 
                   LOOPS. 
  
          ANALYSIS: DLFP SHOULD VALIDATE THE HEADER.
                    CURRENTLY, DLPF ONLY READS IN A 4 WORD
                    HEADER AND VALIDATES IT FOR THE LENGTH BUT
                    NOT THE TEXT. THE HEADER OF THE ZZZZZDN FILE
                    MUST CONTAIN A VALID LEFT JUSTIFIED 7 CHARACTER 
                    APPLICATION NAME. 
  
          SOLUTION: WHEN DLFP READS THE HEADER FROM THE INPUT 
                    FILE, IT CHECKS IF THE APPLICATION NAME 
                    IS ALL BLANKS AND IF IT IS IT ABORTS WITH 
                    THE MESSAGE "BAD DEBUG LOG FILE". 
  
          YCY 86/05/22    NIP 
  
 NA5B674  THIS PSR FIXES THE PROBLEM THAT NAM VALIDATES 
          THE ACN FIELD OF THE HOPALT SUPERVISORY MESSAGE.
          AN ERRLGL WITH REASON CODE 4 (BAD ACN FIELD) IS 
          RETURNED TO THE APPLICATION THAT SENDS THE HOPALT MESSAGE.
          HOWVER, THE HOST APPLICATIONS PROGRAMMING REFERENCE 
          MANUAL SPECIFIES THAT THE ACN FIELD OF THE ALT MESSAGE
          IS RESERVED. CODE IN HPPUT IS CHANGED SUCH THAT 
          NO ACN VALIDATION IS DONE FOR ALL HOP MESSAGES. 
          YCY     86/05/23     HPPUT
 NA5B679  PROBLEM  - NAM ABORTED WITH DAYFILE MESSAGE 'NO INTERLOCK'. 
          ANALYSIS - THERE WERE TWO MDIS IN THE EST TABLE WITH THE SAME 
                     CHANNEL NUMBER.  EACH OF THESE MDIS WAS TO BE
                     DRIVEN BY A DIFFERENT PIP.  SINCE 2 PIPS CANNOT
                     SHARE THE SAME CHANNEL, ONE OF THEM MUST HAVE HUNG.
                     WHEN NIP DETECTED ONE OF THE PIPS NOT RESPONDING 
                     TO AN INTERLOCK REQUEST, IT ABORTED. 
          SOLUTION - PIP HAS BEEN CORRECTED TO CHECK THE CHANNEL AND
                     EQUIPMENT NUMBERS WHENEVER IT DETECTS A NPU/MDI
                     EST ENTRY THAT HAS BEEN TURNED ON.  IF THE CHANNEL 
                     NUMBER MATCHES A PREVIOUS ENTRY THAT IS ALREADY
                     TURNED ON AND DRIVEN BY A DIFFERENT PIP, PIP WILL
                     ISSUE AN INFORMATIVE DAYFILE MESSAGE AND TURN OFF
                     THE BAD EST ENTRY.  IF THE CHANNEL AND EQUIPMENT 
                     NUMBERS MATCH A PREVIOUS ENTRY THAT IS ALREADY 
                     TURNED ON AND DRIVEN BY THE SAME PIP, THEN PIP 
                     WILL ALSO AGAIN ISSUE AN INFORMATIVE DAYFILE 
                     MESSAGE AND TURN OFF THE BAD EST ENTRY (WE HAVE
                     TWO EST ENTRIES FOR THE SAME FRONT END). 
          EG     86/06/03    PIP
 FN6901   INLINE DIAGNOSTICS CODE FOR PIP AND NIP.
          SW/EG  08/20/86    PIP
          YCY    05/04/86    NPININD, NBT, XCHKPCR, XEXEC 
 NA5B687 PROBLEM  - TWO PROBLEMS FOUND IN NVFTRCN WHEN IT PROCESS 
                    THE LIMBO CASE. 
                    1. MODS FS4563B (LINE 565 THRU 577) ADDED CODES 
                       TO SAVE THE VOLUNTEERED APPL NAME, BUT THE 
                       CODES REFER TO AN UNDEFINED VARIABLE "PT". 
                    2. MOD NA5B464 (LINE 21 THRU LINE 41) AND MOD 
                       NA5B473 (LINE 35 THRU LINE 51) DUPLICATE 
                       EACH OTHER.
  
         SOLUTION - 1. MOVE MODS FS4563B (LINE 565 THRU 577) FURTHER
                       DOWN SO THE CODE WILL BE EXECUTED AFTER "PT" 
                       IS DEFINED.
                    2. DELETE ONE COPY OF THE (TWO) DUPLICATED CODES. 
  
         TET    06/13/86    NVFTRCN 
 NA5B691  NDLP DOES NOT INTERPRET A 12 DIGIT FACILITY CODE
          CORRECTLY.
  
          PROBLEM: WHEN NDLP INTERPRETS A 12 DIGIT FACILITY 
                   CODE, IT DISCARDS THE 12TH MOST SIGNIFICANT
                   DIGIT. 
  
          ANALYSIS: IN ROUTINE CHKHEX OF NDLPSS1, THERE IS
                    A CHECK FOR ALLOWING UP TO AND INCLUDING
                    THE 11TH HEX DIGIT IF THE 11TH HEX DIGIT
                    IS BETWEEN A-F. A 60 BIT UNSIGNED INTEGER 
                    CAN PHYSICALLY STORE UP TO 15 HEX DIGITS. 
                    BUT,LEGALLY, A FACILITY CODE CAN HAVE UP
                    UP TO A MAXIMUM OF 12 HEX DIGITS. 
  
         SOLUTION:  ROUTINE CHKHEX IS CHANGED SUCH THAT IT
                    CAN ACCEPT UP TO 12 HEX DIGITS WHOSE
                    VALUES ARE BETWEEN 0 AND F. 
  
 NA5B705  ASSIGNING A RETURN CODE FOR SYCHRONOUS
          SUPERVISORY MESSAGE THAT AN APPLICATION 
          PROGRAM OBTAINS FROM A QTGET CALL.
  
          PROBLEM: CDCHELP AND SOLVER HAVE A PROBLEM
                   WITH THE SYNCHRONOUS SUPERVISORY 
                   MESSAGE RETURNED WITH THE SAME 
                   RETURN CODE OF A REGULAR DATA
                   MESSAGE. 
  
          ANALYSIS: QTRM ALREADY HAS REASON CODE 28 
                    ASSIGNED FOR BI/MARK/R. BUT ANY 
                    OTHER SYCHRONOUS SUPERVISORY
                    MESSAGE IS RETURNED WITH REASON 
                    CODE 0. 
  
          SOLUTION: QTRM NOW ASSIGNS REASON CODE 29 TO ANY
                    SYNCHRONOUS SUPERVISORY MESSAGE OTHER 
                    THAN A BI/MARK/R RECEIVED VIA A QTGET 
                    CALL. REASON CODE 28 IS STILL RESERVED FOR
                    BI/MARK/R SINCE SPECIAL ACTION HAS TO BE
                    TAKEN, WHEREAS IN THE CASE OF REASON CODE 29, 
                    NO EXTRA ACTION HAS TO BE TAKEN BY THE
                    APPLICATION PROGRAM.
          YCY 86/07/30    AIP 
 NA5B708  PROBLEM  - USER-BREAK-2 ENTERED DURING MFLINK HUNG TERMINAL 
                     FOR 3 MINUTES. 
  
          ANALYSIS - THIS PROBLEM IS CLOSELY RELATED TO THAT OF 
                     NA5B664 WHICH FIXED AN "NVF ABORT" PROBLEM.
                     NVF ABORTED IN THAT PROBLEM BECAUSE A CRTRM
                     HAD REACHED NIP BEFORE THE CRRAPN DID (SEE HIS-
                     TORY OF NA5B664). THE CRRAPN WAS SLOWER BECAUSE
                     IT HAD TO GO THRU THE CTQ WHILE THE CRTRM DIDN'T.
                     NA5B664 FIXED THE PROBLEM BY NOT SENDING OUT 
                     A CRTRM IF THE CONNECTION IS IN "CREATE" STATE 
                     (CRRAPN HAS NOT GONE OUT YET). SINCE CRTRM WAS NOT 
                     SENT, THE CONNECTION WOULD NOT BE TERMINATED 
                     UNTIL LATER ON WHEN SOME OTHER SM'S (FC/INIT,
                     CR/SWH, CR/RCN) HAD BEEN PROCESSED. THIS PROCESS,
                     IN SOME CASES, CAN TAKE AS LONG AS 2, 3 MINUTES. 
  
          SOLUTION - THE OBJECTIVE IS TO TERMINATE THE CONNECTION AS
                     SOON AS WE HAVE TO (IN THIS CASE WHEN THE APPL 
                     FAILS), AND ALSO TO ASSURE THAT CRRAPN OR CRIAPN,
                     IF ANY, MUST REACH NIP BEFORE THE CRTRM DOES.
                     WE CHOOSE TO ACHIEVE THIS BY LETTING THE CRIAPN
                     AND CRRAPN BYPASS THE CTQ AS THE CRTRM DID.
  
          TET    07/25/86    NVFARAP, NVAAIAP, NVFAFAI, NVFAVVD 
 NA5B710  PROBLEM  - NIP ABORTED WITH THE DAYFILE MESSAGE 'NIP A-A
                     NETWORK PROTOCOL VIOLATION.' 
          ANALYSIS - NIP RECEIVED A NIP/PP SUPERVISORY MESSAGE FROM 
                     PIP RUNNING ON ANOTHER HOST.  THE DEBUG VERSION
                     OF NIP ABORTS WHEN IT RECEIVES THIS SUPERVISORY
                     MESSAGE.  THE PIP ON THE OTHER HOST SENT THIS
                     SUPERVISORY MESSAGE BECAUSE IT THOUGHT THE PIP 
                     ON THIS HOST HAD VIOLATED THE A-A PROTOCOL 
                     UNFORTUNATELY THERE IS NO ENOUGH INFORMATION TO
                     DETERMINE WHAT THE PIP ON THIS HOST DID WRONG. 
          SOLUTION - NIP HAS BEEN CHANGED TO DUMP ITS FIELD LENGTH
                     WHEN THIS SITUATION OCCURS IRREGARDLESS OF 
                     WHETHER IT IS A DEBUG OR NONDEBUG VERSION OF 
                     NIP.  PIP HAS BEEN CORRECTED TO INCLUDE MUCH 
                     MORE INFORMATION IN THE NPI/PP SUPERVISORY 
                     MESSAGE SO THAT WE CAN FIGURE OUT WHAT IT WAS
                     DOING WRONG.  NIP HAS BEEN CORRECTED TO INCLUDE
                     INFORMATION IN THE NPI/DD SUPERVISORY MESSAGE. 
          EG     10/10/86    NBSTTP, NCSTTP, NNPIIN, NPNPIDP, PIP,
                             SKENIP, SMDEF, SMNIP 
 FN7187   IMPLEMENT NEW CDCNET COUPLER NODE VERIFICATION INTERFACE AS 
          DOCUMENTED IN DAP ARH7197.
  
            1.  PIP SAVES THE MDI NODE NUMBER IN CET TABLE FOR NIP. 
            2.  WHEN PIP FIRST TALKS TO THE MDI,
                PIP WILL READ UP THE DETAILED STATUS TO CHECK THE 
                CHANNEL PROTOCOL VERSION SUPPORTED BY THE MCI.  THE MCI 
                SHOULD HAVE STORED THE NUMBER OF THE HIGHEST CHANNEL
                PROTOCOL VERSION THAT IT SUPPORTS IN THE FIRST BYTE OF
                THE DETAILED STATUS.  IF THIS VALUE IS ZERO, THEN THE 
                MCI IS ASSUMED TO SUPPORT ONLY VERSION 0 OF THE CHANNEL 
                PROTOCOL.  THIS ALSO MEANS THE MCI DOES NOT SUPPORT THE 
                SET PROTOCOL VERSION FUNCTION.  IF THE VALUE IS 
                NONZERO, THEN PIP MUST NEGOTIATE WITH THE MCI TO FIND 
                THE HIGHEST VERSION OF THE CHANNEL PROTOCOL VERSION 
                THAT IS SUPPORTED BY BOTH.  IF THE CHANNEL PROTOCOL 
                VERSION FROM THE DETAILED STATUS IS LESS THAN THE 
                MINIMUM CHANNEL PROTOCOL VERSION SUPPORTED BY PIP, THEN 
                THERE IS NO COMMON CHANNEL PROTOCOL VERSION SUPPORTED 
                BY BOTH.  IF THIS IS THE CASE, PIP SENDS A DAYFILE
                MESSAGE WORKLIST TO NIP AND SETS A 5 MINUTE TIMER.
                AFTER THE TIMER EXPIRES, PIP WILL CHECK THE MCI CHANNEL 
                PROTOCOL VERSION AGAIN.  IF THE MCI CHANNEL PROTOCOL
                VERSION IS GREATER THAN OR EQUAL TO THE MINIMUM CHANNEL 
                PROTOCOL VERSION SUPPORTED BY PIP, THEN PIP WILL NEED 
                TO ISSUE A SET PROTOCOL VERSION FUNCTION TO INFORM THE
                MCI THE HIGHEST CHANNEL PROTOCOL VERSION THAT IS
                SUPPORTED BY PIP AND LESS THAN THE CHANNEL PROTOCOL 
                VERSION THAT WAS SPECIFIED IN THE DETAILED STATUS.
                AFTER ISSUING THE SET PROTOCOL VERSION FUNCTION, PIP
                WILL READ UP THE DETAILED STATUS AGAIN.  IF THE CHANNEL 
                PROTOCOL VERSION IN THE DETAILED STATUS MATCHES THE ONE 
                THAT PIP SENT IN THE SET PROTOCOL VERSION FUNCTION, 
                THEN A COMMON CHANNEL PROTOCOL EXISTS BETWEEN PIP AND 
                THE MCI.  IF THE VERSION NUMBERS DO NOT MATCH, THEN 
                THERE IS NO COMMON CHANNEL PROTOCOL AND PIP AND THE MCI 
                CANNOT COMMUNICATE WITH EACH OTHER. 
  
          ENHANCE NIP DAYFILE MESSAGE PROCESSING WITH NEW ERROR MESSAGES
          EG     12/03/86    BLDLLCB, CET, HPPUT, IMSCET, 
                             IMSLLCB, IMSNBT, LLCB, MISDEF, 
                             NBSTTP, NBT, NEIB, NEIB1, NGIGO, NPPCT,
                             NPPSM, NPPWL, NRPWL, NPREGLL, ODAYFL,
                             PT, SKENIP, SMDEF, SMNIP, XCHKCET, XCHKPCR,
                             XEXEC, PIP 
 FS5148   MODIFICATION OF PIP TO IMPROVE THROUGHPUT SPECIFICALLY FOR
          PACKED EIGHT-BIT TRAFFIC ON AN MDI. THIS FEATURE IS DEPENDENT 
          UPON COMPANION CDCNET CODE, AND CHANNEL PROTOCOL VERSION 2
          MUST BE IN EFFECT FOR THE IMPROVEMENT, ALTHOUGH LOWER VERSIONS
          ARE SUPPORTED.
  
          CMP 12/86     PIP 
  
 FN7464   ENHANCE PIP TO PROCESS THE MODIFIED FORMAT OF THE EST 
          ENTRIES AS DOCUMENTED IN DAP A7464. 
  
          THIS CODE CAN BE APPLIED ONLY AGAINST A 21F2 OR LATER 
          NAMPL.
  
          EG     01/08/87    PIP
 NA5B715 PROBLEM  - NAMI SPENT TOO MUCH TIME PROCESSING THE NAMSTRT 
                    FILE. 
  
         ANALYSIS - 1. NAMI USED A 1-PRU CIO BUFFER TO READ THE NAMSTRT 
                       FILE. SINCE EVERY RECORD IN THE NAMSTRT FILE 
                       CONSISTS OF MANY PRUS, THE BUFFER SIZE SHOULD BE 
                       INCREASE TO REDUCE THE NUMBER OF RA+1 CALLS. 
                    2. NAMI HAS TO GO THROUGH THE NAMSTRT FILE NAMY 
                       TIME, ONCE FOR THE PARAMETER RECORD, AND ONCE FOR
                       EACH JOB IN THE PARAMETER RECORD. IT'S MORE
                       DESIRABLE TO HAVE NAMI SET UP A DIRECTORY DURING 
                       THE FIRST SCAN TO REMEMBER THE RELATIVE ADDRESS
                       OF EACH JOB RECORD, SO THAT NAMI CAN ISSUE RAN-
                       DOM READ REQUESTS TO OBTAIN THE RECORDS IT WANTS.
  
         SOLUTION - 1. THE CIO BUFFER IS INCREASED TO 16 PRU + 1. 
                    2. CODE IS ADDED TO HAVE NAMI SET UP A DIRECTORY
                       TABLE FOR THE RELATIVE ADDRESS OF EACH RECORD, 
                       AND ISSUE RANDOM, INSTEAD OF SEQUENTIAL, READ
                       REQUESTS.
  
         TET    08/15/86    NAMI, NMI=IO1 
 NA5B679  PROBLEM  - PIP HUNG WHEN NETWORK WAS TAKEN DOWN WITH DI,HO
                     COMMAND. 
          ANALYSIS - PIP WAS IN A LOOP WAITING FOR NIP TO DECREMENT THE 
                     COUNT OF ACTIVE PRU BUFFERS.  NIP HAD ALREADY
                     STOPPED EXECUTING SO THERE WAS NO ONE TO DECREMENT 
                     THE COUNT OF ACTIVE PRU BUFFERS. 
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT WAIT FOR NIP TO
                     DECREMENT THE COUNT OF ACTIVE PRU BUFFERS IF 
                     THE NETWORK IS IN A SHUTDOWN STATE.
          EG     86/08/19    PIP
 NA5B718 PROBLEM  - THE CC (CHARACTER COUNT) FIELD IN THE N HEADER
                    OF THE ICNAP IS NOT ALWAYS CORRECT. 
  
         ANALYSIS - WHEN NVF SENDS NIP A CRIAPN, THE TLC FIELD IN THE 
                    HEADER CONTAINS THE LENGTH OF THE SM IN WORDS.
                    NIP CONVERTS THE CRIAPN INTO A ICNAP. TO OBTAIN 
                    THE CHARACTER COUNT FOR THE ICNAP, NIP MULTIPLIES 
                    THE TLC BY 7.5 (1 WORD = 7.5 OCTETS).  WHEN 
                    THE ACTUAL LENGTH OF THE CRIAPN IS NOT AN EXACT 
                    MULTIPLE OF WORDS, NVF ROUNDS THE TLC FIELD UP, 
                    AND MULTIPLYING TLC BY 7.5 WILL RESULT A NUMBER 
                    THAT IS GREATER THAN THE ACTUAL CHARACTER COUNT 
                    FOR THE PACKET. 
  
         SOLUTION - THE CRIAPN SM IS CHANGED TO INCLUDE A NEW FIELD,
                    CRIOCTN (NUMBER OF OCTETS), WHICH CONTAINS THE
                    EXACT COUNT OF OCTETS FOR THE CRIAPN. NIP WILL
                    USE THE NUMBER AS IT; NO CONVERSION IS NEEDED.
                    THE NEW FIELD SHARES THE SAME SPACE WITH THE RC 
                    FIELD. THIS IS FINE BECAUSE RC FIELD IS NOT USED
                    BY THE CRIAPN.
  
         YIU, TET    SMNVF, NVFAIAP, PT, NICNAPX, HCSTTP
 NA5B724 PROBLEM  - NAMI ABORT WHEN NAMSTRT FILE IS NOT PRESENT.
         SOLUTION - A CHECK HAS BEEN INCLUDED TO CHECK FOR ERRORS 
                    AFTER THE ATEMPT TO GET THE FILE. THE PROGRAM 
                    ONLY PROCEEDS TO READ THE FILE IF THE GET WAS 
                    OK. OTHERWISE, LET THE OPERATOR HV THE OPERATOR 
                    HAS A CHANCE TO CORRECT THE FILE NAME.     IES
                    GET THE FILE AGAIN. 
         TET    09/10/86     NAMI 
 NA5B726 PROBLEM  - NVF ABORTED BECAUSE IT COULD NOT FIND PCDT ENTRY
                    FOR SOME CONNECTION.
  
         ANALYSIS - A TERMINAL, WHILE CONNECTED TO IAF (THRU CDCNET)
                    ERRORNEOUSLY  CHANGED ITS TERNIMAL CLASS
                    FROM TC=3 TO TC=9. THE CONNECTION WAS THEN BROKEN.
                    WHEN NVF PROCESSED THE CR/CB, IT TRIED TO DELETE
                    THE PCDT ENTRY FOR THIS CONNECTION, AND ABORTED 
                    BECAUSE IT COULD NOT FIND ONE.
                    NOTE : PCDT ENTRY ONLY EXISTS FOR SYNCHRONOUS 
                    TERMINALS. SINCE THE CONNECTION WAS ESTABLISHED 
                    AS TERMINAL CLASS TC=3. NO PCDT ENTRY HAD BEEN
                    CREATED.
  
         SOLUTION - THEORETICALLY, A TERMINAL CLASS SHOULD NOT GET
                    CHANGED FROM AN ASYNC. TYPE TO A SYNCHRONEOUS 
                    ONE. HOWEVER, NVF SHOULD BE ABLE TO PROTECT ITSELF
                    IN CASE THIS DOES HAPPEN BECAUSE OF ERRORS FROM 
                    OTHER COMPONENTS OF THE NETWORK.
                       CODE HAS BEEN ADDED TO NVF SO THAT IT WILL 
                    REUSE THE ORIGINAL TERMINAL CLASS, FROM VCB FILE, 
                    WHEN IT PROCESSES THE CR/CB, TO AVOID THE SEARCH
                    FOR THE PDCT ENTRY IN CASE THE TERMINAL CLASS HAS 
                    BEEN CHANGED ERRONEOUSLY. 
  
         TET    09/19/86    NVFTRVD 
 NA5B728  NDLP CREATES A BAD NCB WHICH CAUSES A HALT 12 IN CCP
          THERE IS A BAD LOOP IN THE CREATION OF THE SUPERVISION
          TABLE OF THE NCB WHICH IF A NODE NUMBER MATCHES DATA
          OUT OF THE VALID RANGE OF AN INTERNAL TABLE A BAD 
          SUPERVISORY LINK IS CREATED.  THIS CODE FIXS THE LOOP 
          TO PROCESS WITHIN THE VALID RESTRICTIONS
          JDA     86/09/19     NDLNFTM
 NA5B730 PROBLEM  - IF A LOANED CONNECTION GETS BROKEN , THE ACN DID NOT
                    GET RE-USED . 
         ANALYSIS - WHEN NIP SENDS CON/CB/U TO PRIMARY APPLICATION, NIP 
                    SHOULD CLEAN UP THE ACNT TABLE. 
         LTN    09/26/86    HCONCBU 
  
 NA5B731   PROBLEM: -  TWO CON/CB/U WERE SENT TO IAF WHEN CONNECTION
                       IS BEING SWITCHED BACK TO PRIMARY APPLICATION
                       AND THE NETWORK BREAKS THE CONNECTION. 
  
           ANALYSIS: - NIP WILL SEND ONLY CR/CB/U TO NVF WHEN NWTC
                       COMING IN FROM THE NETWORK, IT WILL NOT SEND 
                       CON/CB/U TO APPLICATION IF THE CONNECTION IS 
                       IN STATE 5, WHICH IS WAITING FOR CON/REQ/N.
                       CON/CB/U WILL BE SENT TO APPLICATION WHEN
                       CON/REQ/N RESPONSE COMES FROM APPLICATION. 
  
           LTN         86/10/01       HCONCBU 
  
 NA5B735  PROBLEM:  
          PIP RECEIVED A LEVEL-7 Q-MSG SENT TO INDICATE AN ERROR
          CONDITION THAT WAS DETECTED BY THE SENDER (IN THIS CASE 
          APOLLO). THE MESSAGE CAUSED A STREAM STATE RESPONSE WITH
          ORDINAL <.SRAQ> TO BE EXECUTED. THIS RESULTED IN THE ERROR 76.
          THIS WILL OCCUR IN STREAM STATE 2 OR 9. 
          SOLUTION: 
          THE APPROPRIATE STATE RESPONSE TABLES WILL BE ALTERED VIZ - 
          PIP WILL SEND THE RECEIVED Q-MSG BLOCK ONTO THE APPLICATION AS
          AN ERROR WORKLIST. IT WILL THEN GO TO STATE 61 TO WAIT FOR AN 
          IMMEDIATE WORKLIST PRIOR TO TERMINATING THE CONNECTION. 
  
          CMP 01/26/87       PIP
  
   NA5B736  PROBLEM - NVF SHOULD NOT HANG DURING USER LOGIN WHEN FAMILY 
                      PACK UNAVAILABLE. 
  
           SOLUTION - CODE IS ADDED TO NVF SO THAT WHENEVER THE 
                      LOGIN FAMILY PACK IS NOT AVAILABLE, A NEW 
                      MESSAGE SAYING " FAMILY NOT AVAILABLE .." 
                      WILL BE ISSUED BY NVF TO THE USER.
  
           J. YANG  02/11/87   TXTANVF,TEXTNVF,NVFTPVR,TMSGNVF,NVFTVVD
 NA5B738  PROBLEM  - NIP IS NOT RELEASING THE MCI INLINE DIAGNOSTICS
                     BUFFER.  THIS PREVENTS PIP FROM BEING ABLE TO
                     ECHO ANY MORE INLINE DIAGNOSTICS MESSAGES.  THIS 
                     CAUSES ALL NETWORK TRAFFIC BETWEEN THE DI AND THE
                     HOST TO STOP.
          ANALYSIS - NIP IS RELEASING THE MCI INLINE DIAGNOSTICS FLAG 
                     ONLY IF PIP HAS SET THE REQUEST BUFFER FLAG.  THIS 
                     WILL NEVER OCCUR UNTIL THE OLD BUFFER IS RELEASED. 
          SOLUTION - NIP ROUTINE XCHKPCR HAS BEEN CORRECTED TO NOT CHECK
                     THE REQUEST BUFFER FLAG WHEN DETERMINING IF THE
                     THE BUFFER IS TO BE RELEASED OR NOT. 
          EG     11/19/86    XCHKPCR
 NA5B742 PROBLEM  - PSR NA5B715 CHANGED THE NAMSTART FILE PROCESSING
                    FROM A SEQUENTIAL READ TO A RANDOM READ. THE
                    CODE TERMINATES THE READING WHEN EOF IS ENCOUNTERED.
                    ALTHOUGH THE RELEASED VERSION OF NAMSTRT ALWAYS 
                    HAS AN EOF AT THE END, CUSTOMERS MIGHT ADD
                    THEIR OWN RECORDS TO THE NAMSTRT FILE AND FORGET
                    TO RESTORE THE EOF. 
                    NAMI SHOULD CHECK FOR BOTH EOF AND EOI. 
         SOLUTION - CHANGE NAMI TO TERMINATE THE READING ON BOTH
                    EOI AND/OR EOF. 
         TET    11/24/86    NAMI
 NA5B744  PROBLEM  - NIP FAILED WITH CPU ERROR EXIT WHEN IT TRIED TO
                     RETURN THE ZZZZZDN FILE. 
          ANALYSIS - NIP HAD EXECUTED DATA IN SUBROUTINE OPRETN.
          SOLUTION - NIP ROUTINE OPRETN HAS BEEN CORRECTED SO NIP 
                     WILLNOT TRY TO EXECUTE THE DATA. 
  
          EG             87/02/10       OPRETN
  
 NA5B745  PROBLEM  - A CALL TO QTCLOSE WHEN NAM IS NOT AVAILABLE RESULTS
                     IN AIP ABORTING THE APPLICATION PROGRAM. 
          ANALYSIS - QTCLOSE CALLS NETWAIT TO FLUSH AIP-S BUFFER BEFORE 
                     CALLING NETOFF.  THE NETWAIT CALL WILL RESULT IN 
                     AIP ABORTING THE APPLICATION PROGRAM IF NAM IS NOT 
                     AVAILABLE. 
          SOLUTION - ADD A NEW OPTION TO AIP TO NOT ABORT WHEN NAM IS 
                     NOT AVAILABLE.  THE OPTION IS SELECTED BY THE
                     APPLICATION PROGRAM CALLING NETFUNC WITH A NEW 
                     FUNCTION CODE.  QTCLOSE WILL CALL NETFUNC WITH THE 
                     NEW FUNCTION CODE. 
          EG     11/25/86    NETFUNC, NP$MODE, NP$XFER, QTCLOSE 
 NA5B746  PROBLEM -  NETWORK APPLICATION CANNOT VALIDATE THAT 
                     APPLICATION AT OTHER END OF INTRAHOST A-A
                     CONNECTION IS APPLICATION THAT IT IS SUPPOSE TO
                     BE.
          ANALYSIS - NIP SHOULD INCLUDE NAME OF APPLICATION AT OTHER
                     END OF INTRAHOST A-A CONNECTION IN CON/REQ 
                     SUPERVISORY MESSAGE. 
          SOLUTION - NIP ROUTINE HCONREQ HAS BEEN CORRECTED TO INCLUDE
                     THE NAME OF THE OTHER APPLICATION IN THE CON/REQ 
                     SUPERVISORY MESSAGE FOR INTRAHOST A-A CONNECTIONS. 
          EG     11/06/86    HCONREQ
 NA5B747  PROBLEM  - NIP FAILED WITH NO INTERLOCK MESSAGE AFTER 11TH EST
                     ENTRY WAS TURNED ON. 
          ANALYSIS - PIP ONLY ALLOWS A MAXIMUM OF 10 FRONT ENDS.  WHEN
                     THE 11TH EST ENTRY WAS TURNED ON, THIS RESULTED IN 
                     NIP SETTING THE PIT ENTRY-IN-USE FLAG FOR A PIP
                     THAT NIP NEVER CALLED INTO A PP BECAUSE THE NBT
                     TABLE WAS FULL.
          SOLUTION - NIP HAS BEEN CORRECTED TO NOT SET THE PIT ENTRY-IN-
                     USE FLAG IF THE NBT TABLE IS FULL. 
          EG     11/26/86    XCHKCET
 NA5B478 PROBLEM  - NVF FAILS WITH MESSAGE "NVFTETC - CAN NOT FIND
                    PDCT ENTRY FOR TERM". AFTER AN APPLICATION IS 
                    DROPPED.
  
         SOLUTION - NVF RECEIVED A CR/CB FOR A TERMINAL AND ISSUED A
                    VCB READ REQUEST FOR THE CONNECTION. WHEN RE- 
                    STORING THE TC PARAMETER FOR THE PTAC ENTRY, IT 
                    USED A WRONG INDEX, AND WE HAD A WRONG TC FOR THE 
                    CONNECTION.  THE WRONG TC VALUE HAPPENED TO BE THAT 
                    OF A SYNCHRONEOUS TYPE TERMINAL SO NVF TRIED TO 
                    DELETE THE PDCT TABLE ENTRY FOR THIS CONNECTION.
                    THE ENTRY DID NOT EXIST BECAUSE THE TERMINAL WAS
                    NOT REALLY SYNCHRONEOUS TYPE. NVF ABORTED BECAUSE 
                    IT COULD NOT FIND THE ENTRY.
         TET    12/10/86    NVFTRVD 
 NA5B749 PROBLEM  - NVF REJECTED X.25 CALLS WHEN CALLED ADDRESSES 
                    CONSIST OF ODD NUMBER OF DIGITS.
         ANALYSIS - IN AN X.25 CALL, WHEN THE CALLED ADDRESS CONSISTS 
                    OF AN ODD NUMBER OF DIGITS, THE CALLING HOST
                    WILL PAD IT WITH A ZERO SO THE DTEA ADDRESS FIELD 
                    IS ALWAYS AN EXACT MULTIPLE OF BYTES. IF THE
                    CALLING DTEA ADDRESS ALSO HAPPENS TO HAS AN ODD 
                    NUMBER OF DIGITS, THE TWO ADDRESSES TOGETHER WILL 
                    HAVE AN EVEN NUMBER OF NIBLES (SEMI OCTETS) AND 
                    THEREFORE NO PADDING IS NEEDED. 
                       IN NVFARAP, WHEN DETERMINING WHERE THESE 
                    ADDRESSES END, NVF TREATED EACH ADDRESS SEPARATELY, 
                    AND WHEN THE CALLED ADDRESS HAD AN ODD NUMBER OF
                    DIGITS, IT ROUNDED IT UP. THIS IS WRONG BECAUSE IF
                    BOTH ADDRESSES HAVE ODD NUMBER OF DIGITS, THEY, TO- 
                    GETHER WILL HAVE AN EVEN NUMBER OF DIGITS AND NO
                    ROUNDING IS NECCESSARY. 
  
         SOLUTION - NVF WILL NOW DECIDE WHETHER TO ROUND IT UP OR NOT 
                    DEPENDING ON THE TOTAL NUMBER OF DIGITS WITHIN THE
                    TWO ADDRESSES. NVF WILL ONLY ROUND IT UP WHEN THE 
                    TOTAL IS ODD. 
         TET    12/19/86    NVFARAP 
 NA5B750 PROBLEM  - LONG CONNECT TIMES ON NOS WHEN DISK CONTAINING
                    ACCOUNT DAYFILE UNAVAILABLE.
         SOLUTION - ADD AN ELAPSED TIME OF CONNECTION (XXXXXX IN SE-
                    CONDS) TO "AEUN" ACCOUNT DAYFILE MESSAGE. THE NEW 
                    FORMAT IS:  
                       AEUN, C1, USERNAME, FAMILYNAME, TERMINALNAME.
                       AEUN, C2, XXXXXXSECS.
                    THE NEW MESSAGE WILL SHOW THE CORRECT TIME OF 
                    CONNECTION OF A JOB OR A TERMINAL SESSION.
    J.YANG  12/23/86 TEXTNVF,NVFTIAM,NVFTCCT
          PROBLEM  - PIP SENT ERROR LOGICAL WORKLIST TO PSU BECAUSE 
                     PSU HAD SENT A SET/DEVICE SUPERVISORY MESSAGE
                     TO PIP AFTER PSU HAD STOPPED THE OUTPUT
                     DEVICE.
          ANALYSIS - SINCE PIP ALLOWS THE SET/DEVICE SUPERVISORY
                     MESSAGE IF THE NETWORK HAD STOPPED THE OUTPUT
                     DEVICE, IT SHOULD ALSO ALLOW THE SUPERVISORY 
                     MESSAGE WHEN THE APPLICATION PROGRAM STOPPED 
                     THE DEVICE.
          SOLUTION - PIP HAS BEEN CORRECTED TO ACCEPT BOTH THE
                     SET/DEVICE AND SET/FILE SUPERVISORY MESSAGES 
                     WHEN THE OUTPUT DEVICE IS STOPPED BY THE 
                     APPLICATION PROGRAM. 
          EG     12/12/86    PIP
          PROBLEM  - PIP BY DEFAULTS ALLOWS ONLY UP TO 10 FRONT 
                     ENDS WHILE NIP ALLOWS UP TO 16 FRONT ENDS. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ALLOW UP TO 16 
                     FRONT ENDS BY DEFAULT. 
          EG     12/12/86    PIP
 NA5B753  NETOU DOES NOT ALLOW USER TO EXCUTE COMMAND 
          FILE FROM AN ALTERNATE USER.
  
          CURRENTLY WHEN USER A GIVES PERMISSION (THROUGH 
          NOS *PERMIT* COMMAND) TO USER B TO USE HIS COMMAND
          FILE, USER B ON NETOU TRY TO EXCUTE THIS COMMAND
          FILE THROUGH *EXECF* COMMAND, USER B GETS AN ERROR
          MESSAGE FROM NETOU SAYING COMMAND FILE NOT FOUND. 
          NETOU IS UNABLE TO GET THE FILE FOR USER B. 
          INTERNALLY, NETOU DOES A SET USER INDEX ONLY
          WHEN TRYING TO USER OVER TO USER B'S USER INDEX 
          TO GET THE COMMAND FILE OF USER A.  THIS IS 
          INSUFFICIENT.  NETOU NEEDS TO SET USER INDEX
          AS WELL AS SET USER NAME OVER TO USER B IN
          ORDER TO GET USER A'S COMMAND FILE. 
  
          AML           86/12/10
 NA5B755 PROBLEM  - THE COPYRIGHT BANNER SHOULD BE CHANGED TO 1987. 
         SOLUTION - THE CHANGE IS MADE. 
         TET    12/15/86     CRCOM, TMSGNVF 
 NA5B756 PROBLEM  - NVF ABORTS WITH MESSAGE " CPU ERROR EXIT ..." 
         ANALYSIS - NVF RECEIVED A CR/CB FOR A CONNECTION WHICH 
                    WAS IN SWITCH PENDING STATE. NVF WAS SEARCHING
                    THROUGH THE WBQ FOR THE CR/SWH SO NVF COULD 
                    DELETE IT. THE CR/SWH WAS SOMEHOW NOT IN THE
                    WBQ (IT WAS NOT CLEAR FROM THE DUMP WHY THE 
                    CR/SWH WAS MISSING).  SINCE THERE WAS NO OTHER
                    CONDITION TO STOP THE SEARCHING OTHER THAN
                    FINDING THE CR/SWH, THE SEARCHING WENT OVER 
                    THE WBQ BOUNDARY, AND FINALLY OVER THE FIELD
                    LENGTH. 
         SOLUTION - CODE IS ADDED TO ASSURE THAT THE SEARCHING ONLY 
                    OCCURS WITHIN THE WBQ BOUNDARY. 
  
         TET    12/17/86    NVFCBPA 
 NA5B762 PROBLEM  - NIP FAILED TO CLEAN UP PRU CONNECTION. THE CONNEC-
                    TION WAS LEFT IN NC STATE 12. NIP ABORTED LATER 
                    WHEN LOGICAL LINK WENT DOWN.
         ANALYSIS - THE FOLLOWING EVENTS HAPPEN 
                    . NIP RECEIVED A REG/LL BL=0 WHILE THERE IS A PRU 
                      CONN ON THE LINK. 
                    . NIP SENT PIP A WL WITH OP=9. NC STATE CHANGED 
                      FROM 9 TO 12.    LLCBWOF IS SET.
                    . PIP RESPONDED BY SENDING A WL WITH OP=3. THE WL 
                      WAS QUEUED BECAUSE SOME FILES WERE STILL AROUND.
                    . NIP RECEIVED A REG/LL BL=3. LLCBWOF IS RESET. 
                    . NIP PROCESSED THE QUEUED WL(OP=3). SINCE LLCBWOF
                      HAD BEEN RESET, IT FAILED TO RELEASE THE NCNB 
                      AND THE CONNECTION WAS LEFT IN (NC) STATE 12
                      UNTIL SOME TRIGGER CAUSED NIP TO ABORT. 
         SOLUTION - SINCE THE LLCBWOF IS NOT SUFFICIENT FOR DETERMINING 
                    WHETHER TO RELEASE THE NCNB FOR A CONNECTION, A NEW 
                    FLAG IN THE NCNT TABLE IS DEFINED FOR EACH CONNEC-
                    TION. THE FLAG WILL BE SET IN RELCONN FOR EACH PRU
                    CONNECTION, AND USED IN NPPCT TO DETERMINE WHETHER
                    TO RELEASE THE NCNB.
         TET    02/13/87    NCNT, NPPCT, RELCONN
 NA5B763  PROBLEM  - NIP ABORTED WHEN IT PROCESSED A PWL WORKLIST FROM
                     PIP FOR A NONPRU CONNECTION. 
          ANALYSIS - NIP HAD RECEIVED A PWL (OP=1) WHICH IT COULD NOT 
                     PROCESS IMMEDIATELY.  THE PWL WAS QUEUED TO THE
                     APPLICATION-S ACB.  A TERMINATE PRU CONNECTION 
                     PWL WAS RECEIVED LATER AND PROCESSED.  THIS
                     RESULTED IN THE PRU CONNECTION BEING CONVERTED 
                     BACK TO A NONPRU CONNECTION.  THE PWL QUEUED TO
                     THE ACB WAS SUPPOSE TO BE RELEASED BUT WAS NOT.
                     THE QUEUED PWL WAS PROCESSED LATER AND NIP DID 
                     NOT LIKE IT BECAUSE IT WAS FOR A NONPRU
                     CONNECTION.
          SOLUTION - NIP ROUTINE NPPCT HAS BEEN CORRECTED TO CHECK
                     PROPERLY FOR PWLS THAT NEED TO BE RELEASED 
                     WHEN A PRU CONNECTION IS TERMINATED. 
          EG     01/20/87    NPPCT
 NA5B767 PROBLEM  - NAM ABORTS AN APPLICATION WHEN THERE ARE MORE THAN
                    500 SM'S QUEUED FOR THE APPLICATION. THIS RULE
                    IS NOT APPROPRIATE FOR NVF BECAUSE UNDER NORMAL 
                    SITUATION THERE CAN BE MORE THAN 500 SM'S QUEUED
                    FOR NVF IF THE SITE HAS A LOT (GR 500) OF AUTO
                    LOGIN TERMINALS.
  
         SOLUTION - SPECIAL CASE NVF. NAM NOW ABORTS THE APPLICATION
                    ONLY IF IT IS NOT NVF.
  
         TET    01/29/87    HWLP
 NA5B768  CORRECT A CODING PROBLEM WITH FEATURE FN6901. 
          CMP    02/03/87    PIP
 NA5B772  PROBLEM  - PIP FAILED TO RELEASE EQUIPMENT WHEN IT WAS TURNED 
                     OFF. 
          ANALYSIS - PIP WAS WAITING FOR A REG/CP SUPERVISORY MESSAGE 
                     RESPONSE FROM NIP.  NIP HAD NOT SENT IT BECAUSE
                     NIP WAS WAITING FOR A LOGICAL LINK TO BE CLEANED 
                     UP.  THE LOGICAL LINK WAS NOT CLEANED UP BECAUSE 
                     NIP WAS WAITING FOR PIP TO ACKNOWLEDGE THE 
                     TERMINATION OF A PRU CONNECTION ON THAT LOGICAL
                     LINK.  PIP HAD ACKNOWLEDGED THE PRU CONNECTION 
                     TERMINATION BUT NIP HAD LOST THAT ACKNOWLEDGEMENT
                     SO NIP WAS STILL WAITING FOR IT.  THE
                     ACKNOWLEDGEMENT (A PRU WORKLIST WITH OPCODE = 3) 
                     HAD BEEN QUEUED TO THE ACB PWL RING DUE TO THE 
                     APPLICATION PROGRAM BEING SWAPPED OUT AND A FILE 
                     NEEDED TO BE TRANSFERRED BACK TO THE APPLICATION 
                     PROGRAM.  THIS ACKNOWLEDGEMENT WAS PRECEEDED IN
                     THE QUEUE BY ANOTHER PRU CONNECTION TERMINATION
                     ACKNOWLEDGEMENT FOR A DIFFERENT CONNECTION.  WHEN
                     THE ACKNOWLEDGEMENT FOR THE FIRST CONNECTION GOT 
                     PROCESSED, NIP OVERLAY NPPCT DELINKED THE PRU
                     WORKLIST FROM THE ACB PWL RING.  CONTROL WAS 
                     RETURNED TO XSACB WHO THEN DELINKED THE NEXT 
                     PRU WORKLIST IN THE ACB PWL RING WHICH HAD NOT 
                     BEEN PROCESSED YET. THIS RESULTED IN NIP WAITING 
                     FOR THE ACKNOWLEDGEMENT WHICH IT HAD DELINKED
                     FROM THE ACB PWL RING BY MISTAKE.
          SOLUTION - NIP OVERLAY NPPCT HAS BEEN CORRECTED TO NOT
                     DELINK THE FIRST ENTRY IN THE ACB PWL RING IF
                     IT IS THE SAME PWL THAT IT IS CURRENTLY
                     PROCESSING.
          EG     02/13/87    NPPCT, XSACB 
 NA5B774 - NAM/NVE FAILED -NVF MODED AT 10363.
  
           BEFORE SENDING OUT A CR/TRM TO TERMINATE A CONNECTION, NVF 
           SEARCHED THE WBQ TO DELETE THE CR/SWH SM, SINCE THERE WAS NO 
           LOGIC TO STOP THE SEARCHING EXCEPT THE FINDING OF A CR/SWH,
           THE LOOP KEPT GOING AND WENT OUT THE PROGRAM FIELD LENGTH. 
  
           CODE IS ADDED TO NVF TO ASSURE THE SEARCHING WILL OCCUR
           WITHIN THE WBQ RANGE.
  
           J.YANG  02/17/87   NVFCTRM 
  
 NA5B789 PROBLEM  - NIP RECEIVED PRUWL WITH OP=6 AFTER THE PRU MODE 
                    HAD BEEN TERMINATED, AND NIP ABORTED. 
         SOLUTION - CHANCE NIP SO IT WILL SIMPLY DAYFILE AND DUMP 
                    THE CONTENT OF THE WORKLIST INSTEAD OF ABORTING.
         TET    03/06/87    NPPWL 
 NA50465 PROBLEM  - USER CAN LOG INTO RBF (OR OTHER APPLS) TWICE
                    EVEN IF "UID" HAS BEEN SPECIFIED IN NDL FOR THE 
                    APPLICATION.
  
         ANALYSIS - THIS HAPPENED BECAUSE NOS RETURNED INCONSISTENT 
                    FAMILY ORDINALS (FOR THE SAME USER) TO NVF IN 
                    RESPONSE TO DIFFERENT CPM56 CALLS TO VALIDATE THE 
                    USER. NVF ISSUES A CPM WHEN A USER FIRST LOGS IN
                    AND EVERY TIME THE USER SWITCHES FROM ONE APPL TO 
                    ANOTHER. DEPENDING ON WHETHER IT IS AN ORIGINAL 
                    LOGIN, OR IT IS A SWITCH, NVF WILL GET DIFFERENT
                    VALUES FOR FAMILY ORDINAL. SINCE THE FAMILY ORDINAL 
                    FOR A SINGLE USER WAS INCONSITENT, NVF SOMETIMES
                    FAILED TO IDENTIFY THE USER AND LET THE USER LOG
                    IN TWICE. 
  
         SOLUTION - CHANGE NVF TO USE THE COMBINATION OF FAMILY NAME
                    (INSTEAD OF FAMILY ORDINAL) AND USER NAME TO
                     IDENTIFY USERS.
  
         TET    07/14/86    TEXTNVF,NVFTDSP,NVFTURT 
 NA50473 PROBLEM  - WHILE NOS CONSIDERS ASTERISK (*)  AS A VALID
                    CHARACTER IN COMBINING USER NAMES (MODVAL/SYSTEM
                    MAINTENANCE MANUAL), NVF K-DISPLAY HAS NOT
                    RECOGNIZED ASTERISKS (WITHIN USER NAMES) AS VALID 
                    CHARACTERS. 
  
         SOLUTION - MODIFY SSRGNT SO IT WILL CONSIDER ASTERISKS (*) 
                    AS VALID CHARACTERS IN COMBINING NAMES. 
  
         TET    08/15/86    SSRGNT
 NA50478 PROBLEM  - FOR EACH NETOFF WORKLIST PROCESSING, THERE ARE
                    AT LEAST TWO SHORT TERM CONTROL-POINT CONNECTIONS.
                    WHEN NIP ISSUED SYSTEM CONTROL POINT
                    REQUESTS TO DELETE THESE CONNECTIONS, IT ASSO-
                    CIATED BOTH REQUESTS TO A SINGLE ADDRESS. AS A
                    RESULT, THE APPLICATION WOULD REGAIN CONTROL AS 
                    SOON AS THE FIRST REQUEST WAS DONE. THIS CREATED
                    A WINDOW FOR THE SYSTEM TO SET THE SECOND COMPLE- 
                    TION BIT INTO A BUFFER THAT MIGHT HAVE BEEN REUSED
                    FOR SOMETHING ELSE. 
  
         SOLUTION - ASSOCIAT TWO WORKLIST REQUESTS WITH TWO DIFFERENT 
                    ADDRESSES. THE SECOND REQUEST IS ASSOCIATED WITH
                    THE NETOFF COMPLETION BIT BECAUSE WE DON'T WANT 
                    THE APPLICATION TO REGAIN CONTROL BACK UNTIL BOTH 
                    REQUESTS HAVE BEEN PROCESSED. 
         TET    11/17/86    HPNOFFN 
   NA50506 PROBLEM - NOS INCORRECT FAMILY COUNT CAUSED BY NAM/NVF.
                     NVF INCREMENTS THE FAMILY COUNT EVERY TIME A USER
                     LOGINS IN, BUT DOES NOT DECREMENT IT IF NAM CRASHES. 
          SOLUTION - A NEW GLOBAL TABLE CALLED "IFMC" IS CREATED TO KEEP
                     FAMILY COUNTS INFORMATION FOR ALL THE FAMILIES. WHEN 
                     NAM CRASHES, IN REPRIEVE PROCESSING OR BEFORE COMPLETE 
                     EXECUTION, NVF WILL SEARCH IFMC TABLE AND ISSUE CPM73
                     REQUESTS TO DECREMENT ALL THE FAMILY COUNTS THAT 
                     RECORDED IN THE TABLE. 
          J. YANG   01/13/87  TEXTNVF,TXTANVF,NVFTICR,NVFICNE,NVFUPRP.
 NA50508  THIS PROBLEM WAS CAUSED BY THE FACT THE MODE 4A 
          PRINTER HAS DEFAULT XBZ SET AT 1040. CODE IN
          NDLNFCM WAS CHANGED SUCH THAT FOR 200UT AND 734 
          TERMINAL CLASS, THE DEFAULT XBZ WAS SET AT 1040 
          FOR CONSOLE DEVICES AND CARD READERS, AND AT 1000 
          FOR PRINTER DEVICES.
          YCY     86/05/08     NDLNFCM
 NA50512 PROBLEM  - NVF DID NOT CHECK FOR PRIVILEDGED APPLICATION 
                    WHEN "PRIV" WAS SPECIFIED IN LCF IF MAXCOPYS
                    FOR THE APPL IS GREATER THAN 1. 
  
         SOLUTION - MODIFY NVFSNON TO INCLUDE A CHECK FOR PRIVILEDGED 
                    APPLICATION WHEN "PRIV" IS SPECIFIED IN LCF. THIS 
                    CODE AFFECTS THE CASE WHEN MAXCOPYS IS GREATER
                    THAN 1. THE CASE WHEN MAXCOPY=1 HAS BEEN TAKEN
                    CARE BY THE ORIGINAL CODE.
  
         TET    06/12/86    NVFSNON 
 NA50521  NAM DIED WITH MONITOR CALL ERROR. 
  
          PROBLEM: NAM ABORTED WITH MONITOR CALL ERROR. 
  
          ANALYSIS: THE MONITOR CALL ERROR OCCURRED DURING
          GARBAGE COLLECTION. WE FOUND A PARTIALLY CONVERTED
          PCNB IN THE DUMP. THE NETWORK STATE FOR CONNECTION
          IS 6 AND THE NETWORK STATE FOR BLOCK PROTOCOL IS ALSO 
          6. THAT SUGGESTS THAT THE CONNECTION WAS BROKEN BY
          A TCNTA BEFORE THE PRUON REQUEST WAS PROCESSED BY NAM.
          UNFORTUNATELY, ALTHOUGH NAM IGNORED THE PRUON TRIGGER 
          IN STATE 12, IT FORGOT TO SET THE PARAMP1 TO 1 TO 
          INDICATE THAT NAM DID NOT CONVERT THE NCNB TO A PCNB. 
          SO, NAM WENT AHEAD TO CREATE THE 2 WORD TEMPORARY 
          BUFFER FOR PIP WHICH XEXEC USED TO CONVERT THE
          LCNB TO THE PROPER PCNB.
          IN THIS CASE, THE NCNB WAS EVENTUALLY CONVERTED 
          TO A PCNB WITH THE SIZE OF A NCNB. IN GARBAGE COLLECTION, 
          ROUTINE MAJPTR TRIED TO ADJUST THE POINTERS AND IT FAILED 
          ON THE BAD PCNB.
  
          SOLUTION: A NEW ACTION IS ADDED TO THE HBSTTP TABLE.
          IT SET THE PARAMP1 TO 1 TO INDICATE THAT
          NO PCNB CONVERSION HAS TAKEN PLACE. 
          YCY     86/07/07     STBLDEF,STATTBL,HBSTTP 
 NA50525  CORRECTING THE FIELD DEFINITION FOR CONABN. 
  
          PROBLEM: THE FIELD DEFINITION FOR CONABN DOES 
                   NOT MATCH THE DOCUEMENTATION.
  
          ANALYSIS: THE NAM HOST APPLICATIONS REF 
                    MANUAL SPECIFIES THAT THE CONABN
                    BEGINS FROM WORD 2 AND GOES FROM
                    BIT 24 (BIT 0 ON LEFT) FOR 18 BITS. 
                    BUT CURRENTLY IT IS DEFINED AS
                    U(2,30,12). 
  
          SOLUTION: SMAPPL IS CHANGED SUCH THAT THE 
                    CONABN FIELD IS NOW (2,24,18).
          YCY       86/06/12    NIP 
 NA50530  PROBLEM -  NIP ABORTED WITH NBSTTP STATE TABLE ERROR AFTER
                     DETECTING BLOCK PROTOCOL ERROR.
          ANALYSIS - THE BLOCK PROTOCOL ERROR CAUSED PIP TO TERMINATE 
                     THE CONNECTION.  WHILE THE CONNECTION WAS BEING
                     TERMINATED, THE APPLICATION RECEIVED A SYNC SUP
                     MSG QUEUED ON THAT CONNECTION.  THIS RESULTED IN 
                     A BACK TRIGGER FOR THE NETWORK BLOCK PROTOCOL
                     STATE TABLE WHICH WAS PROCESSED AS A STATE TABLE 
                     ERROR. 
          SOLUTION - THE NETWORK BLOCK PROTOCOL STATE TABLE HAS BEEN
                     CORRECTED TO IGNORE BACK TRIGGERS WHEN IN THIS 
                     TERMINATING CONNECTION STATE.
          EG     07/14/86    STATTBL
 NA50536  NDLP SHOULD NOT ALLOW ILLEGAL PW VALUES 
          ON DEVICE DEFINITIONS FOR 3780 TERMINALS. 
  
          FOR LINE PRINTERS BELONGING TO TERMINAL CLASS 
          2780 AND 3780, NDLP CURRENTLY ALLOWS PW VALUES
          OF 0 WHICH CAUSE PROBLEMS TO CCP. 
  
          CODE IN NDLNFCM IS CHANGED SUCH THAT FOR
          TERMINAL CLASS 2780 AND 3780, THE VALUES OF PAGE
          WIDTH OF THE DEVICE TYPE OF LINE PRINTERS 
          CAN ONLY BE GREATER THAN OR EQUAL TO 50 
          AND LESS THAN OR EQUAL TO 150.
          YCY     86/07/23     NDLNFCM
 NA50537  NDL ALLOWS MORE THAN ONE TERMDEV PER
          SUBTIP TYPE ON AN X.25 LINE.
  
          A BIT MASK "XTERMASK" IS NOW DEFINED IN 
          NDLNFCM. IT IS CLEARED AT THE BEGINNING 
          OF LINGPR AND SET FOR EVERY TERMINAL OR 
          TERMDEV PROCESSED ACCORDING TO
          THE VALUE OF THE SUBTIP. A NEW ERROR CODE 
          167 IS ADDED TO ER2CNDL TO TELL THE USER
          THAT ONLY ONE TERMDEV OR ONE TERMINAL AND 
          ONE DEVICE CAN FOLLOW EACH DISTINCT SUBTIP
          DEFINED.
          YCY     86/07/28     ER2CNDL,NDLNFCM
 FS5221   IMPLEMENTS DAP S5221 WHICH DEFINES NDL A-TO-A ENHANCEMENTS
          FOR CDCNET AND NOS-VE.
  
          YCY            86/08/10       DATANDL 
                                        ER2CNDL 
                                        NDLSTAT 
                                        NDLPSS1 
                                        NDLP2LF 
  
 NA5B757  NDLP  DOES  NOT  DEFAULT  PRID  TO C20000 IF DOS = NOS/VE, AND
          C00000 IF DOS = AOS/VS. 
  
          FEATURE  CODE  FS5221  INTRODUCED  CODE  INTO NDLP TO PROPERLY
          PROCESS OUTCALL TO NOS/VE AND AOS/VS, HOWEVER  IT  DID NOT SET
          THE  PRID  PROPERLY.  INSTEAD OF DEFAULTING PRID TO C20000  IF
          DOS = NOS/VE,  AND  PRID  TO C00000 IF DOS = AOS/VE, NDLP LEFT
          PRID AS C00000
  
          JGS            86/12/18       NDLP2LF 
  
 NA50542 THIS MOD IS TO FIX RBF OFCRSM PROBLEM WITH CURRENT 
         STATE OF 31 OCTAL, AND 42 OCTAL. 
         CC 86/08/18
 NA50551 PROBLEM  - NAM ABORTED SOMETIME WITH MEESAGE "NVF FAILURE" 
                    AND SOMETIME WITH "NIP/HCSP ERRAN6".
         ANALYSIS - NIP IS EXPECTING A CR/RCN/N BUT RECEIVES NWTC FROM
                    THE NETWORK SIDE (HCSTTP FROM STATE 6 GO TO STATE 
                    10) THEN NIP GETS CR/RCN/A, NIP SHOULD SEND CR/CB/U 
                    TO NVF AND CON/CB/U TO PRIMARY APPLICATION. 
         LTN    09/26/86    STATTBL 
  
 NA50552 PROBLEM  - NVF ISSUES ACCOUNT DAYFILE MESSAGE WITH PASSWORDS.
                    NVF ISSUES AN "ABER" ACCOOUNT DAYFILE MESSAGE FOR 
                    EVERY IMPROPER LOGIN. IF YOU TYPE IN THE USER NAME
                    AT THE FAMILY PROMPT AND THE PASSWORD AT THE USER 
                    NAME PROMPT, THE USER NAME AND PASSWORD WILL BE 
                    SHOWED IN "ABER" IMPROPER LOGIN MESSAGE AS FAMILY 
                    AND USER NAMES. 
         SOLUTION - WHENEVER THERE IS A BAD LOGIN, NVF WILL ISSUE A 
                    CPM56 REQUEST TO REVALIDATE FAMILY/USER NAME PACK 
                    WITHOUT REVALIDATING PASSWORD. NVF WILL ISSUE "ABER"
                    WITH USER NAME, FAMILY NAME, AND TERMINAL NAME ONLY 
                    IF THE REVALIDATION OF FAMILY/USER PACK IS VALID, 
                    OTHERWISE, THE MESSAGE WILL CONTAIN ONLY A TERMINAL 
                    NAME AND SKIP FAMILY AND USER NAMES.
     J. YANG   12/22/86   NVFTIAM, NVFTVVD, TEXTNVF 
  
   NA5B775 PROBLEM - SYS - LOGIN PROCESSING CHANGED CAUSED TEST BASE FAILURE. 
  
                     IF THE LOGIN WAS A BAD ONE AND THE REVALIDATION OF 
                     FAMILY/USER PACK RETURNED TO BE GOOD, THE INVALID
                     LOGIN FLAG IN PTAC TABLE IS NOT SET BACK TO 1. 
  
          SOLUTION - CODE IS ADDED IN NVFTVVD TO RESET THE FLAG TO 1 BEFORE 
                     PROCESS UNSUCCESSFUL VALIDATAION . 
  
          J.YANG   02/11/87   NVFTVVD 
  
 NA50554  PROBLEM:  
          IT IS POSSIBLE TO HANG THE NPU CHANNEL ON INPUT OR OUTPUT 
          EVEN THOUGH THE NOHANG BIT IS SET ON THESE INSTRUCTIONS.
          THIS IS BECAUSE THE NOHANG IS PROTECTION AGAINST ACTIVE/
          INACTIVE PROBLEMS, BUT HAS NO RELEVENCE TO FULL/EMPTY 
          CONDITIONS. IN THIS PARTICULAR CASE, THE NPU WAS HUNG BY
          TURNING THE COUPLER BOARD OFF WHILE PIP WAS LOADING CCP.
          SOLUTION: 
          PIP HAS BEEN MODIFIED TO TEST FOR THE APPROPRIATE EMPTY/
          FULL STATUS BEFORE ATTEMPTING INPUT OR OUTPUT.
  
          CMP    02/04/87   PIP 
 NA50561 PROBLEM  - SOME MALFUNCTIONING TERMINAL ERRONEOUSLY
                    GENERATED ENDLESS UPLINE BLK BLOCKS TO NVF, 
                    WHILE NVF IS EXPECTING LOGIN DATA FROM THE
                    CONNECTION. THESE USELESS BLOCKS CAUSED NVF 
                    TO ROLLIN SO OFTEN THAT IT DEGRADED THE 
                    PERFORMANCE OF THE SYSTEM.
         SOLUTION - CHANGE NVF TO ONLY ALLOW A LIMITTED NUMBER (20) 
                    OF BLK BLOCKS FOR EACH LOGIN. IF THE NUMBER 
                    EXCEEDS THIS LIMIT, TERMINATE THE CONNECTION
                    BECAUSE THE TERMINAL IS NOT FUNTIONNING PROPERLY. 
         TET    11/19/86    TEXTNVF,NVFCAUT 
 NA50563 PROBLEM  - THE SECURITY MOD SENDS A MASK TO OVERSTRIKE 
                    THE USER TYPED-IN PASSWORD. IT DOES THAT FOR
                    ALL DEVICES OF TYPE ZERO (INTERACTIVE). SOME
                    SITES HAVE PLOTTERS BEING DECLARED AS DT=0, SUP-
                    PORTED BY THEIR OWN APPLICATION. THESE PLOTTERS 
                    RECEIVED THE PASSWORD MASK AND COULD NOT HANDLE 
                    IT. 
  
         SOLUTION - PASSIVE DEVICES, LIKE PRINTERS AND PLOTTERS,
                    ALWAYS HAVE MANDATORY/PRIMARY USER SPECIFIED
                    IN NDL, DISREGARDING DEVICE TYPE BEING DECLARED.
                    CODE IS ADDED TO NVF TO SEND THE PASSWORD MASK
                    ONLY WHEN THERE IS NO MANDATORY/PRIMARY USER
                    ASSOCIATED TO THE TERMINAL. 
  
         TET    11/10/86     NVFTVVD
 NA50577  PROBLEM  - FILE TRANSFERS FROM NOS 2.4.1 SYSTEM TO NOS 2.5.1
                     SYSTEMS RESULT IN AN END-OF-FILE RECORD PRECEDING
                     THE TRANSFERRED DATA.
          ANALYSIS - IF A FILE IS TRANSFERRED WITHOUT CHECKMARKS, PIP 
                     PERFORMS SEQUENTIAL WRITES ON THE FILE.  HOWEVER,
                     PIP STILL RELIES ON NOS TO RETURN THE CURRENT
                     RANDOM INDEX AFTER ALL I/O OPERATIONS.  FOR
                     SEQUENTIAL WRITES, NOS DOES NOT UPDATE THE CURRENT 
                     RANDOM INDEX.  THUS WHEN PIP PERFORMED A 
                     SUBSEQUENT I/O OPERATION, IT WROTE A EMPTY PRU TO
                     SECTOR ADDRESS ZERO WHICH RESULTED IN AN END-OF- 
                     FILE MARK APPEARING IN THE FILE. 
          SOLUTION - PIP HAS BEEN CORRECTED TO USE RANDOM WRITES ON 
                     FILES TRANSFERRED WITHOUT CHECKMARKS.
          EG     12/17/86    PIP
 NA50578  PROBLEM:  
          THE SENDING PIP RECEIVED A BREAK FROM AN A-A CONNECTION ON AN 
          X25 LINE, WHILST THE SENDING CONNECTION WAS WAITING FOR MASS
          STORAGE TO COMPLETE. PIP SENT A WORKLIST TO NAM TO INFORM IT
          OF THE LEVEL-7 ERROR ON A FILE TRANSFER, BUT DID NOT FIRST
          WAIT FOR THE MASS STORAGE I-O TO COMPLETE. NAM THEN ISSUED THE
          APPROPRIATE SUB-SYSTEM REQUEST TO SWITCH THE FILE BACK TO THE 
          APPLICATION (PTF). CPUMTR DETECTED THE FILE BUSY AND ABORTED
          THE REQUEST (RC=01B). 
          SOLUTION: 
          PIP WILL NOW WAIT IN STATE 59 (REPORT FILE TRANSFER ERROR)
          UNTIL ANY MASS STORAGE I-O HAS COMPLETED, BEFORE ISSUING THE
          ERROR WORKLIST TO NAM.
  
          CMP 01/26/87       PIP
  
 *L688*    ************************************************ 
 FS5325   THIS CODE IMPLEMENTS THE APPLICATION CONNECTION RESERVATION 
          FEATURE AS DESCRIBED IN DAP S5325.
  
          TET,LTN    06/22/87    NVF, NIP, AIP, QTRM
  
 NA5B315  SHOULD REMOVE HD FROM NDLP. 
  
          SINCE THE HD COMMAND HAS BEEN MADE INTO A ONE SHOT PARAMETER, 
          I.E. IT DOES NOT SET ANY VALUES IN THE TCB, IT SHOULD NOT BE
          A PARAMETER THAT CAN BE SET IN THE NDL, AND SHOULD THEREFORE
          BE REMOVED. 
  
          DEPENDENCIES - CC5A425
  
          JDA            85/05/01       NDLSDAT 
                                       ,DATANDL 
                                       ,NDLLIST 
                                       ,NDLNFCM 
                                       ,NDLPSS1 
  
  NA5B759 PROBLEM  - NIP ABORTED BECAUSE IT REACHED ITS MAXIMUM 
                     FIELD LENGTH.
          ANALYSIS - NIP CURRENTLY DOES NOT HAVE A MAXIMUM LIMIT FOR
                     ITS INBOUNND BUFFER SIZE. THEREFORE, NIP KEEPS IN- 
                     CREASING ITS BUFFER SIZE AS LONG AS PIP REJECTS
                     UPLINE DATA. ONCE THE BUFFER SIZE BECOMES TOO LARGE, 
                     NIP WILL ALWAYS ASK FOR MORE MEMORY ALTHOUGH THERE 
                     IS STILL PLENTY OF UNUSED FRAGMENTED MEMORY
                     PIECES WITHIN ITS FIELD LENGTH. THE MAXIMUM FIELD
                     LENGTH IS THEN REACHED AND NIP ABORTS. 
          SOLUTION - DEFINE A MAXIMUM INBOUND  BUFFER SIZE  (4800), AND 
                     ALSO CHANGE THE MEMORY LIMIT NUMBER FOR EACH BUFFER
                     LEVEL, SO THAT NIP WILL GO INTO REGULATION BEFORE
                     THE MAXIMUM BUFFER SIZE IS REACHED.
          TET    02/20/87    FREETAB, MISDEF, STATTAB, NEIB, XTERMST
 NA5B760  NOS-NOS/VE OR NOS/VE-NOS FILE TRANSFERS WILL HAVE 4 UNUSED
          BITS IN THE LAST BYTE IF AN ODD NUMBER OF 60 BIT WORDS IS 
          TRANSFERRED. PIP HAS SET 4 INTO THE UNUSED BIT COUNT OF THE 
          LEVEL-7 HEADER, BUT DID NOT ZERO THESE BITS. CODE HAS BEEN
          ADDED TO DO THIS. 
  
          CMP    02/12/87    PIP
  
 NA5B770  PROBLEM:  
          NOS OUTPUTS AN EXTRA BLANK AFTER ":". WHEN THE ":" TERMINATES 
          A PRINT LINE & IF THE ":" OCCURS IN COLUMN 136 & THE PRINT
          FILE IS BEING PROCESSED OVER AN MDI, THE EXTRA BLANK WILL 
          CAUSE THE LINE TO WRAP AROUND AND GENERATE AN EXTRA LINEFEED. 
          SOLUTION: 
          PIP HAS BEEN MODIFIED TO SCAN LINES ON PRU DISPLAY CODE DEVICES 
          AND REMOVE TRAILING BLANKS (HENCE SHOOTING BLANKS). THIS IS 
          DONE FOR BOTH MDI AND NPU FRONT ENDS. 
  
          CMP    02/16/87    PIP,MISDEF,PCNB
 NA5B776  PIP LOOPED ON TERMINATION WAITING FOR NIP TO HONOUR PIP'S 
          BUFFER REQUESTS. THIS WAS DUE TO A CODING OMISSION IN PSR 
          NA5B716.
  
          CMP    02/16/87    PIP
 NA5B781    PROBLEM: NDLP DOES NOT SUPPORT UNDERSCORE, DOLLAR,
                     COMMERCIAL AT, AND POUND SIGNS ( _, $, @, # ). 
            SOLUTION: THIS MOD WILL MAKE NDLP SUPPORT THOSE SPECIAL 
                      CHARACTERS. 
  
            LTN    87/05/20            NDLPSS1
  
 NA5B788 PROBLEM  - THE CODE FOR NA50563 TRIED TO RESTRICT THE PASS-
                    WORD MASK FROM BEING SENT TO DEVICES THAT HAVE
                    MANDATORY OR PRIMARY USER DATA DEFINED. HOWEVER,
                    NO INDEX HAD BEEN USED IN REFERENCES TO THE PTAC
                    TABLE. THIS MADE NVF ALWAYS USE THE FIRST ENTRY,
                    AND THAT WAS INCORRECT. 
         SOLUTION - REFERENCES TO PTAC TABLE HAVE BEEN MODIFIED, SO 
                    THEY ARE NOW INDEXED BY PT AS THEY SHOULD BE. 
         TET    03/06/87    NVFTVVD 
 NA5B794 PROBLEM  - SOME DAYFILE ERROR MSG AND ERROR LOG MSG
                    DON'T FOLLOW A CONSISTENT FORMAT. 
         SOLUTION - CHANGE THE MESSAGES TO FOLLOW THE DESIRED FORMAT. 
         TET    03/24/87    NPHECP
 NA5B795  THE ERROR PROCESSOR TABLES FOR PIP SHOW ROUTINE PMER (MDI 
          ERROR STATUS REPORTED) AS BEING IN OVERLAY 2IE. IT IS ACTUALLY
          IN OVERLAY 2PE. 
  
          CMP    03/16/87    PIP
  
 NA5B798  ROUTINE PNSS OF 2PE SETS DVM AS THE TIMER TO BE USED WHEN 
          PIP IS TO WAIT BEFORE RECHECKING FOR A NEGOTIATED PROTOCOL
          VERSION BETWEEN PIP AND THE MDI. HOWEVER ALL OTHER ROUTINES 
          CHECK CELL VTM FOR THIS. PIP HAS BEEN MODIFIED TO SET VTM.
  
          CMP  03/30/87   PIP 
  
 NA5B800  PIP RECEIVED A BACK BLOCK ON A PRU STREAM IN STATE 38 (ISSUE
          PRU OUTPUT TO FRONT END).  THIS IS A VALID OCCURRENCE.
          HOWEVER THE STATE TABLES CAUSED A BLOCK PROTOCOL ERROR TO BE
          REPORTED. THE STREAM STATE TABLES FOR STATE 38 HAVE BEEN
          ALTERED TO PROCESS THE BACK CORRECTLY.
  
          CMP   04/08/87   PIP
  
 NA5B806  PIP DIAGNOSED AN ERROR 36 DUE TO INVALID BUFFER POINTERS IN 
          THE NBT INLINE DIAGNOSTICS BUFFER WORDS. THE PROBLEM IS CAUSED
          BY THE LIMIT BUFFER POINTER UPPER BYTE AND THE CHANNEL
          PROTOCOL VERSION STORAGE USING THE SAME BYTE. THE CHANNEL 
          PROTOCOL VERSION WILL BE MOVED TO BYTE 0. 
  
          CMP   05/23/87   PIP
  
 NA5B814 QTRM RETURNS ERROR WHEN CON/END/N IS RECEIVED. 
  
         IF CONNECTION POLLING IS ENABLED, AND QTGET IS CALLED
         WITH ACN=0, AND A CON/END/N IS RECEIVED, THEN QTGET
         RETURNS AN 'INVALID CONNECTION' STATUS (CODE 16) FOR 
         THE CONNECTION THAT RECEIVED THE CON/END/N.
  
         IF CONNECTION POLLING IS ENABLED AND NO RESPONSE IS GENERATED
         BY THE ASYNCHRONOUS MESSAGE PROCESS, THEN RESET THE CONNECTION 
         NUMBER IN THE NIT TO ZERO. 
  
         MRS       87/05/11       QTGET 
  
 NA50565    PROBLEM:  NB STATE TABLE ERROR IN STATE 8 TRIG 7. 
                        "NIP/NBSTTP ERR HN=4,TN=14,CN=31,7,8" IN NAM
                                             DAYFILE. 
            ANALYSIS: APPLICATION SENT FC/BRK THEN NETOFF RIGHT AWAY. 
                      FC/BRK ADVANCED NB STATE TABLE TO STATE 8.
                      CONNECTION SWITCHED TO NVF AND NVF SENT CR/RCN/N
                      THIS TRIGGERS SINITR (TRIGGER 7 = SEND INITR TO CCP)
                      TO STATE TABLE NBSTTP.
            SOLUTION: SINITR TRIGGER SHOULD ADVANCE NBSTTP STATE TABLE TO 
                      A NEW STATE AND ALSO SEND INITR TO CCP. IN THE NEW
                      STATE, WE ARE EXPECTING A RESET FROM CCP (CAUSED BY 
                      FC/BRK FROM APPLICATION) AND A INITN (RESPONSE OF 
                      INITR) FROM CCP.
            LTN       86/11/14         SXTTP
  
 NA50590 PROBLEM  - NVF RECEIVED ERROR LOGICAL WHEN SENDING 
                    CR/RCN/A. 
         ANALYSIS - DURING AN ABNORMAL SWITCHING, USER CHANGED THE
                    CHARACTERISTICS OF TERMINAL ( HSCTTP STATE TABLE, NIP 
                    GOES FROM STATE 6 TO STATE 11), THEN NVF SENT CR/RCN/A
                    FOR THE CONNECTION. 
         SOLUTION - IN STATE 11, NIP SHOULD HONOR CR/RCN/A FROM NVF BY
                    RE-SENDING CR/RCN/R TO SWITCH CONNECTION BACK TO THE
                    PRIMARY APPLICATION AND STAY IN THE SAME STATE SO WHEN
                    THE CR/RCN/N FROM NVF A TCH/TCHAR/U WILL BE SENT. 
  
         LTN       87/02/17       XSTTP 
  
 NA50592  PROBLEM:  
          PIP WAS LOOPING IN THE ERROR PROCESSOR 2IE AFTER RECEIVING A
          BAD PRU INPUT BLOCK FROM AN MDI (ON A PRU CONNECTION). THE
          BLOCK PROTOCOL ERROR IS ANOTHER STORY. HOWEVER PIP LOOPED IN
          2IE BECAUSE IT WAS WAITING FOR THE REAL-TIME CLOCK TIMER TO 
          EXPIRE. BUT PIP WAS NOT READING UP THE TIMER EACH TIME TO 
          CHECK IT IF THE FE WAS AN MDI.
          SOLUTION: 
          PIP HAS BEEN MODIFIED TO READ UP THE TIMER EACH TIME BEFORE 
          TESTING WHETHER IT HAS EXPIRED. 
  
          CMP    03/04/87    PIP
 NA50603 PROBLEM  - NIP LIMITS THE NUMBER OF ASYNC  SMS TO BE QUEUED
                    FOR AN APPLICATION TO 500.  THIS CAN CAUSE SOME 
                    PROBLEM BECAUSE SOME APPLICATION MAY REACH THIS 
                    LIMIT UNDER NORMAL OPERATION. 
         SOLUTION - RAISE THE LIMIT TO 2000.
         TET    03/24/87    AWLDEFS 
 NA50606  PROBLEM:  
          NAM WAS BEING ABORTED BY 1MS WITH THE MESSAGE *INVALID FILE 
          NAME XXXXX  AT YYYYY.* . THE PROBLEM WAS TRIGGERED BY PIP 
          OVERWRITING THE FET FILE-NAME PRIOR TO ISSUING A CIO REQUEST
          DURING PRU OUTPUT. THE CAUSE OF THE PROBLEM IS THE FACT THAT
          MONITOR INCREASES NEGATIVE FIELD LENGTH (EG. TO PLACE A NEW 
          FNT ENTRY THERE) OF NAM WITHOUT SETTING THE STORAGE-MOVE FLAG 
          IN THE CONTROL POINT AREA.  PIP CHECKS THIS FLAG TO DECIDE IF 
          A MONITOR PAUSE FUNCTION IS NEEDED, AND THIS PAUSE FUNCTION,
          IF ISSUED, WILL RESET (RA) AND THE R-REGISTER.  BUT MONITOR IS
          INCREASING NFL WITHOUT MOVING NAM'S ORIGIN, SO IT IS NOT
          SETTING THE STORAGE-MOVE FLAG (ALTHOUGH IT SHOULD BE).
          CONSEQUENTLY PIP IS NOT ISSUING THE PAUSE FUNCTION, SO PIP IS 
          WORKING WITH AN INVALID (RA). THE RESULT IS THAT, IN THIS 
          PARTICULAR CASE, AN FNT ORDINAL OF 511B IS GIVEN TO PIP BY NAM
          WHILE THE RA=400500B. THE NFA MACRO GENERATES AN ADDRESS FOR
          THIS FNT OF 377767B, WHICH MEANS THAT A SUBSEQUENT *CRD* WILL 
          NOT HAVE BIT 17 OF THE A-REGISTER SET. THUS THE HARDWARE WILL 
          NOT ADJUST THE ADDRESS BY USE OF THE R-REGISTER PRIOR TO
          READING IT UP. SO THE WRONG WORD IS READ. 
  
          SOLUTION: 
          PIP HAS BEEN MODIFIED TO ISSUE A PAUSE FUNCTION PRIOR TO ANY
          USE OF THE NFA MACRO. THIS SHOULD ENSURE THAT IT IS WORKING 
          WITH THE MOST UP-TO-DATE (RA) AND R-REGISTER VALUES. THIS IS
          NOT COMPLETELY VALID IF NO INTERLOCK AS PROVIDED BY THE 
          STORAGE MOVE FLAG IS USED, BUT NFL IS ONLY EVER INCREASED 
          WHILE NAM IS AT A CONTROL POINT IE. IT IS NOT DECREASED.
          THUS THE RA AND R-REGISTER VALUES WILL AT LEAST BE WITHIN 
          NAM'S FL AND WILL READ THE CORRECT WORD.
  
          CMP    06/25/87   PIP 
  
 *L700*    ************************************************ 
NA5B821   NVF FAILED
  
          AN  INVALID  TERMINAL  CLASS  SENT BY NIP CAUSED NVF TO ABORT.
          NVF IS MODIFIED SO THAT INSTEAD OF ABORTING, IT WILL ISSUE THE
          MESSAGE  "INVALID  TERMINAL  CLASS  TRANSITION"  AND  END  THE
          CONNECTION. 
  
          J. YANG        08/07/87       NVFTRVD 
  
 NA5B823  PROBLEM  - NETIO DOES NOT HAVE ENTRY POINT FOR QTREL AND
                     QTLGS. THIS CAUSES SOME QTRM APPLICATIONS TO 
                     GET UNSATISFIED EXTERNAL ERRORS WHEN TRYING
                     TO LOAD FROM NETIO.
  
          SOLUTION - ADD ENTRY POINT FOR QTREL AND QTLGS IN NETIO.
  
          TET            08/05/87       NETREL, NETLGS
  
 NA5B833  *COLLECT* DOES NOT PICK UP FILES CREATED BY *FTP*.
  
          *COLLECT* HAS BEEN CHANGED TO PICK UP THE FOLLOWING FILES 
          CREATED BY THE *FTP* PROGRAMS - DDNS=DD, FTPI=TI, FTPS=TS.
  
          RWH            09/17/87       CLT=INI 
  
  NA5B843 - UNRECOGNIZED SUPERVISORY MESSAGE FROM NAM/NVF.
  
            THE NEW SM HAS BEEN ADDED TO THE COMMON DECK SMAPPFC IN 
            NVF AND NVFDDNT HAS BEEN MODIFIED TO IGNORE THE NEW SM. 
  
            J. YANG    12/04/87      SMAPPFC,NVFDDNT
 NA5B856  CHANGES TO *COLLECT* FOR FTP/NOS FULL RELEASE.
  
          THIS MODSET CHANGES *COLLECT* TO DELETE THE *DD* FILE 
          DESIGNATOR (DDNS IS NO LONGER PART OF FTP/NOS), AND 
          CHANGES THE *TI* DESIGNATOR FOR FTPI TO *PI*. 
  
          RWH            3/15/88        CLT=INI 
  
 NA5B859   THIS MOD IMMPLEMENTED THE FEATURE SPECIFIED IN DAP S5440.
           ALLOWS NIP TO SUPPORT THE FTP CLIENT.
           LTN          88/04/11            SMAPPDEF,SMDEF,NIPDEF 
                                            ACB,SMNIP,HPPUT,HHIR
                                            HCONCBU,HSFCINA,
                                            HPNOFF,HAPFAIL,XABTAPP, 
                                            HPSHISD,XSACB,XSTTP 
  
 NA5B860   THIS MOD INTRODUCES A NEW WORKLIST THAT WILL BE PROCESSED
           BY NIP, RESET WORKLIST (OP=12). THIS WORKLIST WILL RESET 
           THE OUTSTANDING WORKLIST IN NIP. 
           LTN          88/04/12       NP$NWL,NP$CODE,NETRR 
  
 NA5B861   NIP WILL NOT HANG UPON RECEIVING SCP RETURNED REASON CODE OF 
           63B. NIP WILL JUST ONLY DAYFILE IT AND CONTINUE TO PROCESS.
           LTN          88/04/27       OSCCALL
  
 NA5B863   APPLICATION GETS ABORTED WITH "NOT YET NETTED ON" MESSAGE. 
           NETTRR SHOULD NOT WRITE RECORD HEADER SINCE APPLICATION FTPI/
           FTPS WILL NOT WRITE EOR BEFORE CALLING NETRR.
           LTN               88/04/18       NETRR 
  
 NA5B866   WHEN NIP PROCESSES NETRR WORKLIST, IT SHOULD CLEAR THE 
           NETWAIT FLAG IN AT IN CASE THE PREVIOUS WORKLIST WAS A 
           NETWAIT WORKLIST.
           LTN          88/04/28            HHIR
  
 NA50623  A QUEUE FILE DESTINED FOR A VE LID HANGS QTF. 
  
          AFTER REJECTED 4 TIMES (MAXIMUM RETRY LIMITS) OF A QTF OUTCALL
          REQUEST  TO  AN  INVALID  LID,  NVF  REJECTED  ALL QTF OUTCALL
          REQUESTS TO ANY LID.  THE MAXIMUM RETRY LIMIT IN  NVF HAS BEEN
          CHANGED  FROM  4  TO  128.
  
          J. YANG        08/03/87       TXTANVF 
  
 NA50631- NVF DELETES THE RML TABLE FOR USER DISCONNECTED AT PID PROMPT 
  
          IF  A  USER IS VALIDATED FOR A SINGLE LOGIN AND IF THE USER IS
          CURRENTLY  LOGGED  IN TO ONE TERMINAL AND TRIES TO LOG IN TO A
          SECOND TERMINAL, AND BEFORE RECEIVING THE MESSAGE OF "MULTIPLE
          LOGIN  PROHIBITED",  THE  SECOND  CONNECTION  IS  BROKEN,  NVF
          DELETES THE RML TABLE ENTRY  FOR  THE  1ST  LOGIN  WHICH STILL
          HOLDS THE CONNECTION. 
  
          SUBROUTINE NVFTETC IS MODIFIED TO FIX NVF.
  
          J. YANG        09/03/87       NVFTETC 
  
 NA50632  FAMILY COUNT IS NOT DECREMENTED IF A BREAK IS ENTERED AT
          THE PID PROMPT. 
  
          NVFTBRK  IS  MODIFIED  SO  THAT IF A USER RESPONDS THE THE PID
          PROMPT WITH A USER BREAK, FAMILY  COUNT  WILL  BE  DECREMENTED
          BEFORE THE FAMILY PROMPT IS REISSUED. 
  
          J. YANG        09/03/87       NVFTBRK 
  
 NA50633  NVF INCORRECTLY DECREMENTS THE FAMILY COUNT ON INVALID LOGINS 
  
          IF  A  LOGIN IS INVALID, USER_INDEX FIELD OF PTAC TABLE SHOULD
          BE CLEARED AFTER THE 2ND CPM56 CALL IS RETURNED.
  
          J. YANG        09/03/87       NVFTVVD 
  
 NA50635  NVF ABORTS WITH NVFVDCD - ERRONEOUS READLS CALL.
  
          THIS MOD FIXES VCBFILE PROBLEM THAT WAS CAUSED BY WRITEF CALL.
  
          J. YANG        09/18/87       NVFIIVF 
  
*COMIPLE HISTORY
 NA50636  NVF'S VCBFILE IS NOT BIG ENOUGH TO HOLD MORE THAN 750 
          CONNECTIONS.
  
          THIS MOD DOUBLES THE VCBFILE SIZE FOR NVF.
  
          J. YANG        09/18/87       TXVCBNV 
  
  NA50638 - PASSWORD EXPIRATION MSG. NOT WRITTEN IF INITIAL LOG-IN
            WAS IN ERROR. 
  
            PASSWORD EXPIRATION MESSAGE FLAG NEEDS TO BE RESET
            BEFORE REISSUING THE FAMILY PROMPT. 
  
            J. YANG    11/02/87      NVFTPUV
 NA50660  PROBLEM:  
          THE CODE IN PSR NA50606 WAS CAUSING SEVERE PERFORMANCE
          DEGRADATIONS IN NAM. THIS WAS DUE TO THE FACT THAT EACH CALL
          TO TEST IF A PAUSE WAS NEEDED, WAS ACTUALLY ISSUING A PAUSE.
          ROUTINE FTN IN PP RESIDENT (PPR) WAS BEING CALLED WITH THE
          PAUSE FUNCTION IN THE A-REGISTER, INSTEAD OF 0. THIS CAUSES A 
          PAUSE MONITOR REQUEST TO ISSUED EACH TIME WHETHER NEEDED OR 
          NOT. THE ORIGINAL INTENTION OF NA50606 WAS HOWEVER TO ALLOW 
          THE CODE IN FTN TO DECIDE WHETHER A PAUSE FUNCTION WAS NEEDED.
          IF IT WAS NOT, FTN SIMPLY RETURNS AFTER UPDATING RA AND FL. 
          HOWEVER TO USE THIS FACILITY OF FTN, IT MUST BE CALLED WITH 
          0 IN THE A-REGISTER.
  
          SOLUTION: 
          PIP HAS BEEN MODIFIED TO ISSUE THE CALL TO FTN WITH A 0 IN
          THE A-REGISTER. 
  
          CMP    04/14/88   PIP 
  
 *L716*    ************************************************ 
 FS5162   THIS IS THE NIP/AIP CODE FOR THE DOWNLINE MESSAGE BUFFERING 
          FEATURE.  THIS FEATURE CAN BE ENABLED TO IMPROVE THROUGHPUT 
          OF THE AIP/NIP INTERFACE BY SENDING MULTIPLE LARGE NETWORK
          DATA BLOCKS PER SCP CALL.  THE COMPLETE DETAILS OF THIS 
          FEATURE ARE DOCUMENTED IN DAP S5162.
          PAM     88/06/20     NP$NWL,NP$CODE,NP$STAT,NP$MODE,NETFUNC,
                               NETON,NP$ERR,NETPUTF,NP$PUT,NP$SEND, 
                               NETGETF,NP$SN,NP$GSM,NP$RESP,NETCHEK 
          LTN     88/06/20     NWLHEAD,NWLNTRY,HWLP,HPPUTQ,SKENIP 
  
 FS5500  THIS FEATURE ENHANCE THE UDATA KEYWORD DEFINITION IN 
         NDL OUTCALL STATEMENT. 
  
         IF UDATA SPECIFIED IS ENCLOSED IN DOUBLE QUOTES, NDLP
         CONVERTS THE ASCII STRING TO THE HEXADECIMAL REPRESENTATION
         OF THE STRING. 
  
         CC   06/24/88
 NA5B733  PROBLEM - TYPO IN CS COMMAND HELP PAGE OF K-DISPLAY.
          SOLUTION - CORRECT THE TYPO (CHANGE "BYE" TO "BY"). 
  
          PAM     88/02/01     CSCPHT 
  
 NA5B845  PROBLEM  - PIP NEEDS TO BE CHANGED TO SUPPORT THE MCI SPECIFIC
                     CHANNEL CONNECTION PROTOCOL. 
          SOLUTION - PIP HAS BEEN CHANGED TO RECOGNIZE THE NEW MCI
                     STARTING STATE AND TO PERFORM PROTOCOL VERSION 
                     VERIFICATION AND CLEAN UP IN THIS STATE. 
          EG     12/14/87    PIP
 NA5B846  PROBLEM  - PIP NEEDS ADDITIONAL CODE TO SUPPORT THE MCI 
                     SPECIFIC CHANNEL CONNECTION PROTOCOL.
          SOLUTION - PIP HAS BEEN CHANGED TO SEND NORMAL OPERATION
                     TRANSPARENT FUNCTION, TO SUPPORT MCI PROTOCOL
                     VERSION 4, TO SEND THE REQUEST PROTOCOL VERSION
                     TRANSPARENT FUNCTION INSTEAD OF THE SET PROTOCOL 
                     VERSION TRANSPARENT FUNCTION IF IT IS VERSION 4, 
                     AND TO RECOGNIZE THE NEW FLOW CONTROL BIT IN THE 
                     MCI GENERAL STATUS.
          EG     12/17/87    PIP
 FS5378           CHANGES TO DETECT A PACER EQUIPMENT BASED ON THE
                  CHANNEL PROTOCOL VERSION REPORTED BY A MDI. 
                  RMK    5/25/88     PIP
  
 NA5B858  PROBLEM  - THE NOS SCHEDULER ENHANCEMENTS FEATURE HAS CAUSED A
                     CHANGE IN THE STORAGE MOVE PP INTERFACE.  PIP NEEDS
                     TO BE CHANGED TO SUPPORT THE CHANGED STORAGE MOVE
                     INTERFACE. 
          SOLUTION - PIP HAS BEEN CORRECTED TO USE THE CHANGED STORAGE
                     MOVE.  THIS PIP CODE IS DEPENDENT ON THE SCHEDULER 
                     ENHANCEMENT NOS CODE AND CANNOT BE BUILT FOR A NOS 
                     SYSTEM WHICH DOES NOT CONTAIN THE NOS CODE.
          EG     03/23/88    PIP
 NA5B867   INCREASE THE LENGTH OF CON/REQ/SM TO 16 WORDS LONG.
           LTN          88/04/28       SMAPDEL,SMAPPL 
  
 NA5B870  PROBLEM:  
          PIP ISSUES UNNECESSARY PRLM MONITOR FUNCTIONS AT A HIGH 
          RATE OF SPEED, WHICH CAN LEAD TO SYSTEM PERFORMANCE 
          DEGRADATION.  THIS IS BECAUSE PIP DOES NOT CHECK FOR
          STORAGE MOVE REQUESTED CORRECTLY. 
  
          SOLUTION: 
          CHANGE PIP TO CALL PPR SUBROUTINE FTN WITH A FUNCTION CODE
          OF ZERO INSTEAD OF WITH A FUNCTION CODE OF PRLM WHEN
          PAUSING FOR STORAGE MOVE.  REMOVE CODE FROM PIP WHICH 
          ATTEMPTS TO DETERMINE IF A PAUSE IS NECESSARY, BECAUSE THIS 
          CHECK IS AUTOMATICALLY DONE BY PPR SUBROUTINE FTN WHEN
          CALLED WITH A FUNCTION CODE OF ZERO.
  
          NOTE: 
          IF MODSET NA5B858 IS ALSO INSTALLED, THIS MODSET SHOULD 
          BE INSTALLED AFTER NA5B858.  THIS MODSET COMPLETELY DELETES 
          THE CODE WHICH NA5B858 MODIFIES, AND THUS REMOVES THE NEED
          FOR MODSET NA5B858. 
  
          PCS    05/05/88    PIP
  
 NA5B817  THIS PSR FIXES A HOLE IN THE PIP-1DL PROTOCOL USED BY PIP TO
          LOAD ITS OVERLAYS THROUGH PIP'S PP MESSAGE BUFFER, PRIOR TO 
          LOADING THESE OVERLAYS INTO NAM'S FIELD LENGTH. THE HOLE IN 
          1DL IS FIXED BY NS2F781, WHILE THE CORRESPONDING FIX FOR PIP
          IS DONE HEREIN. 
          **** NOTE ****  THESE TWO PSRS MUST BE INSTALLED TOGETHER.
  
          CMP  07-30-87  PIP
  
 NA5B876    THIS MOD IMPLEMENTS THE FEATURE DESIGNED BY DAP NUMBER
            S5378 (PIP SUPPORT FOR PACER DAP). IT MODIFIES THE K-DISPLAY
            TO DISPLAY THE PROTOCOL VERSION NUMBER AND CHANGE THE HOST
            NUMBER FROM 2 DIGITS TO 3 DIGITS. 
            LTN              88/05/24            NIPTXT,KDISLN
  
 NA5B879  PROBLEM  - NVF DOES NOT ALWAYS DECREMENT THE INCOMING CONN. 
                     COUNT FOR AN APPLICATION WHEN A CR/CB IS RECEIVED. 
                     AS A RESULT, NVF MAY REJECT AN INCOMING CONNECTION 
                     FOR AN APLLICATION ALTHOUGH THE APPLICATION DOES 
                     NOT ACTUALLY HAVE THE MAXIMUN INCOMING CONNECTIONS.
  
          SOLUTION - MODIFY NVF TO DECREMENT THE COUNT CORRECTLY. 
  
          TET   03/13/86    NVFATAC 
 NA50646  PROBLEM:  
          PSR NA5B770 CAUSED CERTAIN FILES WHEN PRINTED VIA AN NPU (AS
          OPPOSED TO AN MDI) TO CAUSE THE NPU TO FAIL WITH HALT CODE 13.
          NA5B770 WAS IMPLEMENTED TO DO TRAILING BLANK DELETION ON PRINT
          FILES SO THAT TRAILING COLON PROTECTION COULD NEVER CAUSE AN
          EXTRA LINE FEED. THE CODE COUNTS ALL SPACES AND DOES NOT
          OUTPUT THEM UNTIL A NON-BLANK CHARACTER IS DETECTED, OR EOL 
          IN WHICH CASE THEY ARE DISCARDED. IF THE BLANKS BEING COUNTED 
          SPAN A BLOCK BOUNDARY, THEN THEY MAY NOT BE OUTPUT UNTIL THE
          NEXT BLOCK. BUT THE ORDER WORD SENT TO THE NPU PRIOR TO 
          SENDING THE NEXT BLOCK WILL NOT INCLUDE THE COUNT OF THESE
          EXTRA SPACES. THIS MAY CAUSE THE NPU TO ABORT WITH A HALT-13. 
  
          SOLUTION: 
          THE CODE IS MODIFIED TO NOT ATTEMPT ANY TRAILING BLANK
          DELETION FOR NPUS. IT IS NOT NECESSARY ANYWAY FOR NPUS
          BECAUSE ALL THE NPU TIPS DO THIS FUNCTION AS WELL IE
          TRAILING BLANK DELETION IS ONLY NECESSARY FOR MDI/URI'S.
  
          CMP 06/88  PIP. 
 NA5B880  DEFAULT NUMBERS OF PRU BUFFERS (4,8,4) ARE TO SMALL,
  
          SOLUTION: THIS MOD CHANGES THE DEFAULT VALUES INTERNALLY. 
                    SITES COULD RESET THEM BY EDITTING THE N1, N2, N3 
                    PARAMETERS OF NIP CONTROL CARD STATEMENT IN THE 
                    NAMSTRT FILE. 
          CC 88/08/02 
 NA5B881  PROBLEM:  
          AN MDI WAS HUNG AND TURNING ITS EST OFF MADE NO DIFFERENCE. 
          THE PROBLEM WAS CAUSED BY A PRU INPUT STREAM ON ANOTHER NPU 
          BUT ON THE SAME PIP, THAT HAD HUNG FOR SOME REASON (EG TRACK
          LIMIT). THIS INPUT STREAM HAD ALL THE AVAILABLE PRU BUFFERS 
          ASSIGNED TO IT. THE RESULT WAS THAT PRU OUTPUT STREAMS ON 
          THE MDI STAYED IN A STATE WAITING FOR BUFFERS AND NO STATE
          ADVANCING WAS POSSIBLE. WHEN THE MDI WAS OFFED, THE SAME
          PROBLEM APPLIED. THUS NAM COULD NOT RELEASE THE PCNBS AND 
          THUS THE OFFING DID NOTHING.
          SOLUTION: 
          THE PROBLEM OF THE HUNG MDI WILL BE FIXED BY ALTERING PIP 
          TO NOT ASSIGN ALL BUFFERS TO INPUT. PIP ALREADY NEVER ASSIGNS 
          ALL BUFFERS TO OUTPUT. IT WILL BE ALTERED TO NOT ASSIGN THE 
          LAST AVAILABLE BUFFER TO INPUT IF ALL BUFFERS WOULD THEN BE 
          ASSIGNED TO INPUT AND THE NUMBER CURRENTLY ASSIGNED EQUALS
          THE MAXIMUM THAT CAN BE ASSIGNED. 
          THE PROBLEM OF THE HUNG INPUT STREAM IS ANOTHER MATTER. 
          NOTE:- THIS PSR DEPENDS ON NA50646 - ONLY FOR THE SPACE IN PIP
                 THAT IS CREATED BY THAT PSR. 
  
          CMP 06/88  PIP. 
  
 NA5B884  FOR INTERHOST A-A CONNECTION, THE SENDER DOESN'T
          GET THE CALLED APPLICATION NAME IN CON/REQ. 
          CC 88/07/22 
 NA5B888  CHANGE THE EST SCAN TIME TO 2000 MS FROM 10000 MS.
          LTN    88/08/15    XCHKCET
  
 NA5B891  IF AN APPLICATION IS USING THE DOWNLINE BUFFERING 
          FEATURE, AND IF THE APPLICATION IS IN PARALLEL MODE,
          UNDER CERTAIN CONDITIONS, NIP WILL ABORT THE APPL.
          THE CONDITIONS ARE:  AIP HAS COLLECTED THE DOWNLINE 
          MESSAGES IN THE APPL BUFFER, NP$SEND HAS BEEN CALLED
          TO BUILD A PUTQ ENTRY IN THE WORKLIST AND SEND IT 
          TO NIP, BUT NIP IS BUSY AND NEVER PICKS UP THE
          WORKLIST.  THE APPL CALLS NETCHEK, WHICH CALLS NP$SEND
          TO RESEND THE BUFFER.  BUT NP$SEND GETS CONFUSED AND
          COPIES 2 WORDS OF THE APPL BUFFER INTO THE WORKLIST,
          AND SO WRITES OVER THE PUTQ ENTRY.  THIS CAUSES NIP 
          TO GET A "BAD ENTRY WORD COUNT" AND ABORT THE APPL. 
  
          TO FIX THIS, AIP WILL KEEP TRACK OF A RESEND FLAG,
          AND IF THIS FLAG IS TRUE, IT WILL RESEND WHATEVER IS
          IN THE WORKLIST, AND NOT COPY WORDS OVER FROM THE 
          APPL BUFFER.
          PAM     88/08/03     NP$MODE,NETCHEK,NP$SEND
 NA5B895  PROBLEM - WHEN THE DOWNLINE BUFFER FEATURE IS TURNED ON,
                    A USER SHOULD NOT BE ALLOWED TO CALL NETGTFL. 
                    THERE IS NO CHECK IN AIP, HOWEVER, TO PREVENT 
                    THIS. 
  
          SOLUTION - IN ROUTINE NETGETF, FOR THE ENTRY POINT NETGTFL, 
                     CHECK IF THE DOWNLINE BUFFER FEATURE IS TURNED 
                     ON AND IF SO, ISSUE AN ERROR AND ABORT THE 
                     APPLICATION. 
  
          PAM     88/08/25     NETGETF
  
 NA5B897  SINCE NIP NOW WILL IGNORE THE REASON CODE 63B FROM
          OPERATING SYSTEM (SHORT TERM CONNECTION IS GONE), NIP 
          WILL TREAT IT AS APPLICATION HAS GONE AWAY. 
          LTN    88/09/29    HPAWL,HPWAIT,HWRTDA,XABTAPP,XSACB, 
                             XSAPP
  
 NA5B898  THE PIP/PACER SUPPORT CODE ALTERED THE MAXIMUM NUMBER OF
          FRONT-ENDS PIP CAN SUPPORT FROM 4 TO 3. THIS IS NOT 
          ACCEPTABLE. 
  
          CMP  09/88  PIP.
  
 NA5B899  THIS CODE CHANGES THE COPYRIGHT STATEMENT IN THE NVF
          BANNER TO 1988. 
  
          PAM     88/10/04     TMSGNVF
  
  NA50572 - NVF SECURITY CODE ACTS AS UNSECURITY CODE IN SOME CASES.
  
            THE SIZE OF BLANKING MASK FOR LOGIN STRING HAS BEEN CHANGE
            FROM THE SIZE OF INPUT STRING TO THE MAXIMUN OF 60 CHARS. 
  
            J. YANG   01/15/88       NVFTVVD
  
 NA50649  WHEN THE LOGICAL LINK WENT DOWN, PRU CONNECTION WAS BEING 
          TERMINATED, WAITING FOR PIP TO RESPOND. MEANWHILE LOGICAL 
          LINK CAME BACK UP, AND LLCBWOF FLAG WAS CLEARED.
          NPREGCP CALLED RELCONN TO DISCONNECT THE PRU CONNECTIONS, 
          AND GOT THE NCSTTP ERROR WITH STATE 12 AND TRIGGER 8. 
          SOLUTION IS TO IGNORE LLFAIL TRIGGER IN THIS CASE.
  
          CC/LTN    01/22/88       XSTTP
  
 NA50651  USERS ARE GETTING APPLICATION BUSY WHEN APPLICATION STILL 
          HAVE ENOUGH CONNECTIONS.
  
          NVF DOESN'T DECREMENT THE RACN IF CR/CB COMES IN ON A 
          LOAN CONNECTION.
          NVF CHECKS PTS$STATE OF LSA, BUT LSA WAS NEVER SAVED IN 
          IN VCB. 
  
          THE SOLUTION IS TO USE PTA$LCF, WHICH IS TRUE ONLY IF 
          PTS$STATE IS LSA. 
  
          CC  88/03/16,88/04/07 
 NA50652  AT NOS 2.4.3 NOS TRANSMITTED A NEW APPLICATION NAME OF MAIL 
          EQUIVALENCED ON THE IAF APAW BIT TO PERMIT USE OF THE QTRM
          MAIL APPLICATION WITHOUT REVALIDATION OF ALL IAF USERS.  NVF
          NO LONGER WILL ALLOW MANDATORY, UNPROMPTED APPLICATION
          CONNECTION TO IAF AS A RESULT.  THIS CODE SPECIAL CASES THE 
          MAIL APPLICATION EQUIVALENCE IN SETTING THE APPLICATION UNIQUE
          FLAG (AST$BNUF) FOR IAF TO ALLOW IAF AS A MANDATORY APPLICATION.
          SCC    88/01/28    NVFIAST
  
  NA50664 NIP CAN LOOSE UPLINE MESSAGES ON AN INBOUND BUFFER SWITCH 
  
  PROBLEM  - NIP IS NOT CORRECTLY CHECKING FOR BUFFER EMPTY BEFORE
             SWITCHING INBOUND BUFFERS. 
  
  SOLUTION - MODIFY NIP TO CORRECTLY CHECK FOR INBOUND BUFFER EMPTY 
             BEFORE SWITCHING INBOUND BUFFERS.
  
          RMF                88/08/03              NEIB 
                                                   PURGREG
  
 NA50665 NIP HAS PROBLEM SUPPORTING SIXTEEN FRONT ENDS. 
         THE PROBLEM IS THE FIELD FOR THE CURRENT NBT 
         ENTRY INDEX IS TOO SMALL. WITH SIX BITS, IT COULD
         ONLY SUPPORT UP TO TEN FRONT ENDS. 
         SOLUTION: TO INCREASE THE NBTCCI FIELD TO 9 BITS.
         RMF   88/08/08 
 NA50674  PROBLEM:  
          FILES WERE GETTING CORRUPTED WHEN TRANSFERRED BETWEEN 2 CYBERS
  
          SOLUTION: 
          NA5B760 HAS A BUG IN IT SUCH THAT IF THE FILE TRANSFER IS DONE
          USING MORE THAN 1 PRU PER PRU BUFFER, THEN MORE THAN JUST THE 
          UNUSED BITS MAY BE CLEARED IN THE FINAL BUFFER OF THE FILE
          TRANSFER. THE PROBLEM IS DUE TO THE CODE NOT PROPERLY 
          DETECTING THE LAST PORTION OF THE TRANSFER FROM PIP OF THE
          LAST BUFFER.
  
          CMP  09/88  PIP.
  
 *L739*    ************************************************ 
 NA5B885  THIS CODE DELETES THE REFERENCE TO JOVEC IN THE NIP IMS,
          AS JOVEC IS NO LONGER SUPPORTED.
          PAM     09/28/88     NIP
  
 NA5B910  PROBLEM:  
          CODE INSERTED BY NA5B196 CAN CAUSE A DEADLOCK AS FOLLOWS: 
          - PIP INPUTS PRU BLOCK AND QUEUES TO PCNB 
          - NPU GOES INTO REGULATION AND WILL NOT ACCEPT A BACK 
          - STATE PROCESSOR SPIQ WHICH IS TO PROCESS THE QUEUED BLOCK,
            EXITS TO ATTEMPT TO OUTPUT A BACK (PER NA5B196) 
            BUT FAILS (REGULATION). CURRENTLY QUEUED BLOCK IS NOT 
            PROCESSED.
          - FURTHER BLOCKS COME IN UNTIL ALL BUFFERS ARE USED UP VIA
            THE ABOVE SCENARIO
          - NO BUFFERS CAN BE RELEASED BECAUSE NO PROCESSING IS DONE
            ON THE QUEUED BLOCKS BECAUSE A BACK IS OUTSTANDING. 
          SOLUTION: 
          PIP HAS BEEN MODIFIED TO COUNT THE NUMBER OF QUEUED BUFFERS 
          ON A PCNB. IF THIS COUNT BECOMES 7 OR MORE, PIP WILL BYPASS 
          OUTPUTTING A BACK AND PROCESS THE FIRST QUEUED BUFFER. THIS 
          WILL REDUCE THE QUEUED BUFFER COUNT AND RELEASE A BUFFER. 
  
          CMP  10/88  PIP 
 NA5B911  THE MAXIMUN A-A RETRY COUNT (AL) IN THE NVF CONTROL STATEMENT 
          IS NEVER USED. THE HARD CODED VALUE MATRY$ IS USED INSTEAD. 
          THIS PSR MODIFIES NVF, SO IT USES THE AL VALUE FOR
          APPLICATION RETRY COUNT. THE RANGE IS BETWEEN 1 AND 256.
          DEFAULT VALUE IS 128. 
          CC     89/03/31       NVFAIAP 
 NA5B917 THE COPYRIGHT BANNER SHOULD BE CHANGED TO 1987.
  
         CC     02/17/89     CRCOM, TMSGNVF 
  
 NA5B918  PROBLEM  - NIP DELAYS DELIVERY OF QUEUED DATA ANYWHERE FROM 
                     200 TO 500 MILLESECONDS. 
          ANALYSIS - NIP PROCEDURE XEXEC WILL WAIT FOR DATA FROM PIP OR 
                     A SCP WORKLIST OR 500 MILLESECONDS BEFORE EXECUTING
                     ITS MAIN LOOP EVEN IF IT HAS DATA QUEUED FOR AN
                     APPLICATION PROGRAM WITH AN OUTSTANDING WORKLIST.
          SOLUTION - NIP PROCEDURE XEXEC HAS BEEN CORRECTED TO ALSO 
                     CHECK THE GLOBAL VARIABLE MSG$AN BEFORE DETERMINING
                     IF IT SHOULD GO INTO ITS RECALL LOOP.
          EG     12/08/88    XEXEC
 NA5B922  THIS MOD ADD THE VTP VERSION NUMBER IN THE CON/REQ/R MESSAGE. 
          THE VERSION NUMBER IS PASSED BY CDCNET TO NIP THROUGH ICN/TE/R. 
          NIP THEN PASSES IT TO NVF BY CR/ITE/R. NVF PASSES BACK TO NIP 
          BY CR/SWH/R. NIP THEN PASSES IT TO APPLICATION BY CON/REQ/R.
  
          CC   89/02/09   SMAPPL,SMNIP,SMNVF,HCRITER
                          TEXTNVF,TXTANVF 
                          NVFTACC,NVFTDSP,NVFTITE,NVFTRLC,NVFTRVD 
  
 NA5B927  PROBLEM  - NIP FAILED WITH A CPU ERROR EXIT WHEN THE 16TH ND
                     EST ENTRY WAS TURNED ON. 
          ANALYSIS - MANY OF NIP'S TABLES USE A FOUR BIT FIELD TO 
                     CONTAIN THE FRONT END INDEX.  HOWEVER, THE FRONT 
                     END INDEX CAN HAVE A VALUE FROM 1 TO 16.  WHEN 
                     THE 16TH ND EST ENTRY WAS TURNED ON, NIP TRIED TO
                     STORE THE FRONT END INDEX VALUE OF 16 INTO THESE 
                     FOUR BIT FIELDS, WHICH RESULTED IN A VALUE OF ZERO 
                     BEING STORED IN THE FIELD INSTEAD.  WHEN NIP USED
                     THE BAD FRONT END INDEX VALUE STORED IN THESE FIELDS,
                     THE RESULT WAS A CPU ERROR EXIT. 
          SOLUTION - NIP HAS BEEN CORRECTED TO USE A RANGE OF 0 TO 15 
                     FOR THE FRONT END INDEX INSTEAD OF 1 TO 16.
          EG     07/25/89    MAJPTR, NFOB, NLOBCH, NLOPIP, NPESTOF, 
                             NPREGCP, XCHKCET 
 NA5B935  PROBLEM  - PIP CAN SEND A PRU DATA BLOCK TO THE MDI MUCH
                     LARGER THAN WHAT THE MDI WAS EXPECTING.  THE 
                     RESULT IS THAT THE MCI CHANNEL IS RESET. 
          ANALYSIS - THE PROBLEM OCCURS WHEN PIP IS TRYING TO 
                     TRUNCATE TRAILING BLANKS AND ENCOUNTERS
                     HUNDREDS OF CONTIGUOUS BLANK CHARACTERS. 
          SOLUTION - PIP HAS BEEN CORRECTED TO ONLY TRUNCATE
                     TRAILING BLANKS IF THE NUMBER OF TRAILING
                     BLANKS DOES NOT EXCEED 255 CHARACTERS. 
          EG     09/05/89    PIP
 NA50657   THE PASSWORD EXPIRATION MESSAGE IS UNGRAMMATICAL.
           SAME CODE WAS IMPLEMENTED FOR NOS AT L700. 
  
           MEVM/CC   89/05/18.    NVFTDSP 
  
 NA50671  NVF NETON MESSAGE DOESN'T HAVE THE NIN IN IT. 
          SINCE NVF'S NETON IS A SPECIAL CASE, NIP FORGOT TO
          PUT THE NIN IN THE NETON APPLICATION WORKLIST.
          CC   89/02/10 
  
 NA50689   WITH ONLY DEBUG DEFINED DURING THE AIP (NETIO) BIULD,
           ROUTINE NETOFF WILL GET COMPILATION ERROR. 
           SOLUTION IS TO JUGGLE THE DEF FOR STAT AND DEBUG.
  
           CC 89/05/17     NETOFF 
  
 NA50692   QTRM DOESN'T PASS THE CONNET (CDCNET CONNECTION FLAG) TO 
           THE APPLICATION. 
           THE SOLUTION IS TO PUT THE CONNET FLAG IN THE NIT TABLE. 
           THERE ARE SEVERAL BITS AVAILABLE. THE BIT USED IN THIS CODE
           IS BIT 47 IN THE 5TH WORD (WORD 4 IF START WITH WORD 0) IN 
           IN CONNECTION ENTRY. 
           CC 89/03/13    QTRMNIT,QTGET 
 NA50693  NIP NEVER RELEASES BUFFERS WITH NETGETF REQUESTS. 
          AND THE MAXIMUM FIELD LENGTH IS REACHED.
          SOLUTION: RELEASE THE BUFFER IN PROC NETGTF.
          CC 89/01/16 
 NA50694   L716 PSR NA5B879 DECREMENTS AST$ICCN ONCE TOO MANY. AST$ICCN 
           BECOMES NEGATIVE, AND THE A-A CONNECTION IS NEVER ESTABLISHED. 
           SOLUTION IS TO DELETE SOME LINES IN NA5B879. 
  
           NOTE - THIS MOD ONLY APPLIES TO L716.
  
           CC 89/03/01    NVFATAC 
  
 NA50700  PROBLEM  - AFTER NVF SWITCHED A BATCH CONSOLE TO RBF, IT
                     SWITCHED THE WRONG BATCH DEVICES (I.E. BATCH 
                     DEVICES ASSOCIATED WITH A DIFFERENT BATCH
                     WORKSTATION) TO RBF. 
          ANALYSIS - NVF GOT CONFUSED BECAUSE THE BATCH DEVICES FOR 
                     EACH WORKSTATION HAD THE SAME TERMINAL NAMES 
                     AND NVF WAS RELYING ON THE TERMINAL NAMES TO 
                     ALWAYS BE UNIQUE.
          SOLUTION - NVF HAS BEEN CORRECTED TO ALSO CHECK THE TERMINAL
                     NAME OF THE OWNING CONSOLE BEFORE SWITCHING THE
                     BATCH DEVICES. 
          EG     06/16/89    NVFTACC
 *L750*    ************************************************ 
 NA5B931  PROBLEM  - INTERLOCK BIT IS SET IN EST ENTRY FOR WHICH NO 
                     INITMDI JOB IS PROCESSING.  THIS LEAVES THE
                     MDI EQUIPMENT IN A STATE WHERE THE HOST WILL 
                     NEVER TALK TO IT UNTIL THE EST ENTRY IS TURNED 
                     OFF AND THEN BACK ON.  IF THERE IS NO OPERATOR 
                     AROUND, THE EQUIPMENT IS DOWN INDEFINITELY.
          SOLUTION - PIP SHOULD CLEAR THE INTERLOCK BIT IN THE EST
                     ENTRY AND START OVER AGAIN TRYING TO TALK TO 
                     THAT MDI IF THE INTERLOCK BIT REMAINS SET TOO
                     LONG.
          EG     11/21/89    PIP
 NA50720  PROBLEM  - A BAD SHORT REMOTE BATCH JOB (MISSING USER 
                     STATEMENT) FOLLOWED BY A GOOD SHORT REMOTE JOB 
                     WOULD PERIODICALLY CAUSE A PRU BLOCK PROTOCOL
                     ERROR AND THE HASP CARD READER CONNECTION TO BE
                     TERMINATED.
          ANALYSIS - WHEN PIP IS INFORMED BY RBF THAT IT IS RECEIVING 
                     A BAD REMOTE BATCH JOB, PIP WILL CHANGE THE
                     STREAM STATE OF THE CONNECTION TO A STATE
                     WHERE IT WILL THROW AWAY ALL PRU DATA RECEIVED 
                     ON THAT CONNECTION UNTIL IT PROCESSES THE
                     ACCOUNTING MESSAGE FOR THE BAD REMOTE JOB.  THIS 
                     COULD RESULT IN PIP DISCARDING PRU DATA FOR A GOOD 
                     REMOTE BATCH JOB THAT FOLLOWS THE BAD REMOTE BATCH 
                     JOB.  WHEN PIP RECEIVES THE ACCOUNTING MESSAGE 
                     FOR THE SECOND REMOTE BATCH JOB, PIP DETECTS THIS
                     AS A BLOCK PROTOCOL ERROR BECAUSE THE CONNECTION 
                     IS NOT IN A STREAM STATE IN WHICH THE ACCOUNTING 
                     MESSAGE SHOULD BE PROCESSED.  THE CONNECTION GOT 
                     INTO THE WRONG STATE BECAUSE PIP HAD THROWN AWAY 
                     THE PRU DATA BLOCKS THAT WOULD HAVE PUT THE
                     CONNECTION IN THE RIGHT STATE. 
          SOLUTION - PIP HAS BEEN CORRECTED TO NOT IMMEDIATELY DISCARD
                     PRU DATA WHEN IT RECEIVES SUCH DATA ON A CONNECTION
                     WHICH IS IN THIS STREAM STATE OF DISCARDING ALL
                     PRU DATA.
          EG     12/06/89    PIP
 NA5B936 PROBLEM  - NIP AND PIP MAY BOTH TRY TO WRITE TO THE FIRST
                    WORD OF THE SECOND PSEUDO FET OF A NBT ENTRY
                    AT THE SAME TIME.  THIS MAY RESULT IN THE FLAG
                    (RELEASE FLAG) THAT PIP IS TRYING TO SET NOT
                    BEING SET.  IF THIS OCCURS, PIP AND NIP WILL
                    GET OUT OF SYNC IN MANAGING THE NETWORK INBOUND 
                    BUFFERS.  THE RESULT IS THAT PIP MAY ABORT NAM
                    WITH A PIP ERROR 60 (INBOUND BUFFER TOO SMALL)
                    OR NIP MAY PROCESS THE INBOUND MESSAGES FROM
                    THE WRONG BUFFER.  THIS COULD RESULT IN NIP 
                    THINKING THAT THE MDI DID SOMETHING WRONG AND 
                    TERMINATING THE LOGICAL LINK BETWEEN THE HOST 
                    AND THE MDI.  IT COULD RESULT IN NIP TERMINATING
                    ONLY ONE CONNECTION.  IT CAN ALSO CAUSE PIP TO
                    NOT RELEASE THE MDI EQUIPMENT, WHEN THE EST 
                    ENTRY FOR THAT MDI IS TURNED OFF. 
         SOLUTION - THE FIELDS THAT NIP WAS TRYING TO UPDATE IN 
                    THE FIRST WORD OF THE SECOND PSEUDO FET OF A
                    NBT ENTRY HAVE BEEN MOVED TO ANOTHER WORD.
         EG     12/30/89    IMSNBT, MISDEF, NBT, PIP
 *L774*    ************************************************ 
 NA5B937  PROBLEM - CANNOT BUILD NAM WITH JUST *STAT* DEFINED.
          PSR NA50689, RELEASED AT LEVEL 739, INTRODUCED THE
          PROBLEM.
  
          SOLUTION - CORRECT THE PROBLEM INTRODUCED BY NA50689. 
  
          DEPENDENCIES - NA50689. 
  
          WMB    90/10/08.   NETOFF 
  
 NA50726  PROBLEM  - TWO NETCHEK CALLS IN A ROLL MAY RESULT IN AN 
                     UNWANTED WORKLIST TRANSFER FROM AIP TO NIP, IF 
                     THE AIP MULTIPLE UPLINE DATA MESSAGE QUEUING 
                     FEATURE IS BEING USED. 
  
          SOLUTION - AIP HAS BEEN CORRECTED TO NOT SEND A WORKLIST
                     REQUEST TO NIP TO GET DATA, IF THE SCP WORKLIST
                     BUFFER IS EMPTY AND WOULD NOT OTHERWISE BE SENT. 
  
          EG     10/03/89    NP$SEND
  
 NA50739  PROBLEM  - PIP ATTEMPTS TO CLEAR THE INTERLOCK BIT OF AN MDI
                     IF IT IS SET LONGER THAN TWO MINUTES.  HOWEVER THE 
                     EST ORDINAL SAVED FOR THE REQUEST GETS CLOBBERED,
                     CAUSING THE INCORRECT INTERLOCK BIT TO BE CLEARED. 
  
          SOLUTION - PIP HAS BEEN MODFIFIED TO SAVE THE EST ORDINAL AND 
                     THEN USE THE SAVED VALUE WHEN SETTING UP THE MTR 
                     CALL TO CLEAR THE INTERLOCK BIT. 
  
          REQUIRES - FS5378, NA5B931. 
  
          GAH    02/28/91    PIP
  
 *L780*    ************************************************ 
 NA5B939  PROBLEM  - THE NEW *NAM* APPLICATION TO SUPPORT THE NOS 
                     AUTOMATED CARTRIDGE SUBSYSTEM IS NOT SUPPORTED 
                     BY THE *NAM* COLLECT UTILITY.
  
          ANALYSIS - THE *NAM* APPLICATION AUTOMATED CARTRIDGE FACILITY 
                     (ATF) CREATES DUMP, TRACE, STATISTIC, AND DAYFILE
                     LISTINGS FILES WITH AN *AT* PREFIX.  *COLLECT* 
                     IGNORES ALL FILE CONTAINING PREFIXES NOT INFORMED
                     OF.
  
          SOLUTION - THE *COLLECT* ROUTINES HAVE BEEN MODIFIED TO 
                     SUPPORT THE ADDITION OF FILES BEGINNING WITH THE 
                     *AT* PREFIX CREATED BY THE *NAMSTRT* *JOBATF*
                     PROCEDURE. 
  
          GAH    03/11/92    COLLECT, CLT=INI 
  
 *L797*    ************************************************ 
 *L803*    ************************************************ 
 NA5B941  PROBLEM  - USER GETS APPLICATION BUSY, TRYING TO LOGIN TO 
                     IAF.  PROBLEM WAS THE AST$RACN FIELD FOR IAF WAS 
                     -1, WHICH IS 7776 FOR SYMPL UNSIGNED INTEGER.
                     THIS CODE DOES NOT ACUALLY FIX THE PROBLEM;
                     HOWEVER IT ELIMINATES THE SIDE AFFECT OF HAVING
                     USERS BEING UNABLE TO LOGIN DUE TO NAM THINKING
                     THE APPLICATION CONNECTION LIMIT HAS BEEN REACHED. 
                     MANY SITES ALREADY ARE RUNNING THIS MODSET UNDER 
                     IDENT NA50716. 
  
          SOLUTION - DEFINE AST$RACN AS INTEGER.
  
          CC    89/05/18
  
 *L826*    ************************************************ 
 NA5B943  PIP GETS ASSEMBLY ERRORS ON THE NOS 840C1 SYSTEM, 
          DUE TO THE CHANGED VALUE OF SYMBOL *RPPM*.
          SOLUTION: CHANGE *LDN* INSTRUCTIONS TO *LDK*. 
          PCS    94/02/23    PIP
 NA5*94   PROBLEM -  COPYRIGHT STATEMENTS NEED TO BE UPDATED. 
  
          SOLUTION - UPDATE ALL COPYRIGHTS TO 1994 AND CHANGE ANY REFERENCES
                     TO CONTROL DATA CORPORATION TO CONTROL DATA SYSTEMS INC. 
  
          BAO    02/14/94    COPYRIGHT,COPYRITB,COPYRITE,COMCCDD,COMCCOD, 
                             COMPCHNM,NP$CRT,COMCWTW,COMTVDT,TMSGNVF, 
                             MACREL,QTOPEN,PIP,TVF,SYNGEN,NMI=UPC,NAMI, 
                             NMI=CR1,COLLECT,IATTACH,IGET,IMNS
 *L840*    ************************************************ 
 NA50754  PROBLEM  - THE NETWORK JOBS USE A 24-BIT UNSIGNED FIELD TO
                     TRACK TIMED EVENTS.  WHEN THERE IS NO EVENT
                     PENDING, THE TIME OF THE NEXT EVENT IS SET TO
                     37777777 OCTAL.  IF 95.8 DAYS ELAPSES BETWEEN
                     DEADSTARTS, NOS-S REAL TIME CLOCK (RTCL) WILL
                     EXCEED 37777777 OCTAL.  WHEN THAT OCCURS, THE
                     NETWORK JOBS ALWAYS CONCLUDE THAT THEY HAVE WORK 
                     TO DO, AND THEY NEVER RELEASE THE CPU.  THIS 
                     PREVENTS ALL LOWER PRIORITY JOBS FROM RUNNING. 
  
          SOLUTION - SET THE TIME OF THE NEXT EVENT TO 77777777 OCTAL 
                     WHEN THERE IS NO WORK PENDING. 
  
          REQUIRES - NONE.
  
          JMM    09/15/94    SSCCTR, SSCRTR, CSISIT, CSLSIT, NVFIITR. 
  
 *L847*    ************************************************ 
 *L851*    ************************************************ 
 NA5B945  CORRECT *DLCND* COMPUTATION OF THE NUMBER OF SECONDS BETWEEN
          TWO DATES AND *NAMI* DERIVATION OF THE DAY OF THE WEEK FROM 
          THE JULIAN DATE TO INCLUDE THE CENTURY IN THE CALCULATIONS. 
          RED.   97/10/20.   DLCND, NAMI. 
  
 *L871*    ************************************************ 
 PSRLEVEL CHANGE PSR LEVEL NUMBER 
          DPO    78/09/08    NAMLEV 
 NIPIMS   CORRECTING IMS OF NIP IN NAMPL. 
 NA5A223  DURING PROCESSING OF IVT OUTPUT FOR AN NPU PIP DOES NOT 
          LOOK FOR HIGHER LEVEL OUTPUTS ONCE PROCESSING STARTED FOR 
          A LOWER LEVEL OUTPUT. 
          CHANGE IS MADE FOR PIP TO SEARCH FOR OUTPUT OF THE HIGHEST
          LEVEL EACH TIME AFTER AN OUTPUT IS PROCESSED. 
          SW     83/04/18    PIP
          LTN    11/01/82    NIP,COMDECKS.
  
 CRMOD    FIX UP CRCOM PROBLEM. 
          JCL    82/11/11    CRCOM
  
  
