LISTLOG/PRINTLOG Printing Log Streams, 393

Chapter 23. LISTLOG/PRINTLOG - Printing Log Streams

Both VSE and OS/390 provide facilities to capture system log data in a hardcopy file, and means to display, print and archive it.

There are two utilities in VSE that help you print copies of your system hard-copy file and information about jobs that run in your system: PRINTLOG and LISTLOG.

In OS/390, the system hardcopy log can be saved on JES spool or in a log stream managed by the system logger, and printed by JES.

23.1 VSE PRINTLOG Utility

The IBM utility program PRINTLOG prints the hardcopy file from disk to SYSLST. Each line that appears on the screen of the display console is written to the hardcopy file, which resides on SYSREC. It may become necessary to print all or part of the hardcopy file. You may need to print the hardcopy log in order to review system events, or to determine which messages were issued for a certain partition. You should also print its contents before it is overwritten (see

²Hardcopy File Full Condition² in the VSE/ESA Guide for Solving Problems).

23.2 VSE LISTLOG Utility Program

The LISTLOG utility program is used to gather information about how a particular job has run on the system. LISTLOG derives the information to be printed from the hardcopy file. It prints all messages and commands relevant to the partition in which the job ran. LISTLOG will provide a listing of the following items on

SYSLST:

∙

job control statements which are written to the console console messages for the job

operator responses for the job

attention routine messages and commands issued while the job was running.

See IBM VSE/ESA System Utilities for additional information on LISTLOG.

23.3 OS/390 Hardcopy Processing

Hardcopy processing provides a permanent record of your OS/390 system activity and helps you audit the use of operator commands. You can record system messages and, optionally, commands, by using either the system log (SYSLOG), the operations log (OPERLOG), or an MCS printer. The group of messages and commands that are recorded is called the hardcopy message set. The system log, operations log, or MCS printer that receives messages is called the hardcopy medium. You can specify a group of console devices that can serve as backup devices for the hardcopy medium. You can also allow an extended MCS console to receive hardcopy messages from one or more systems in a sysplex.

The following describes the SYSLOG and OPERLOG and how to print them. See OS/390 MVS Planning: Operations, GC28-1760 for details.

393 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.

IBM OS/390 manual LISTLOG/PRINTLOG Printing Log Streams, VSE Printlog Utility, 393

Models: OS/390