delete the first character of each record, and will delete the END OF MEMBER statements. The last statement placed on the output tape will be the IEBUPDTE statement ./ ENDUP. This tape will then become the input to the IEBUPDTE utility on an MVS system. Information about the PDS to be created will be contained in the MVS JCL used to invoke IEBUPDTE.

No matter what method you choose for migrating ICCF members to data sets accessible to TSO/E, you should not attempt to move ICCF Procedures or Macros, or IPF panels and tables contained in ICCF libraries. For information on the requirements for the MVS utility IEBUPDTE, see MVS/Extended Architecture Data Administration: Utilities.

7.5.2 ICCF Procedures and Macros

ICCF procedures and macros cannot be used under TSO/E. It is therefore necessary to determine what function is performed by an ICCF procedure or macro and determine how this function can be implemented in TSO/E.

For example, the SUBMIT procedure of ICCF is used to submit jobs to a batch partition for execution. TSO/E provides this facility through the SUBMIT command. If you have modified the ICCF SUBMIT procedure to enforce JCL standards, you will need to investigate the exit routine capability of the TSO/E SUBMIT command processor.

Most of the function provided by IBM supplied ICCF procedures is available either through TSO/E commands, or in services provided though MVS. An example of function provided by ICCF procedures that is implemented in MVS services would be the GETL and GETP procedures. These ICCF procedures allow you to move list and punch output respectively from the VSE/POWER queues to an ICCF member. Since MVS, through the job entry subsystems (JES2 or JES3), allows you to direct your program output to a data set accessible to TSO/E, the function of these two ICCF procedures is also available to you as a TSO/E user.

If you have written your own ICCF procedures or macros to perform frequently executed sets of ICCF commands, you will find that you have the same capability under TSO/E through CLISTs or COMMAND procedures.

Chapter 7. ICCF and TSO 167

Page 191
Image 191
IBM OS/390 manual Iccf Procedures and Macros

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.