Cisco IOS for S/390 Operation

If you are using the Inter-User Communications Vehicle (IUCV), examine the T01LOG output data set for message T01IU001I (Connection to IUCV Established). If Cisco IOS for S/390 cannot connect to IUCV, message T01IU004I displays.

If Cisco IOS for S/390 fails to connect to IUCV, it will continue to retry at 30 second intervals until successful connection.

Each task group is started by an IFS START command in the command file. This command, in turn, specifies the configuration file member that contains the parameters to be used by the task group as it starts. The main configuration member for the task group is specified by CNFG(xx) on the IFS START command for the task group. Some task groups also use secondary configuration members from the PARM data set as specified in their main configuration file. Generally speaking, a task group dynamically loads various other programs and tables from the STEPLIB data set during initialization and later, as needed.

The IJT task group uses IJTCFGxx, as this task group controls all other task groups. Therefore, you cannot restart this task group without stopping and restarting the entire Cisco IOS for S/390 address space.

The MVS operator is prompted after the STOP command to confirm the shutdown operation.

The first P command causes the following for each task group:

• TCP: APEND and TPEND are driven with DRAIN and STOP for all applications and Gated is stopped. If all applications issue TClose and AClose, then TCP continues shutdown automatically, stopping each LNI and freeing resources.

• APP: All Ptasks are notified of termination. They should also see APEND and TPEND from TLI (for example TCP). If all Ptasks terminate, then the APP task group stops.

• MAP: Should exit immediately.

• SNM: Should exit immediately.

• DNR: Attempts to stop the receive, send and timer threads. When all threads have ended, shutdown continues.

Since no new API endpoints or protocol sessions can be established when drain mode is in effect, listening endpoints receive a return code indicating the drain state. The socket interface interprets this return code and terminates certain socket functions in drain mode. Idle server tasks should disconnect from the API in this situation, letting Cisco IOS for S/390 come down.

The second P command causes the following for each task group:

• TCP: If any active TLI, OE socket, or IUCV socket applications are active, message T01SO010 is issued. This indicates TERM phase and displays the number of active address spaces using API services. APEND and TPEND with the TERM indication is issued to all remaining TLI users. If PROMPT was specified in IJTCFGxx, message T01SO012 is issued asking the operator if shutdown should continue. If the operator replies Y, shutdown of TCP continues immediately, otherwise shutdown is delayed.

• APP: Any active Ptasks are again notified to stop. All active TLI connections are immediately closed if still open (usually TPEND STOP from the first P command causes them to close immediately).

• DNR: Continues shutdown.

• MAP: Continues shutdown.

• SNM: Continues shutdown.

The third P command causes the following for each task group:

TCP: Stop immediately regardless of active users. Note that if the operator replied N to message T01SO012, this is treated as a second stop and message T01SO012 is reissued.

APP: Stops immediately.

DNR: Stop immediately.

MAP: Stop immediately.

SNM: Stops immediately.

If the address space does not terminate normally after 3 stop commands, issue the F TCPACCES,ILATCH command to see if there are any hung latches. If any latches are hung, issue F TCPACCES,ILATCH FREE LATCH(nn), where nn is the latch number for each hung latch. Shutdown should then proceed. If there are no hung latches after the third P command, issue F TCPACCES,SVCDUMP. When the SVCDUMP is complete, issue C TCPACCES to cancel the address space and contact technical support, supplying the SVCDUMP for problem resolution.

or

The P CLEAR command specifies to clear modules and control blocks from CSA and the subsystem hooks installed by this address space.

In addition, the P CLEAR command also performs the normal processing associated with an MVS STOP (P) command. Use the CLEAR option to stop Cisco IOS for S/390 before applying the updates. This command also lets Cisco IOS for S/390 use the most recent versions of the base modules when it is restarted.

The command must be issued using the subsystem recognition character, (in other words, P CLEAR) or by using the MVS modify command (in other words, F Cisco IOS for S/390,P CLEAR).

This command also activates the naval LUs required for Server Telnet and the client user commands (for example, FTP, FTP2, etc.).

//RUNTCP JOB
//*
//*    SAMPLE JCL PROCEDURE TO RUN TCP/IP
//*    THIS JCL CAN BE USED WITH ANY INTERFACE 
//*
//*    EDIT THE TRGINDX, SSN, SRC, SOUT, CMND SYMBOLIC PARAMETERS
//* 
//*    VERIFY THAT THE JOB CARD AND NAMING CONVENTIONS MEET 
//*    YOUR SITE'S JCL REQUIREMENTS, THEN SUBMIT THIS JOB. 
//* 
//TCPIP PROC TRGINDX='TRGINDX', TARGET LIBRARIES DSN INDEX 
//            SSN=ACSS,        DFLT SUBSYSTEM NAME 
//            SRC='%',         DFLT SUBSYSTEM RECOGNITION CHAR 
//            SOUT='*',        CHOOSE A HOLD NONPURGE SYSOUT CLASS 
//            CMND=START00     DFLT STARTUP COMMAND SCRIPT NAME 
//            CNFG=00          IJTCFGxx SUFFIX 
//* 
//TCPIP EXEC PGM=IFSSTART,REGION=6144K,TIME=1440, 
// PARM='IFSINIT,U=&SSN,P=T01,SR=&SRC,SO=&SOUT,CM=&CMND,CF=&CNFG' 
//* 
//STEPLIB  DD  DISP=SHR,DSN=&TRGINDX..LOAD 
//         DD  DISP=SHR,DSN=&TRGINDX..SASLINK 
//* 
//* WARNING:  THE LOAD DATA SET MUST NEVER BE ADDED TO THE LINK LIST. 
//*           TCPACCESS' ELEMENT NAMES ARE NOT UNIQUE AND COULD AFFECT 
//*           THE OPERATIONS OF OTHER SOFTWARE. THE LOAD DATA SET SHOULD 
//*           ALWAYS BE REFERENCED THROUGH A STEPLIB OR JOBLIB STATEMENT. 
//* 
//*        CONFIGURATION DATA SETS 
//* 
//SYSPARM  DD  DISP=SHR,DSN=&TRGINDX..PARM 
//SYSPROC  DD  DISP=SHR,DSN=&TRGINDX..PARM 
//* 
//*        LOG DATA SETS 
//* 
//T01LOG   DD  SYSOUT=&SOUT 
//SYSPRINT DD  SYSOUT=&SOUT 
//DNRLOG   DD  SYSOUT=&SOUT 
//DNRERR   DD  SYSOUT=&SOUT 
//GTDLOG   DD  SYSOUT=&SOUT 
//GTDERR   DD  SYSOUT=&SOUT 
//GTDTRC   DD  SYSOUT=&SOUT 
//MAPLOG   DD  SYSOUT=&SOUT 
//MAPERR   DD  SYSOUT=&SOUT 
//SNMLOG   DD  SYSOUT=&SOUT 
//* 
//*        DUMP DATA SETS 
//* 
//SYSUDUMP DD   SYSOUT=&SOUT 
//* 
//*        MISC DATA SETS 
//* 
//ARPAHELP DD  DISP=SHR,DSN=&TRGINDX..HELP 
//SYSHELP  DD  DISP=SHR,DSN=&TRGINDX..HELP 
//ABNLIGNR DD  DUMMY                       /* DISABLE ABEND-AID PROCESSING */ 

These are the only changes required. Copy the JCL stream from TRGINDX.CNTL(RUNTCP) to your started task procedure library.

You are now ready to start Cisco IOS for S/390. Before doing so, it is a good idea to review the installation steps in the Cisco IOS for S/390 Release Notes to ensure that you have made all the necessary changes.

To shut down the address space you can use either the subsystem recognition character (%) or the MVS STOP command (P Cisco IOS for S/390). The system will request confirmation with the following message:

As termination continues, messages will be issued indicating that various components are terminating.

The default file, START00, as distributed, contains the following:

DISPLAY IFS
DISPLAY SRC
START TCP CNFG(00)
START APP CNFG(00)
START DNR CNFG(00)
START MAP CNFG(00)
START SNM CNFG(00)
SET TEST ON TGB(IJT)

• Make a copy of the START00 member, giving it a new name (such as START01).

• Change the CNFG parameters on the START TCP and START DNR commands to match the two character suffixes you used for the TCPCFGxx and DNRCFGxx parameter files.

• When this has been done, modify the JCL startup procedure and point to your updated STARTxx member.

The most commonly used commands are the following:

SRC is an optional parameter. If no SRC is specified, there will not be an SRC (and all commands issued to the Cisco IOS for S/390 address space must be done via the MVS MODIFY command).

Use this command to direct the SNAP command to the API task group:

The SNAP command, entered simply as SNAP, is directed to the jobstep task group (IJT) since the task group identifier is omitted. The keyword ALL indicates to SNAP the IFS trace table.

These are the valid task group identifiers:

Some command objects, such as SNAP, support only the DISPLAY form and ignore the another specified verb.

• DISPLAY SNAP

• SNAP

You can enter command objects spelled exactly as they are shown or you can use an acceptable abbreviation. You can abbreviate any object by entering only the significant characters. That is, you must type as much of the object as is necessary to distinguish it from other objects.

These operands for the SNAP command specify either a JES SYSOUT class or, alternately, an MVS SNAP:

SNAP CLASS(A)            /* JES SYSOUT CLASS      */
SNAP MVS                 /* MVS SNAP              */

The types of operands used with commands are positional and keyword.

You must replace the TGI with the actual three-character task group identifier when you enter the command.

When you want to enter a positional operand that is a list of several names or values, the list must be enclosed within parentheses. The names or values must not include unmatched parentheses.

Some keywords let you specify values. Place the value inside parentheses following the keyword. The following is a typical keyword with a value:

You select the task group identifier desired and substitute that value for TGI when you enter the operand.

The SNAP command includes the keywords CLASS and MVS. Abbreviations for CLASS are C, CL, CLA, and CLAS; abbreviations for MVS are M and MV.

In addition, some commands allow unique abbreviations or aliases for some of their keywords.

The LNI and DEVICE commands activate and de-activate local network hardware interfaces.

The DELETE command removes specified items from the active configuration.

The UPDATE command is not a single action command, but instead reads a member containing a list of commands and/or configuration statements. The configuration statements are identical to those in the startup TCPCFGxx member, and the LNI, DEVICE, and DELETE commands can be included. The default member name is TCPCFGUP, but command syntax allows any name to be used.

The provision to include commands among configuration statements becomes significant where state conditions are enforced. For example, to replace an active LNI, it must first be stopped, then deleted, before the configuration statement is processed. Finally, since this is not in startup, the device must be started manually. The member to the UPDATE command can contain a list of these activities, and the entire sequence can be activated with one command.

The distinction between adding to a configuration, or replacing, is based on whether the item itself allows multiples. For example, multiple LNIs are permissible, so a replacement will require a prior deletion. Inversely, a statement like TCP is always a total replacement.

For example, you have a configuration with a MEDIA named CETIETH, and a CETI device with the address 884 and DEVICE name CETI0884. You want to replace the CETI controller with one with an address of E50. The MEDIA name came from the NAME keyword on the MEDIA statement, and the DEVICE name was internally generated. Both names can be displayed with a NETSTAT CNFG command.

The typical sequence of steps would be as follows:

1 . Extract the CETI statement from the TCPCFGxx startup member into a new member (conveniently named TCPCFGUP). This CETI statement will contain the following:

DEVADDR(E50),MEDIANAME(CETIETH)
.
.
.

2 . Since this is a replacement, the previous LNI must be stopped and deleted. Ahead of the CETI statement, add the following commands:

DEVICE STOP NAME(CETI0884)
DELETE LNI NAME(CETI0884)

3 . Since this is NOT started, LNI activation is not automatic, so following the CETI statement, add the following:

DEVICE START NAME(CETI0E50)

The DEVICE name is predictable in this case, as the last 4 characters consist of the hardware channel/device address.

4 . Execute the UPDATE command.

If this is an addition of a new LNI, rather than a replacement of an existing one, Step 2, above, is not required.

All statements in TCPCFGUP are assumed to be additions to the existing configuration.

In addition to the startup statements in the TCPCFGUP member, TCPCFGUP can also contain any of the other three dynamic configuration operator commands. When placed in the TCPCFGUP member, these commands will be executed as individual commands entered from the console. This allows combining a series of sequences, such as deletions and additions, into one member, then executing them all with one command.

The UPDATE command also allows for some items that are not in the startup file, in addition to the other three dynamic configuration commands.

The UPDATE command adds new configuration data to an operational gateway. The parameters for the UPDATE command specify a member name that contains configuration statements as they would appear in the startup member TCPCFGxx. The update member name can default to TCPCFGUP, and must be available in the same DD definitions as the TCPCFGxx member.

For more details, read the description of the TCPCFGxx member in the Cisco IOS for S/390 Customization Guide.

The alias for the ILATCH command is ILA.

There are three different versions of the ILATCH command:

Syntax Description

CONVXL8 creates a data set with three records. Each record is 256 bytes in length. The first record has "*TCP/IP translate tables" (in EBCDIC) starting in column one, with the remainder of the record padded with EBCDIC blanks (X'40'). The second record will have 256 EBCDIC values representing the ASCII-to-EBCDIC translation. The third record will have 256 ASCII values representing the EBCDIC-to-ASCII translation.

File names use TSO prefix as defined by TSO rules. A fully qualified data set name needs to be enclosed in quotes. A data set name without quotes may have a user specified prefix placed before the name. This prefix is defined by the user's TSO profile. Refer to TSO documentation for more information about prefixes.

These output files are used by OpenEdition (UNIX System Services) DNR services only. Cisco IOS for S/390 continues to use its own translation load modules within the product. You can convert several members and place them in a PDS but OpenEdition (UNIX System Services) will use only the one placed in the sequential data set 'PREFIX.STANDARD.TCPXLBIN'.

Command scripts are read from the SYSPROC DD data set(s) and a sample START00 script is provided in the PARM data set. A command script can be invoked at address space initialization by specifying the command script name with the CMND= parameter in the JCL procedure for an IFS address space. Command scripts can also be invoked using the IJT START command with the MEMBER(xxx) option.

SET GTF OFF                      /*  TURN GTF MODE OFF FOR ALL TASK GROUPS       */
SET GTF ON TG(TGI)               /*  TURN GTF MODE ON FOR TGI                    */
MOD GTF OFF ALL                  /*  TURN OFF ALL GTF EVENTS                     */
MOD GTF ON CB(SDWA PARM MODI)    /*  TURN ON DESIRED EVENTS                      */
%TGICMNDS                        /*  INVOKE COMMAND SCRIPT FOR TGI TASK GROUP    */

Special command statements valid only within a command script are provided to do these tasks:

• Control the display of command statements before being executed

• Control command statement processing if a command fails