USING STARSQL WITH NETWARE FOR SAA 1.3 & 2.0 STARSQL 1.04 September 19, 1995 Copyright 1995, StarWare Connectivity Software, Inc You use the NetWare for SAA connection method primarily for DB2 MVS, since configuration for access to an AS/400 is simplified by using the NetWare AS/400 Router for PC Support or NetSoft NS/Router. StarWare recommends the use of NS/Router for ease of configuration and performance (see NSROUTER.TXT). NetWare for SAA 2.0 includes a version of NetSoft NS/Router that works only with NetWare for SAA. It is available free of charge to Novell customers who use NetWare for SAA 1.3b. Contact: (Internet) www.novell.com/ServSupp/texttids/netware/250063.tid (CompuServe) NOVLIB+ FORUM Lib 9 Communications Product NSROUT.EXE. NETWARE FOR SAA 1.3b StarSQL has been tested with NetWare for SAA v1.3b and NetWare for SAA v2.0 (see NetWare for v2.0 below). In addition, the Novell-supplied patches SAA007.EXE and SAA008.EXE were installed on the server, and SAA012.EXE was installed on the client. The latter is important for correct operation of StarSQL, as it contains fixes for the NetWare LU6.2 for Windows client support. These patches are available directly from Novell and from Novell's on-line support areas such as Compuserve (NetWire) and the Internet (www.novell.com, gopher.novell.com, and ftp.novell.com). The latest Novell-recommended patches for the NetWare for SAA v1.3B server are SAA008.EXE and SAA014.EXE. Please contact Novell for information about special considerations when using NetWare client software with Windows for Workgroups; for ease of configuration, use Windows 3.1 rather than WFW. Installation and configuration of the NetWare LU6.2 for Windows client support is described in the NetWare LU6.2 for Windows Configuration Guide (100-001208-001). Procedure for setting up a NetWare client: INSTALLATION: 1. Install the standard NetWare DOS & Windows client software, including Windows support (e.g. the diskettes "WSDOS_1", "WSDRV_2", "WSWIN_1"). 2. Install the NetWare for SAA NetWare LU6.2 Client Support Files (Disk 10 of the Netware for SAA 1.3B diskette set): Create a new directory (e.g. C:\LU62WKS) and copy the contents of this diskette into the directory. 3. Install the SAA012 patch - Run SAA012.EXE in an empty directory to extract its contents, read SAA012.TXT, and copy the files to LU62WKS, replacing the older version of each file. 4. Edit AUTOEXEC.BAT: Add C:\LU62WKS to the PATH statement and run AUTOEXEC or restart to have the change take affect. 5. In Windows, create a program item for C:\LU62WKS:WINAPPC.EXE in the NetWare Tools program group. 6. Install StarSQL. CONFIGURATION: 1. Copy WS.CFG from C:\LU62WKS to C:\WINDOWS and edit the copy in C:\WINDOWS (e.g. with NotePad) - Enter: NETWARE_SAA_SERVER NETWARE_USER_NAME NETWARE_SERVICE_NAME (i.e. the NetWare for SAA profile name). This avoids having to enter this information everytime you use the LU6.2 for Windows support. 2. Within Windows, start WINAPPC.EXE (program item "NetWare LU6.2 for Windows)". 3. Create the CPI-C side information file (in C:\LU62WKS). See the Novell documentation for details. See "CPIC SIDE INFO RECORD SETUP FOR DB2 MVS" below for hints on setting up for connection to MVS. 4. If you wish to automatically start the LU6.2 for Windows support when you start Windows, add the following to AUTOEXEC.BAT: WIN /3 WINAPPC CPIC sideinfo.cpi /A See SAA012.TXT (the readme that comes with the SAA012.EXE patch) for more information. Be aware that this statement may cause problems if the NetWare server is unavailable. OPERATION: 1. Start Windows 2. Start WINAPPC.EXE (Program item "NetWare LU6.2 for Windows") 3. Load Protocol Boundary. 4. Load CPI-C. Leave the WINAPPC.EXE program running while you use StarSQL (you can minimize the program window). PASSWORD PROMPTING: If the Netware user account that is entered in \WINDOWS\WS.CFG requires a password to access the NetWare server, it is possible that Windows will hang when the user is presented with the password prompt on connecting a data source. If this happens, a suggested workaround is to create a NetWare user (e.g. "SAAUSER") that does not require a password, but that has no file server privileges, and use this user ID in the NETWARE_USER_NAME field of \WINDOWS\WS.CFG. TRACING: To enable tracing between the client to the Novell server, add these fields to the WS.CFG file in the WINDOWS directory: TRACE_API = 1 TRACE_MSG = 1 This will create an output.pc in the C:\ directory and will show the binds being sent when loading cpi-c. SIDE INFO RECORD SETUP FOR DB2 MVS: Edit the side information database as follows: First setup screen: Local LU Name - This is the VTAM/Novell SAA name . PC's LU name from VTAM. See Example on Page 2 of the DB2MVS.txt file, LOCALLU1 is an example of an LUname. PU Name - Use the Name of the PU from the example on Page 1. STAR1 is the PU name in the example on Page 2 of the DB2MVS.TXT file. Network Name - Must match HOST network Name ( get from VTAM administrator). Security type - Enter 2 UserID/Password - Enter Userid and Password that you will use to log onto host. If security is 2 then Userid and Password are required. Local LU address - 0 for independent sessions, decimal equivalent of the hex port for dependent sessions. LU Session Limit - 1 for dependent, 10 for independent. Detach PU type - Enter 1. Second setup screen: Remote LU Name - This is the DB2 LU Name (get from VTAM/System administrator) Use VTAM change Log Inventory Utility. Data Link Control - Typically the value is ITRN (for Token Ring). See the LU6.2 manual for Windows Configuration Guide that is included with Novell SAA Gateway. SDLC if the SAA is dialing in via leased line or direct dial up. Network Adapter Number - Almost always 0 Network Adapter Address - This value is the IBM HOST address (ie: 400037450001). (get from VTAM administrator). If SDLC and Leased line could be the same as the address of the gateway(C2) LU Session Limit - Enter 1 for dependent sessions, or 10 for independent sessions. Max Logical record Size - This value is from the LOGMODE table in VTAM(examples are 256, 512) 32767 is the entry here. Character Set - 2 indicates that TABLEG.DAT will be used. Make sure the table has been moved to the LU6.2 directory from the LU6.2 set up disks. Local Program Name - STARSQL Remote Program Name - OVERRIDE Third setup screen: Mode Name - Enter the HOST Mode Name. Get from VTAM administrator. Example on Page 3 of DB2MVS.TXT has MLU62A as a dependent node Max Negotiable Session Limit - Enter 1 for dependent, or 4 for independent. Automatic Activate Session Limit - Enter 0 for dependent, 4 for independent. Minimum Contention Winners - Enter 1 for dependent, 4 for independent. Minimum Contention Winners target - Enter 0 for dependent, 4 for independent. Pacing Size - This comes from the DB2APPL or Mode Definition. Get this info from VTAM administrator. Max RU Size - Also in the MODE ENTRY TABLE. Example on Page 3 of the DB2MVS.TXT file has RUSIZES=X'8989' This means 4096 (8*2 to the 9th power). Min RU Size - 256 from MODE ENTRY TABLE. 256 CNOS Flag - Enter 0 for dependent, or 4 for independent sessions. CNOS Termination Set - Enter 0 SNA Service Profile Name - Enter the Profile Name containing the LU6.2 definition on the Novell SAA Server. NETWARE FOR SAA 2.0 StarSQL has been tested with NetWare for SAA 2.0. NetWare for SAA 2.0 must be installed on the NetWare server before beginning the client setup and configuration process. The current recommended patches for NetWare for SAA 2.0 are SAA016 and SAA017. The manual "NetWare for SAA 2.0 Installation Guide" describes how to install this product on a NetWare server. The NetWare for SAA 2.0 INSTALL utility install the API client software in the SYS\SYSTEM\NWSAA\APIS\WINDOWS directory on the server. Instructions for configuring the NetWare for SAA 2.0 server can be found in "NetWare for SAA Administration Guide for Mainframes and Peer Nodes". Instructions for installing and configuring the client to run NetWare for SAA 2.0 can be found in the Novell Netware document "API Configuration Guide for MS Windows Clients". The client configuration process involves two steps: 1. Use the Netware for SAA 2.0 API Setup utility to install the client software. This creates a program group that contains an icon for the Netware for SAA 2.0 API Configuration utility. Then you use this utility to create the CPI-C Side Information record. The Symbolic Destination Name that you specify when creating this record corresponds to the Side Information Record Name that you will need to enter on the StarSQL Connection Setup. In addition, you will need to add the directory of the NetWare API directory (typically C:\NWSAAAPI) to your path. 2. To use StarSQL, the Partner TP of the Side Information Record needs to be 076DB and TP Type Service should be selected. This TP corresponds to the IBM Distributed Relational Database transaction program.