The preceding combination of VSE macro instructions allows you to execute a routine when an operator attention interrupt occurs and to return to the program that was being executed before the interruption.

MVS has no equivalent function. It is possible, however, to simulate this function by using the WTOR macro. This MVS macro writes a message requiring a reply on the operator console and provides the information required by the control program to relay the reply to the issuing program. You must wait for the reply.

This macro could also be executed without a following WAIT macro and coding inserted in the program loop to test the completion of the event. Upon completion, it is possible to execute the communication routine and later resume normal processing. Another solution is to include the communication routine as a subtask with the WTOR macro instruction followed by a WAIT instruction.

Alternately, you can use the Job Control PARM Field (see Register 1 in ªRegister Conventionsº on page 269) to pass information to the program. You may realize throughput improvements because there is no wait for operators reply.

Under VSE, you can initiate communication with the background partition using the interrupt key on the console. You can use the MSG (message) command to initiate communication with a foreground partition.

Under MVS, the operator interfaces with job management to provide operator-to-system communication via commands entered on the operator console. This allows the operator to respond to requests from processing programs. However, operator-to-processing program communication must be initiated internally by the processing program. There is no support of the external interrupt key for operator-to-program communication; it switches from the primary to the alternate console.

13.2.4Virtual Storage Macros

13.2.4.1GETVIS and FREEVIS Macros

The MVS GETMAIN, FREEMAIN and STORAGE macros have functions similar to the VSE GETVIS and FREEVIS macros. Example:

(VSE)

GETVIS LENGTH=1000,ADDRESS=PTR1

 

 

LTR

R15,R15

GETVIS OK?

 

BNZ

ERROR1

NO, CANCEL

 

. . . .

 

 

FREEVIS LENGTH=1000,ADDRESS=PTR1

 

. . . .

 

PTR1

DS

A

 

(MVS)

GETMAIN RC,LV=1000

 

 

 

 

LTR

R15,R15

GETVIS OK?

 

BNZ

ERROR1

NO, ABEND

 

ST

R1,PTR1

save storage address

 

. . . .

 

 

L

R1,PTR1

pick up storage address

 

FREEMAIN RC,LV=1000,ADDRESS=(1)

 

. . . .

 

PTR1

DS

A

 

Chapter 13. A s s e m b l e r 289

Page 313
Image 313
IBM OS/390 manual Virtual Storage Macros, Getvis and Freevis Macros

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.