ABPERC In LE/VSE you can specify the abend code to the option ABPERC in one of three formats. These formats are:

∙

∙

∙

Shh

Ihh

Udddd

In OS/390 Language Environment you can only specify Shh or Udddd. Ihh is not allowed, and if you specify it you will receive an error message similar to:

CEE3616I The string ′ I12′ was not a valid suboption of the run-time option ABPERC.

You should review your use of the ABPERC option carefully before migrating to OS/390 Language Environment as the meaning of the OS/390 system abend codes specified by Shhh are different to the VSE/ESA cancel codes specified by Shh.

NATLANG The default setting for the NATLANG option in LE/VSE is NATLANG(UEN). The default setting for the NATLANG option in OS/390 Language Environment is NATLANG(ENU). UEN is upper-case U.S. English. ENU is mixed-case U.S. English.

The NATLANG option specifies the initial language to be used for the run-time environment, including error messages, month names and day-of-the-week names. If you specify an unknown national language, the error messages and so on, are displayed in the default national language.

MSGFILE The MSGFILE option has different suboptions and default values in OS/390 Language Environment to its LE/VSE counterpart. You should read the description of MSGFILE in the OS/390 Language Environment Programming Reference.

In LE/VSE, MSGFILE has only one suboption, filename. The default is SYSLST. If you specify or default to SYSLST for MSGFILE, all output from CEEMSG and CEEMOUT callable services, and RPTOPTS and RPTSTG options is written to

SYSLST.

In OS/390 Language Environment there are four suboptions, ddname, recfm, lrecl, blksize. The defaults for these suboptions are (SYSOUT,FBA,121,0). However, if you continue to use SYSLST this is accepted by OS/390 Language Environment and the output is written to SYSOUT. If SYSOUT is specified in your OS/390 job control //SYSOUT DD SYSOUT=* then the output from CEEMSG, CEEMOUT, RPTOPTS and RPTSTG will appear in your listing.

TERMTHDACT TERMTHDACT in LE/VSE has only four suboptions, TRACE, QUIET, MSG and DUMP. TERMTHDACT in OS/390 Language Environment also has the UADUMP suboption. If specified, on an abnormal termination, the UADUMP suboption generates a system dump of the user address space. TERMTHDACT in OS/390 Language Environment is described in the OS/390 Language Environment Programming Reference.

Note: The UADUMP option is available in LE/VSE releases later than 1.4, and also in LE/VSE 1.4 via APAR PQ08538. Its usage is the same as for OS/390 Language Environment.

360VSE to OS/390 Migration Workbook

Page 383 Page 385
Page 384
Image 384
IBM OS/390 manual Shh Ihh Udddd, Syslst
Page 383 Page 385

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