NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: PTF410 - NetWare SAA 1.3 Maintenance DOCUMENT ID: TID250010 DOCUMENT REVISION: B DATE: 25MAR94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: PTF410.EXE NOVELL PRODUCT and VERSION: NetWare for SAA 1.3 ABSTRACT: PTF410, 411, 412, 413, 414, and 415 files together are the latest Maintenance PTF for NetWare for SAA 1.3. (PTF412 and 413 are required for NetWare 3.11 ONLY) *BEFORE YOU UNZIP THESE FILES, YOU MUST READ DOWNLOAD AND READ PTF41X.TXT. The PTF41X series allows NetWare for SAA to run on a NetWare 4.x server; it also contains all the latest patches and additional features. The PTFs update NetWare for SAA 1.3 to 1.3.43. (effectively the same as 1.3.42, which is shipping as "1.3B"). After you have applied these PTF files, you may apply the PTF443.EXE patch. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ADDITIONAL CONFIGURATION Other: GENERAL SYMPTOM If two DownStream PUs were configured with the same address, it was sometimes not detected causing an error message and the eventual crash of NetWare for SAA. SOLUTION Apply the PTF 41X series. SYMPTOM Auto-disconnect/connect not working with QLLC and downstream PUs. SOLUTION Apply the PTF 41X series. SYMPTOM Sometimes when messages pertaining to the link status used, remained queued showing only one links' status. If there were several downstream links this resulted in resources not being released when the SNA profile was unloaded. SOLUTION Apply the PTF 41X series. The DLCI code has been changed so that all messages pertaining to link status will be displayed at all the times. SYMPTOM Incorrect sense code displayed from a received XID3. SOLUTION Apply the PTF 41X series. An incorrect sense code will no longer be displayed from a received XID3. SYMPTOM If a SNA profile was unloaded in the middle of data transfer there were problems reconnecting until DLM, protocol stack, and driver were started again. SOLUTION Apply the PTF 41X series. SYMPTOM Workstations sometimes crashed because C-Worthy was freeing memory addressed by uninitialized pointers, when using CSCON. SOLUTION Apply the PTF 41X series. SYMPTOM Incorrect display of PU 2.1 LU numbers. SOLUTION Apply the PTF 41X series. A change was made so that PU 2.1 LU numbers display correctly from LU1 to LU 128 for independent LUs. SYMPTOM Some segments not counted for NMA number of bytes received count. SOLUTION Apply the PTF 41X series. A change was made to SNA to fix the number of bytes received count for NetWare Management Agent statistics. Previously, all segments (FIS, MIS, LIS) were not counted. SYMPTOM The number of UP-BOUND LUs was incorrectly reported to SSM when requests were made for specific attributes of a Host Link object. This value was being overwritten by the value for UP-INACTIVE LU count. SOLUTION Apply the PTF 41X series. SYMPTOM If OS/2 CM was a DSPU, (and if the host sent segmented FMD RUs under a SSCP-LU session, host link would constantly connect and disconnect. SOLUTION Apply the PTF 41X series. SYMPTOM RequestID reset. SOLUTION Apply the PTF 41X series. NMAUTIL was changed to set the request ID correctly so that when the host sends more than 15 RUNCMDS, the requestID does not reset. SYMPTOM On a NetWare 4.01 LAN, API errors occurred when CSCON was brought up. SOLUTION Apply the PTF 41X series. SYMPTOM System Log pages not formatted correctly. SOLUTION Apply the PTF 41X series. The code for maintaining the SYSTEM.LOG has been modified to format the pages correctly. SYSTEM.LOG files are now named according to the service profile name. When the file reaches .5 MB, it is saved as ".log>." Writes to the SYSTEM.LOG have also been streamlined to work faster. ADDITIONAL CONFIGURATION Other: AS/400 SYMPTOM If AUTOEXEC.NCF had the following consecutive statements, the following message was displayed: AUTOEXEC.NCF Statements CSLOAD SNAPROF LOAD AS400PCS MESSAGE AS400PCS unloads with "AS400PCS - SNA profile name is known, but..." SOLUTION Apply the PTF 41X series. PB_NWSAA has been modified so AS400PCS will not unload with the error if the previously mentioned lines are in the AUTOEXEC.NCF file. ADDITIONAL CONFIGURATION Other: SNA LINKS SYMPTOM When "Set Msg Destination" was selected, the server would hang. SOLUTION Apply the PTF 41X series. ADDITIONAL CONFIGURATION Other: LU6.2 SYMPTOM In CSSTATUS, if there were multiple or parallel sessions, all attributes did not display. SOLUTION Apply the PTF 41X series. SYMPTOM The LU6.2 transaction program sometimes hung if allocate was done and the link went down. SOLUTION Apply the PTF 41X series. SYMPTOM A LU 6.2 protocol violation occurred when the Change Direction Indicator was being incorrectly set by NWSAA in a LUSTAT, which was causing the partner LU to UNBIND. SOLUTION Apply the PTF 41X series. SYMPTOM MC_TEST, when issued from SEND state was erroneously returning the return codes of STATE_CHECK and NOT_RCV_STATE. SOLUTION Apply the PTF 41X series. After the installation of the PTF, the MC_TEST verb can be issued when the conversation is in any state. SYMPTOM The Transaction Program would hang because the protocol stack was waiting on Change Direction before sending FMH-7 (to service SEND_ERROR verb). SOLUTION Apply the PTF 41X series. ADDITIONAL CONFIGURATION Other: QLLC SYMPTOM If a remote target X.25 address was not configured correctly, the resources allocated were not freed after the configuration was corrected. Instead, they were not released until the unload of QLLCS. SOLUTION Apply the PTF 41X series. SYMPTOM DISPLAY_CV22_MSG incorrectly displayed QLLC target names. SOLUTION Apply the PTF 41X series. SYMPTOM QLLCS not working with downstream PUs during reconnection. SOLUTION Apply the PTF 41X series. With these files applied, QLLCS will now work with downstream PUs during the reconnection process. ADDITIONAL CONFIGURATION Other: SDLC SYMPTOM If the SNA profile loaded and unloaded before SDLC link was up, DTR stayed on even after the unload. SOLUTION Apply the PTF 41X series. SYMPTOM If two SNA profiles were on the same SDLC card; when the first profile was unloaded, DTR went down causing the link to disconnect. This in turn caused the second profile to get disconnect also. SOLUTION Apply the PTF 41X series. SYMPTOM No alert message when link activity timer expires. SOLUTION Apply the PTF 41X series. With these files applied, two new alert messages have been added for frame reject condition. SYMPTOM Disconnect message not displayed. SOLUTION Apply the PTF 41X series. With these files applied, an inactivity timer alert message will now display when the link activity timer expires. SYMPTOM SDLCS (SDLC protocol stack) on a V.35 link, when using multidrop feature on R3SDLC card, would not display a link disconnected message if the host link was inactivated. SOLUTION Apply the PTF 41X series, which correct the Link lost problem when using multidrop feature on R3SDLC card with V.35 link. SYMPTOM When the host link was inactivated, sometimes all the sessions showed Up Status and the link never showed disconnect status. SOLUTION Apply the PTF 41X series. ADDITIONAL CONFIGURATION Other: Token-Ring SYMPTOM The Token Ring would flood with XIDs if the host was not ready to bring up the link. SOLUTION Apply the PTF 41X series. Self-Extracting File Name: PTF410.EXE Revision: B Files Included Size Date Time \ PTF410.TXT (This File) 3X.TXT 18166 09-29-93 6:31p 4X.TXT 22236 09-27-93 5:01p PTF41X.TXT 4852 09-29-93 6:30p COMMEXE1.ZIP 490118 09-27-93 11:06a Note: These are only the files in PTF410. See the .TXT files in PTF 411, 412, 413, 414, and 415 for the file listing of each of PTF. Installation Instructions: *** WARNING *** Failure to read PTF41X.TXT first may cause you do perform procedures incorrectly and problems with your files may occur. 1. Do not simply copy the files, FIRST, read PTF41X.TXT. 2. To install on a NetWare 3.11 or 3.12 server, please read 3X.TXT. 3. To install on a NetWare 4.0 or 4.21 server, please read 4X.TXT. *** Do not simply copy the files in, you MUST follow the instructions listed above. *** Patch History: The PTF 41X series supersedes PTF 400, 401, 402, 403, 404, and 406. It also supersedes PTF 354, 367, and 368. Solution Specifics: NEW FEATURES 1. TRFORMAT.EXE now decodes LUx information. 2. HELP file added to WEEAS for OS/2 access support. 3. SNMP alert support for NMS, added generic MLID object for third-party driver support. 4. NetWare Management Agent a. Remote 3 adapter now compatible with SSM. b. Flow of NetView alerts is now restricted if a limit is exceeded. This is configurable through NVCMDS.DB. c. A NetView alert will be generated if registered end point servers go down. d. Allow RUNCMD retry limit, retry timer and response timer are now configurable through NVCMDS.DB. This replaces the configuration available previously in NetWare for SAA 1.2 through CSPARM. e. Allow APPL names in runcmds to eight characters without padding. 5. Support was added for License diskette. 6. CPIC and AS/400 file names now conform to the CD-ROM ISO convention. 7. Two additional NetView alerts can now be generated: - File server error limit reached: Server configuration - Failure Alert: THRESHOLD REACHED These alerts mean the number of NetView alerts generated by the collection point and end point servers has exceeded the HIGHWATERMARK parameter setting in NVCMDS.DB. Alert forwarding to the NetView console has been stopped until the number of generated alerts drops to or below the LOWATERMARK setting in NVCMDS.DB. Action: Request the LAN administrator to check for LAN conditions that may be generating excessive NetView alerts. Check the HIGHWATERMARK setting in NVCMDS.DB on the collection point server and raise it if it is set too low. _________________________________________________________________ DISCLAIMER Novell, Inc. makes no representations or warranties with respect to this software program, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Novell's intentions for this software program is to provide a temporary workaround to the anomalies described in this document. Such workarounds are typically addressed in future releases of the product. Novell will not be responsible for any data loss that may result from implementing this program. Novell strongly recommends a backup be made before any program is applied. Technical support for this program is provided at the discretion of Novell. _________________________________________________________________ �