DOS/VS COBOL Option

COBOL for OS/390 and VM Equivalent (If Any)

 

 

B U F = n n n

BUFSIZE(nnn)

 

 

CATALR/NOCATALR

NAME/NONAME

 

 

CLIST/NOCLIST

OFFSET/NOOFFSET

 

 

COUNT/NOCOUNT

None

 

 

FLAGE/FLAGW

FLAG(E)/FLAG(W)

 

 

FLOW/NOFLOW

None

 

 

LANGLVL(1/2)

None. COBOL for OS/390 and VM supports only the

 

COBOL 85 Standard and COBOL 74 Standard (if

 

using CMPR2 option) as implemented by VS COBOL

 

II release 2.

 

 

L V L = A B C D N O L V L

None. COBOL ANSI 74 FIPS is not supported by

 

COBOL for OS/390 and VM.

 

 

MIGR/NOMIGR

None. Not required by COBOL for OS/390 and VM.

 

 

P M A P = h

None. Obsolete option.

 

 

SPACEn

SPACE(n)

 

 

STATE/NOSTATE

TEST

 

 

SUPMAP/NOSUPMAP

COMPILE/NOCOMPILE

 

 

STXIT/NOSTXIT

None. Function not required.

 

 

SXREF/NOSXREF

XREF(SHORT)

 

 

SYMDMP/NOSYMDMP

ABEND dumps and dynamic dumps are available

 

through Language Environment services. Symbolic

 

dumps are available using the TEST compiler option.

 

 

SYNTAX/CSYNTAX/NOSYNTAX

COMPILE/NOCOMPILE

 

 

VERB/NOVERB

LIST/NOLIST

 

 

VERBREF/NOVERBREF

VBREF/NOVBREF

 

 

VERBSUM/NOVERBSUM

VBREF/NOVBREF

 

 

DECK/NODECK(LISTER)

None. The LISTER feature is not supported.

 

 

COPYPCH/NOCOPYPCH

None. The LISTER feature is not supported.

 

 

LSTONLY/NOLSTONLY

None. The LISTER feature is not supported.

 

 

PROC=12col

None. The LISTER feature is not supported.

 

 

Figure 19. Compiler Options Comparison DOS/VS COBOL and COBOL for OS/390 and

VM

12.8.1.2 Compiler Option Considerations for VS COBOL II

The VS COBOL II and COBOL for OS/390 and VM compile-time environments are very similar. If you use the same compiler options that are specified in your current VS COBOL II applications, some internal changes may take effect, but basically the behavior is unchanged.

If you recompile your VS COBOL II applications with COBOL for OS/390 and VM and change compiler option settings, you should understand the possible effects on your applications. For information on compiler options with COBOL for OS/390 and VM see the COBOL for OS/390 and VM Programming Guide.

Figure 20 on page 262 lists the COBOL for OS/390 and VM compiler options that have special relevance to programs converted from VS COBOL II.

Chapter 12. COBOL 261

Page 285
Image 285
IBM OS/390 manual Compiler Option Considerations for VS Cobol

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.