Text Part Number: 78-5661-01 Rev. B0 1 Cisco IOS for S/390 Release 2.0 Release Notes October, 1998 These release notes provide information for system administrators and installation managers who are responsible for the installation and support of the Cisco IOS for S/390 product. This document includes information specifically related to Cisco IOS for S/390 release 2.0 only.
Enhanced Features Enhanced Features This section describes the new product features of Cisco IOS for S/390 release 2.0. Improved Performance and Efficiency • Increased throughput, reduction in CPU utilization, and inbound and outbound multiprocessing. TCP/IP processing is now multi-threaded instead of single-threaded.
Enhanced APIs Enhanced APIs • OS/390 OpenEdition (UNIX System Services) asynchronous I/O (required for DB2 V5 TCP/IP support) and SRB mode. • Multiple BIND support for server applications (parallel processing for FTP, Telnet, and vendor applications). • • Enhanced TLI interface—data spaces, cross memory, SRB mode, etc. SAS 6.0 support. Other Enhancements • Year 2000 support. • FTP server support for IP address as RACROUTE TERMID—allows security rules to deny FTP access unless permitted by IP address.
Product Changes Table 1 Parameter Aliases (continued) MAXQSEND MAXQSND MAXQRECV MAXQRCV TADDRUSE PORTUSE TADDRASSIGN PORTASGN KEEPALIVETYPE KEEPALIVE KATIMER KEEPALIVETIMER KACOUNT KEEPALIVECOUNT ROUNDTRIPDEV RTD ROUNDTRIPINIT RTO • PORTASSIGN The ACPCFG00, APICFG00, and XITCFG00 configuration members have been removed. The TCP/IP stack configuration has moved into a new configuration member, TCPCFG00. The applications, such as Server FTP, Server Telnet, etc.
Product Changes As for parameters in the Cisco IOS for S/390 Release 1.0 configuration member APICFG00, the TPCB was replaced with the SPCB. You will only need 3 (default) because there are only 3 API's. CBUFs were replaced with the set of MBUFs. Previously, there were two CBUFs per session, one for input and one for output. Now all data is buffered in MBUFs, so there is no relation between the size of the CBUF pool, and the sizes of the MBUF pools.
Product Changes • Most of the prefixed messages have a consistent message format of the form pppmmxxxs, where: — ppp is a letter followed by 2 numbers which identifies the component: T00mmxxxs Messages issued by IFS common routines T01mmxxxs Messages issued by Cisco IOS for S/390 routines T02mmxxxs Messages issued by IUCV routines T03mmxxxs Messages issued by Component Trace routines — mm is a pair of letters that identifies the subcomponent: pppAPxxxs Messages issued by API common application s
New Features — xxx is a number in the range of 000 - 999, uniquely identifying the message — s is a letter indicating the severity level of the message: pppmmxxxR Response message produced in response to a command pppmmxxxF Fatal message signifying that a catastrophic error has occurred pppmmxxxE Error message indicating that some kind of error has occurred and action should be taken to correct it pppmmxxxW Warning message indicating that an action did not happen entirely correctly, but TCP could ma
Cisco Connection Online Cisco Connection Online Cisco Connection Online (CCO) is Cisco Systems’ primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services. Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco’s customers and business partners.
The Product Documentation Library The Product Documentation Library The Cisco IOS for S/390 manual set has been reorganized along functional lines. The complete manual set includes these documents: • Cisco IOS for S/390 Planning Guide Describes the Cisco IOS for S/390 architecture, how to prepare for installation, customize system security, and how to use OpenEdition and user exits.
Documentation Changes to the Documentation Set The Cisco IOS for S/390 Planning and Operations Guide and Cisco IOS for S/390 Installation Guide of previous releases have been reorganized as described below: • Cisco IOS for S/390 Planning Guide This guide provides information to help you plan your installation of Cisco IOS for S/390. It will ship prior to shipment of the product.
Cisco IOS for S/390 Planning Guide Exit Work Area If requested, the exit facility provides a work area to the exit program upon each invocation, except the INIT exit point. Request the work area with the EWALENGTH parameter of the EXIT statement in member IJTCFGxx, or with a parameter returned by the program at the INIT exit point (the program parameter taking precedence).
Documentation Exit Recovery Routine The exit program can supply the address of a recovery routine via a parameter returned at the INIT exit point. The exit facility calls this routine in the event of an ABEND in the exit program. The recovery routine is called in the same mode as the ABENDing exit program, and is passed the System Diagnostic Work Area (SDWA) address and the EWA address (if any).
Cisco IOS for S/390 System Management Guide Customizing CA-ACF2 Version 6 or Later A correction is required for Chapter 3 of the Cisco IOS for S/290 Planning Guide. Under the heading Customizing CA-ACF2 Version 6 or Later (page 3-12), step 2 is Update GSO Records for Cisco IOS for S/390. The code listed in this step is incorrect. The correct code is: ACF SET CONTROL(GSO) INSERT CLASMAP.AC#CMD RESOURCE(AC#CMD) RSRCTYPE(SAF) ENTITYLN(8) CHANGE INFODIR TYPES(D-RSAF) INSERT SAFDEF.
Documentation The REFRESH command is described in the “Cisco IOS for S/390 Operation” chapter. Parameters for the SVCDUMP Command Two parameters have been added to the SVCDUMP command, ASID and JOBname. These parameters let the user request that other address spaces be dumped along with Cisco IOS for S/390. ASID(asid_list) A list of address space IDs. Cisco IOS for S/390 will include these address spaces in the dump.
Cisco IOS for S/390 Customization Guide NETSTAT RTM Command The NETSTAT diagnostic commands are described beginning on page 5-12. The NETSTAT RTM command can be used by a Telnet user to display a continuous activity report on all active hardware interfaces. The frequency is determined by the value in seconds, and defaults to 9 if not entered. Permissible values are between 1 and 32767. Once activated, the RTM command will continue to display a time-stamped connection counter, and LNI counts and rates.
Documentation TCP MINDEV and RTO Defaults Changed Two of the defaults in the TCPCFG00 file have changed. For the TCP statement, the MINDEV parameter defaults to 40 (0.10 second). Also on the TCP statement, the RTO parameter defaults to 0; range 0 - 6000. APPEND Keyword for LUPOOL Statement In configuration member APPLUP00, a new keyword, APPEND has been added to the LUPOOL statement. LUPOOL NAME(pool_name) APPEND(lu_name,...,lu_name) Syntax Description APPEND Specifies additional LU names for an LUPOOL.
Cisco IOS for S/390 Customization Guide Note that Cisco IOS for S/390 does not configure TOS for SNMP or DNR queries, and NNTP is not implemented. Telnet and the FTP control connection can be configured in the Service statement. The FTP data connection can be configured in the FTP statement. The SMTP connection can be configured on the Service statement.
Documentation LOGGING SPIN NOW Spins the log now; leaves all specifications unchanged. LOGGING SPIN(LINES(5000) MINUTES(60)) Resets spin to every 5000 lines or 60 minutes, whichever comes first; leaves remaining keywords unchanged. LOGGING PRINT(ALL) WTO(ALL) WRITER(TOLSTOY) SPIN(SYNC) NOW Prints and WTOs all message, resets SYSOUT writer to TOLSTOY and defaults CLASS, DEST, and FORM. Also resets spin to every hour on the hour, ignoring line count, and spins the log now.
Cisco IOS for S/390 Unprefixed Messages and Codes T01CF084W Refresh of USSTAB failed, tbl_name not used in APP task task_num Explanation There was a negative response to REFRESH USSTAB(tbl_name) TASK(task_num) operator command. tbl_name for APP task task_num was not specified in the active APPCFGxx SERVICE segment. Recommended Action Check the spelling of tbl_name and APP task task_num that may have been entered correctly.
Documentation Table 6 X’C245’ Instance Codes (continued) 4-byte code 2-byte code Description C2450002 0702 Recursive error C2450003 0703 Error copying TPL to secondary C2450004 0704 Error copying exit codes to TPL C2450005 0705 VTPL abend C2450020 0720 SAW not obtained C2450021 0721 ASCB validation failed C2450022 0722 TCB address is negative C2450023 0723 31-bit TCB address passed C2450024 0724 Close-pass:Close-pass pending C2450025 0725 Close-pass:Accept pending C245002
Cisco IOS for S/390 Unprefixed Messages and Codes Table 7 X’C24C’ Instance Codes (continued) 4-byte code 2-byte code Description C24C0020 0E20 SAW not obtained C24C0021 0E21 TLI state invalid C24C0022 0E22 No option buffer provided C24C0023 0E23 Option buffer length not positive C24C0024 0E24 Option length not positive C24C0025 0E25 OPTCD=API and option number negative C24C0026 0E26 OPTCD=API and option number out of range C24C0027 0E27 OPTCD=TP and option number not positive C
Documentation 4-byte code 2-byte code Description C25B0002 1D02 Recursive error C25B0003 1D03 Error copying TPL to secondary C25B0004 1D04 Error copying exit codes to TPL C25B0005 1D05 VTPL abend C25B0006 1D06 Abend obtaining TEM storage C25B0007 1D07 Abend building TEM C25B0020 1D20 SAW not obtained C25B0021 1D21 TPL is active C25B0022 1D22 STORAGE OBTAIN for TEM failed C25B0023 1D23 Summary format not supported C25Fxxxx (21xx) T01PSTUB This table replaces Table 84 “X'C25F
Installing Cisco IOS for S/390 Release 2.0 Table 10 X'C262'Instance Codes 4-byte Code 2-byte Code Description C262000B 6F0B SEPM storage verification failed C909xxx T01SISND The following 4-byte code has been added to Table 116, “X’C909’ Instance Codes,” in the “API Diagnostic Codes” chapter: Table 11 C909000C X’C909’ Instance Codes Unable to find a route because SO_DONTROUTE was set. Installing Cisco IOS for S/390 Release 2.
Installing Cisco IOS for S/390 Release 2.0 Media media_name is now operational with one or more active interfaces. Callable System Services Library You must have the Callable System Services library, SYS1.CSSLIB, available for the installation. Modules from this library are linked with Cisco IOS for S/390 release 2.0 for OpenEdition support. This library is distributed with MVS/ESA. If you do not have this library available, OpenEdition support will not function properly.
Installation Requirements • DB2/CONNECT V5 requires Fix Pack WR09014. Do not apply Fix Pack WR09024. Common Inet Sockets in OpenEdition You must install the APAR OW20620 in order to use Common Inet sockets in OpenEdition. RS6000 You must install the RS/6000 patch U432867 to use the CLAW driver. With earlier RS/6000 maintenance, MVS error recovery problems can occur. VTAM Release 3.3 VTAM Release 3.3 users must apply PTF UY67100 or UY69746, or their equivalent.
Installing Cisco IOS for S/390 Release 2.0 IP Hardware, Cisco IOS Software, and CIP Microcode Compatibility The following table lists the compatibility requirements for Cisco IOS for S/390. However, we recommend that you refer to the CCO service and your Systems Engineer to choose the most appropriate level for your configuration. Table 13 Hardware/Software/Microcode Compatibility CIP Hardware Version Minimum Cisco IOS Release Required Minimum CIP Microcode Version Recommended CIP 4.4 or later 11.
Installation Process Note Some members of the CNTL library are now under SMP/E control and some members will be loaded as part of the APPLY process. When modifying the ALLOCT00 JCL stream, verify that the TCPJCL DDDEF points to your CNTL library. Also, you should exit the CNTL library as soon as the INSTSMPE job stream is submitted. Keeping the data set open in your TSO session will cause the APPLY job to fail. Allocate the Data Set Names for Cisco IOS for S/390 release 2.
Installing Cisco IOS for S/390 Release 2.0 — Verify that the Linkage Editor/Binder attributes for the CSI include NCAL, LET, and SIZE=(660000,160000). If you are using the linkage editor you must remove the NCAL, LET, and SIZE parameters from the ALLOCSMP JCL. You must also change your maximum return code to a 4. — For users running MVS/ESA 4.3 or above, Binder is now supported. To use the Linkage Editor, update the options entry for IEWL to point to HEWLF064. In Cisco IOS for S/390 release 2.
Installation Process Note Exit the CNTL library as soon as the INSTSMPE job stream is submitted. Keeping the data set open in your TSO session will cause the APPLY job to fail. 6 HOLDDATA Before installing system maintenance, obtain the most recent HOLDDATA file. You can obtain this file through anonymous FTP by logging in to ftp.interlink.com and requesting it as shown in the following example. For user ID, use anonymous; for password, user your email address. ftp2 open ftp.interlink.
Installing Cisco IOS for S/390 Release 2.0 — If you are using JES3, add the following statement: //*MAIN LINES=(999,W) — Verify that the tape unit is correct. It is hardcoded as CART. Submit SMPECUMT. SMPECUMT will generate the following message: GIM34701E: SMPE expected to find ++MCS This is expected and normal. View the SDSF job output log to verify accuracy of the job. Execute the ISPF Browse or SDSF View command F ‘APPLY PROCESSING WAS SUCCESS’ ALL.
Installation Process PARM Customization The statements described in this section are all described in the Cisco IOS for S/390 Customization Guide. That document is the definitive source of information for these members. These members are all shipped with the product. Note PARM members are now under SMP/E control. In order to avoid possible overwrite by future PTFs, copy your 00 members to 01 or another suffix of your choice.
Installing Cisco IOS for S/390 Release 2.0 TCPCFG01: There is a new NETMASK parameter that lets the Network Information Center (NIC) divide the Class B addresses into Class C addresses to alleviate some of the worldwide IP address shortages. If your installation is affected you will have already applied to the NIC for these addresses. USERMOD Customization The statements described in this section are all described in the Cisco IOS for S/390 Customization Guide. These members all ship with the product.
Diagnosis and Problem Reporting — If you are using JES2 add: /*JOBPARM LINES=9999 — If you are using JES3, add: //*MAIN LINES=(999,W) • To prepare RUNTCP as a batch job: — Complete your RUNTCP JOBCARD and add the following JCL statements to the end of the RUNTCP JCL stream: // PEND //label EXEC TCPIP To prepare RUNTCP as a started task: — Delete the RUNTCP JOBCARD and comments that appear prior to the PROC statement. — Copy member RUNTCP into a system PROCLIB. Submit RUNTCP.
SAS/C Usage Notes F RUNTCP,TCP SNAP ALL Obtaining a TCPEEP Read the Cisco IOS for S/390 System Management for information to help you set up and submit your trace address space and submit the TCPEEP TSO command. Obtaining an SVC Dump Read the IBM document MVS/ESA System Commands Reference Summary for the syntax of the required DUMP commands. In particular, include all jobs involved in the problem using the JOBNAME parameter of the DUMP command.
ACPCFG00 HOST Statement For complete information on the Cisco IOS for S/390 product, please refer to your documentation set.
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.
Application Statement Mappings Application Statement Mappings The application statements in the former ACPCFG00 file can be mapped to the same statements in the APPCFG00 member, although the SMF statement has been moved to IJTCFG00. These release 1.0 statements have been removed: • VTAM New parameters for release 2.
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0 There are new parameters for the TCP statement in release 2.0: • • • • • • IPNOTIFY KEEPALIVECOUNT RTD RTO TIMEWAIT TIMEWAIT The following diagram shows the parameters.
UDP Protocol Parameters UDP Protocol Parameters The ACPCFG00 TIB and UDP mappings have been moved to TPPCFG00. Parameters removed from release 1.0: • • PROTOCOL(UDP) UDP IDLE, RABLIM, WRELIM Parameters renamed for release 1.0: • • TADDRASSIGN -> PORTASSIGN TADDRUSE -> PORTUSE New parameters for release 2.0.
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0 New parameters for release 2.0.
ROUTE Parameters Figure 6 NETWORK Parameters ACPCFG00 NETWORK NAME(name) ARPIPTIMEOUT(num) ARPTIMEOUT(num) ARPTABLE(name) TCPCFG00 MEDIA NAME(name) ARPTIMEOUT(router host) ETHERNET|VIRTUAL|TOKEN4| TOKEN16|FDDI|HYPERCHANNEL| CLAW|CLDC MSSDEF(num) MSSOPT(NEVER|SUBNET| NET|ALWAYS) MSSDEF(num) MSSOPT(NEVER|SUBNET| NET|ALWAYS) MTU(num) IDLENET(seconds count) CHECKSUM(HOST|YES| OFFLOAD|NO) MTU(num) IDLENET(seconds count) HOSTCKSUM|OFFLOADCKSUM HOST(internet_addr) DEST(internet_addr) SUBNET(mask) LNID(na
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.
Driver Configuration Figure 8 CETI Driver Parameters ACPCFG00 TCPCFG00 CETI CUTYPE(cutype) DEVADDR(ccuu) IBUF(number) IPARM(buf_thresh gat_time) OBUF(number) OPARM(buf_thresh gat_time) RETRY(sec) WTIME(number) LOGOUT(num [SYNC|NOSYNC]) OPTIONS((ASYNC|SYNC) {DSM|ESM} {GETMAIN|PCORE} {LOOP|NOLOOP} {DOCP|EOCP}) SIDB(sense_id) SIDM(sense_mask) TRACE|NOTRACE NAME(lniname) ERROR(ABEND) LNICETI CUTYPE(3752|3762)) DEVADDR(ccuu) IBUF(number) IPARM(buf_thresh gat_time) OBUF(number) OPARM(buf_thresh gat_time) R
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0 Figure 9 CLAW Driver Parameters ACPCFG00 TCPCFG00 LNICLAW CLAW DEVADDR(ccuu) CHARSET(name) HOSTNAME(name) WSNAME(name) IBUF(number) OBUF(number) RETRY(sec) SINGLENOOP|DOUBLENOOP BUFSIZE(1024|2043|3072|4096) TRACE|NOTRACE ERROR(ABEND) NAME(lniname) DEVADDR(ccuu) CHARSET(name) HOSTNAME(name) WSNAME(name) IBUF(number) OBUF(number) RESTART(sec) SINGLENOOP|DOUBLENOOP BUFSIZE(1024|...
Driver Configuration Figure 10 CDLC Driver Parameters ACPCFG00 TCPCFG00 LNICDLC CDLC DEVADDR(ccuu) IBUF(number) OBUF(number) RETRY(sec) TRACE|NOTRACE ERROR(ABEND) NAME(lniname) DEVADDR(ccuu) IBUF(number) OBUF(number) RESTART(sec) MEDIANAME(media_stmt_name) AUTOSTART|NOAUTOSTART LNIHYPR ACPCFG00 LNIHYPR parameters have been moved to the TCPCFG00 HYPER statement. Parameters removed from release 1.
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.
IJTCFG00 Changes Figure 12 LCS and LINK Parameters ACPCFG00 TCPCFG00 LNILCS LCS DEVADDR(ccuu) BUFSIZE(number) CUTYPE(type) IBUF(number) OBUF(number) RESTART(sec) NAME(LCS_stmt_name) LINK LOCALADDR|NOLOCALADDR LNILINK DEVADDR(ccuu) BUFSIZE(number) CUTYPE(type) IBUFFS(number) OBUFFS(number) RETRY(sec) NAME(LCS_stmt_name) NOTLADDR|LOCLADDR ERROR(ABEND) DEVNAME(devname) ADAPTER(number) ALLRT|SINGLERT NAME(lniname) TRACE|NOTRACE LINK DEVNAME(devname) ADAPTER(number) ALLRT|SINGLERT PFILTER|NOPFILTER ME
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0 Figure 13 IFSPARM and AUTH Statements IJTCFG00 (4.1) IFSPARM IFSPARM PROMPT|NOPROMPT VMCFNAME(name) GTFID(value) MAXSTGPCT(below, above) DATASPACESIZE TIMER(ticks) TIMEZONE(ATLANTIC| EASTERN|CENTRAL| MOUNTAIN|PACIFIC| char hours) TRACENAME(name) VSREPORT(interval) | NOVSREPORT PROMPT|NOPROMPT VMCFNAME(name) GTFID(value) MAXSTGPCT(below, above) ROUTECDE(list) AUTH IJTCFG00 (5.
LOGGING Statement Cisco IOS for S/390 Release 2.
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0 This document is to be used in conjunction with the Cisco IOS for S/390 publications.
