SAA Gateway Operational Procedures

Starting the Gateway

The gateway contains a DOS boot partition. At power on, or warm reboot, the gateway will go to the power on self tests, load DOS command.com and present the date for verification. Press ENTER. The time will be presented for verification. Press ENTER again. The DOS C:\> prompt will then be displayed. Type the word

server

and press ENTER.

The Netware 3.11 Runtime Operating System will load. This may take up to a minute, or so. Various messages will be displayed. Messages regarding errors with printers may appear. Press ESC as instructed to continue. After this, two paragraphs of messages should appear describing the environment. The first will be a 'disconnect' message of the gateway from the local 3174 controller, UWMLOC6. This should be followed immediately by a 'connect' message paragraph. At this time, the gateway is communicating with the controller. If the mainframe setup (described below) has been accomplished, the gateway (except for HostPrint) should be ready for operation.

Load the HostPrint software at this time by entering

load hostprt

A number of messages about missing forms on various servers will appear. These are normal. Messages about not being able to connect to servers are not normal. These may be caused by servers being down or missing GUEST accounts.

Swapping Gateway Machines

The PC rack in the machine room has two IBM PS/2 Model 57 SAA Gateway machines. At any given time only one of the machines is running. The second machine is configured and ready to be plugged into the network in case the first machine fails. To perform the swap, do the following:

Power down both machines
Move the two token ring connections. Stickers on the media filters have info on what should connect to what.
Move the keyboard connection.
Connect a monitor
Check to make sure there is a power cord on the machine to be used.
Power up.

Before resorting to a machine swap, reboot the currently operational machine. In many cases, this will be all that is required to restore service.

Preparing the IBM Mainframe

Before the gateway can be used, the mainframe VTAM facilities have to be started. Activate the mainframe I/O port by entering:

v 5fd,online

at the system console and pressing ENTER. Then, again at the system console, type:

v net,id=uwmsaa,act

and press ENTER to start the gateway physical unit (PU). The mainframe system log should show that the PU UWMSAA is active. If so, type:

s saaon

and press ENTER to start the procedure to activate the logical units (LUs) controlled by the UWMSAA PU. Messages should appear in the system log showing the vary commands and eventually the resulting active status of each LU. At this point, users should be able to log on the mainframe.

Starting the Gateway Monitor

The gateway software contains a status monitor which presents a good picture of all the gateway connections. To start the monitor, go the the gateway screen and verify that the : prompt is present. At the prompt, type:

csstatus

and press Enter. A graphic presentation with a 'CSStatus Options' menu will appear along with some general information at the top of the screen. With the arrow keys, hilite the menu item, 'Service Options' and press ENTER. A'Product Name' menu will appear. Select 'Netware for SAA' and press ENTER. A 'Service Function' submenu will appear. Select 'Display Status for Service' and press ENTER to bring up the status screen for the PRODuction service profile. The 'Status Summary and Session Information' window shows the number of currently configured LU's, the number of active LU's (actually connected at the time), the host connection type (ITRN means token ring) and Host Link Status which should be "CONNECTED." The LU listing in the bottom portion of the screen contains a number of headings:

LU - the hex address of the LU
Userid - the Netware userid of the person currently using the session. Some offices, such as the Grad School do not require a Netware login, so this field may be blank or contain a name common to all users in that office or department.
Internetwork Address - the Netware internet address of the workstation including an 8-char. network no. followed by a 12-char. network interface card no. On a token ring LAN this last no. is the token ring address of the LAN adapter. On an ethernet LAN, it is the 12-char. ethernet adapter no.
LU Pool - each office or department is assigned a pool of sessions for their exclusive use. This column shows the pool name of the session.
Status - a two-part description of the current status of the session. The first part describes the gateway-to-workstation status and is either UP or DN (down). UP means a PC is running the workstation emulation software and has made a gateway connection. DN means the session is not currently in use. The second part describes the VTAM status of the session and is INA (inactive), ACT (active), BND (bound) or UNBD (unbound). INACT means the session is inactive to VTAM, i.e., the PU and/or the LU have been varied inactive. ACT means the session is active on VTAM. BND means the session is active and is attached to a mainframe application such as TPX, i.e., the terminal should be ready for use.
Appl_ID - the VTAM application name the workstation is connected to. This field is non-blank only while the status is UP-BND.
WS Uptime - the elapsed time since the workstation connected to the gateway.

Additional information on the session is available by hiliting the LU of interest (using the arrow and PgUp and PgDn keys) and pressing ENTER. An LU Operations window will open in which the Display Additional Information for LU is the first choice. Hilite this option and press ENTER. An Additional Information window will appear containing the following items:

LU Category - POOLED for all of our sessions.
LU Name - the VTAM LU name of the session (without the leading @ sign).
User Name - the Netware userid (could be different from the mainframe userid).
Protocol - SPX for our sessions.
Trace Status - ordinarily not being traced.

Press Escape to return to the previous window. The RESET functions may be useful in situations where a particular user is experiencing problems. Using these functions will cause the session to be disconnected, so, if possible, have the user save any pending updates before doing a reset. The trace functions would not normally be used.

Press Escape to return to the LU status display.

Shutting down the Gateway

If the status monitor is running, press Escape and follow the instructions to leave the status monitor or ALT-ESCape to go from the HostPrint control panel to the : prompt. At the : prompt, type:

unload hostprt

and press ENTER to shutdown HostPrint. Then type:

csunload prod

and press ENTER. You should receive a message about PROD being unloaded. At the : prompt, type:

csdown

and press ENTER. A series of NLMs will be unloaded. Then to take the runtime server down, enter:

down

and press ENTER. Per the instructions, type

exit

to return to the DOS prompt. At this time the PC can be shut down, rebooted or restarted with the server command, as necessary.

Reloading a Profile after a Configuration Change

Assuming the gateway sessions are up and available for use:

At the mainframe main console, vary the gateway sessions INACTIVE by entering

s saaoff

and pressing ENTER.

Vary the mainframe PU INACTIVE by entering

v net,id=uwmsaa,inact,f

The SAA Gateway PC will beep when the PU goes inactive and if the status monitor is not running, a disconnect status paragraph will appear on the PC screen.

Go to the SAA Gateway PC keyboard. If the status monitor is running, press Escape and follow the instructions to leave the status monitor or ALT-ESCape to go from the HostPrint control panel to the : prompt. At the : prompt, type:

unload hostprt

and press ENTER to shutdown HostPrint. Then type:

csunload prod

and press ENTER. You should receive a message about PROD being unloaded.

At the : prompt, type:

csload prod

and press ENTER to load the revised profile.

Return to the mainframe console and type:

v net,id=uwmsaa,act,scope=all

and press ENTER to start the gateway physical unit (PU). The mainframe system log should show that the PU UWMSAA is active. At this point, users should be able to log on the mainframe. The SAA Gateway PC should beep and show a connection status paragraph.

Load the HostPrint software at this time by entering

load hostprt

and pressing ENTER at the Gateway keyboard. A number of messages about missing forms on various servers will appear. These are normal. Messages about not being able to connect to servers are not normal. These may be caused by servers being down or missing GUEST accounts.

Updating the SAA Gateway Profile (Configuration)

Use the following procedure to add one or more sessions to the PROD profile. Although it is possible to configure and store a number of profiles, we currently use only one. Both the mainframe PU definition (stored in SYS1.VTAMLST(UWMSAA)) and the PC gateway profile can be updated while either or both systems are operational. The changes will not take effect until the start/stop procedures described in this document are carried out. I prefer to update the mainframe definition first, print out the resulting member (or changed lines) and then update the gateway definition. I have included quite a bit of commentary information in the mainframe definition to make it easier to keep the two configurations in sync. Ideally all the LU's for a given pool or department should be defined as a set. However, sessions are added more or less randomly based on demand, so pools are fragmented in some cases. In general, new sessions get added at the end.

On the mainframe, edit SYS1.VTAMLST(UWMSAA) to add the new LU definitions. Update the comments section at the beginning with the date and short description. Print off the sections that contain the changes.
Edit IPO1.PROCLIB(SAAON) and (SAAOFF) to include or delete 'vary' statements for the LU's that have been added or deleted.
Go to a PC and login to the SAA Gateway machine as SUPERVISOR. At the DOS prompt type g: and press ENTER. Type cd \system\cscon and press ENTER to get to the configuration directory.
Type cscon to start the configuration utility. Select the SAA server, and type in the password at the prompt. This brings up the Available Topics menu.. Select Configure Communication Services. Then select Netware for SAA on the following menu. Choose the PROD profile on the Select Service Profile menu.
If you are adding or deleting LU's, choose Configure Host Connection. Update the Number of Dependent Sessions Supported. Press ENTER then ESC to return to the previous menu.
To add display sessions, choose Configure Sessions Then choose Configure LU Pools. Select the pool to be updated. Select the LU Address and press ENTER. A box containing the starting and ending values for the LU ranges will appear. The LU numbers start with 2 and end at one plus the number of sessions defined for the profile. If you need to update a range, select it from the list. If you need to add a range, press INSERT. The LU Range box will appear. Update the starting and ending LU numbers. Use decimal numbers from the listing of UWMSAA. Press ENTER and then ESC. Add ranges to pools as necessary to define the desired LU's.
Press ESC to return to the LU Pool Configuration screen. Select the VTAM LU Name item and press ENTER. Tab to the VTAM LU Name field to be updated and press ENTER. Tab to the name field on the resulting box. CSCON will not accept the @ character or any special characters in a name. I use the UWMSAA LU name without the @ sign. There is no requirement that the LU names defined here be the same as those used on the mainframe definition. The names defined here are shown on the gateway status screens. Using the names without the @ make it easy to determine the mainframe LU name for troubleshooting purposes. Fill in the names as required. Press ESC to return to the LU Pool Configuration screen.
If the LU's being defined are not MOD 2 (24x80), update the Model Number field. It is not possible to define more than one MOD type in a given pool.
The default values should be used for the remaining fields on the LU Pool Configuraiton screen.
Press ESC and ENTER as required to terminate the CSCON utility. Both the mainframe and the gateway are now ready for the installation of the revised configuration.

HostPrint Definitions

Defining a Hostprint Printer requires the following processes:

Selecting an existing or defining a new print device.
Importing print devices.
Defining a print job.
Defining the dedicated LU.
Defining the printer to JES on the mainframe.

Details for each step are defined in the following sections. See also the Netware Hostprint 1.1 Quick Configuration card and the Hostprint manual.

Defining a Print Device

Login to the SAA Gateway server as supervisor.
Check to make sure you are at the SYS:SYSTEM directory.
Type hpdef and press Enter.
If you know of a device that is close to what you need, you should copy it to a new definition. Then edit the new defintion to make the necessary changes. A print device name can be up to 32 characters long. Spaces and special characters are supported.
Return to the HPDEF Options Menu and choose Edit Print Devices. Press Enter. Hilite the device name to be changed and press Enter.
Hilite the name of the device function to be updated and press Enter. Change or add the code sequence to be updated. Press Escape when finished. Hilite Yes and press Enter to finalize the change.
Make any more changes that are required. Then press Escape twice to return to the HPDEF Options menu.
Select Export Print Devices and press Enter.
Press Escape to return to the HPDEF Options menu.
Press Escape to display the HPDEF Exit options menu. Select Save Data and press Enter.

Importing the updated Print Devices to the Printdef Database

Login as supervisor to the SAA Gateway, if not already logged in. Go to the SYS:SYSTEM directory, type printdef and press Enter.
Select Print Devices and press Enter.
Select Import Print Device and press Enter.
Select the print device name to be added and press Enter.
Repeat the process until all the new devices have been added.
Press Escape as necessary until the Exit PRINTDEF confirmation box appears. Select Yes to exit. Select Save Data Base, press Enter to exit.

Defining a Print Job

Login as supervisor on the SAA Gateway server. Map a search drive to INFOSYS/SYS:PUBLIC. map ins s16:=infosys/sys:public Enter your INFOSYS userid and password when prompted.
Type printcon and press Enter.
Select Edit Print Job Configurations and press Enter.
If you need to update an existing job, select it and press Enter. To create a new print job, press Insert and enter a meaningful name. I use the printer LU name without the @.
Enter information for the file server that contains the print queue to which HostPrint will send the mainframe printer output.
Press Escape when the setup is complete. Select Yes to save the settings.
Press Escape one or more times until the Exit Printcon confirmation box appears. Select Yes to return to exit Printcon. Select Yes to return to the DOS prompt.

Configuring a HostPrint Session

In order to run the CSCON utility, COMMEXEC.NLM must be loaded on the SAA Gateway. If the gateway is up and running, COMMEXEC is loaded.
Login to the SAA Gateway from a workstation and go to the SYS:SYSTEM\CSCON directory. At the DOS prompt, enter cscon and press Enter. Select Configure Communications Services and press Enter. Select Netware for SAA and press Enter. Select the PROD service profile and press Enter. Select Configure Sessions and press Enter. Select Configure Dedicated LUs and press Enter.
To create a new LU definition:

Press Insert.
Enter the new LU Name and address. The name does not have to match the LU name in the mainframe SYS1.VTAMLST definitions. However, the address must match the local address for the session in the mainframe definition.
Press Escape one or more times until the Create Dedicated LU? confirmation appears. Select Yes and press Enter to create the LU.

To configure or update an LU, select it from the list and press Enter.

HostPrint Printers