Cisco IOS for S/390 Release 2.0 Release Note
Available Languages
Table Of Contents
Cisco IOS for S/390 Release 2.0 Release Notes
Improved Performance and Efficiency
The Product Documentation Library
Changes to the Documentation Set
Cisco IOS for S/390 User's Guide
Cisco IOS for S/390 Planning Guide
Enhancements to the Global Exit Facility
Customizing CA-ACF2 Version 6 or Later
Cisco IOS for S/390 System Management Guide
Parameters for the SVCDUMP Command
Protocol Layer Events (Subtypes 110 - 123) Descriptions
Capture of User Data in a TLI Trace
Cisco IOS for S/390 Customization Guide
TCP MINDEV and RTO Defaults Changed
APPEND Keyword for LUPOOL Statement
Recommendations on Setting TOS
LOGGING Keywords Logically Grouped
Cisco IOS for S/390 Prefixed Messages
Cisco IOS for S/390 Unprefixed Messages and Codes
Installing Cisco IOS for S/390 Release 2.0
Callable System Services Library
Common Inet Sockets in OpenEdition
MVS/ESA Release 5.1 Considerations
Walker, Richer, & Quinn Software
Allocate the Data Set Names for Cisco IOS for S/390 release 2.0
Invoking Cisco IOS for S/390 Release 2.0
Diagnosis and Problem Reporting
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0
Application Statement Mappings
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.
This document contains these sections:
•
"Enhanced Features," page 2, provides a list of feature enhancements in Cisco IOS for S/390 release 2.0.
•
•
•
•
•
•
•
•
Enhanced Features
This section describes the new product features of Cisco IOS for S/390 release 2.0.
Improved Performance and Efficiency
•
•
•
Improved Management
With Cisco IOS for S/390 release 2.0 you can dynamically:
•
•
•
•
•
•
Enhanced Functionality
•
•
•
•
•
•
•
Enhanced APIs
•
•
•
•
Other Enhancements
•
•
•
Product Changes
•
•
•
ACC210I Internet Protocol Task Startedno longer displays to indicate that startup has completed. A message will display indicating startup completion in Cisco IOS for S/390 release 2.0. The message number will vary, depending on the device you are using; the message text will beMediamedia_nameis now operational with one or more active interfaces.Initialization and termination messages now appear in mixed case. This may impact some automated operations packages that search for messages to invoke some action. You should review these messages and take appropriate action.
•
•
Table 2 ACPCFG Member 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. Pool sizes are based on the amount of data buffered, not on the number of endpoints.
In Cisco IOS for S/390 Release 2.0, usage of the API is no longer limited, so there was no need for the (1.0) API statement.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Returning the value of zero is correct since the default for Cisco IOS for S/390 release 2.0 is do not allow broadcast. Therefore, the SO_BROADCAST flag is not set. To set this flag to ON, you must run TOPTION with OPTCD=DECLARE and the TPOIPBRO option set to a value of 1 to override the default. After the flag is set, TOPTION OPTCD=QUERY will return a value of 1.
New Features
•
•
•
•
•
•
•
•
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. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
•
•
•
•
•
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note
Documentation
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
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:
•
Describes the Cisco IOS for S/390 architecture, how to prepare for installation, customize system security, and how to use OpenEdition and user exits. It also includes information about editing tools, information to help configure Cisco IOS for S/390 for Cisco routers and plan storage usage, and about the CDLC driver. This manual is targeted for Computer Operations personnel.
This document ships prior to shipment of the product.
•
Complete guide to customizing Cisco IOS for S/390 for your site. A bound copy of this document is included with the product shipment.
•
Describes the operator commands (startup and shutdown of Cisco IOS for S/390), how to use the System Management Facility (SMF), diagnostic procedures, diagnostic commands, and Inter-User Communications Vehicle (IUCV) sockets.
A bound copy of this document is included with the product shipment.
•
Guide to the Cisco IOS for S/390 Client FTP2, Client FTP3, Client FTP, Server FTP, Telnet, and Mail commands, USPOOL, remote executor, API and socket applications, and programmable batch interface for Client FTP2 and Client FTP3.
•
Describes all messages that have an alphanumeric prefix and are printed to the console or the Cisco IOS for S/390 log files.
•
Describes messages from FTP, Telnet, Mail, and general API return codes.
•
Describes the concepts, flow, and operation of the Cisco IOS for S/390 API.
•
Guide to the Assembler API macros.
•
Describes calls for the basic C library and for the Socket API. This manual contains a chapter describing the OpenEdition (UNIX System Services) socket interface.
•
Describes the RPC and XDR API calls.
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:
•
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.
•
This guide provides information about Cisco IOS for S/390 operation and system commands. It will ship with the product.
•
The release notes now contain installation information. They will ship with the product.
Cisco IOS for S/390 User's Guide
A correction is required for Chapter 9, "Remote Executor," of the Cisco IOS for S/390 User's Guide. On page 9-2, in the section "What is the Remote Executor?" the following statement is incorrect:
This product uses version 5.5 of SAS C.
You must use SAS/C Release 6.00.
Cisco IOS for S/390 Planning Guide
The information in this section should be added to the Cisco IOS for S/390 Planning Guide.
SERVICE Startup Statement
Keywords IBUF(aaa bbb) and OBUF(aaa bbb) have been added to the SERVICE startup statement to allow default override:
The minimum value for IBUF and OBUF is 512; it is the product of multiplying the buffer size times the number of buffers. The buffer size cannot be less than 256, and the number of buffers cannot be 0, so the lower limit would be (2 256) or (1 512).
Enhancements to the Global Exit Facility
The following enhancements have been made to the Global Exit Facility.
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).
The Exit Work Area (EWA) addressed will be passed to the exit program at each exit point as the fifth parameter, following the address of the message-writing routine.
Note
The EWA size can be from 1 to 65532 bytes. It is taken from pooled storage; the smallest pool that will satisfy the requested size will be used. Pool usage can be monitored via the IFS POOL command. One of the following pools will be used:
Table 3 EWA Pools
256B
1-252
512B
253-508
01KB
509-1020
04KB
1021-4092
08KB
4093-8188
16KB
8189-65532
Note
Add the following parameters to the INIT exit parameter list, following the subsystem ID address:
Table 4 INIT Exit Parameters
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). Since the exit's recovery routine is called after the system's Recovery and Termination Manager (RTM) has finished processing the ABEND, it should perform only local clean-up functions. Any updates to the SDWA are ignored. The recovery routine should not attempt to free the SDWA, since this will be done by the exit facility.
Recovery Exit
Exit Point: When an ABEND has occurred in an exit program.
Function: Perform clean-up associated with the exit program.
Dispatchable Unit: Identical with the ABENDing exit program.
Register contents are shown in the following table.
Table 5 Recovery Exit Register Contents
On return from the recovery exit, R13 must be restored.
Exit Parameter List Mapping Macro - T00DEXPL
A new macro, T00DEXPL, is supplied to map the parameter lists to the exit program at the various exit points. The macro is distributed in the SAMP library.
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:
ACFSET CONTROL(GSO)INSERT CLASMAP.AC#CMD RESOURCE(AC#CMD) RSRCTYPE(SAF) ENTITYLN(8)CHANGE INFODIR TYPES(D-RSAF)INSERT SAFDEF.ACSECPC1 ID(ACSECPC) MODE(GLOBAL) REPPROGRAM(BYPASS#1) RACROUTE(SUBSYS=SNSTCP,REQSTOR=ACSECPC)INSERT SAFDEF.ACSECPC2 ID(ACSECPC) MODE(GLOBAL) REPPROGRAM(BYPASS#2) RACROUTE(SUBSYS=SNSTCP,REQSTOR=ACSECPC)INSERT SAFDEF.ACSECPC3 ID(ACSECPC) MODE(GLOBAL) REPPROGRAM(BYPASS#3) RACROUTE(SUBSYS=SNSTCP,REQSTOR=ACSECPC)INSERT SAFDEF.ACSECPC4 ID(ACSECPC) MODE(GLOBAL) REPPROGRAM(BYPASS#4) RACROUTE(SUBSYS=SNSTCP,REQSTOR=ACSECPC)INSERT SAFDEF.ACCFTP2 ID(ACCFTP2) MODE(GLOBAL) REPPROGRAM(ACCFPT2) RACROUTE(REQUEST=EXTRACT)INSERT SAFDEF.FTP ID(FTP) MODE(GLOBAL)PROGRAM(FPT) RACROUTE(REQUEST=EXTRACT)INSERT SAFDEF.FTP2 ID(FTP2) MODE(GLOBAL)PROGRAM(FPT2) RACROUTE(REQUEST=EXTRACT)INSERT SAFDEF.FTP3 ID(FTP3) MODE(GLOBAL)PROGRAM(FPT3) RACROUTE(REQUEST=EXTRACT)Cisco IOS for S/390 System Management Guide
The information in this section should be added to the Cisco IOS for S/390 System Management Guide.
Refreshing USSTAB
USSTAB tables can be refreshed with the REFRESH command.
In the "APP Commands" section, which describes the REFRESH command, the second sentence of the description of the REFRESH command, the USS Table should be added. That sentence should be corrected to read as follows:
"It can be used to refresh the LU pool, greeting member, or the USS Table used by Server Telnet."
The correct syntax is:
[ APP ] REFRESH TASK ( n ) [ LUPARM ( mem_name ) | GREETING ( mem_name ) |
USSTAB ( tbl_name ) ]
Syntax Description
USSTAB (tbl_name)
Specifies the USS Table tbl_name coded in the active APPCFGxx SERVICE segment to be refreshed.
Note
The following is an example of the usage of the REFRESH USSTAB command.
REFRESH USSTAB( T01USS01 ) TASK( 1 )
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.
The SVCDUMP command is described in the "Cisco IOS for S/390 Operation" chapter.
Protocol Layer Events (Subtypes 110 - 123) Descriptions
The SMF subtype 110-123 records, described on page 3-17, are written to record certain protocol-related events, such as a bind or connect request.
The following table describes the relationship of each of these subtypes:
MU1IUCV USERMOD Correction
The zap example for EZASOK03 configuration overrides and defaults on page 4-14 and the USERMOD on page 4-15 are incorrect. Use USERMOD MU1IUCV in the SAMP data set instead.
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. The display itself will appear after the specified interval in seconds, but the rate is based on a time difference between now and the last sampling. If multiple RTM commands are in effect, the rates will not always be consistently smooth.
To terminate the RTM command, press Enter.
Capture of User Data in a TLI Trace
You can use the trace facility or TCPEEP to capture user data in a TLI trace. The data is from the TPL field DABUF.
To capture and view user data, two actions are required.
•
For example, the following command will capture up to 100 bytes of data:
GROUPS( ( TLI,'MTDATA( 100 ) ' ) )
•
•
•
•
For example, the following command will display up to 50 bytes of captured data:
FORMAT( TLIEBCDIC( 50 ) )
The TCPEEP command is described in the "Diagnostic Commands" chapter.
Cisco IOS for S/390 Customization Guide
The information in this section should be added to the Cisco IOS for S/390 Customization Guide.
TCPEEP NETIF Option
The default maximum data captured by the TCPEEP option NETIF is now 256 bytes of data, which includes device header, IP header, etc. A new filter option, MAXDATA (alias MDATA), allows resetting this to a maximum of 65,535.
This is an example of the usage of the MAXDATA (MDATA) filter option:
GROUPS( (NETIF,'MDATA( 512 ) ' ) )
This command will capture up to 512 bytes of data. The FORMAT options DATA(nn), EBCDIC(nn), and ASCII(nn) still limit what is seen.
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
Example:
LUPOOL NAME(VLTPOOL0) LU(T20000,T20001,T20002,T20003,T20004,T20005,T20006,T20007,T20008)LUPOOL NAME(VLTPOOL0) APPEND LU(T20010,>T20011,T20012,T20013,T20014,T20015,T20016,T20017,T20018)CDLC Considerations
The 3746-900 unit is configured with a network MTU size, but will override it with the lowest MTU size it encounters. That MTU size will be applied to whatever mainframe software will be running next. Therefore, if a small MTU size is used, that will become the restriction for subsequent IP packet sizes and may cause problems if fragmentation is not allowed. The CDLC MTU size should correspond to its network configuration parameter.
Recommendations on Setting TOS
The following recommendations for setting TOS (type of service) have been added to the Cisco IOS for S/390 Customization Guide.
When setting TOS, precedence bits should be set to zero.Of the next 4 bits, only one is to be set on in any one packet: 16 = mindelay, 8 = max thruput, 4 = reliability, 2 = min cost. These should be set as follows:
•
•
•
•
•
•
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.
LOGGING Keywords Logically Grouped
The LOGGING command has been changed slightly to introduce a logical grouping of the keywords that control SYSOUT attributes and when the log is spun. The changes in this section apply to the Cisco IOS for S/390 System Management Guide.
This change makes the command easier to use in that you do not need to specify all of the keywords for an action, as is shown in the following table.
The SYSOUT attributes that are grouped are:
•
•
•
•
The SPIN attributes that are grouped are:
•
•
•
Note
LOGGING Examples
Here are some examples of the usage of these grouped keywords.
LOGGING PRINT(ALL)
Prints all messages; leaves WTO, SYSOUT, and spin unchanged.
LOGGING WTO(ALL)
WTOs all messages; leaves PRINT, SYSOUT, and spin unchanged.
LOGGING CLASS(X)
Resets SYSOUT class to X; defaults DEST, FORM, and WRITER, and leaves remaining keywords unchanged.
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 Prefixed Messages
The following error messages should be added to the Cisco IOS for S/390 Prefixed Messages manual to support the REFRESH USSTAB:
These messages are described in the chapter "T01CFnnn Configuration Messages."
T01CF080R
USSTAB tbl_name successfully refreshed for APP task task_numExplanation The REFRESH USSTAB(tbl_name) TASK(task_num) operator command executed successfully.
T01CF081W
Refresh of USSTAB failed, APP task task_num inactive.Explanation There was a negative response to a REFRESH USSTAB(tbl_name) TASK(task_num) operator command. The APP task task_num was not fully initialized or is in the process of stopping.
Recommended Action Wait for the APP task to complete initialization or restart the APP task task_num if it was stopped.
T01CF082W
Refresh of USSTAB failed, tbl_name not found.Explanation There was a negative response to a REFRESH USSTAB(tbl_name) TASK(tasknum) operator command. tbl_name was not found in the JOBLIB/STEPLIB or link-listed library.
Recommended Action You will need to research what happened to the USS Table.
T01CF083W
Refresh of USSTAB failed, invalid format in tbl_nameExplanation There was a negative response to REFRESH USSTAB(tbl_name) TASK(task_num) operator command. tbl_name has an invalid format (it should start with X'BD').
Recommended Action You will need to research what happened to the USS Table.
T01CF084W
Refresh of USSTAB failed, tbl_name not used in APP task task_numExplanation 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.
T01NT069I
HH:MM:SS - nnn active TCP connectionsT01NT070I
LNI aaaaaaaa : bbb / ccc bytes/packdts in, at ddd bytes/secSyntax Description
aaaaaaaa
Hardware interface name
bbbb
Total byte count.
ccc
Total packet count.
ddd
Rate based on the time difference from the last sampling.
T01NT071I
LNI aaaaaaaa: bbb/ccc/ bytes/packets out, at ddd bytes/secSyntax Description
aaaaaaaa
Hardware interface name
bbbb
Total byte count.
cccc
Total packet count.
ddd
Rate based on the time difference from the last sampling.
Cisco IOS for S/390 Unprefixed Messages and Codes
The information in this section should be added to the Cisco IOS for S/390 Unprefixed Messages and Codes manual.
C245xxxx (07xx) T012TCLS
The following table replaces Table 60 "X'C245' Instance Codes" in the "API Diagnostic Codes" chapter:
C24Cxxxx (0Exx) T012TOPT
This table replaces Table 67 "X'C24C' Instance Codes" in the "API Diagnostic Codes" chapter:
C25Bxxxx (1Dxx) T012TERR
The following table replaces Table 82 "X'C25B' Instance Codes" in the "API Diagnostic Codes" chapter:
Table 8 X'C25B' Instance Codes
C25Fxxxx (21xx) T01PSTUB
This table replaces Table 84 "X'C25F' Instance Codes" in the "API Diagnostic Codes" chapter:
Table 9 X'C25F' Instance Codes
C262xxxx (6Fxx) T012TPLK
There is a duplicate entry in Table 85, "X'C262' Instance Codes," in the "API Diagnostic Codes" chapter. The second C262000A 4-byte code entry:
...should be C262000B and the 2-byte code should be 6F0B, as follows:
Table 10 X'C262'Instance Codes
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 X'C909' Instance Codes
Installing Cisco IOS for S/390 Release 2.0
This section contains information about installing Cisco IOS for S/390 release 2.0.
Installation Requirements
Cisco IOS for S/390 Version release 2.0 is composed of the base Cisco IOS for S/390 release 2.0 distribution tape and a tape containing additional PTFs. You must install both tapes.
MVS Releases
Cisco IOS for S/390 release 2.0 requires MVS/ESA Release 5.1 or higher. MVS/SP releases are not supported. OpenEdition support is available only at MVS/ESA Releases 5.x and above.
The MVS PTF associated with APAR OW30322 must be applied prior to starting Cisco IOS for S/390 release release 2.0.
APF Authorizations
The PFSLOAD library is used with OpenEdition and contains Physical File System (PFS) modules. It must be APF-authorized to work correctly.
If you use the SASLINK data set as described in the ALLOCT00 section of these instructions you must also APF-authorize that library.
Link List Data Sets
TCPLOAD must never be in the link list. If SASLINK is used, you must place it after the LINK library in any concatenation to ensure that the Cisco IOS for S/390 version of LSCNCOM is used.
Automated Operations Impact
The message
ACC210I Internet Protocol Task Startedno longer displays to indicate that startup has completed. A message will display indicating startup completion in Cisco IOS for S/390 release 2.0. The message number will vary, depending on the device you are using. The message text will beMedia 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.
TSO/E
New users must verify that the IBM program product TSO/E is installed. Cisco IOS for S/390 configuration files are parsed using TSO/E parsing routines and S0C4 ABENDs can result if these routines are not available.
ACF/2
For some users of CA-ACF2, the CA-ACF2 fixes listed here affect the way the Cisco IOS for S/390 SAF security interface to CA-ACF2 works. These fixes should be reviewed by the CA-ACF2 Systems Programmer to determine if they are still applicable or have been superseded by later maintenance.
Table 12 CA-ACF2 Fixes
TW87092
G016544
TW95626
G025907
TW95673
G023824
CO96846
G026166
CO97436
G026702
G031029
TA1294B
SAS/C Release Level
Cisco IOS for S/390 release 2.0 is designed to work with SAS/C Release 6.00, which is included with the product. If you are not running with the correct SAS/C libraries, unpredictable results may occur.
The zap associated with Usage Note 1670 for SAS/C 6.0 must be applied in order to run applications via IUCV over the SAS LSCNCOM interface, including SAS/connect.
Asynchronous Sockets
Cisco IOS for S/390 release 2.0 supports asynchronous socket calls from OpenEdition. The following system levels are required to run this option:
•
•
•
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. If this is not possible, contact Cisco TAC and request APAR MB18602. If the PTFs or APAR are not applied, problems can occur handling control vector X'5F' and cause connection errors.
MVS/ESA Release 5.1 Considerations
Interlink 3722 users must install the latest release of the CETI microcode. Interlink 3762 users must install the latest release of the ECA CETI microcode. The CETI driver may terminate at startup if you are using earlier releases.
Novell LAN Workplace
We recommend that you apply Novell fixes LWP41N and LWP168 (to correct an FTP hang condition). These fixes are available on NetWire.
Walker, Richer, & Quinn Software
If you are using software from Walker, Richer, & Quinn, we recommend that you install version 2.1.2 or above of Reflection 8+ (for DOS using IBM 3270) and Version 2.2 of WRQNET TCP/IP. Users of earlier releases can experience a tn3270 hang condition.
Hardware Requirements
These minimum hardware levels are required for Cisco IOS for S/390 release 2.0, including Cisco IOS for S/390 Fault Tolerant:
Interlink 3762 ECA CETI 3.0 Checksum B030
Interlink 3762 TCA 4.0 Checksum 5841
Interlink 3762 FCA 2.5 Checksum 6273
Interlink 3722 ELC2 CETI 2.2 Checksum 67FE
Interlink 3722 ELC2 8232 3.1 Checksum 4132
IBM 2216 MAS V1 R1.1
IBM 3172 Model 3 ICP 3.3
IBM 3172 Model 1 ICP 1.1 and higher (ICP 1.1 with patch PLXXX48)
NSC HYPERchannel DX CDA 7.2
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
Note
Installation Process
Use these instructions to install Cisco IOS for S/390 release 2.0 and to upgrade from a previous release of Cisco IOS for S/390.
Note
Control File JCL
Copy and execute the JCL below to unload the control file from which you will be able to install and customize Cisco IOS for S/390 release 2.0. The control file is on your Cisco IOS for S/390 release 2.0 base tape.
//UNLDTCP JOB (Cisco IOS for S/390),'UNLOAD TCP CNTL',MSGCLASS=X//*//UNLOAD EXEC PGM=IEBCOPY//INDD DD DSN=CNTL,DISP=SHR,VOL=SER=TCP001,// LABEL=(27,SL,EXPDT=98000),UNIT=tapunit//OUTDD DD DSN=trgindx.CNTL,DISP=(NEW,CATLG,DELETE),// VOL=SER=trgvol,SPACE=(TRK,(30,2,25)),UNIT=trgunit,// DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=6160)//SYSPRINT DD SYSOUT=holdcl//SYSIN DD *COPY INDD=((INDD,R)),OUTDD=OUTDD
Note
Allocate the Data Set Names for Cisco IOS for S/390 release 2.0
References to member names in the following instructions are located in the control file that you loaded onto your system in Control File JCL.
1
Member TCPNAMES in the CNTL library is used to customize all other installation members.
The TCPNAMES member, a REXX EXEC, lets you assign consistent data set name allocations. You can customize member TCPNAMES so that you do not need to edit the other installation members manually.
Step 1
Verify adequate space on the volume specified.
The LNKINDX data set is allocated as a SYS1 data set in job ALLOCT00. You can change to a different high level node if you do not have authority to allocate SYS1.
Step 2
Determine the name of your logon procedure. It is identified on the first screen of your TSO logon.
Determine the data set in which your logon procedure is located. It is most likely in SYS1.PROCLIB. If not, from your TSO command line execute the command TSO LISTA, which will list all data sets allocated to your TSO session. Your TSO logon procedure is most likely located in a data set with final node of PROCLIB.
Determine the CMDLIB you will use. Select the member containing your logon procedure, find the SYSPROC DD, and select a CMDLIB to copy TCPNAMES into.
If you are copying TCPNAMES into a VBA library, you must delete the line numbers that appear in columns 73 through 80 after you copy it in.
2
Member JOBCARD in the CNTL library is used by the TCPNAMES EXEC to customize the jobcards of all other installation members.
Choose a jobcard and copy it into the CNTL data set member JOBCARD.
If you are using JES3, replace the JOBPARM card with the following:
//*MAIN LINES=(999,W)3
Member ALLOCSMP allocates the data sets that contain your consolidated software inventory. Edit and submit member ALLOCSMP according to the instructions below.
Before submitting the ALLOCSMP member, consider the following:
•
•
•
•
Edit the ALLOCSMP member by entering TCPNAMES at the command line.
Submit ALLOCSMP.
4
Member ALLOCT00 in the CNTL library allocates the libraries that will contain the Cisco IOS for S/390 base product.
Before submitting the ALLOCT00 member, consider the following:
ALLOCT00 requires 2333 tracks. You may choose to distribute some of the libraries across multiple volumes. This requires manual editing of ALLOCT00 after you execute TCPNAMES.
The PFSLOAD and FTPLOAD libraries are allocated. The PFSLOAD library is used with OpenEdition and contains Physical File System (PFS) modules. It must be APF-authorized. If you are not using OpenEdition, the library is not required. The FTPLOAD library will contain the FTP3 load module for IBM-FTP client compatibility.
Edit the ALLOCT00 member by entering TCPNAMES at the command line.
Submit ALLOCT00.
5
Member INSTSMPE in the CNTL library is used to install the base product.
Before submitting the INSTSMPE member, consider the following:
The Cisco IOS for S/390 release 2.0 product consists of four FMIDs. You must apply the Cisco IOS for S/390 FMID, T01T520, and the translate table FMID, T01X520. Optional FMIDs are the development FMID, T01D520, and the SAS 6.0 runtime FMID, SAS0600. No user changes are required.
You may submit only the RECEIVE portion of this job first. This will let you review the HOLDDATA, especially any hold action that may appear, and take appropriate action. It will also let you add additional BYPASS HOLD keywords to your APPLY statement.
Edit the INSTSMPE member by entering TCPNAMES at the command line.
If you are using a tape management system such as CA1, you must modify the label parameter on your DD statements to include EXPDT=98000.
LABEL=1,NL,,EXPDT=98000If you are using JES3, replace the JOBPARM card with the following:
//*MAIN LINES=(999,W)Submit INSTSMPE.
Note
6
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.com
cd pub/ptf520
ascii
get hold.txt
At the prompt for a storfile name, enter the following (including the single quotation marks):
'your_80byte_pds(member)'
quit
This file is in ASCII and is to be downloaded to MVS for processing by SMP/E. Translation of ASCII text to EBCDIC is automatic during transfer.
PTFs may have a HOLD status associated with them that should be reviewed before you begin the APPLY process. Review the ++HOLD requirements after you RECEIVE the SYSMODS. When satisfied, use a BYPASS(HOLDSYS) on the APPLY command and rerun the APPLY job without the CHECK parameter.
Use this HOLDDATA file as your SMPHOLD file in the SMPHOLD DD statement. If you do not have Internet access, contact Cisco TAC for the latest HOLDDATA file.
7
Member SMPECUMT in the CNTL library is used to apply maintenance to the base product.
The non-labeled (VOL=SER=PTFTAP) maintenance tape distributed with the product contains the latest maintenance for the Cisco IOS for S/390 product. Apply this maintenance, as well as any maintenance obtained interactively from our web site, prior to beginning any customization, as configuration files or parameters may have changed.
Before submitting the INSTSMPE member, consider the following:
•
Edit the SMPECUMT member by entering TCPNAMES at the command line.
•
LABEL=1,NL,,EXPDT=98000•
/*JOBPARM L=9999•
//*MAIN LINES=(999,W)•
Submit SMPECUMT.
SMPECUMT will generate the following message:
GIM34701E: SMPE expected to find ++MCSThis 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. Confirm that the number of occurrences matches the number of PTFs you applied.
8
If you require additional PTFs that are not on the CUM tape received with your installation package, access the following web site for a list of PTF numbers available:
http://www.interlink.com/support/
Scroll down approximately two pages and select the hypertext /pub directory.
Select the ptf520 directory.
Note
Create a data set to contain the PTFs you will select. we recommend you use the same naming convention you used in the TCPNAMES High Level Qualifiers (HLQ) for your LNKINDX variable.
When you know the PTF numbers you want from the web site, set up a batch job with multiple GET commands using the specific PTF numbers and FTP to the Interlink anonymous FTP site. For User ID, use anonymous; for password, use guest.
open ftp.interlink.com
anonymous
guest
bin
cd /pub/ptf520
get TPnnnnn.BIN `your_data_set_name( TPnnnnn ) '
bye
Customization
This section describes the members that can be customized.
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
Some of the Cisco IOS for S/390 release 1.0 members have been changed or deleted and many parameters have been relocated to different members in Cisco IOS for S/390 release 2.0. We recommend that you select your Cisco IOS for S/390 release 2.0 members and then split screen to browse your Cisco IOS for S/390 release 1.0 members in order to transfer the appropriate parameters to the correct Cisco IOS for S/390 release 2.0 members. Use the chart at the beginning of this document to see where parameters were in Cisco IOS for S/390 release 1.0.
APPCFGxx: Verify that the service statements that were in member ACPCFGxx in Cisco IOS for S/390 release 1.0 are now in APPCFGxx.
APPLUPxx: The LUPOOL statement has a new ALLOCATE parameter:
DNRxxxxx: In general, you can transfer or copy these members from the Cisco IOS for S/390 release 1.0 PARM library to the Cisco IOS for S/390 release 2.0 PARM library. However, be sure to verify accuracy and validity of the parameters and their placement.
DNRALCxx: Users running in a multihomed environment must place entries in the DNRALCxx member for all non-loopback LNIs to allow domain name resolution to occur. If only one is defined, expect the following message:
T01CF150E APP configuration error: invalid SUBSYS Name subsysnameProcessing continues after the message displays.
DNRCFG01: Replace NAMESERVER(NONE) with NAMESERVER(DNRNSC01). You will be customizing this member later.
DNRNSC01: Complete the lines requesting that you "set server for your domain."
IJTCFGxx: The existing Cisco IOS for S/390 release 1.0 authorization keys work for Cisco IOS for S/390 release 2.0 if you use the same CPU. CPU serial numbers, processor status, and other information can be obtained via execution of the MVS command D M=CPU.
STARTxx: To aid in diagnosis, insert the following statement on the first line of the STARTxx member:
MODIFY TRACE ON SIZE(256)
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.
UMODTRAN: Read the section "Maintaining Translation Tables Using UMODTRAN" in the "Telnet and tn3270 Configuration Chapter" of the Cisco IOS for S/390 Customization Guide.
UMODAPPL: This is the usermode that you will most likely apply. In order for UMODAPPL to run, you must modify member APPLNAME in the SAMP library with your correct VTAM APPL.
UMODPOOL: UMODPOOL uses member ACCPOOL in the SAMP library. Old style 3174 controllers did not let things start with 01, so the starting name is ACSVLT02.
Invoking Cisco IOS for S/390 Release 2.0
The startup member, RUNTCP, is located in the control library you designated in your installation JCL. This member will invoke Cisco IOS for S/390 release 2.0. You will have a choice to submit RUNTCP as either a started task or as a batch job.
Before submitting the RUNTCP member, consider the following:
•
•
Note
Edit the RUNTCP member.
•
•
•
•
•
•
•
/*JOBPARM LINES=9999•
//*MAIN LINES=(999,W)•
•
// PEND//label EXEC TCPIPTo prepare RUNTCP as a started task:
•
•
Submit RUNTCP.
•
•
•
ACC210I Internet Protocol Task Startedno longer displays to indicate that startup has completed. A message will display indicating startup completion in Cisco IOS for S/390 release 2.0. The message number will vary, depending on the device you are using. The message text will beMedia media_name is now operational with one or more active interfaces.To stop RUNTCP, issue the MVS command F RUNTCP,P CLEAR and answer YES to the reply. This reply is generated if you have the PROMPT parameter specified in your IJTCFGxx member.
If RUNIUCV is to be stopped, it must be done after RUNTCP has terminated.
Diagnosis and Problem Reporting
Generally, Cisco needs the following documentation to help diagnose problems thoroughly:
•
•
•
•
Obtaining GTF Output
The "Command Scripts" section of Chapter 2, "Cisco IOS for S/390 Operation" in the Cisco IOS for S/390 System Management Guide provides a sample command script to start GTF and turn on tracing.
Obtaining a SNAP Dump
As soon as a problem occurs, enter the following MVS command to your Cisco IOS for S/390 address space:
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.
Obtaining JCL Output
Copy the JCL output of RUNTCP to a file using the following procedure:
•
•
SAS/C Usage Notes
You must use the SAS 6.0 compiler, header files, object files, and runtime libraries to COMPILE and LINK using the Cisco IOS for S/390 release 2.0 socket library
You can run a down-level (SAS 5.5) c program against Cisco IOS for S/390 release 2.0, and it can be compiled and linked using the Cisco IOS for S/390 release 1.0 (or lower) socket library. However, it must be run using the SAS 5.5 runtime library. This program can then run over the Cisco IOS for S/390 release 2.0 stack.
•
•
•
In addition, in SAS 6.0, LSCNCOM is always dynamically loaded. If linked with the application program in 6.0, LSCNCOM will cause ABENDs.
Converting from Cisco IOS for S/390 Release 1.0 to Cisco IOS for S/390 Release 2.0
This section provides information on how to convert your Cisco IOS for S/390 release 1.0 configuration files to the configuration files used for Cisco IOS for S/390 release 2.0. There is also a discussion on the use of the LOGGING statement.
Several diagrams are given to show the parameter changes. In the diagrams, parameters not available in Cisco IOS for S/390 release 2.0 are shown crossed out (OLDPARM). New parameters are shown in boldface type (BOLD).
For complete information on the Cisco IOS for S/390 product, please refer to your documentation set.
This section contains the following topics:
•
ACPCFG00 HOST Statement
Many of the ACPCFG00 HOST statement parameters were distributed into new and existing configuration files for release 2.0. Parameters that affect applications have been moved to APPCFG00, system parameters have been moved to IJTCFG00, and protocol parameters have been moved to TCPCFG00.
These release 1.0 parameters have been deleted:
•
•
•
•
•
Parameters renamed for release 1.0:
•
New statements/parameters for release 2.0:
•
•
The following diagram illustrates the changes.
Figure 1 HOST parameters
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:
•
New parameters for release 2.0:
•
Figure 2 Application Parameters
TCP Protocol Parameters
The TIB, TCP and UDP parameters from ACPCFG00 have been moved to TCPCFG00. These parameters are now defined under each protocol, TCP, UDP, IP, and RAW. There was only one parameter name change. TADDRASSIGN and TADDRUSE have been renamed to PORTASSIGN and PORTUSE, respectively. Aliases have been added to support former names, including the TADDRASSIGN and TADDRUSE parameters.
Parameters removed from release 1.0:
•
•
•
Parameters renamed for release 1.0:
•
•
There are new parameters for the TCP statement in release 2.0:
•
•
•
•
•
•
The following diagram shows the parameters.
Figure 3 TCP Parameters
UDP Protocol Parameters
The ACPCFG00 TIB and UDP mappings have been moved to TPPCFG00.
Parameters removed from release 1.0:
•
•
Parameters renamed for release 1.0:
•
•
New parameters for release 2.0.
•
Figure 4 UDP Parameters
RAW Protocol Parameters
The ACPCFG00 TIB parameters for the RAW protocol have been moved to TCPCFG00.
Parameters removed from release 1.0:
•
Parameters renamed for release 1.0:
•
New parameters for release 2.0.
•
Figure 5 RAW Protocol Parameters
NETWORK Parameters
NETWORK parameters have been moved to TCPCFG00 NETWORK and MEDIA statements.
Parameters removed from release 1.0:
•
•
•
Parameters renamed for release 2.0:
•
New parameters for release 2.0.
•
•
•
Figure 6
NETWORK Parameters
ROUTE Parameters
The following diagram shows the routing statements from Cisco IOS for S/390 release 1.0 and their usage in Cisco IOS for S/390 release 2.0. Most important to notice is that the old ROUTE NET parameter is now a ROUTE MEDIANAME parameter.
Parameters removed from release 1.0:
•
•
•
Parameters renamed for release 2.0:
•
New parameters for release 2.0.
•
Figure 7 ROUTE Parameters
Driver Configuration
Driver configuration has been moved to TCPCFG00.
CETI Driver
CETI driver commands have been moved to TCPCFG00.
Parameters removed from release 1.0:
•
•
•
•
•
•
•
Parameters changed:
•
•
New parameters for release 2.0.
•
•
Figure 8 CETI Driver Parameters
LNICLAW
ACPCFG00 LNICLAW parameters have been moved to the TCPCFG00 CLAW statement.
Parameters removed from release 1.0:
•
•
•
Parameters changed:
•
•
New parameters for release 2.0.
•
•
•
•
Figure 9 CLAW Driver Parameters
LNICDLC
ACPCFG00 LNICDLC parameters have been moved to the TCPCFG00 CDLC statement.
Parameters removed from release 1.0:
•
•
•
Parameters changed:
•
•
New parameters for release 2.0.
•
•
Figure 10 CDLC Driver Parameters
LNIHYPR
ACPCFG00 LNIHYPR parameters have been moved to the TCPCFG00 HYPER statement.
Parameters removed from release 1.0:
•
•
•
Parameters changed:
•
•
New parameters for release 2.0.
•
•
Figure 11 HYPR Driver Parameters
LNILCS and LNILINK
ACPCFG00 LNILCS and LNILINK parameters have been moved to TCPCFG00 LCS and LINK statements.
Parameters removed from release 1.0:
•
•
•
Parameters changed:
•
•
•
•
New parameters for release 2.0.
•
•
•
•
Figure 12 LCS and LINK Parameters
IJTCFG00 Changes
There have been minimal changes to the IJTCFG00 IFSPARM and AUTH statements. The LOGGING statement haas been added to IJTCFG00.
Parameters removed from release 1.0:
•
Parameters changed:
•
New parameters for release 2.0.
•
•
•
•
•
•
Figure 13 IFSPARM and AUTH Statements
LOGGING Statement
One of the design goals of Cisco IOS for S/390 release 2.0 was to reduce the volume of message output printed. SMF recording was enhanced to allow many of the events previously recorded only by a message to be written to the SMF datasets.
Messages were renumbered so that each message now has a unique prefix, which includes both a severity, and a component code to identify the area of the product which issued the message. The LOGGING statement was added in IJTCFGxx to give you control over which messages will be written to the log or to the console. Message routing can be controlled by severity and component, using the LOGGING statement.
By default, many events previously reported by messages will go unreported in Cisco IOS for S/390 release 2.0. Some customers may prefer to continue seeing the same level of message output as in previous releases of the product. The following LOGGING statement parameters are designed to give a level of event recording reasonably close to what was provided by previous releases of Cisco IOS for S/390:
LOGGING PRINT(ALL,(DN,RFEW),(IF,RFEWIS))
WTO((LL,RFEWIS),(CF,RFEWI))
You may find that there are other defaults you will wish to change. The LOGGING parameters can be changed dynamically by means of the new LOGGING command, making it easy to experiment with different configurations.
For complete information on the LOGGING statement, and the LOGGING operator command, refer to the Cisco IOS for S/390 documentation.
78-5661-01 Rev. B0
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)
This Document Applies to These Products
- Collaboration Endpoints - Retired Products
- Conferencing - Retired Products
- Contact Center - Retired Products
- Optical Networking - Retired Products
- Routers - Retired Products
- Security - Retired Products
- Servers - Unified Computing (UCS) Retired Products
- Storage Networking Retired Products
- Switches - Retired Products
- Video - Retired Products
- Wireless - Retired Products