Manuals / IBM / Computer Equipment / Server

IBM OS/390 28.4.3 JES2 Devices, Sdsf Device Panels, Controlling TSO Users, Jobs and Started Tasks

Models: OS/390

1 673
Download 673 pages 53.75 Kb
Page 473
Image 473

28.4.3 JES2 Devices

Devices such as printers, punches, TP lines, and spool offload tapes can be allocated by JES2 dynamically. The following JES2 command verbs are used to control JES2 devices and are followed by the device name such as PRT1, PUN(12), LINE(5).

$D Display the device $S Start the device

$P Stop the device when it is through with the current job $Z Halt the device immediately

$C Cancel the job currently being processed on the device $T Change the device setup characteristics

$I Interrupt printer or punch $N Repeat printer or punch

$E Restart the device (interrupt and re-queue) $B Backspace printer or punch

$F Forward space printer or punch

PSF printers are defined as JES2 printers and controlled through the same commands used for JES2-controlled printers.

28.4.4 SDSF Device Panels

There are separate SDSF panels for JES2 devices such as printers, punches, readers, lines, remote workstations, and NJE nodes. These may be more convenient than the JES2 commands, because you can:

∙

∙

∙

∙

Display many devices in a tabular format,

Issue any operator command in a simpler form (complete with ²Help²), Change the characteristics of a device by over-typing fields,

Manage input and output queues for these devices.

28.5 Controlling TSO Users, Jobs and Started Tasks

Time-sharing users, batch jobs, and started tasks all represent work being performed on the system and reside in their own address space. They are initiated in different ways, but all can be displayed and controlled in similar ways with MVS commands, JES2 commands and SDSF panels. However, there are subtle differences that make some better than others.

28.5.1 Displaying Work on Your System

TSO users, batch jobs, and started tasks each run in their own address space, and represent work by one or more users on your system. There are MVS and JES2 commands to display and control them. SDSF, RMF, and other monitors also have operator interfaces to monitor and control.

Each of these has different information and presentation. Try each of them and use what seems best for your purposes.

Chapter 28. Orientation to OS/390 Console Operation 449

Page 472 Page 474
Page 473
Image 473
IBM OS/390 manual 28.4.3 JES2 Devices, Sdsf Device Panels, Controlling TSO Users, Jobs and Started Tasks
Page 472 Page 474

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.