contained in register 13. Therefore, you must specify a save area to receive the registers.

PROGA START

PROGB CSECT

PROGC CSECT

(MVS)

(MVS)

(MVS)

.

 

.

 

.

 

.

 

.

 

.

 

STM 14,12,12(13)

STM 14,12,12(13)

STM 14,12,12(13)

ST

13,SAVEA+4

ST

13,SAVEB+4

ST

13,SAVEC+4

LA

11,SAVEA

LA

11,SAVEB

LA

11,SAVEC

ST

11,8(13)

ST

11,8(13)

ST

11,8(13)

LR

13,11

LR

13,11

LR

13,11

.

 

.

 

.

 

.

 

.

 

.

 

Application

Application

Application

Program

Program

Program

Logic

 

Logic

 

Logic

 

.

 

.

 

.

 

.

 

.

 

.

 

CALL PROGB

CALL PROGC

 

 

L

13,4(,13)

L

13,4(,13)

L

13,4(,13)

Return (MVS)

Return (PROGA)

Return (PROGB)

SAVEA DC

18F′ 0 ′

SAVEB DC

18F′ 0 ′

SAVEC DC

18F′ 0 ′

.

 

.

 

.

 

END

END

 

END

 

 

 

 

 

 

Figure 28.

MVS Subroutine Linkage

 

 

 

If a standard save area of 18 fullwords is reserved in the calling program, the save area contains the following information at completion of the called programs initialization logic.

Word 1

Used by LE-compliant languages

Word 2

Address of the callers save area (the backward chain).

Word 3

Address of the save area of the called program (the forward chain).

Word 4

Register 14.

Return address within the calling module.

Word 5

Register 15.

Entry point address of called module.

Words 6-18

Registers 0 through 12, respectively, of the calling program.

Consider three programs using the concept of forward and backward chains with standard linkage conventions. Under VSE, these could be three application programs, while under MVS, the highest-level program that must be considered is the MVS control program because it calls the MVS highest-level application program.

Linkage Macros

CALL, SAVE, and RETURN macros are available under VSE and MVS. This set of macros performs the general housekeeping required to maintain subroutine conventions within the CSECTs of a simple program structure. In general, these MVS macros provide additional functions not available in VSE. You can use the VSE versions of these macros under MVS without any modification.

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

Page 295
Image 295
IBM OS/390 manual Proga Start Progb Csect Progc Csect MVS, 11,SAVEA 11,SAVEB 11,SAVEC, Call Progb Call Progc, Savea DC

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.