VS COBOL II Option

Comments

 

 

FDUMP/NOFDUMP

COBOL for OS/390 and VM does not provide the FDUMP compiler

 

option. For existing applications, FDUMP is mapped to the COBOL

 

for OS/390 and VM compiler option TEST(SYM). This provides

 

equivalent function and more.

 

Language Environment generates a better formatted dump than VS

 

COBOL II, regardless of the FDUMP option. But the presence of

 

FDUMP enables Language Environment to include the symbolic

 

dump of information about data items in the formatted dump.

 

For information on how to obtain the Language Environment

 

formatted dump at abnormal termination, see Language Environment

 

Debugging Guide and Run-Time Messages.

 

If FDUMP is used, COBOL for OS/390 and VM issues the warning

 

message:

 

IGYOS4045-W The ²FDUMP² option is not supported.

 

This specification was interpreted as ²TEST(NONE,SYM)² .

 

If NOFDUMP is used, COBOL for OS/390 and VM issues the

 

message:

 

IGYOS4003-E Invalid option ²NOFDUMP² was found and

 

discarded.

 

 

FLAGSAA

COBOL for OS/390 and VM does not support the FLAGSAA option. If

 

FLAGSAA is specified, COBOL for OS/390 and VM issues the

 

message:

 

IGYOS4008-W The ²FLAGSAA² compiler option was specified, but

 

is not supported. The option was discarded.

 

 

RES/NORES

COBOL for OS/390 and VM does not provide the RES/NORES

 

compiler option. If RES is used, COBOL for OS/390 and VM issues

 

the message:

 

IGYOS4046-I The ²RESIDENT² option specification is no longer

 

required. The resident runtime library support is always used.

 

If NORES is used, COBOL for OS/390 and VM issues the message:

 

IGYOS4047-W The ²NORESIDENT² option is not supported.

 

The resident runtime library support is always used.

 

 

Figure 21. Compiler Options Comparison VS COBOL II and COBOL for OS/390 and VM

12.9 Reserved Words

This section discusses some of the reserved word considerations when converting from the various VSE COBOL compilers to COBOL for OS/390 and VM.

COBOL for OS/390 and VM has many reserved words that are not reserved with DOS/VS COBOL. There are two additional reserved words that are not reserved with VS COBOL II. There are additional reserved words in COBOL for OS/390 and VM for object-oriented COBOL that are not reserved in any VSE COBOL compiler.

12.9.1 Reserved Word Considerations for DOS/VS COBOL

COBOL for OS/390 and VM has reserved words that are not reserved in DOS/VS COBOL. They are listed in Figure 22 on page 264. If you used any of these words in your DOS/VS COBOL programs, you will need to replace them.

Chapter 12. COBOL 263

Page 287
Image 287
IBM OS/390 manual Reserved Words, Reserved Word Considerations for DOS/VS Cobol, Fdump/Nofdump, Flagsaa, Res/Nores

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.