∙

∙

∙

NetView Consoles

TSCF Consoles

Programmed Operator Subsystems

This chapter will only deal with MCS and SDSF consoles.

28.2.1 Controlling Consoles

There is more to operating an OS/390 system than just entering commands and reading the messages. You should also be familiar with various console configuration options. See Chapters 2 and 3 in MVS Commands for a description of these console operations:

∙

∙

∙

∙

∙

∙

Defining and Changing Console Characteristics

Potential Effects of Altering Console Attributes

Changing Console Characteristics

Controlling System Messages and Commands

Defining Program Function Keys (PFKs)

Hardcopy Processing

28.2.2 Managing Display Consoles

For MCS consoles (those attached to non-SNA control units), you will need to understand how to use some of the basic CONTROL (alias K) command parameters when you first start operating an OS/390 system. Otherwise, you can easily get your console ²locked up² by non-deletable messages or not scrollable.

Here are some examples of the basic ²K² commands:

K - clear the screen.

K S - show the current settings so they can be over-typed.

K E,4 - delete the message on line 4.

KE,4,10 - delete the non-action messages on lines 4-10. K E,D - delete a status display from a display area.

K A,NONE - get rid of display areas on this console.

Use the ²D C,K² command to display the CONTROL command functions and ²D C,A² to display the status of active consoles.

See Chapters 2 and 3 and Section 4.7 in MVS Commands for details. (Most of these do not apply to Extended MCS consoles.)

28.2.2.1 Console Modes

There are several ²modes² by which MCS consoles can operate and by which messages are cleared from the screen. Type ²K S² to see the current setting of the console you are sitting at, and then you can over-type what parameter values you want to change. Here is an example of ²Roll² mode which is recommended for unattended console operation:

K S,DEL=R,SEG=28,CON=N,RNUM=14,RTME=001,MFORM=(T,J)

If there is always an operator present, you can use ²D E L = R D ² which rolls the deletable messages, but not those messages requiring action.

444VSE to OS/390 Migration Workbook

Page 467 Page 469
Page 468
Image 468
IBM OS/390 Controlling Consoles, Managing Display Consoles, Console Modes, DEL=R,SEG=28,CON=N,RNUM=14,RTME=001,MFORM=T,J
Page 467 Page 469

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.
Top Page Image Contents