Whichever method you use, be very careful and ensure backups are made before either process is allowed to modify the DSNZPARM values. Even something as simple as ISPF’s compare option (option 3.13) can be used to check for changes between old and new copies of DSNTIJUZ. There are also DB2 and vendor-supplied methods of verifying the values in DSNZPARMs. Remember that if you’re running all the steps created in the DSNTIJUZ job stream, this job will also run DSNTIMQ and assemble and link the DSNHDECP module. 

The installation panels are used to set more than the DSNZPARM values. Other values set up by the install process include values for the IRLM procedure and the data-only modules DSNHDECP and DSNHMCID.

And on the subject of macros and load modules, let’s consider “who” these macros are, how they’re used, and the steps associated with becoming a functioning DSNZPARM load module. 

DSNZPARM results from expanding seven macros: DSN6ENV, DSN6ARVP, DSN6LOGP, DSN6FAC, DSN6GRP, DSN6SYSP, and DSN6SPRM. Each has multiple keywords that can be “set” to some value, or allowed to default to a predefined value, that controls DB2’s behavior: 

-        The DSN6ENV macro describes the DB2 environment and sets global variables the other DSN6 macros use.

-        DSN6ARVP contains the parameters used to control selected archive log functions. 

-        DB2’s log manager externalizes its initialization parameters through the DSN6LOGP macro. 

-        DSN6FAC controls the start options of the Distributed Data Facility (DDF) and other related distributed functions. 

-        DSN6GRP includes miscellaneous initialization parameters for group functions in a data-sharing environment.

-        DSN6SYSP contains miscellaneous system initialization parameters. 

5 Pages