Restrictions and Limitations

A control block formatter exit routine is considered to be an extension of the data area formatter service, and as such is exposed to both the basic and the extended format interfaces.

Any control block formatter exit routine should be able to interpret the format parameters ADPLPFMT and ADPLPFXT. For those that can only interpret the basic format interface (ADPLPFMT only), the control block formatter service will attempt to convert to the basic interface. Specify JBB2125 as the second parameter of the FORMAT parameter of the DATA statement in BLSCUSER parmlib member that defines your control block formatter exit routine:

DATA FORMAT(name,JBB2125)

When writing a control block formatter exit routine for systems that support 64-bit storage, specify HBB7703 as the second parameter of the FORMAT parameter of the DATA statement in BLSCUSER. Exits written to accept the HBB7703 API that also need to run against dumps of earlier releases should check the format of the BLSRESSY structure(s) passed. Ones solely designed to run on HBB7703 or higher levels may assume that the 64-bit format will be passed.

The interface cannot be converted if the block does not reside in:

Virtual storage
Real storage
The dump header record
The CPU status record

Reference

See z/OS MVS Initialization and Tuning Reference for information about creating a BLSCUSER parmlib member.