JES2 sample initialization data sets

IBM distributes the HASIxxxx members in the SYS1.SHASSAMP data set library that you can tailor to meet your installation's needs. To ensure that your SYS1.SHASSAMP is not overwritten, IBM suggests moving these data sets to an installation library before tailoring the HASIxxxx members. The following table lists these initialization data sets and their specific roles.

Table 1. JES2 Sample Initialization Data Sets
Member Name	Contents	Use
HASIPROC	Sample JCL procedure	Tailor, rename, and move to the production JCL procedure library for use as the JES2 subsystem JCL.
HASIPARM	Sample JES2 initialization parameter templates	Use to create production JES2 initialization parameters in other libraries.
HASIASM	Sample JCL procedure.	Use when assembling an IBM® JES2 source module or an installation JES2 exit routine (it saves the resulting object code). This member can be tailored, placed in a production procedure library, and used when the SMP/E system installation and maintenance tool is not managing JES2 code.
HASIBLD	Sample job stream that uses the HASIASM procedure.	Assembles IBM JES2 source-distributed modules (including sample exit routines) and link edits each of the production load modules. This member can be tailored, placed in another procedure library, and used when the SMP/E system installation and maintenance tool is not managing JES2 code.
HASISMPA	Sample job stream.	Tailor, then use to force the SMP/E system installation and maintenance tool to reassemble all modules for the JES2 release it manages. This two-step procedure might be necessary to assemble all modules at an installation with the same level of MVS™ system macros.