IBM OS/390 18.4.3 TSO/E Environment, Rexx Exec Sample for the OS/2, TSO and CMS Environments

Models: OS/390

1 673
Download 673 pages 53.75 Kb
Page 395
Image 395

18.4.3 TSO/E Environment

TSO/E provides among others the following host command environments:

TSO allows you to invoke TSO/E commands and services.

CONSOLE allows you to invoke MVS system and subsystem commands during an extended MCS console session.

ISPEXEC and ISAREDIT allows you to invoke ISPF commands and services, and ISPF edit macros.

CPICOMM, LU62, and APPCMVS allows you to use the SAA common programming interface (CPI) Communications calls.

MVS gives you a host environment which is available in any MVS address space.

18.4.4 REXX Exec Sample for the OS/2, TSO and CMS Environments

/* REXX

*/

 

 

say ¢ REXX Exec is executed in the¢

address() ¢ environment¢

 

if address() = ¢ CMD¢ then

/* OS/2 environment

*/

do

 

 

 

infile = ¢ my.data¢

 

 

do until lines(infile) = 0

 

 

say linein(infile)

 

 

end

 

 

 

end

 

 

 

else

 

 

 

do

 

 

 

if address() = ¢ TSO¢ address() = ¢ CMS¢ then

 

do

 

 

 

io_op = ²EXECIO * DISKR²

/* common used EXECIO part

*/

if address() = ¢ TSO¢ then

/* TSO environment

*/

do

 

 

 

e1 = ²ALLOC FI(DATAIN) DA(my.data) SHR²

 

e2 = io_op ²DATAIN (FINIS²

 

 

end

 

 

 

if address() = ¢ CMS¢ then

/* CMS environment

*/

do

 

 

 

e1 = io_op ²my data A²

 

 

e2 = ²FINIS my data A²

 

 

end

 

 

 

e1;e2

 

/* execute I/O

*/

do i = 1 to queued()

 

 

parse pull line say line

end end

end

18.5 Migration Issues

²The REXX language is independent of both system and hardware. REXX procedures, though, must be able to interact with their environment. Such interactions necessarily have system dependent attributes. However, these system dependencies are clearly bounded and the rest of the language has no such dependencies.² (M. F. Cowlishaw: The REXX Language)

REXX is compatible with the VM, VSE, MVS, AIX, OS/400, and OS/2 operating systems, among others, and allows system independent coding.

Chapter 18. Procedure Language REXX 371

Page 395
Image 395
IBM OS/390 manual 18.4.3 TSO/E Environment, Rexx Exec Sample for the OS/2, TSO and CMS Environments, Migration Issues

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.