FEATURES OF VS COBOL II - IBM Mainframe

The following features are available with VS COBOL II:

  • MVS/XA and MVS/ESA support - The compiler and the object programs it produces can be run in either 24- or 31-bit addressing mode.
  • VM/XA and VM/ESA support - The compiler and the object programs it produces can be run in either 24- or 31-bit addressing mode.
  • VSE/ESA support - The compiler and the object programs it produces can be run in 24-bit addressing mode, or under VSE/ESA Version 1 Release 3 or later, in either 24- or 31-bit addressing mode.
  • High Subset COBOL 85 Standard support - VS COBOL II incorporates all of the major and minor language enhancements of the required modules of the high subset of COBOL 85 Standard when run under MVS.
  • Systems Application Architecture (SAA) support - The FLAGSAA option identifies elements that are not portable under SAA COBOL Level 1.
  • VSAM (Virtual Storage Access Method) support - VSAM provides features like fast storage and retrieval of records, password protection, centralized and simplified data and space management, advanced error recovery facilities, system and user catalogs, etc. Using VSAM, COBOL supports sequential files (through VSAM ESDS capabilities), indexed files with alternate indexes (through VSAM KSDS capabilities) and relative files (through VSAM RRDS capabilities). Expanded VSAM file status codes enhance your ability to identify and handle exception conditions using the FILE STATUS clause.
  • Program-related information and listings - You can request and control a variety of listing and program-related information:
  • Print or suppress the listing of your source program by using the SOURCE option.
  • Produce a listing of the assembler-language expansion of your source code by using the LIST option.
  • Control the appearance and content of your source listing by using the TITLE statement, LANGUAGE, LINECOUNT, SEQUENCE, SPACE, OFFSET, and NUMBER options.
  • Obtain cross-reference information for statements (verbs), data-names, procedure-names, and program-names by using the VBREF and XREF options.
  • Obtain Data Division map listing, nested program structure map, global tables and literal pools by using the MAP option.
  • Control the error level for which diagnostic messages are to appear in your listing by using the FLAG option.
  • Flag specific elements in your source listing. Use FLAGSTD to identify the level or subset of COBOL 85 Standard that is being regarded as conforming. Use FLAGSAA to identify elements that are not portable across environments for SAA COBOL Level 1. Use FLAGMIG to identify elements that will have to be changed when migrating from VS COBOL II Release 2 to 4.
  • Obtain a system dump for diagnostic use by using the DUMP option.
  • Optimized object code - Produces object programs that generally use less processing time.
  • COBOL library management facility - Allows installations running with multiple COBOL regions/partitions to save considerable main storage by sharing some or all of the COBOL library.
  • Syntax-checking compilation - Saves machine time while debugging source syntax errors. When the NOCOMPILE compiler option without any sub-parameter is used, the source program is scanned for syntax errors and diagnostic messages are produced, but no object code is produced. When you use the NOCOMPILE option with W, E, or S, a full compilation is produced with object code when no diagnostic message is found with higher severity than that requested. When you use the COMPILE option, a full compilation is produced even in the presence of serious errors. All diagnostics and object code will be produced.
  • Separately located installation defaults - Allows an installation to define the default compiler options, rather than have the definition in the compiler code.
  • Installation control of defaults - Prevents specific installation defaults from being overridden. (This allows enforcement of certain customer standards.)
  • Reentrant compiler - Allows the VS COBOL II compiler to reside in the common virtual area so that it can be shared by multiple users.
  • Reentrant object code option - Allows the object code for a VS COBOL II program compiled with the RENT compiler option to reside in the common virtual area so that one copy of it may be shared among all callers.
  • SSRANCE - Checks subscript and index values to see that the composite of the subscripts does not address an area beyond the region of the table. Checks to see that a variable-length item is within its defined maximum length. It also checks reference modification values to see that they do not address an area outside the region of the subject data item.
  • RTEREUS - In a non-CICS environment, RTEREUS is a run-time option that implicitly initializes the run-time environment for reuse when the first COBOL program is invoked.
  • LIBKEEP - In a non-CICS environment, LIBKEEP is a run-time option that improves performance when COBOL main programs are invoked repeatedly by non-COBOL programs.
  • User exits - The EXIT compiler option provides you with a way to specify a program that will supply your own source, copy-library, or receive the listing. The BLDL user exit is provided so that you can maintain directory information look-aside tables in a non-CICS application under MVS.
  • Installation of global run-time default options - Allows an installation to define global run­time default options.
  • Reserved word control - Allows specification (with the WORD option) of an alternative reserved word table to be used by the compiler. A user-defined reserved word table can be used as an alternative to the IBM-supplied default reserved word table. A CICS-specific reserved word table is also provided as an alternative table for flagging syntax not supported under C1CS.
  • Tuning tables - Allow some space management at run time. Defaults are supplied for space management tuning factors, but these defaults can be overridden for an installation or for individual applications.
  • Support for mixed residency modules - In a non-CICS environment, the MIXRES run-time option allows COBOL programs compiled with either RES or NORES, to be .included in the same application. All combinations of OS/VS COBOL and VS COBOL II, RES and NORES modules are supported.
  • Static to dynamic call conversions - In a non-CICS environment, static calls from NORES or RES NODYNAM programs can be converted to dynamic calls without recompilation by using the IGZBRDGE macro.
  • Hexadecimal notation for nonnumeric literals - Allows the use of hexadecimal notation in nonnumeric literals.
  • Batch compiling - A batch compiling technique and the use of the NAME compiler option allows you to create one or more load modules with a single invocation of the compiler.
  • Tools for migration from Release 2 - The CMPR2 and FLAGMIG options help you to migrate your VS COBOL II Release applications to Release 4.
  • Structured programming support - Constructs are provided that enables you to develop and maintain a structured application program. Such things as nested programs, WITH TEST BEFORE and AFTER phrases, and explicit scope terminators, aid in the development of structured programs.
  • Nonnumeric literal with double-byte characters - Allows the use of both EBCDIC and double-byte characters in nonnumeric literals.
  • National Language Support - The LANGUAGE compiler option allows you to select a national language for compiler listing headings and compiler messages. The national language for library messages, FDUMP output messages, and ABEND output messages is selectable when the library is installed at your site.
  • Mixed-case headings and messages - The LANGUAGE compiler option allows you to select between mixed-case and uppercase compiler listing headings and compiler messages.
  • Numeric sign processing compiler option (NUMPROC) - Allows you to select from three different kinds of sign processing, including one that provides sign processing similar to that used by OS/VS COBOL.
  • Numeric truncation compiler option (TRUNC) - Allows you to select from three different types of numeric truncation for receiving fields.
  • Relaxed compiler limits - Many limits imposed by OS/VS COBOL are relaxed in VS COBOL II. These limits are for VS COBOL II programs executing under MVS/XA and MVS/ESA. Other operating systems may impose further limits.

Compiler Limits Relaxed by VS COBOL IIIBM Extensions

Compiler Limits Relaxed by VS COBOL IIIBM Extensions

IBM Extensions

  • ADDRESS special register - Allows the address of a record area to be passed and received, using a CALL statement.
  • LENGTH special register - Provides the number of single-byte character positions used by an identifier.
  • TITLE page heading specification - Displays the literal in the title portion of the page heading of succeeding pages. It replaces the title portion provided by the compiler or a prior TITLE statement.
  • Double-Byte Character Set (DBCS) - Supports USAGE option (DISPLAY-1) and PICTURE character (G) that defines a 16-bit data item. Support includes DBCS user names and literals, special registers for shift-out and shift-in characters, and comparison between DBCS items, based on the binary collating sequence. You can also get a sorted cross-reference list of DBCS names by using a DBCS ordering product. In addition, nonnumeric literals can contain a mix of DBCS and EBCDIC characters, and can also be used as titles in the TITLE statement. VS COBOL II also provides two service routines (IGZCA2D, and IGZCD2A) for converting alphanumeric and DBCS data items. DBCS is used primarily in conjunction with applications that support large character sets; for example, the Kanji character set used in Japan.
  • Hexadecimal notation for nonnumeric literals - Allows the use of hexadecimal notation in nonnumeric literals.
  • POINTER data item - Supports a USAGE option (POINTER), which defines a new data type that can be used to hold addresses.
  • Complex OCCURS DEPENDING ON - Adds support to OCCURS DEPENDING ON (ODO) for the following IBM extensions:
    1. In all formats with the OCCURS DEPENDING ON clause, any subordinate entry may be variable in length—that is, can contain an OCCURS DEPENDING ON clause.
    2. An entry containing an OCCURS DEPENDING ON clause need not be the last in a record or group. It can be followed by non-subordinate entries, any of which can contain an OCCURS DEFENDING ON clause.
  • Floating-point data - Includes support for COMP-1 (single-precision internal floating point). COMP-2 (double-precision internal floating point), and DISPLAY (external floating point) data types and fractional exponentiation.
  • Parentheses in abbreviated conditions - Provides support for the use of parentheses in abbreviated expressions to specify an intended order of evaluation and to clarify the expression for readability.
  • APPLY WRITE-ONLY - Allows the user to store data more efficiently on external media.
  • TALLY special register - An internally defined data-name that can be referenced or modified by the user. It is commonly used in conjunction with such verbs as INSPECT, STRING, and UNSTRING.
  • SORT special registers - Compiler-defined data-names that may be referenced or modified by the user and will be used in the SORT interface. The six SORT special registers are SORT-CONTROL, SORT-CORE-SIZE, SORT-FILE-SIZE, SORT-MESSAGE, SORT-MODE-SIZE, and SORT-RETURN.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Mainframe Topics