For more information see the OS/390 ISPF Software Configuration and Library Manager Developer¢s Guide, OS/390 ISPF Software Configuration and Library Manager Project Manager¢s Guide, and OS/390 ISPF Software Configuration and Library Manager Reference.

27.1.6 Tracking Jobs

SDSF allows you to monitor any job in the system or sysplex. Values such as CPU time and I/Os per second are displayed for all of the jobs running in the system. Sophisticated and easy-to-use sort and filter functions let users customize SDSF¢s display of jobs. In addition the TSO user who submitted a job can generally view any of the JES spool data sets for that job as they are being created. This includes any of the SYSOUT spool data sets in addition to the message spool data sets. SDSF allows users to control jobs with short commands. These ²action characters² can be used, for example, to hold, release, or cancel one or more jobs. In addition if you are properly authorized you can view the SYSLOG and see the messages for all jobs. For more information see the OS/390 SDSF Guide and Reference.

27.1.7 Retrieving Output

SDSF provides the ability to view any JES spool data set that you are authorized to view. In most cases this would be the output from a job you submitted. Most of the output will be queued to a held output class such that it does not get sent to a printer. If after viewing the output the user determines that it does need to be printed, then the output can be re-queued using SDSF commands. JES spool data sets awaiting a printer can also be viewed. Using ISPF split screen for example, you could view a job message spool data set on one part of the split screen and view a SYSOUT spool data set on the other part.

ISPF also provides an option to directly retrieve (or view) JES spool data and store it in a sequential or partitioned data set, however this option is rarely used if SDSF is available.

27.1.8 Using SDSF for Operators

Some data centers may choose to use SDSF to run the OS/390 system since given the proper authority, all OS/390 operator commands can be entered through SDSF. This makes it very convenient since the operator using SDSF does not physically need to be located near the CPU. In this scenario, the operator would use SDSF to view the SYSLOG, entering commands, replying to WTORs as required. Other SDSF panels are available to show jobs awaiting execution, job executing, to allow display and control of such things as jobs awaiting execution, devices (printers, initiators, lines, and so on) and system resources (members of the MAS, nodes, and so on). It¢s important to give proper consideration to the security and levels of commands available through SDSF, such that application programmers are not allowed to enter normal operator commands. For more information see the OS/390 SDSF Customization and Security manual.

Chapter 27. Orienting ICCF Users to TSO/ISPF 441

Page 464 Page 466
Page 465
Image 465
IBM OS/390 manual Tracking Jobs, Retrieving Output, Using Sdsf for Operators
Page 464 Page 466

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.
Top Page Image Contents