OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / patches / nts2 / wr07020.inf (.txt) < prev next >

Wrap

OS/2 Help File | 1993-10-01 | 26.7 KB | 661 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ This package is a refresh of NTS/2 LAPS in a PKZIP container. It is intended to replace licensed instances of IBM LAN Adapter and Protocol Support (LAPS). As such, its use is limited to the license agreement under which you obtained the original licensed copy. The versions which are suitable for replacement are: o "LAPS V2.00" as used in "Extended Services Version 1.0" o "LAPS V2.01" as used in "Lan Server V2.0" and "LAN Enabler V2.0" o "LAPS V2.11" as used in "LAN Server V3.0" and "NTS/2 V1.0" Title to the contents herein and any copies made is retained by the International Business Machines Corporation, Armonk, New York, 10504. ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ The following installation instructions presume that the Container File WR07020.ZIP or W07020.ZIP has been downloaded or copied to a hardfile. Some electronic delivery repositories or bulletin boards restrict file names to six characters; hence the Container File name may vary. ΓòÉΓòÉΓòÉ 2.1. Installation of NTS/2 LAPS from Fixed Disk ΓòÉΓòÉΓòÉ 1. Use PKUNZIP2 -D to unzip the Container File into a separate directory. The '-D' parameter is required in order to preserve the LAPS directory structure. Detailed Steps: a) Ensure that the Container File is in the current directory. (Enter "DIR" and the Container File should appear in the list). b) From the current directory, create a directory called TEMP by entering "MD TEMP". c) Unzip the Container File into the TEMP directory by entering "PKUNZIP2 -D WR07020 TEMP" or "PKUNZIP2 -D W07020 TEMP", whichever is appropriate. 2. Establish the new directory as the current directory by entering "CD TEMP" Note: Click Here to view the intended directory tree. 3. Run LAPS by entering from command line "LAPS", and follow the prompts. CAUTION: If LAPS is run from a directory containing the Container File it will incorrectly unzip this file into the target \IBMCOM directory. 4. Shut Down and Reboot the system. 5. If you wish to discard WR07020.ZIP and the contents of TEMP, you can do so now. ΓòÉΓòÉΓòÉ 2.2. Installation of NTS/2 LAPS from Diskette ΓòÉΓòÉΓòÉ 1. Use PKUNZIP2 -D to unzip the Container File onto a formatted diskette. The '-D' parameter is required in order to preserve the LAPS directory structure. Detailed Steps: a) Ensure that the Container File is in the current directory. (Enter "DIR" and the Container File should appear in the list). b) Obtain a freshly formatted diskette and label it (externally) "LAPS 2.14". Insert this diskette in drive A:. c) Unzip the Container File by entering "PKUNZIP2 -D WR07020 A:\" or "PKUNZIP2 -D W07020 A:\" whichever is appropriate. Warning: The file WR07020.INF will not fit when unzipping to a 1.2 Meg diskette. Do not be alarmed. It is only an information file and can be obtained by entering: "PKUNZIP2 WR07020 x:\outpath WR07020.INF" where "x:outpath" is a drive and directory with sufficient space. 2. Establish A:\ as the current directory by entering "A:". Enter "CD \" if necessary. Note: Click Here to view the intended directory tree. 3. Run LAPS by entering from command line "A:\LAPS", and follow the prompts. 4. Shut Down and Reboot the system. 5. You can discard WR07020.ZIP from fixed disk now. ΓòÉΓòÉΓòÉ 2.3. Upgrading RIPL Servers ΓòÉΓòÉΓòÉ LAPS does not install Transport Services to the \IBMLAN\RPL\IBMCOM directory. To service the RIPL tree: 1. XCOPY the entire tree structure of IBMCOM to the RIPL directory on which IBMCOM exists. ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Example ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé XCOPY /S C:\IBMCOM\*.* D:\IBMLAN\RPL\IBMCOM Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ 2. Run GETRPL to update Access Control Lists, etc. This requires that the RIPL server be started and that a LAN administrator be logged on. ΓòÉΓòÉΓòÉ <hidden> Directory Tree ΓòÉΓòÉΓòÉ \ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇ\IBMCOM ΓöÇΓöÇΓöÇΓöÉ Γö£ LAPS.EXE Γö£ IBMCOM.ZIP Γö£ LAPSDEL.EXE Γö£ LT0.MSG Γö£ LAPSDISK.EXE Γö£ LT0H.MSG Γö£ LAPSRSP.EXE Γö£ XI0.MSG Γö£ WR07020.INF Γö£ XI0H.MSG Γö£ PKUNZIP2.EXE Γöé Γö£ README.1ST Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ\PROTOCOLΓöÇΓöÇΓöÇΓöÉ Γö£ THINLAPS.EXE Γöé Γöö PROTOCOL.ZIP Γö£ XIHELP.HLP Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ\MACSΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöö MACS.ZIP Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ\DLLΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γö£ DLL.ZIP ΓööΓöÇΓöÇΓöÇΓöÇΓöÇ\LANLK ΓöÇΓöÇΓöÇΓöÇΓöÉ Γö£ LANMSGDL.DLL Γö£ IBMLANLK.EXE Γö£ LAPSCID.DLL Γö£ IBMLANLK.SYS Γö£ LAPSPM.DLL Γö£ LSI.MSG Γöö LAPSRES.DLL Γöö LSIH.MSG ΓòÉΓòÉΓòÉ 3. Things that Changed ΓòÉΓòÉΓòÉ The following sections describe changes that have been made to the product's executables, publications, and messages/helps. ΓòÉΓòÉΓòÉ 3.1. NTS/2 Enhancements ΓòÉΓòÉΓòÉ The following sections explain new and enhanced NTS/2 features. ΓòÉΓòÉΓòÉ 3.1.1. TRACENAMES - New Parameter for NETBIOS Traces ΓòÉΓòÉΓòÉ The TRACENAMES parameter is used to limit tracing activity to the interaction between specified machines. Prior to the offering of this parameter, tracing at the transport level picked up all frame activity on the line, causing the trace buffer to quickly fill with irrelevant frame records. This parameter is ideal for isolating a problem between a server and requester on a large network. Tracing is limited by selecting NETBIOS names on remote machines using the TRACENAMES parameter. Names can be specified as either a 16-byte ASCII or 32-byte Hex value. Up to four names can be selected in either format. The asterisk wildcard character (*) can be used in the ASCII format for ease of use, or to increase the number of remote names traced if machines have similar names. All names must reside on the same line as the TRACENAMES parameter. Incorrect length or invalid hex numbers cause an error and NETBEUI will not load. TRACENAMES works in conjunction with the OS2TRACEMASK parameter and the TRACEOFF parameter already available for NETBEUI in NTS/2 version 1.0 and LAN Server 3.0. The OS2TRACEMASK must be set to the necessary nonzero values to activate any NETBIOS traces. The recommended setting is 0x07FF. NDIS activity will not be filtered if the NDIS bits are activated in OS2TRACEMASK. The TRACENAMES parameter must be inserted into the PROTOCOL.INI file using an editor and is not yet a part of the LAPS config and install tool. TRACENAMES must be placed only in the NETBEUI_nif section. The following example shows the general location and format of the parameter: PROTOCOL.INI [NETBEUI_nif] DriverName = netbeui$ Bindings = IBMTOK_nif ... ... DLCRETRIES = 5 OS2TRACEMASK = 0x07FF TRACENAMES = "req1 " "req2 " "req3 " Other valid TRACENAMES formats are: TRACENAMES = "72617131202020202020202020202000" "req2 *" TRACENAMES = "req*************" "72617131202020202020202020202020" Activity relevant to the remote NETBIOS is traced. This includes NCBs issued with that remote name, as well as all session activity related to that remote name. All statuses from the lower layers are reported whether related to the remote station or not. Frame activity between the remote and local machines is traced by LSN number after the session is established with the remote machine. A maximum of 12 active sessions is traced. Some NCBs are not associated with a remote name or LSN and are not traced: o Add Name o Add Group Name o Delete Name o Cancel o LAN Status o Session Status o Receive Broadcast Datagram o Send Broadcast Datagram NCB.Reset is traced even though it is not related to sessions or specific names. Datagrams and other UI frames are traced if they contain a remote name specified in TRACENAMES. RECEIVE.ANY type commands are traced on completion if they report a session event related to a specified remote machine. ΓòÉΓòÉΓòÉ 3.1.2. ODI2NDI Obtains Universal Address Automatically ΓòÉΓòÉΓòÉ For ODI2NDI.OS2(V1.0), configuration of the NETADDRESS parameter was required, even if the user wanted to use the Network adapter universally administered address. This requirement is necessary because ODI2NDI must provide the NETADDRESS to the ODI protocol (IPX) before ODI2NDI can obtain the adapter netaddress through the NDIS interface. ODI2NDI.OS2(V1.1) is modified so that it obtains the Network adapter universal address automatically when the NETADDRESS parameter is not configured for ODI2NDI.OS2. To take advantage of this enhancement, the following manual modifications of CONFIG.SYS are required. 1. Configure ODI2NDI for a Network adapter MAC using the LAPS configuration. 2. Manually perform the following updates to CONFIG.SYS: a) Locate the Network adapter MAC device driver statement in CONFIG.SYS. For example, for IBM Token Ring Network Adapters, the MAC device driver statement is: DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 b) Position the the MAC device driver statement after the PROTMAN.OS2 device driver statement, but before the ODI2NDI.OS2 device driver statement in the CONFIG.SYS file. An example CONFIG.SYS fragment is: : DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM : : DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 : : REM --- NetWare Requester statements BEGIN --- DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE device = C:\ibmcom\protocol\odi2ndi.os2 : : c) Save the modified CONFIG.SYS. You must restart your computer for the change to take effect. The manual updates to the CONFIG.SYS file need to be done only the first time the ODI2NDI protocol is configured for a Network Adapter MAC. Modifying ODI2NDI or MAC parameters does not require additional updates to CONFIG.SYS. Note: This enhancement does NOT work with ALL Network adapters. If the enhancement does not work with your Network adapter, message LT80227 is displayed when you start your computer. This message is also logged in the LANTRAN.LOG file located in the IBMCOM subdirectory. If message LT80227 occurs, use the LAPS configuration utility to configure the NETADDRESS for ODI2NDI.OS2. ΓòÉΓòÉΓòÉ 3.1.3. LAPS Icon on the Desktop ΓòÉΓòÉΓòÉ After NTS/2 LAN Adapter and Protocol Support (LAPS) has been installed and configured on an OS/2 2.x system, a LAPS icon is placed in the System Setup folder. Double clicking on the icon brings up the LAPS installation/configuration utility. ΓòÉΓòÉΓòÉ 3.2. NETBIOS Protocol Stack Defects ΓòÉΓòÉΓòÉ Files that changed: \IBMCOM\PROTOCOL\NETBEUI.OS2 \IBMCOM\PROTOCOL\NETBIOS.OS2 ΓòÉΓòÉΓòÉ 3.2.1. Fixed APARs ΓòÉΓòÉΓòÉ o IC04951 - UNC Name failures with IBM Ethernet References to a resource by UNC names failed with error code SYS0240 on the server that was working on the NETBEUI stack with IBM Ethernet. o IC05402 - SOURCE ROUTING FIXES IN NETBEUI Fixes were required for receiving frames on a link that crosses source-routing bridges - the route of the incoming frame should not be assumed to be the same as the route used for outgoing frames. For TEST frames received with 2 bytes of Routing Information, the TEST response was built incorrectly. o IC05486 - TRAP IN NETBEUI ON A VALUEPOINT MACHINE Residual code from an OS/2 EE 1.3 environment remained in NETBEUI. Residual code caused the Trap D. o IC05526 - HPFS386 SIDEBAND TRAP D ON ETHERNET When running HPFS386 on Ethernet and attempting to copy a file from a redirected drive, a Trap D occurred at CS:C08 EIP:8A5. o IC05551 - TRAP D IN NETBEUI - INITDS CORRUPTED Trap D was caused by an invalid selector for low memory data segment. o IC05673 - Four Separate Symptoms o IC05673 - 1) SESSION NOT ESTABLISHED IF SABMES ARRIVE AT WRONG TIME If sessions were being brought up simultaneously on two machines, SABMEs and UAs can conflict causing session establishment to fail. The data area is then corrupted because the link state is wrong. o IC05673 - 2) RECEIVE BROADCAST LOOPING When two or more applications have a receive_broadcast NCB outstanding, issue the next receive_broadcast on appendage. NETBEUI goes into a loop processing the appendage NCB as an additional receive on the receive_broadcast queue. o IC05673 - 3) SESSION_ALIVE SENT WITH INCORRECT LSN NUMBER CAUSES CORRUPTION Session_Alive sent with incorrect LSN number causes corruption of the NTE Listen queue. Links can drop afterward. Fix was to correct sending of Session_Alive frame to have correct LSN number only from links in Normal state. o IC05673 - 4) ADJUST ORDER OF SABME/UA RESPONSES Reordered processing of link establishment and closing prevents case of extra receive ready, or FRMR. o IC05780 - STARTING LS 3.0 WHILE 3270 COMING UP CAUSES COM505 ERROR - If starting LAN Server and Communications Manager 3270 feature at the same time, Communications Manager 3270 will hang with COM505 Error. o IC05794 - NETBIOS RESET RETURNS RC=23 Applications on Token Ring Network can issue "Reset" before NETBIND has completed. When this occurs, NETBIOS returns RC=38 (Requested Resource Not Available) and then RC=23 (Invalid LAN Adapter Number). Serialization of the NETBIND execution process can solve the problem. This fix increases the number of "Reset Retries" which should mask any such race condition. o IC05869 - TRAP E IN NETBEUI Trap E occurs during Remote IPL of OS/2 2.0 or OS/2 2.1. o IC05902 - XMIT_TEST_CMD RESPONSE LOST BY NETBEUI Under certain circumstances Transmit_Test_Cmd is rejected by Netbeui and passed to the next protocol stack. o JR06350 - Redirector failing to Reset NETBEUI was clearing a flag bit whether it actually issued the hard reset or not. Clearing this flag bit when a different flag bit was set prevented NETWKSTA.SYS from issuing the reset. o JR06550 - WCMME - CLIENT REMOTE BUSY STATE CAUSED SERVER HANG Client remote busy state caused server to stack up I frames of session alive. ΓòÉΓòÉΓòÉ 3.2.2. Other Fixes ΓòÉΓòÉΓòÉ o NETBEUI INITIALIZATION FAILS Some configurations caused NETBEUI to fail to initialize. o INCORRECT PACKET SIZE BROUGHT DOWN LAN SERVER 3.0 An Ethernet-only requester reaching a token-ring Busmaster server through an 8209 bridge eventually caused the server to have multiple sessions and then the server could not communicate with the Ethernet requester or the token-ring requesters. The packet size was being altered by the 8209 bridge. o NETBEUI WAS NOT LOOKING FOR 2 IN MINOR NDIS VERSION IN THE COMMON CHARACTERISTICS TABLE To determine if a MAC driver supports an extension to the MAC Service-Specific Characteristics, NETBEUI should be looking for a 2 in the Minor NDIS Version in the Common Characteristics table. o ILLEGAL FRAME SIZE CAUSED TRAP D When an illegal frame size was checked, it caused a Trap D in NETBEUI. o TRAP D WHILE RUNNING NETSERV.EXE A Trap D occurred in CS:OC78 EIP:EC9 o NETBIOS FAILED TO INITIALIZE ON ANY OS/2 VERSION GREATER THAN 2.0. Install NTS/2 on OS/2 2.1 and configure for NETBIOS. During IPL, NETBIOS failed to initialize. This indicated the wrong version of the operating system. o AFTER RUNNING A LONG PERIOD OF TIME, NETBIOS RETURN ERROR 22 Too many outstanding NCBS (un_freed) cause NETBIOS to return "to Many Commands Pending" (RC=22). This occurs over a varying period of time depending on LAN activity. ΓòÉΓòÉΓòÉ 3.3. IBM Token Ring Busmaster MAC Driver Defects ΓòÉΓòÉΓòÉ Files that changed: \IBMCOM\MACS\IBMTRBM.OS2. ΓòÉΓòÉΓòÉ 3.3.1. Fixed APARs. ΓòÉΓòÉΓòÉ o JR05729 - BUSMASTER DOES NOT RECOVER FROM LOBE FAULT. LAN Server/Requestor 2.0 could not be restarted on machines equipped with Busmaster cards after the cable was unplugged and replugged. o JR06486 - BUSMASTER TRAP D UNDER HEAVILY STRESSED NETWORK The Busmaster driver was performing a call that was not legal at the time. This caused a Ring 0 Trap D. ΓòÉΓòÉΓòÉ 3.3.2. Other Fixes ΓòÉΓòÉΓòÉ o BUSMASTER UNABLE TO RE-ENTER RING AFTER DUPLICATE ADDRESS One machine booted and got a particular token ring address. Another machine (with Busmaster) booted requesting the same address, and got a duplicate address indication, closing the adapter. The first machine left the ring, freeing the address. Any attempt to reopen the previously failed busmaster adapter using Communication Manager failed, still indicating a duplicate address. o WRONG FILTER VALUE USED Prior to deleting an address, the first byte of the address was checked against 80h, which is the equivalent of universal group. It should be checked against C0h, which is local group. This caused what was accepted in the add to be rejected in the delete. Making this change created consistency with the add address. ΓòÉΓòÉΓòÉ 3.4. Install & Configuration Defects (LAPS) ΓòÉΓòÉΓòÉ Files that changed: \IBMCOM\DLL\LAPSPM.DLL \IBMCOM\DLL\ LAPSCID.DLL \IBMCOM\DLL\BMLXCFG.DLL \IBMCOM\LAPS.EXE \IBMCOM\LAPSICON.EXE \IBMCOM\LAPSRSP.EXE ΓòÉΓòÉΓòÉ 3.4.1. Fixed APARs ΓòÉΓòÉΓòÉ o IC04997 - USING ADAPTER NUMBERS TO GUARANTEE UNIQUENESS FOR LANVMAC LANVMAC requires that its upper boundary be strictly defined; the Media Access Control (MAC) for adapter 0 can only be defined for adapter 0. o IC04999 - LAPS CONFIGURATION NEEDS TO TREAT LANVMAC NETADDRESS LIKE LANDD Function was added that treats the LANVMAC netaddress field the same as the LANDD netaddress field. o IC05159 - MAINTENANCE INSTALL OF LAPS DURING CID FAILS ON OS/2 2.1 When running maintenance LAPS installation using CID on OS/2 2.1, LAPS failed while attempting to update the IBMLVL.INI file. o IC05553 - NTS/2 INSTALL DID NOT PUT LANVDD AND LANPDD IN THE CONFIG.SYS FILE (LAPSPM.DLL) On OS/2 2.1, the NTS/2 install did not place statements for LANVDD.OS2 and LANPDD.OS2 in the CONFIG.SYS file. ΓòÉΓòÉΓòÉ 3.4.2. Other Fixes ΓòÉΓòÉΓòÉ o ERROR IN NIF VALIDATION WHEN CHECKING DEFAULT AGAINST RANGE (LAPSCID.DLL LAPSPM.DLL IBMLXCFG.DLL) The NIF validation code was incorrectly handling the case in which a default value of type HexString was being checked against the arguments of the Range keyword. The check failed if the default value was enclosed with double quote characters or specified with a "0x" prefix. The problem only occurred in the situation where the parameter was of type HexString, had a default value, had a specified range, and the default value had quotes and/or a prefix. o VDD/PDD CONFIG.SYS PROBLEM Eliminates LANVDD and LANPDD device statements from the CONFIG.SYS file if 802 or NETBIOS are not configured. o FIX REDIRECTOR STATEMENT Fixed redirector statement position in the CONFIG.SYS file. o LAPS CONFIGURATION GENERATES DIFFERENT RESULTS Upon configuring the LANVMACs, LAPS configuration set the drivername on entries 2-n to LANVMA2 and the module names for entries 2-n end in "_nif2". o CREATING RESPONSE FILE FROM LAPSRSP.EXE - IMPROPER TARGET KEYWORD Specifying a target using LAPSRSP.EXE generates a response file containing "target_drive" instead of "target". ΓòÉΓòÉΓòÉ 3.5. 802.2 Protocol Stack Defects ΓòÉΓòÉΓòÉ Files that changed: \IBMCOM\PROTOCOL\LANDD.OS2 \IBMCOM\PROTOCOL\LANDLLDD.OS2 ΓòÉΓòÉΓòÉ 3.5.1. Fixed APARs ΓòÉΓòÉΓòÉ o IC04923 - MULTICAST ADDRESS SUPPORT FIX The multicast address support functions in 802.2 fixes to loopback path, error codes, and command codes. o IC05000 - TRAP D IN LANDD CODE RUNNING 75+ WORKSTATION GATEWAY (LANDD.OS2) Each time the links were deactivated, the downstream emulators reactivated the link and the LU-LU sessions were automatically reestablished. A Trap D occurred. o IC05001 - COMMUNICATIONS MANAGER (CM) UNABLE TO STOP NORMALLY OR ABNORMALLY CM was unable to exit because it cannot close the token-ring link to the AS400. The hang was due to the Close.Station being issued on the completion appendage for a Transmit.I.Frame, resulting in a DISC sent to the MAC, the T1 timer started and the Link state set to disconnecting. When the completion appendage returns to NETBEUI, it continues processing the I-frame completion which stops T1. o IC05003 - UNABLE TO REOPEN BUSMASTER ADAPTER AFTER LOBE FAILURE (LANDLLDD.OS2) o IC05360 - TRAP D IN LANDLL; CS=0C38; Attempting to bring up LAN Net Manager (LANDLLDD.OS2) results in TRAP=000D with the CS register at x'0C38' o IC05753 - LANDD INCORRECT FRAME CAUSED TRAP D (LANDD.OS2) The Trap D occurred when remotely configuring a LAN-attached printer. A pop-up said the action was successful, then there was an OK button. If the button was not clicked, after about 20 seconds, a Trap D occurred. ΓòÉΓòÉΓòÉ 3.5.2. Other Fixes ΓòÉΓòÉΓòÉ o RECEIVE COMMAND WITH RETURN CODE = 20 SHOULD ZERO OUT THE BUFFER POINTER (LANDLLDD.OS2) When the receive command completed with return code = 20 (lost data, no buffers), the buffer pointer should be 0 since there were no partial buffers. o SERVER ACCESS POINT POOL SIZE OF 1000H NOT HANDLED (LANDD.OS2) When the maximum size, 0x1000 was used for pool_length in a DIR.OPEN.DIRECT, a return code of 0x16 was returned. The value should work appropriately. ΓòÉΓòÉΓòÉ 3.6. 802.2 and NETBIOS Virtual Device Driver Defects. ΓòÉΓòÉΓòÉ Files that changed: \IBMCOM\LTSVCFG.COM \IBMCOM\PROTOCOL\LANVDD.OS2 ΓòÉΓòÉΓòÉ 3.6.1. Fixed APARs ΓòÉΓòÉΓòÉ o JR06756 - DIR.INTERUPT RETURNS 0 IF ADAPTER NOT OPEN (LANVDD.OS2) Attempting to run an Ethernet packet driver for TCP/IP. It failed when it attempted to initialize, because the executable ran a dir.interrupt command to see if the adapter was open. VDD returned a return code = 0 if the adapter was not open. It should have returned a bad return code. ΓòÉΓòÉΓòÉ 3.6.2. Other Fixes ΓòÉΓòÉΓòÉ o THE DOS 8209 BRIDGE UTILITY CAN NOT FIND ADAPTER WITH VDD The DOS version of the 8209 Bridge Utility could not find the adapter when running under the VDD. o LTSVCFG ALWAYS RETURNS NONZERO When LTSVCFG was run, an error code environment variable was always set to nonzero. Even though LTSVCFG executed successfully, a nonzero return code was always returned. o NETBIOS and 802.2 SUPPORTS ONLY 8 DOS SESSIONS DOS Virtual Device Support for Netbios and 802.2 should support 16 sessions, not just eight. ΓòÉΓòÉΓòÉ 3.7. Protocol Manager Defects ΓòÉΓòÉΓòÉ Files that changed: \IBMCOM\PROTMAN.OS2 ΓòÉΓòÉΓòÉ 3.7.1. Fixed APARs ΓòÉΓòÉΓòÉ There are no fixed APARs for Protocol Manager. ΓòÉΓòÉΓòÉ 3.7.2. Other Fixes ΓòÉΓòÉΓòÉ o PERFORMANCE AND NDIS SUPPORT IN PROTMAN PROTMAN supports the GET_PPATINFO IOCTL for the NDIS requirements and the GET_MODULE_CHAR_ TABLE IOCTL for the Monitor product. ΓòÉΓòÉΓòÉ 3.8. IBM Netware Requester Support Defects ΓòÉΓòÉΓòÉ Files that changed: IBMCOM\PROTOCOL\ODI2NDI.OS2 IBMCOM\LT8.MSG IBMCOM\LT8H.MSG ΓòÉΓòÉΓòÉ 3.8.1. Fixed APARs ΓòÉΓòÉΓòÉ o IC05437 - LOTUS NOTES RUNNING ODI2NDI OVER ETHERNET LOST SESSION While running Lotus Notes over ODI2NDI Ethernet, the session between the server and client was eventually lost. ΓòÉΓòÉΓòÉ 3.8.2. Other Fixes ΓòÉΓòÉΓòÉ o ODI2NDI FAILS WHEN TCP/IP USES DIRECT STATION OF IEEE 802.2 A NetWare Requester for OS/2 over ODI2NDI stops working when an application using the direct station interface of IEEE 802.2 is started.