Functional stabilization of the Endevor "Expand Include" utility program (ENBX1000)
Article ID: 22497
Updated On:
Products
Issue/Introduction
Effective November 1, 2010, the Endevor product team formally announces the functional stabilization of the product's expand-include utility component (ENBX1000).
Resolution
Functional stabilization of the Endevor "Expand Include" utility program (ENBX1000)
Effective November 1, 2010, the Endevor product team formally announces the functional stabilization of the product's Expand Includes utility (ENBBX1000). While the development and timing of CA products remains at the sole discretion of CA Technologies, there are no current plans to remove ENBX1000 from the Endevor product. However going forward, ENBX1000 will not be enhanced.
Specifically, the product team will continue to distribute and provide support for ENBX1000; we will answer questions as well as diagnose and correct ABENDs, in accordance with the CA Technologies Support Policy and Terms. However, we will not provide any additional modifications that alter the syntax logic to accommodate specific customers' implementations.
This functional stabilization of ENBX1000 is necessary, because it has become increasingly difficult to provide timely support for the various language syntax options and the syntax changes that have been implemented by the IBM COBOL compiler. In addition, IBM has announced the introduction of the Integrated Co-processor feature, which can eliminate the need for ENBX1000 as well as improve performance.
ENBX1000 was created, when Legent Corporation owned the product, to provide similar functionality as CA Librarian, that is to expand CA Librarian include members and COBOL COPY members at the time the member was written from a CA Librarian data set. Legent went a step further to attempt to support the include and COPY member expansion when writing members from any type of data set (CA Panvalet, PDS, or PDSE). We soon discovered that CA Endevor SCM customers were using every kind of COBOL COPY syntax option available, including some that seemed to violate syntax rules.
As time went on, ENBX1000 support became very difficult, because a correction for one client's syntax nuance broke someone else's ENBX1000 implementation. The time and effort to support everyone's flavor required significant time and effort - to the detriment of the product team's overall product support responsibilities.
The support issue was resolved when IBM announced the introduction of the Integrated Co-processor feature for their compiler. This feature allows the expansion of both EXEC CICS and EXEC SQL during the compile step. This means that the burden of supporting the variations of the COBOL COPY statement can be placed back on the COBOL compiler. Also, there is a performance benefit introduced by this change. The existing two-step precompile-compile process is no longer necessary; the precompile step can be completely eliminated.
The expansion of the CA Librarian and CA Panvalet include syntax can be performed by the Endevor processor utility CONWRITE.
How to Replace the Expand Includes Utility
If ENBX1000 is used only to expand CA Panvalet ++INCLUDE or CA Librarian -INC include statements, you can use the Endevor CONWRITE processor utility program instead. To remove the need for the Expand Includes utility:
- You must use the CONWRITE utility. For CONWIRTE to expand include members, make sure the utility specifies: PARM=EXPINCL(Y).
- Remove the Expand Includes utility.
How to Remove the Expand Includes Utility
Follow these steps to remove ENBX1000, the DB2 pre-compiler and CICS translator processor steps:
- Add the DB2 libraries, or CICS libraries, or both to the compile's STEPLIB concatenation.
- Add the //DBRMLIB DD.
- Move your ENXINC data sets to the SYSLIB concatenation.
- Specify 'SQL("option, option, option") or 'CICS("option, option, option")' or both to the compile parameters. You can specify these as CBL statements in the program or as in-stream SYSIN.
Feedback
