TRANSACTION/RESTART

this option now governs restart in two separate types of situation.

TYPETERM/RECOVNOTIFY

the scope of this parameter is extended to cover VTAM persistent sessions. In CICS/VSE this parameter was meaningful for CICS regions running with XRF only.

6.1.8 CICS System Data Sets Requirements

Before you install your CICS data sets you should determine the DASD requirements for all CICS data sets and MVS data used by CICS.

Below are the data sets needed to implement CICS TS. You should review the CICS System Definition Guide, SC33-1682 and the CICS Installation Guide, GC33-1691 for full details on the facilities, functions and usage for each data set listed below:

Temporary storage data set

Transient data destination data sets

CICS log streams

System definition data set

Catalog data sets

Auxiliary trace data sets

Dump data sets

Availability manager data sets

CMAC messages data set

After you have installed CICS, and applied any necessary service, you can run the DFHCOMDS, DFHDEFDS, and DFHCMACI jobs to create the CICS data sets. MVS storage management facility (SMS) should facilitate the placement, and allocation of your data sets. Still, you should keep an eye on extent allocations for the data sets used by CICS, for performance reasons (that is, is the single extent allocation too small).

Be sure you note that CICS Log is unique to CICS TS, and requires special consideration as opposed to journal files used in CICS/VSE. In OS/390 Version 2 Release 4, the CICS log manager supports the DASD-only option of the MVS system logger. This means that individual CICS log streams can use either Coupling Facility structures or DASD-only logging.

Figure 13 on page 146 shows the choices you have when defining individual log streams, depending on the hardware and software you are using.

Chapter 6. CICS 145

Page 169
Image 169
IBM OS/390 manual Cics System Data Sets Requirements, Typeterm/Recovnotify

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.