Enterprise COBOL for z/OS

Enhancements to XML parsing
In V4.2, XML parsing using the z/OS XML System Services parser has been enhanced:

• You can now parse XML documents with validation against an XML schema, using the VALIDATING phrase of the XML PARSE statement.

• Performance is improved for nonvalidating parsing.

• Character processing is enhanced for any XML document that contains a reference to a character that is not included in the single-byte EBCDIC code page of the document.

Compiler message severity customization
When Enterprise COBOL compiles your source program, it checks for COBOL language problems, and issues diagnostic messages. These messages are collated in the compiler listing (subject to the FLAG option). Each message in the listing provides information about the nature of the diagnostic and its severity. Message severity falls into one of five categories: Informational, Warning, Error, Severe, or Unrecoverable. The final return code at the end of the compilation is generally the highest return code that occurred for any message during compilation.

In V4.2, you can customize compiler diagnostic message severity, which can affect the final compilation return code. The new MSGEXIT suboption of the EXIT compiler option lets you specify a module that is called for each compiler diagnostic message and each FIPS (FLAGSTD) message. Using the MSGEXIT module, you can change the severity of messages, suppress messages, and convert FIPS messages into diagnostic messages.

Compiler option BLOCK0 to exploit system-determined block size for QSAM files
In V4.2, a new compiler option, BLOCK0, lets programs take advantage of system-determined block size for QSAM output files. When a program is compiled using the BLOCK0 compiler option, an implicit BLOCK ONTAINS 0 clause is activated for all eligible QSAM files in the program, which can result in enhanced processing speed and minimized storage requirements for output files.

If BLOCK CONTAINS 0 is specified for a QSAM file, then the block size is determined at run time from the DD parameters or the data set label of the file. For output data sets, the DCB used by Language Environment® will have a zero block size value. When the DCB has a zero block size value, the operating system might select a system-determined block size (SDB).

COBOL user-defined words can now include the underscore character
In V4.2, COBOL user-defined words such as data names and program names can now include underscore characters (_). Underscores are also supported in the literal form of program names.

Compiler listings display CICS options in effect
In V4.2, when COBOL applications with embedded CICS statements are compiled using the integrated CICS translator, compiler listings will show the CICS options that are in effect. This facility provides the same benefit to CICS users as was previously made available to DB2® users.

Java interoperability: support for Java 5 and Java 6
In V4.2, Enterprise COBOL applications using object-oriented syntax for Java interoperability can now run with Java 5 or Java 6. Java SDK 1.4.2 continues to be supported.

Improved application development
Enterprise COBOL for z/OS provides a set of intrinsic functions including string handling, financial capabilities, statistical functions, and mathematical formulas. You can also use the COBOL CALL statement to take advantage of Language Environment® services for everything from storage management to condition handling. The condition-handling support enables you to write programs in which error handling is done in a separate routine that is loaded only when needed. You do not have to write the error-handling routines in assembler; with Language Environment® you can write them in COBOL. Enterprise COBOL for z/OS offers support for recursive calls in COBOL, structured programming, improved interoperability with other languages, and dynamic link library support. The Enterprise COBOL for z/OS runtime library, Language Environment®, also supports PL/I, C/C++, and Fortran programs.

Ease into migration
Enterprise COBOL for z/OS gives you a migration path from OS/VS COBOL, VS COBOL II, IBM COBOL for MVS & VM, and IBM COBOL for OS/390® & VM. Most of your current programs will continue to compile and to run without modification, while you selectively update existing applications to take advantage of the new functions.

COBOL across platforms
Enterprise COBOL for z/OS is part of a large family of compatible compilers, application development tools, and maintenance tools. In addition to Enterprise COBOL, IBM offers IBM COBOL compilers for Windows®, AIX®, VSE, and System i®. Host-based development tools include ISPF, File Manager, Fault Analyzer, and IBM Debug Tool as well as the workstation-based development tool, Rational® Developer for System z®, which integrates with many of these host-based offerings. You can also take advantage of IBM’s extensive suite of COBOL maintenance tools to improve your existing applications. These tools assist you with source code conversion from former ANSI standards to ANSI 85 COBOL syntax; code analysis, and reporting; CICS source conversion; Report Writer code support; and regression testing of interactive applications.