Embedded Source Support listing

ESS allows the LP to store an IBM language listing (the SYSPRINT output) in the same language PDSE program object produced by the compiler. ESS is an alternative to the traditional DDIO file. You can have the LP embed the listing into z/OS Binder CLASS records with the NOLOAD attribute of the PDSE program object.

Components of our Abend-AID, Strobe, Workbench, and Code Debug products, in addition to CSS, accommodate this ECC functionality.

Historically, CSS DDIO files that are used for source listing and report data have been the framework architecture used by CSS COBOL, PL/I, HLASM and C/C++ source support. DDIO file is a generic term used to refer to data sets that store the reports, dumps, and listings from BMC AMI products that use CSS. These DDIO files are integrated into our source support by each of BMC AMI source support-enabled products and has functioned as the single and main repository of CSS source support data.

ESS listing extends this DDIO file technology by supporting PDSE Program Objects as an alternative repository.  The Embedded Source Support (ESS) feature allows the actual source listing of the compiled program to be embedded into the PDSE Program Object executable.

Data written to the PDSE Program Object executable, record by record, byte by byte, is virtually identical to that written to a DDIO file source listing member; the technology used is virtually identical to that used by DDIO files. By allowing an alternative to the end repository, either a DDIO file or a PDSE Program Object, additional advantages and flexibility are realized.

Currently, ESS is implemented for the following:

• IBM Enterprise COBOL for z/OS V5.x or higher.
• IBM Enterprise PL/I for z/OS V4.5 and higher.

Where to go from here?

For understanding how useful ESS listing is, see Advantages and for detailed information about how to effectively use ESS listing, see Using-ESS-Listing.