$D MMn,′Please restart my printer′

Send a message to the operator on member n

See JES2 Commands for details. The ªRemote Job Entryº section in Chapter 2 has good guidance information for RJE operations, and Chapter 5 has detailed command syntax descriptions.

Remotes Without Consoles

If you don′t have a console on your remote workstation, you can still submit commands and JES2 control cards through the logical (or physical) card reader.

JES2 Control Cards

The following JES2 control cards can be placed within a jobstream to communicate with the host system or central operator. (They can also be used by anyone submitting a job, subject to installation restrictions.)

/*$command Enter a JES2 operator command (for example, /*$SPRT1)

/*MESSAGE Send the message to the operator console

/*NOTIFY Send notification messages to specified users

/*SETUP Hold the job for specified volumes to be mounted

Other JES2 control cards such as /*JOBPARM, /*ROUTE, and /*PRIORITY can also be used to control specific jobs. See OS/390 MVS JCL Reference, GC28-1757 for details.

Command Authority for Remote Operators

In general, a remote operator can only display and control jobs which are submitted or ªownedº by that remote system, and devices that are attached to that remote system.

The table titled ªRemote Entry Restrictionsº in Chapter 2 ofJES2 Commands describes the RJE and NJE authority required for all JES2 commands.

28.6.1.3 Using SDSF Panels for RJE

The Line panel in SDSF allow you to monitor and manage RJE lines and devices. The Printer, Punch, and Reader panels also show remote (RJE) devices and can be configured for remote operators.

28.6.2 NJE Operations

Host operators on each node can display and manage NJE lines, sessions, connections and paths to other nodes. They can also send commands to display the configuration on other nodes. Here are some JES2 commands to support NJE:

$S LGNn

Start the JES2/VTAM ACB (for SNA remotes)

$S LINE(nn)

Start the line

$S N,NODE=node_name

Start the NJE session

$D NODE(node_name)

Display the status of a node

Chapter 28. Orientation to OS/390 Console Operation 453

Page 476 Page 478
Page 477
Image 477
IBM OS/390 NJE Operations, Using Sdsf Panels for RJE, Remotes Without Consoles, Command Authority for Remote Operators
Page 476 Page 478

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