NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: SAA010.EXE, DOS Client LUx API Support DOCUMENT ID: TID250352 DOCUMENT REVISION: A DATE: 09AUG94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: SAA010.EXE NOVELL PRODUCT and VERSION: NetWare for SAA 1.3B NetWare for SAA 1.3A NetWare for SAA 1.3 ABSTRACT: SAA010.EXE provides all versions of NetWare for SAA 1.3 with DOS Workstation API support to use SNA communications for secondary dependent logical units using the LU 0, LU 1, LU 2, and LU 3 protocols. SAA010.TXT does not provide instructions regarding the writing of LUx applications. If you wish to write applications contact Novell Marketing for assistance at the address shown in SAA010.TXT. ----------------------------------------------------------------- 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. ----------------------------------------------------------------- SYMPTOM GENERAL 1. RUI or SLI verbs may not post as complete. 2. The NWSAA_INIT verb was not checking all eight bytes of the profile name. 3. A new return code was added to LUX. 4. Nearest server determination 5. RUI_WRITE problems 6. Applications that poll the primary return code may fail. Self-Extracting File Name: SAA010.EXE Revision: A Files Included Size Date Time \ SAA010.TXT (This File) LUX.EXE 88266 05-25-94 3:58p *602 LUX.LIB 13487 05-25-94 3:44p *602 CCSLOAD.EXE 20489 05-25-94 3:42p *602 LOADBASE.EXE 8417 05-25-94 3:43p *602 *Novell Internal Control Number INSTALLATION INSTRUCTIONS 1. Create a directory in the SAA server. (SYSTEM\NWSAA\LUX\DOS) 2. Copy the files the files in SAA010 into the directory. SOLUTION SPECIFICS A. GENERAL 1. RUI or SLI verbs may not post as complete, even though a trace run at the server shows the response returned to the client (eg. the trace obtained via CSSTATUS may show an RUI_READ request RET TIME:00:00:00:60 VPL= RUI_READ 000000 ......................... followed by the response returned to the client REQ TIME:00:00:00:60 VPL= RUI_READ 000000 ................... but the verb remains stuck IN_PROGRESS 2. The NWSAA_INIT verb was not checking all eight bytes of the profile name. When the first four bytes were not unique, LUX returned a primary return code of SV_STATE_CHECK and a secondary return code of SV_SESSION_ALREADY_OPEN in error. 3. A new return code was added to LUX when NWSAA is unloaded or a hard reset LU is performed at the server: Primary return code LUX_SESSION_FAILURE and secondary return code LUX_NWSAA_SESSION_RESET. 4. For DOS only, if the nearest server cannot be determined within fifteen seconds, THE SLI_OPEN or RUI_INIT fails. 5. RUI_WRITE with no data was being rejected with a parameter error, but is valid (eg. RH with change direction ) 6. Applications that poll the primary return code may fail. The return codes were set prematurely when the data size exceeded the packet size (approximately 500 bytes for DOS and 4000 bytes for NLM) Applications that use LUX callback posting are not impacted. TO RUN LUx ---------- Prior to running a LUx DOS application: - the LUX TSR may be loaded via "CCSLOAD LUX". or - the application may be allowed to load the TSR. In either case, LUx dynamically links to the code in the TSR when the application makes the initial load request. The EXEs provide LUx services to LUx applications. They work together at the DOS Client to communicate with a host system. TO UNLOAD THE LUx TSR --------------------- Following the completion of LUx applications: CCSLOAD /U LUX Files Description ----- ----------- SYSTEM\NWSAA\LUX\DOS\CCSLOAD.EXE LUx loader SYSTEM\NWSAA\LUX\DOS\LOADBASE.EXE Lux loader TSR SYSTEM\NWSAA\LUX\DOS\LUX.EXE LUx API TSR SYSTEM\NWSAA\LUX\DOS\LUX.LIB LUx API Library (linked with application) The EXEs provide LUx services to LUx applications. They work together at the DOS Client to communicate with a host system. Developing LUx Applications --------------------------- The LUX library is used by the application developer to build LUx applications. It is not required at the DOS Client to run the application. A LUx application is linked with the Novell LUX.LIB when the application is developed. The LUx Library provides the following LUx entry points: SETUP_NWSAA - Setup APIs for loading,linking & unloadingsoftware. SVC_NWSAA - Service APIs for Initializing and Terminating NetWare for SAA LUx sessions, and for the Convert function. LUX_NWSAA - LUx APIs - Request-unit interface (RUI) - Session-level interface (SLI) FOR MORE INFORMATION For information regarding the writing of DOS LUx applications write to: Novell, Inc Attn: Product Marketing 890 Ross Drive Sunnyvale, CA 94089 Patch History: SAA010.EXE supersedes SAALUX.EXE. ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ÿ