Scope: Tulsa Complex A (SYK, SYV, SYZ) & Complex B (PB02)
Effective Date: September 11th-12th, 2011
Group Name: Software Services Mainframe
Affected Locations: Tulsa
Summary: The currently installed version of the Enterprise COBOL compiler is being upgraded from Version 3 Release 4 to Version 4 Release 2. While this is mainly a maintenance release there are some new features which are detailed below. Other than the addition of some reserved words there are no major chnages and your existing COBOL program should be fully compatible with this new version.
Justification:
Maintain software currency
Benefits to Users:
Latest supported version of the COBOL compiler
Details:
• Further enhancements to XML parsing using the z/OS XML System Services parser:
– 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 non-validating 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.
• A new facility lets you customize message severity:
– The new MSGEXIT sub-option 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.
• 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 CONTAINS 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.
• COBOL user-defined words can now include the underscore character (_):
– 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:
– When applications 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.
• Additional SDKs supported for Java interoperability:
– 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.
Enterprise COBOL for z/OS, Version 4 Release 2 is fully source and object compatible with
Enterprise COBOL for z/OS, Version 3 Release 8, except:
• There are new reserved words:
o XML-NAMESPACE
o XML-NAMESPACE-PREFIX
o XML-NNAMESPACE
o XML-NNAMESPACE-PREFIX
o XML-SCHEMA
• The SIMVRD runtime option and simulated variable length relative record data sets are no longer supported.
• The sub-options of the TEST compiler option are simplified. Existing sub-options are tolerated for compatibility, and are automatically mapped to the new sub-option values. Symbolic debugging information is always generated when the TEST option is in effect.
• See the Enterprise COBOL for z/OS Compiler and Runtime Migration Guide, Version 4 Release 2 for complete details.
Primary Contact:
please send an email to the MVS ATS mailbox (sabremvsats@hp.com)
Secondary Contact:
Richard Reed (Richard.Reed@hp.com)
Additional Information:
Latest Enterprise COBOL documentation -
http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp?topic=/com.ibm.entcobol.doc_4.2/PGandLR/pgtitlemvs.htm
|
Usercomm - Tulsa - Complex A & B - Enterprise COBOL 4.2 Upgrade 