Citrix WinView Application Notes Attachmate's Extra! for Windows This application note is for informational use only and Citrix makes no representations or warranties with respect to the contents or use of this document or of any of third-party products discussed within. March 11, 1994 Citrix Systems 210 University Drive Suite 700 Coral Springs, FL 33071 (305)755-0559 FAX: (305)341-6880 Overview -------- This application note discusses the use of the Attachmate Extra! for Windows product (referred to as Extra!) with the Citrix WinView Application Server (referred to as WinView) product. Extra! is a Windows-based 3270-type terminal emulator that allows access to an IBM mainframe from a Windows workstation. Using Extra! on a WinView application server rather than on a DOS station provides all the benefits of application servers to Extra! users: high-speed remote access, enhanced WAN access, and access for underpowered LAN stations. The intended audience for this document is a engineer who has had hands on experience with WinView, NetWare, and Attachmate's Extra! products. The scenarios described in this document have been thoroughly tested by Citrix and Citrix believes you should have no problems using Extra! with WinView if you follow carefully the information and steps in this document. Other variations to the scenarios described in this document may in fact work fine, however they have not specifically been tested by Citrix. In order to maximize your chance for success, you should use the specified revision levels of all software products described in this document and stay within the bounds of the features and functions described in this document. Please note that this application note document is a living document and will be modified as new information and versions of the software described herein become available. Make sure you have the latest version of this document before you begin. The latest version is always available in the Citrix Forum on CompuServe. Requirements ------------ To use Extra! on a WinView application server you will need to have the following: Software Requirements - Citrix WinView 2.2 or 2.21 - Attachmate Extra! for Windows 3.5 or 4.0 - Novell NetWare 3.11, 3.12 or 4.01 - Novell NetWare for SAA 1.3b Hardware Requirements - NetWare file server - Mainframe Gateway server > NetWare for SAA server (may be same as file server) - WinView server > 486DX-25 CPU or larger > 12 meg memory or more > NetWare supported network adapter Configuration Notes ------------------- The desired number of concurrent Extra! users will help determine the hardware configurations of the WinView server and the mainframe gateway server. It is possible for the gateway server to service Extra! users from multiple WinView servers and also from DOS network nodes. For a large number (more than 15) of total Extra! users using the NetWare for SAA mainframe connection, you should consider installing NetWare for SAA on its own server rather than on the NetWare file server. The maximum number of concurrent Extra! users supported on a single WinView server is determined by the hardware specifications of that WinView server. Memory is the most critical resource for the WinView server in determining the number of users. Use the following rule of thumb: 8 megabytes base memory plus 2 megabytes for each Extra! user. Thus, a 16 megabyte system will support 4 concurrent Extra! users. To go beyond 16 megabytes, you will need either a EISA system or a 32-bit MCA system. Also, you should increase the CPU size as the user count goes up. The Network Interface Card (NIC) can also make a difference. For large user count systems, you should use a high performance bus master NIC in your WinView server. The following table shows recommended hardware configurations for your WinView server according to user count: USERS MEMORY CPU/mhz BUS NIC 2 12meg 486-25 ISA low performance 4 16meg 486-25 ISA low performance 6 20meg 486-33 EISA med performance 8 24meg 486-33 EISA med performance 10 28meg 486-50 EISA high performance 12 32meg 486-50 EISA high performance It is important to note that the above user count recommendations are based on the assumption that each user will only be running Extra!. If the users are running other applications along with Extra!, the memory requirements per user will go up. You may also need to increase the CPU power accordingly. Limitations of Extra! under WinView ----------------------------------- Not all features and functions of Extra! are supported under WinView. Limitations under WinView are itemized below: 1) Of thirteen mainframe connection types that Extra! offers, only the NetWare for SAA gateway is recommended for use with WinView at this time. Citrix will test the Attachmate 3270 Gateway and will update this update this document accordingly when complete. 2) Only the US English language option has been tested and is known to work. 3) Only the standard PC 101-key keyboard is supported. None of the optional keyboards are supported. Attachmate License Agreement ---------------------------- Before using Extra! from a WinView server, it is important to understand Attachmate's licensing policy. Each WinView user who can potentially run Extra! is required by Attachmate to have a separate license for Extra!. For example, if you have ten users configured on the WinView server and each is setup to run Extra! then you will need ten Extra! licenses. Even if only five of the ten users would ever log into the WinView server concurrently, you will still need ten Extra! licenses. An Extra! license is obtained by purchasing a shrink-wrapped copy of Extra! or by purchasing an Additional License Agreement for Extra!. Installation ------------ The Extra! installation, as described in the Extra! shrink- wrap product, has no server-based installation procedure. Attachmate has a server-based installation procedure that is available from Attachmate upon special request, however this has not been tested by Citrix. Consequently, each WinView user of Extra! will have to install Extra! from the diskettes. The installation of Extra! on WinView has an additional caveat. The Extra! Setup program creates a temporary directory in the C:\ root directory of the installing system. Unfortunately, WinView secures the C:\ root directory and will not let ordinary users read or write to it. One solution to this problem is to make each WinView user an administrator so that he can override the security. This, however, would leave your WinView system unsecured. Another solution to this problem is for the WinView administrator to create the Extra! temporary directory by hand and then change the access control list (ACL) to allow access for all users. This can be accomplished by the following procedure: 1) Log into WinView as an administrator. 2) Go to an OS/2 command prompt. 3) Make your working drive C: by typing: C: 4) Go to the root directory by typing: CD \ 4) Create the temporary directory by typing: MD E4WTEMP 5) Change the security of the directory by typing: CONFIG ACCESS E4WTEMP *.* RWCXA The above procedure will allow each Extra! user on WinView to install Extra! without being a administrator level user in WinView. It has one side effect, however, that the temporary directory will not be removed at the end of each Extra! install. Extra! 3.5 Installation The following steps must be repeated by each WinView user of Extra! 3.5: 1) Enter a Windows standard mode session from any WinView station. Make sure you are logged into the NetWare server. 2) Select the RUN menu item from the FILE pulldown menu in the Program Manager and then enter A:\SETUP. You could also click on A:\SETUP.EXE from the Windows File Manager. 3) Click on Continue when you see the Extra! welcome screen. 4) You will be prompted for the path name of the directory in which you wish to install Extra!. Since we are doing individual installs rather than a server-based install, each user must specify a unique directory here. You could specify your personal directory on the NetWare server, such as Z:\USERS\RANDYW\EXTRAWIN, or you could specify your personal directory on the WinView server, such as C:\USR\RANDYW\EXTRAWIN. 5) When prompted to install the Extra! program files or the Extra! help files, select both and click on Continue. 6) Next, you will be prompted for the connection type. Select only Novell SAA Gateway. Do not select any other connection types since no other options have been tested by Citrix. 7) Now, the Extra! Setup program will copy the files from the diskettes to your specified directory. Insert disks 2 and 3 when prompted. 8) You will be prompted to change your AUTOEXEC.BAT file at this point. You should say no. Since WinView has an AUTOEXEC.BAT per user which resides in your \USR\username directory and since Extra! assumes a single global AUTOEXEC.BAT, you will have to hand edit these Extra! changes in your local \USR\username\AUTOEXEC.BAT file. 9) Extra! is now successfully installed. You will be asked to edit the configuration. The first configuration option you will be asked to edit is the SAA Adapter Parameters. You should specify your User name and password if desired. Then click on the Edit button and fill in the name of the NetWare for SAA gateway server name. Note that the server name is case sensitive. Next, fill in the SNA Service name which was specified during configuration of the NetWare for SAA server. Also here specify No Pooled Resources and No Keyboard Override. Then click on OK. 10) The next configuration option you will be prompted for is the Number of Sessions. The default is 16, however you should choose the number this user will actually need. Keep in mind that both terminal and printers require a separate session. 11) The last configuration option you will be prompted for is to configure each session. You should specify for each session whether it is a terminal session or a printer session. If it is a terminal session, then you should select the Auto Sense Screen Size Terminal as the type of terminal. If it is a printer session, you should specify DFT LU1 8KB Printer for the type of printer. 12) The Extra! Setup program is now complete and it will ask you to Run Extra! at this point or Exit to Windows. You may select either option. 13) Note: the Extra! documentation suggests that you should install two TSR programs before running Extra! under Windows: IPXINTFC.COM and E4WTIMER.COM. DO NOT install either of these TSRs. Neither of these are required under Citrix WinView and may actually cause problems if you install them. Extra! 4.0 Installation The following steps must be repeated by each WinView user of Extra! 4.0: 1) Enter a Windows standard mode session from any WinView station. Make sure you are logged into the NetWare server. 2) Select the RUN menu item from the FILE pulldown menu in the Program Manager and then enter A:\SETUP. You could also click on A:\SETUP.EXE from the Windows File Manager. 3) You will be prompted for the path name of the directory in which you wish to install Extra!. Since we are doing individual installs rather than a server-based install, each user must specify a unique directory here. You could specify your personal directory on the NetWare server, such as Z:\USERS\RANDYW\EXTRAWIN, or you could specify your personal directory on the WinView server, such as C:\USR\RANDYW\EXTRAWIN. 4) When prompted, select the type of installation you want to perform. If you are not sure, select Complete install. 5) Now, the Extra! Setup program will copy the files from the diskettes to your specified directory. Insert disks 2, 3 and 4 (and disk 5 if you have a 5.25" drive) when prompted. 6) You will be asked if you want to add Extra! to your path. You should answer yes. 7) Extra! has now been installed and you will next be asked if you want to continue and configure Extra!. You should configure Extra! at this point. 8) You will be prompted for the connection type. Click on Network and then select IPX/SPX to Novell SAA Gateway from the menu box. Do not select any other connection types since no other options have been tested by Citrix. 9) Next, you will be asked to the SAA Adapter Parameters. You should specify your User name and password if desired. Then click on the Edit button and fill in the name of the NetWare for SAA gateway server name. Note that the server name is case sensitive. Next, fill in the SNA Service name which was specified during configuration of the NetWare for SAA server. Also here specify Pooled Resources and no for Prompt for Alternate Resource Names. Then click on OK. 10) You will last be asked to specify each session. You should specify for each session whether it is a terminal session or a printer session. If it is a terminal session, then you should select Auto Sense for Screen Size. If it is a printer session, you should specify LU1 (8K) Printer for the type of printer. You can also add and delete sessions at this point. 11) The Extra! Setup program is now complete and it will ask you to Run Extra! at this point, view the Extra! read me file or Exit to Windows. You may select any option. 12) Note: the Extra! documentation suggests that you should obtain two files from Novell, NWIPXSPX.DLL and VIPX.386, and install them before running Extra! under Windows. DO NOT install either of these files since they are come with your WinView system and are already installed. Many NetWare network administrators like to avoid going through the Windows' Setup procedure for each user. In some cases, they copy .INI files from a master or template user or other such acts. Citrix recommends that you run the Extra! Setup program for each WinView user since trying to avoid the Setup step is both tricky and error prone. Operation --------- After Extra! is successfully installed for each WinView user, running Extra! should be no different, operationally, than running Extra! from a DOS node. However, there are some additional considerations described below. Having enough LUs Each Extra! user can have multiple concurrent mainframe sessions as either terminal or printer sessions. It is important to keep in mind that each mainframe session requires an LU, including printer sessions. Your mainframe gateway server must support enough LUs to satisfy all of your users' needs. Windows Enhanced Mode Extra! will function under WinView in either Windows Standard Mode or Windows Enhanced Mode. To start Windows in enhanced mode you will execute WIN /3 from the command prompt or select the WINENH.PSF file as your First User Program in the Config Profiles for that user. Closing Sessions If you are using WinView 2.2, you may experience a hang in your Windows session when you close a terminal session by using the Close Session option in the Extra! terminal emulator's pulldown. There are several workarounds for this problem. First you should consider upgrading your WinView to 2.21 which does not exhibit this problem. Alternatively, you can install the 2.2 updates which are available on CompuServe. If you cannot upgrade your WinView 2.2 system, the problem can be worked around by exiting the Extra! terminal emulator without explicitly closing the session first. The terminal will close the session automatically as it exits. Another work around is to run Extra! in Windows Enhanced Mode as described above. Finally, you can obtain from Attachmate an new SESSION.DLL which also fixes the problem. File Transfer When using the file transfer feature in Extra!, you can have the file transfer take place to or from the NetWare file server, or from the WinView server. If you are using Citrix LANLINK to connect to the WinView server, you potentially have an additional option of transferring files to or from the local hard disk on your client PC. This can be accomplished by using the "Client Drive Mapping" feature of LANLINK. All file transfer operations are accomplished the same way, regardless of where your file resides. The drive letter will determine which hard disk your file will be transferred to or from. Thus, it is important to understand where each drive is MAPped to before you begin a file transfer function. If you are connected to WinView with a Citrix RLINK client, you have to use a two-step process to transfer files to or from you local hard disk. For example, if you are trying to upload a file to the mainframe from your local hard disk, you would first upload the file to the WinView server's hard disk using WinView's upload command. The second step is to upload it to the mainframe from the WinView server's hard disk using the Extra! file transfer program. To download a file from the mainframe to your local hard disk, you would first use Extra! to download it to the WinView server's hard disk. Then you would use the WinView download command to transfer the file down to your local hard disk. Printing Printing with Extra! also has several options. Your mainframe program can print to a printer attached to the mainframe, to a printer attached to the NetWare print server, or to a printer attached to your WinView client PC. To print to a mainframe printer, you need to only specify the name of a printer located on the mainframe. To print on either the network printer or on your local printer, you must specify to the mainframe the name of a printer that has its LU assigned to the mainframe gateway server. To print on the NetWare print server, you must use the NetWare CAPTURE command to redirect one of your Windows' print devices (eg. LPT1.DOS) to a NetWare print queue. You can perform the Netware CAPTURE function from within Windows by going to the Windows Print Manager, selecting Options and then selecting Network Connections. After you have CAPTUREd your printer, you will need to start an Extra! 3270 Printer session configured to your CAPTUREd print device (eg LPT1.DOS) and leave it running in an online state. Finally, tell your mainframe program to print to a printer with its LU assigned to the mainframe gateway server. To print to the local printer attached to your client PC, you must use the WinView local printing feature. Do not use the NetWare CAPTURE command for your Windows' print devices (eg. LPT1.DOS). Instead you will specify a printer device name in the "Printer Port" field of your LANLINK or RLINK setup screen before you log onto the WinView server. This will redirect any print jobs directed to LPT1 to your local LPT1 port. Next, you will need to start an Extra! 3270 Printer session configured to your LPT1 and leave it running in an online state. Finally, tell your mainframe program to print to a printer with its LU assigned to the mainframe gateway server. If you wish to use a device other than LPT1, you can use the WinView "CHANGE MAP" command to configure the local printer. See the Citrix WinView Command Reference, page 2-29, for more details. Compatibility ------------- There are no known hardware incompatibilities when using Extra! and WinView at this time. When selecting a hardware platform for WinView, make sure you choose from the list of supported hardware devices in the "Citrix Compatibility Guide". Diagnosing Problems ------------------- The most common problem encountered using Extra! under WinView is not being able to get a mainframe connection. This usually has nothing to do with WinView but rather is a problem in connecting to the gateway server or a problem connecting the gateway server to the mainframe. The first step in diagnosing a connection problem is to run Extra! on a DOS/Windows node and try to connect. This will remove WinView from the picture to help isolate the problem. If you cannot get a connection from the DOS/Windows node, you should contact Attachmate's tech support for help. If you do get a connection from the DOS/Windows node, make sure that Extra! under WinView is configured the same as the DOS/Windows node. If you are still unsuccessful making a connection from WinView, contact Citrix's tech support.