Getting listings of JES2 data areas

When writing and debugging an installation exit, it is sometimes useful to get listings of JES2 data areas similar to what is available in the z/OS® data areas books. There are a number of ways to do this depending on what data you need.

To get a listing of all the JES2 data areas, you can assemble the module HASPDOC; the JES2 source code distribution library SYS1.SHASSRC provides this module. You can assemble this module by using either SMP/E, the sample JES2 assembly PROC HASIASM in SYS1.SHASSAMP, or using your own assembly procedure. The output listing contains all the JES2 data areas. If you request the assembler produce a full cross reference using the XREF(FULL) parameter, you will get an alphabetic listing of all the symbols.

You can also use the same source module to get a listing of the z/OS data areas that JES2 uses. To do this, include the assembler parameter SYSPARM((,,,GEN,GEN)) on the assembly. You can find the operands of SYSPARM for any JES2 module in z/OS JES2 Macros under the SYSP= operand of the $MODULE macro.

If you need a listing of just one data area (either JES2 or z/OS), you can create an assembler module with only a $MODULE statement listing the data areas you want listings for and an END statement. The following is an example of an assembler module that creates a listing of the JES2 $HCT data area. The assembler listing produced will have only the $MODULE expansion and the $HCT data area:

             $MODULE ($HCT,GEN)          
             END

This method works for any mapping macro supported by $MODULE. All required macros for the assembly are automatically included and only the requested data area is generated in the listing. You can get more than one data area by just adding it to the $MODULE list:

             $MODULE ($HCT,GEN),($PCE,GEN)          
             END

This gets the $HCT and the $PCE data areas.

You can also add the GEN operand to data area specifications in the $MODULEs in your exits. This puts any requested data areas on to the listing for your exits.

If there is no label on the $MODULE and the only operands specified are the data areas to generate, $MODULE will not generate the JES2 $MIT data structure. If you do place a label on the $MODULE invocation or add any other operands, $MODULE will attempt to build a JES2 load module. Without other structures, it might get assembly errors. Using a $MODULE without operands or a label can be useful when you need to include JES2 mapping macros in code that is not going to be run as a JES2 exit.