28.2.3.2 Using SDSF for System Operation

Below is the Primary Option Menu for SDSF showing you the basic panels you can use as a full-screen system operator.

￿

 

 

 

 

￿

HQX1800

-----------------

SDSF PRIMARY OPTION MENU

 

 

 

-------------------------

 

 

COMMAND INPUT ===>

SCROLL ===> CSR

 

LOG

-

Display the system log

 

 

 

DA

-

Display active users in the sysplex

 

 

I- Display jobs in the JES2 input queue

O - Display jobs in the JES2 output queue

H - Display jobs in the JES2 held output queue

 

ST

- Display status of jobs in the JES2 queues

 

 

PR

- Display JES2 printers on this system

 

 

PUN

- Display JES2 punches on this system

 

 

RDR

- Display JES2 readers on this system

 

 

INIT

- Display JES2 initiators on this system

 

 

MAS

- Display JES2 members in the MAS

 

 

LINE

- Display JES2 lines on this system

 

 

NODE

- Display JES2 nodes on this system

 

 

SO

- Display JES2 spool offload for this system

 

 

ULOG

- Display user session log

 

￿

END

- Exit SDSF

￿

 

 

Displaying the system log is handy because you can scroll back and forth and search for text strings. There are several panels to display jobs and output, which can show you the backlog of work for initiators, printers, and transmitters. There are also panels for JES2 devices such as printers, punches, readers, lines, nodes, members, spool offload devices, and other JES2 resources.

You can issue MVS and JES2 operator commands from the command line, and many panels support simple action characters and over-typeable fields for JES2 devices and parameters.

Each of these panels provide simple action commands (modeled after the JES2 command verbs) to control the work such as: B-Backspace, C-Cancel, D-Display, E-Restart, F-Forward, I-Interrupt, N-Repeat, P-Stop, S-Start, and Z-Halt.

SDSF has online HELP panels, a Tutorial, and can link to online (softcopy) books on BookManager READ/MVS for Messages.

28.2.4 Understanding Message Formats and Replies

See OS/390 MVS System Messages, Volumes 1 to 5, GC28-1784 thru GC28-1788 for detail message descriptions. The front of each book also describes the general format of MVS messages.

To reply to a WTOR (Write To Operator with Reply), you can either enter

Rnn,¢reply¢ or use the short form and type the one or two-digit reply ID followed by the reply. For example, to reply ²U² to a WTOR with the ID=07, you can either enter ²R 07,¢ U¢², or you can enter ²7u².

The short form is not available when JES2 is not up unless you specify

CON=NOJES3 in the IEASYSnn member of parmlib.

446VSE to OS/390 Migration Workbook

Page 470
Image 470
IBM OS/390 manual Understanding Message Formats and Replies, Using Sdsf for System Operation

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.