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.

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:

The CMND data set is no longer allocated or used. The START00 member is now located in the PARM data set. The RUNTCP member in the CNTL data set reflects this change.

Two libraries, PFSLOAD and FTPLOAD, are allocated. The PFSLOAD library is used with OpenEdition and contains Physical File System (PFS) modules. It must be APF-authorized to work as specified in the Installation Requirements section earlier in this document. If you are not using OpenEdition, the library is not required. The FTPLOAD library is reserved for future use.

Note TCPLOAD must never be in the linklist. 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.

Edit the RUNTCP member.

Do not execute TCPNAMES.

Change the symbolic ‘TRGINDX’ to the value you specified in member TCPNAMES.

Verify that the symbolic SSN=ACSS is available for use. The MVS command D SSI will display subsystem names that have been invoked during the life of the current IPL. You can use ACSS if it either does not display or if it shows as inactive. If ACSS is active, you must choose a different name for your subsystem.

Verify that the symbolic ‘SRC=%’ is available for use.

If you are using a user VTAMLIB, you must add it to your STEPLIB concatenation to make sure RUNTCP can find your USSTAB.

You need to add one of the following lines immediately after the JOBCARD to support diagnostics.

32Cisco IOS for S/390 Release 2.0 Release Notes

Page 32
Image 32
Cisco Systems manual Usermod Customization, Invoking Cisco IOS for S/390 Release

S/390 specifications

Cisco Systems S/390, also known as IBM's S/390 architecture, is a revolutionary mainframe computing solution that has significantly impacted enterprise computing since its introduction. Though primarily associated with IBM, its integration with Cisco Systems technologies has fostered enhanced networking capabilities, creating a robust platform for organizations to leverage.

One of the most notable features of the S/390 architecture is its scalability. The system is designed to manage workloads efficiently, enabling organizations to scale their operations seamlessly as their requirements grow. This architecture supports an extensive range of applications, from transaction processing to complex data analysis, making it suitable for diverse industries.

The S/390 systems are known for their reliability and resilience. With advanced error detection and correction mechanisms, the architecture minimizes downtime, ensuring that mission-critical applications remain operational. The mainframe's design accommodates redundancy and fault tolerance, reinforcing its reputation as a dependable computing solution.

Moreover, security is a core characteristic of the S/390 infrastructure. It incorporates various security features, such as encryption and robust access control mechanisms, to safeguard sensitive data against unauthorized access and cyber threats. This level of security is particularly critical for industries such as finance, healthcare, and government, where data protection is paramount.

The integration of Cisco networking technologies with the S/390 architecture brings enhanced connectivity and streamlined communication capabilities. Cisco’s advanced routing, switching, and security solutions bolster the mainframe's communication prowess, enabling organizations to create seamless, high-performance networks. This ensures that data flows efficiently between the mainframe and other networked devices.

Additionally, S/390 supports an array of middleware solutions, facilitating better interoperability with modern applications and cloud services. Organizations can take advantage of this flexibility to leverage existing investments in technology while embracing innovative solutions.

In summary, Cisco Systems S/390 embodies a potent combination of scalability, reliability, security, and advanced networking features. Its architecture serves as a cornerstone for enterprise computing, allowing organizations to meet their evolving business needs while maintaining high-performance standards. As businesses increasingly rely on data-driven decision-making, S/390 remains a critical asset for organizations striving for efficiency and innovation in their operations.