Both IMS and Enterprise COBOL had new and exciting announcements this year. COBOL and IMS continue to deliver leading edge technologies to facilitate application integration, modernization, as well as improving application performance. Roland Koo, Product Manager for Rational Compilers, and Haley Fung, IMS Senior Developer, identify why it is important to upgrade to the latest versions of IMS and COBOL together. Speakers: Haley Fung, Roland Koo, and Kimberly Gist. Go HERE to listen to this informative podcast.
The COBOL for AIX Fix Pack 10 (December 2013 PTF) for 4.1.1 is now available at the following links and on Fix Central : COBOL for AIX Fix Pack 10 (December 2013 PTF) for 4.1.1 Fix list for COBOL for AIX Fixed APARs are listed on the 'Fix list' page, along with links to all COBOL for AIX Fix Packs. Please note that the term 'Fix Pack' is equivalent to 'PTF', and both terms may be used... [More]
The SMP/E REPORT MISSINGFIX command helps determine whether fixes exist that are applicable but have not yet been installed. We recommend using the SMP/E REPORT MISSINGFIX command with the FIXCAT keyword for COBOL V5.1 which is: IBM.TargetSystem-RequiredService.Enterprise-COBOL.V5R1 The command to use to find all of the service required to use COBOL V5.1 or run programs created with COBOL V5.1 is: SET BDY(GLOBAL). REPORT MISSINGFIX ZONES(URZONE1,URZONE2) FIXCAT(... [More]
With COBOL for z/OS, V5.1, you can use the AFP option to control the compiler usage of the Additional Floating Point (AFP) registers that are provided by z/Architecture processors. The syntax is as follows: --VOLATILE--. >>-AFP(-+-NOVOLATILE-+-)---------------------->< The default is AFP(VOLATILE). The Enterprise COBOL compiler generates code that uses the full complement of 16 floating point... [More]
Standard COBOL 85 requires that program-name be specified as a user-defined word. IBM COBOL compilers extends the standard rule and allow program-name to be a user-defined word or alphanumeric literal, but not a figurative constant, that identifies your program. It must follow the following rules of formation, depending on the setting of the PGMNAME compiler option: PGMNAME(COMPAT) If program-name is an alphanumeric literal, the rules for the name are the same except that the extension characters $, #, and @ can be included in the name of the... [More]
With COBOL for z/OS, V5.1, you can use the ARCH option to specify the machine architecture for which your executable program instructions are to be generated. The syntax is ARCH( n ). Parameter n is an integer between 6 and 10 inclusive, specifying the machine architecture for which instructions are to be generated. ARCH(6) is default. If you specify a higher ARCH level, the compiler generates code that uses newer and faster instructions. Your application might abend if it runs on a processor with an architecture level lower than what you... [More]
End markers are a combination of words followed by a separator period that indicates the end of a COBOL program, method, class, factory, or object definition. The following end marks are IBM extensions for both AIX and Enterprise. Please pay attention to the conventions when you use them: For programs - program-name must be identical to the program-name of the corresponding PROGRAM-ID paragraph. Every COBOL program, except an outermost program that contains no nested programs and is not followed by another batch program, must end with an END... [More]
Enterprise COBOL Developer Trial for z/OS, V5.1 is now available. The Trial lets you assess the value that could be gained from migrating to Enterprise COBOL for z/OS , V5.1, before making a formal, upgrade decision. This trial enables the evaluation of the latest IBM COBOL capabilities, in a non-production environment, without the prerequisite time and resources commitments required for a full, production migration project. For more information please visit the following URL:... [More]
Watch as James Governor, Principal Analyst and Founder, RedMonk, and Kevin Stoodley, IBM Fellow and CTO, IBM Rational, discuss the benefits of the new IBM Enterprise COBOL compiler for z/OS. Jeff Heath, Development Manager, IBM Rational, demonstrates some of the benefits of this new version. As mentioned in the video, please ask any followup questions in our COBOL Cafe forum .
In COBOL for z/OS, V5,1, when compiling your source files that are too complex or in a relatively large size, and if you have specified the OPTIMIZE level, it may take excessive amount of time or storage. Thus a new compiler option, MAXPCF , is introduced to allow you to control the amount of time and storage used when optimizing a program. You can specify the maximum program complexity factor with this option. The new term, Program Complexity Factor (PCF), is a value calculated by the compiler, and represents the complexity of the program... [More]
COBOL for AIX version 4.1 introduces a new utility, the source conversion utility (scu), to assist the conversion of programs in non-IBM COBOL source formats. The main function for utility is to “normalize” COBOL source input text so that the resulting output source text can be compiled by IBM COBOL for AIX V4.1. The input formats that are specifically addressed are some non-IBM fixed-format source and COBOL standard free-format source. The individual transformations done by scu includes the following: Converting... [More]
The COBOL for AIX compiler supports the extended source format as an IBM extension. Fixed source format consists of the following areas in a 72-character line. Extended source format consists of the following areas in a 252-character line. Sequence number area Columns 1 through 6 Indicator area Column 7 Area A Columns 8 through 11 Area B Columns 12 through 72 in fixed source format Columns 12 through 252 in extended source format Note that in fixed source format and extended source format , lines shorter than the maximum length are... [More]
To define variable length tables in COBOL, we usually specify the OCCURS ... DEPENDING ON clause in the data description entry for an item contained within a group structure. While this defines an item with a variable number of occurrences at run time, in earlier versions before Enterprise COBOL V5.1, we also need to specify a maximum number of occurrences in the syntax , and hence a maximum size for the table and the containing group, which causes usability problems in some contexts. In particular, this problem occurs when defining... [More]