IBM OS/390 Controlling Time Sharing Users, Controlling Batch Jobs, Controlling Started Tasks

Models: OS/390

1 673
Download 673 pages 53.75 Kb
Page 475
Image 475

28.5.2 Controlling Time Sharing Users

TSO/E users logon through terminals controlled by VTAM. You can use MVS or JES2 commands to control TSO users and their output:

Send a Message to a TSO User with the MVS

²SEND ¢message_text¢,U = u s e r i d ² command. Be careful not to omit the

²,U = ( )² operand, or your message will be sent to all TSO users and they will get aggravated with this if it happens repeatedly.

Cancel the TSO session with the MVS ²CANCEL U=userid² command, or the JES2 $C command.

There may also be times when you cannot cancel a TSO user with the $C command, so you will have to force the address space down with the

²FORCE² command. This may be necessary for a TSO user to get out of a ²hung² condition, and log back on again.

Release, Cancel, or Modify TSO held output with the JES2 $O or $TO command.

The SDSF DA, ST, O and H panels can also be used to control TSO users or their queued output. (Any JES2 command can be issued through these panels.)

28.5.3 Controlling Batch Jobs

Batch jobs are submitted by TSO users, or by other programs such as batch job scheduling systems like OPC/A. They are queued on the ²Job Queue² by JES2 and selected by batch initiators according to your installation¢s job scheduling criteria. (WLM or JES can manage the initiators.)

Jobs can also be started by the operator from the console with the MVS START command, but then they behave very much like ²started tasks². (See the next topic below.)

Jobs can be canceled by the operator with either an MVS Cancel command, or the JES2 $C command.

The SDSF DA, ST, O and H panels can also be used to control batch jobs or their queued output.

28.5.4 Controlling Started Tasks

Started Tasks (or ²STCs²) are like batch jobs, but started by the MVS ²START² command (abbreviated ²S²) from an operator console instead of submitted by a TSO user or another job. You can override many parameters on the START command, including the name that shows up on a display.

Other commands used to control started tasks are described in OS/390 MVS

System Commands, GC28-1781.

Display status about the started task with the MVS ²DISPLAY² command or JES2 $D command.

Modify the started task with the MVS ²MODIFY² command.

Stop the started task with the MVS ²STOP² command.

Cancel the started task with the MVS ²CANCEL² or JES2 $C command.

If they fail to stop or cannot be canceled, they can be ²Forced² with the MVS ²FORCE² command.

Chapter 28. Orientation to OS/390 Console Operation 451

Page 475
Image 475
IBM OS/390 manual Controlling Time Sharing Users, Controlling Batch Jobs, Controlling Started Tasks

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.