Manuals / IBM / Computer Equipment / Server

IBM OS/390 manual Accounting Comparisons, Job Accounting, JES2 SMF Accounting Records

Models: OS/390

1 673
Download 673 pages 53.75 Kb
Page 247
Image 247

Subsystem Version ID You can obtain version-specific information about a subsystem with SSI function code 54. See Using the Subsystem Interface.

Command Interface You can also use the MGCR service to submit JES2 or MVS operator commands to control jobs. See OS/390 MVS Auth Assembler Services Guide, GC28-1763.

10.3.9Accounting Comparisons

10.3.9.1Job Accounting

JES2 records the following accounting information:

∙Job Purge - SMF Type 26 - This is the primary source of information about a job′s use of JES2 resources and history.

∙

∙

∙

∙

∙

∙

∙

∙

Output - SMF Type 6 - Cut by JES2, XWTR, PSF and others

NJE SYSOUT Transmit - SMF Type 57

JES2 Subsystem Start/Stop - SMF Types 43, 45

JES2 Spool Offload - SMF Type 24

RJE/NJE Line Start/Stop - SMF Types 47, 48, 52, 53

RJE Signon/Signoff - SMF Types 47, 48, 52, 53

NJE Signon/Signoff - SMF Types 55, 58

RJE/NJE Signon Password Violations - SMF Types 49, 56

JES2 SMF Accounting Records

SMF (System Management Facilities) is a function of OS/390 that collects and records various system and job data related to the use of resources. This information is recorded in the form of a number of different records, which are numbered. Installations can process the SMF records with any number of application programs to analyze the data, produce reports and so on.

JES2 uses SMF Type 26 (job purge) records to collect all successful SYSIN job transmissions, and SMF Type 57 records to collect all successful SYSOUT transmissions. Since multiple SYSOUT data sets may be transmitted within a job header and trailer, this record may represent multiple SYSOUT data sets.

Note that none of these record the node name of the local node. This can be a problem when combining records from multiple sites.

Job Purge RecordsType 26 Records are cut when a job is purged from the system. The execution node name (and other execution-related fields) are not recorded in the type 26 record when the job executes on the origin node.

SYSOUT Transmission Records Type 57 Records are cut for each group of SYSOUT files sent to another NJE node, but do not contain the Jobname, or Time and Date on the reader at the original node.

Chapter 10. POWER and JES2 223

Page 246 Page 248
Page 247
Image 247
IBM OS/390 manual Accounting Comparisons, Job Accounting, JES2 SMF Accounting Records
Page 246 Page 248

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.