|
|
March 15, 1999
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 Version 1.0.
In addition to the cumulative maintenance tape you received with the product, there may be other installation or maintenance requirements. Please contact your local support office for the latest information or HYPER PTFs.
This document contains the following sections:
This section describes additions and corrections to the Cisco IOS for S/390 Version 1.0 documentation set.
This section describes additions and corrections that have been made since the release of the Cisco IOS for S/390 Version 1.0 Customization Guide.
On page A-12 of the Customization Guide:
The ACPCFGxx FTP DATAIDLE parameter default has been changed from 60 seconds to 600 seconds.
The definition for the LOGALC parameter on the HOST statement has been modified for the Logspin enhancement. For the LOGALC parameter (on page A-25 of the Customization Guide), the existing definition has been changed to:
Specifies output class, destination, form, and writer for log files, where:
This parameter affects only WTPLOGs; it does not affect DNR logs, MAP logs, or GTD logs.
The &SOUT parameter from the PARM= string on the JCL EXEC statement defines the absolute default SYSOUT class. The default is &SOUT LOCAL STD blank.
Also, add the following usage notes to the HOST Usage Notes on page A-29 of the Customization Guide:
LOGALC (P LOCAL STD LOGWTR)
On page A-82 of the Customization Guide, in the section on the Transport Services Information Block (TIB), replace the definition for MAXQLSTN with the following information:
Specifies the maximum number of requests for connections or associations that can be queued to a bound and enabled API endpoint.
The defqlstn (default qlstn value) is determined in the following manner:
If using BSD or OE sockets
defqlstn is set in the backlog parameter
on the sockets listen( ) call
If using the assembler API
defqlstn is set to the value in the QLSTN= parameter
of the TBIND macro
The MAXQLSTN is the largest defqlstn value supported on any of the above listen calls. Defqlstn values greater than MAXQLSTN are silently trimmed. The default is 25.
Delete the following statement from the first bullet item of the TIB Usage Notes (on page A-83 of the Customization Guide):
Note that there is no DEFQLSTN to correspond to the MAXQLSTN parameter. The QLSTN value that is in effect for an API endpoint is always zero unless it is set with the QLSTN parameter of the TBIND statement.
Information has been added for the TADDRASSIGN and TADDRUSE, parameters on the Transport Services Information Block (TIB) statement of ACPCFGxx. On page A-82 of the Customization Guide, add the following information for these two parameters:
The default for TDRASSIGN has changed. The default is now 4096, 65535.
Add the following paragraph after the current paragraph:
Assignment of ports via the ASSIGN parameter occurs only from the ranges specified on the TADDRASSIGN statement. Note that if the TADDRUSE statement overlaps the port ranges on the TADDRASSIGN statement, a port set aside for USE may be ASSIGNed. This change might affect the availability of a port for a server (typically servers use the USE parameter). We recommend that TADDRUSE and TADDRASSIGN port range parameters not overlap.
See the TADDRUSE parameter section for more information on port assignment.
The default for TADDRUSE has changed. The default is now 1, 4095.
Add the following paragraphs after the current paragraph:
Ports are assigned through the use of a bitmap. Each bit represents a port. Allowable values are 1 through 65535. All bits are set to indicate "not available" initially. Ports are then set to be available through use of the TADDRASSIGN and TADDRUSE statements (or the default values, if no TADDRASSIGN or TADDRUSE statements are coded). Either statement specifies a port or range of ports and marks the ports available.
Any port specified in either statement will be available for use via OPTCD=USE, whether or not it exceeds the specific ranges specified on the TADDRUSE statement. However, only the ports ascribed via the TADDRASSIGN statement will be used for assignment via OPTCD=ASSIGN.
It is a function of TCP/IP that any allowable port not already in use that is specified on the BIND statement can be used. Within this feature of TCP/IP, the recommended use of the TADDUSE and TADDRASSIGN parameters ensures that certain ports are always available to servers, while clients still have a large number of ports available for spontaneous assignment.
In Customizing Your Mail Environment, Step 5, sub-step 3 (on page 2-40 of the Customization Guide), the OUTCLASS (E) and (F) parameters should be replaced with:
OUTCLASS(A) BLNKTRNC=YES, /* Truncate trailing blanks
OUTDISP=(WRITE,WRITE), /*
OUTPUT=PRINT, /* Print Class
TRKCELL=YES /* Track-Cell this Class
In SNMP Agent Configuration, under SNM Usage Notes (on page A-144 of the Customization Guide), add the following usage note about the community_name parameter on the COMMUNITY statement:
This section describes document additions that have been made since release of the Cisco IOS for S/390 Version 1.0 Planning and Operations Guide.
In the SMF Record Formats chapter (on page 5-3 of the Operations Guide), one of the numbers in the "Descriptor Section" table is incorrect. In the third row, second column, the second offset for the field SMFACPLN should be 18, not 28.
The following change has been made in the ACP Commands section, on page 6-20 of the Operations Guide. Replace this line:
Use the REFRESH command to initiate a refresh of ACP LUPOOL configuration data. The only ACP configuration data that can be refreshed is the LUPOOL facility
With this line:
Use the REFRESH command to initiate a refresh of ACP LUPOOL configuration data or USS Tables.
/[ACP] REFRESH [ LUPARM ( ACPLUPxx ) | USSTAB ( tbl_name ) ]
Where:
A new example has been added:
Example:
REFRESH USSTAB(T01USS01)
The following change has been made to the ACTEST commands section (on page 7-11 of the Operations Guide) for VLT ON | OFF:
Change AMDUSR to IPCS GTFTRACE.
The example for tracert (on page 7-31 of the Operations Guide) has changed. The correct example is:
tracert -n -s 138.42.220.13 ibmnt.westend.com traceroute to IBMNT.WESTEND.COM. (194.231.119.65) from 138.42.220.13, 30 hops max, 40 byte packets 1 138.42.220.18 19 ms 18 ms 18 ms 2 138.42.200.7 24 ms 22 ms 19 ms 3 204.70.101.77 165 ms 163 ms 164 ms 4 204.70.101.77 172 ms 161 ms 144 ms 5 204.70.98.17 145 ms 148 ms 147 ms 6 166.48.44.1 160 ms 162 ms 163 ms 7 204.70.4.9 171 ms 174 ms 195 ms 8 206.157.77.114 191 ms 194 ms 184 ms 9 137.39.21.74 166 ms 181 ms 207 ms 10 137.39.69.69 207 ms 193 ms 203 ms 11 137.39.11.4 219 ms 228 ms 254 ms 12 137.39.156.246 395 ms 418 ms 345 ms 13 194.77.0.6 372 ms 381 ms 323 ms 14 194.77.0.78 346 ms 356 ms 396 ms 15 194.77.26.32 623 ms 510 ms 570 ms 16 194.231.119.65 577 ms * 522 ms ***
The following changes and additions have been made since release of Cisco IOS for S/390 Version 1.0. These changes affect the Cisco IOS for S/390 Version 1.0 Prefixed Messages manual.
The following changes have been made to the messages.
Under the Action Required heading, the syntax for the DNRGET command is incorrect. Replace SUBSYS with SYSID. The following statement:
DNRGET H BYN ACSS SUBSYS(ACSS)
should be changed to:
DNRGET H BYN ACSS SYSID(ACSS)
Remove the following line from error message ACC841I:
This message only comes out when VLT ON has been set under ACTEST.
The following messages have been added.
Explanation Cisco IOS for S/390 has recognized that the IUCV subsystem subsysid has terminated. Cisco IOS for S/390 will try to reconnect with a New IUCV address space every 30 seconds.
Source Module: T01AMIUC
Explanation When the ptask is T01AMIUC and the module is IFSPPCEX then Cisco IOS for S/390 was unable to find the ASID for IUCV from the MVS PC tables. The pc_num is the PC number that it failed to convert into an ASID. The ret_code is the return code from module IFSPPCEX that details the specific error. This could lead to a situation where Cisco IOS for S/390 might not be able to recognize when the IUCV address space is shutting down.
R15 is one of the following:
Recommended Action Save all job output from the Cisco IOS for S/390 job. Contact your local TCP support personnel.
Source Module: T01AMIUC
Explanation The inbound mailer ptask SSMTP discovered that its subsystemid maps to a name that contains invalid syntax. Ptask SSMTP issues message T01SM008I and exits with a return code of 1024. The cause of the problem could be one of the following:
Recommended Action Check your DNRCCCxx configuration file for errors. Examine the DNRLOG for errors. Check that the TCP subsystem id in the DNRALCxx file maps to the fully qualified host name in file DNRHSTxx. When running DNR in global mode, verify that the nameservers know your TCP MVS host name. Issue the following command under TSO while Cisco IOS for S/390 is running (where LINK library routine DNRGET is available via STEPLIB or LNKLSTxx:
DNRGET HOST BYNAME ssss SY(ssss)If the DNRGET does not return the fully qualified host name for your MVS host and its IP address, then your site's DNR configuration or its name servers configuration should be examined in detail.
Explanation An error occurred during the attempted delivery of a mail message. Usually an error of type err_type will stop delivery of the message to all affected users. However, the UMAPTEMP configuration parameter in startup file ACPCFGxx maps this error to a temporary error. The outbound mailer USMTP will attempt redelivery of the mail message at its next scheduled cycle for the mail message.
Source Module: SMTPSM
Explanation The REFRESH USSTAB(tbl_name) operator command executed successfully.
Recommended Action None required.
Source Module: ACPOREFR
Explanation This is a negative response to the REFRESH USSTAB(tbl_name) operator command. The ACP task was not fully initialized or is in the process of stopping.
Recommended Action Wait for the ACP task to complete initialization or restart the APP task if it was stopped.
Source Module: ACPOREFR
Explanation Negative response to REFRESH USSTAB(tbl_name) operator command. The tbl_name was not found in the JOBLIB/STEPLIB or link-listed library.
Recommended Action Add the tbl_name to the JOBLIB/STEPLIB or link-listed library.
Source Module: ACPOREFR
Explanation Negative response to REFRESH USSTAB(tbl_name) operator command. The tbl_name has invalid format (should start with X'BD').
Recommended Action Correct the format of the tbl_name.
Source Module: ACPOREFR
Explanation Negative response to REFRESH USSTAB(tbl_name) operator command. The tbl_name for ACP task was not specified in active APPCFGxx SERVICE segment.
Recommended Action Check for proper spelling of tbl_name.
Source Module: ACPOREFR
Where:
Explanation The subroutine discovered a nameda control block that has an invalid length field. The subroutine called subroutine badlimb() to report the problem nameda cache entry. If there was a previous nameda structure it will be at prev_nameda. See related message, DNR181E, for more information in the failing nameda entry.
If this error has not occurred in the last 24 hours since the DNR task group was started, then an SVC dump will be generated. The cache limb will be removed from the DNR cache to prevent potential S0Cx abend situations. The problem may be a storage overlay of the nameda control blocks. The problem may involve mishandling of the nameda control blocks. The nameda storage structure is orphaned. The previous nameda or hash table entry is zeroed out to prevent potential abend situations.
Recommended Action Contact your local Cisco IOS for S/390 support personnel. Send in all the Cisco IOS for S/390 job output and the SVC dump for examination. If you stop and start the DNR task group, the DNR control blocks will be freed and you might avoid potential trouble.
Source Module: DNRPURG
Where:
Explanation Fields of a bad nameda (The nameda structure address is in message DNR180E) structure are dumped. The DNR181E message is printed after the DNR180E error message.
Recommended Action See related message DNR180E.
Source Module: DNRPURG
Where:
Explanation The working length field has exceeded the length field boundaries for an entry. Subroutine caddnam discovered a logic error inserting nameda entries into the cache. This represents a logic error in the caddnam program that should never occur. The attempt to insert any more nameda entries into the cache will be abandoned for this current name entry. If this error has not occurred in the last 24 hours since the DNR task group was started, then an SVC dump will be generated.
Recommended Action Contact your local Cisco IOS for S/390 support personnel. Send in all the Cisco IOS for S/390 job output and the SVC dump for examination.
Source Module: NDCACHE
Explanation DNR attempted to take an SVC dump in routine NDSVCD.
The SDUMPX ...TYPE=(FAILRC) call failed with a reason code of reason_code.
Recommended Action Contact your local Cisco IOS for S/390 support personnel. Send in all the Cisco IOS for S/390 job output and the SVC dump for examination. The SDUMPX reason_code should guide addressing the problems with NDSVCD.
Source Module: NDCACHE DNRPURG
Explanation The DNR184I message is used for the title of an SVC dump. DNR took an SVC dump in routine NDSVCD to document a logic error issue.
Module module_name uncovered the logic error. See message DNR18xE (in the DNRLOG DD) that was issued at the same time the SVCDUMP was taken for details on which logic error was uncovered. The storage_location is the storage location module from which NDSVCD was called.
Recommended Action Contact your local Cisco IOS for S/390 support personnel. Send in all the Cisco IOS for S/390 job output and the SVC dump for examination.
Source Module: NDSVCD
Where:
Explanation The attempt to load the IBM module BPXVOSIT for the Open Edition master socket failed.
Recommended Action Verify that Open Edition is installed correctly.
Source Module: ACSXINIT
This section documents messages that have been added or changed since the release of the Cisco IOS for S/390 Version 1.0 Unprefixed Messages and Codes manual.
This section describes new Cisco IOS for S/390 FTP Server messages.
User entered LIST/NLST command that requires a protected catalog to be read but access was denied by the security system of the host.
This section describes new Cisco IOS for S/390 API return codes.
New return codes have been added in the Execution Environment Errors: RTNCD 0Cxx section. On page API/RET-37 of the Unprefixed Messages and Codes, two new return codes have been included in Table 2 (X'02') TESUBSYS. They should be added after X'0C66'.
X'0C6B' TCONNECT failed. IPB address is not an IPB.
X'0C6C' TCONNECT failed. P3CB address is not a P3CB.
A new return code has been added in the Execution Environment Errors: RTNCD 0Cxx section. On page API/RET-43 of the Unprefixed Messages and Codes, a new return code has been included in Table 6 (X'06') TEDRAIN. It should be added after X'0A03'.
X'0B17' This code is set when a TLISTEN is in effect and the ACP and/or API task group is in soft shutdown or drain mode. The application should initiate shutdown procedures.
This section describes new Cisco IOS for S/390 DNR return codes.
A new diagnostic code has been added in the Execution Environment Errors: RTNCD 08xx section for return code "8(X'08') DERSOURCE. On page DNR/RET-19 of the Unprefixed Messages and Codes, replace the first row of the table for DERSOURCE with the following:
X'xxyy' An integer representing the function is designated by the x. An integer representing the specific line number is designated by the yy.
Where xx can be:
A new diagnostic code has been added in the Format or Specification Errors: RTNCD 0Cxx section for return code "5(X'05') DEBDNAME. On page DNR/RET-22, the following diagnostic code should be inserted at the end of the table:
X'200 A NABUF address was passed but the NALEN field was invalid (for example, NALEN=0). You must pass a valid positive length in the NALEN field when setting the NABUF field.
The Cisco IOS for S/390 manual set has been reorganized along functional lines. The complete manual set includes these documents:
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.
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 and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Tue Mar 9 10:03:05 PST 1999
Copyright 1989-1999©Cisco Systems Inc.