13.2.3 Interrupt Handling Routines

Interrupt routines take care of the interval timer, abnormal conditions, and operator communication interrupts. Abnormal condition interrupts will not be addressed in this publication.

13.2.3.1 Interval Timer Interrupts

Basically, the two ways of utilizing the interval timer in your programs are routine handling and wait handling.

Routine Handling

This method allows a branch to your own routine when the interval timer interrupt occurs. The following illustrates the VSE macros and corresponding MVS macro needed to perform this operation:

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿

￿STXIT

￿IT, rou￿ine address ,

save area

￿

￿

￿

￿

(0)

(1)

￿

￿ VSE ￿SETIME

￿seconds

 

￿

￿

￿

￿

(1)

 

￿

￿

￿EXIT

￿IT

 

 

￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿

￿

￿REAL

, ￿imer comple￿ion exi￿ address

￿

￿

￿

￿TASK

(2-12)

￿

￿

￿

￿WAIT

 

￿

￿

￿

￿

,DINTVL = address

￿

￿

￿

￿

(2-12)

￿

￿ MVS ￿STIMER

￿

,BINTVL = address

￿

￿

￿

￿

(2-12)

￿

￿

￿

￿

,TUNINTVL=address

￿

￿

￿

￿

(2-12)

￿

￿

￿

￿

,TOD = address

￿

￿

￿

￿

(2-12)

￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

The VSE macro instructions allow you to execute a routine when a timer interrupt occurs and then to return to the program that was being executed prior to the interruption. The STXIT macro provides the address of the routine to be executed. A register save area must also be specified in the STXIT macro. The saving and restoring of the registers are performed automatically by the supervisor. The SETIME macro sets the interval timer. The EXIT macro returns from the specified routine (STXIT macro) to the point in the interrupted program where the interruption occurred.

The single MVS macro (STIMER) also allows you to execute a routine when the timer interrupt occurs. The REAL parameter indicates that time is to be decreased continually, while TASK means that the timer is stopped or adjusted only when the task is active. WAIT means that the job step is to be placed in a wait state until the interval expires. The timer completion exit address parameter is the same as the routine address used in the VSE STXIT macro.

The DINTVL parameter indicates that the time interval requested is in decimal units and is stored in the address specified. The MVS timer routine must follow the standard conventions for handling registers.

You must save the registers on initiation and restore them at routine termination.

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

Page 311
Image 311
IBM OS/390 manual Interrupt Handling Routines, Interval Timer Interrupts

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.