Db2 subsystem identification (ssid)

This parameter identifies the Db2 subsystem to which Log Master connects.

Log Master uses the subsystem identifier (SSID) to locate the Db2 address space and the Db2 logs. The SSID can be one to four characters long. You can also use a group attachment name (for Db2 data sharing) for this parameter. By using a group attachment name, you can run the same JCL on any member of a data sharing group. When you submit a job with a group attachment name, a Db2 subsystem in the group that is represented by the name must be running on the system where you submit the job.

Related topic

Specifying-the-EXEC-statement

Log Master does not require this parameter. If you omit the SSID, Log Master examines the libraries that are listed in your STEPLIB or JOBLIB statements, attempts to load a DSNHDECP module from those libraries, and then obtains the SSID from that module.

MAINT parameter

In some situations, you might need to use a special EXEC statement parameter called MAINT instead of the SSID.

The MAINT parameter prints the control section (CSECT) that tracks maintenance that is applied to Log Master. This information can help to determine whether a fix has been applied to your installation of the product. Log Master does not perform any other processing if you specify the MAINT parameter. The following example shows an EXEC statement that uses the MAINT parameter:

Example
   //stepname EXEC PGM=ALPMAIN,REGION=0M,
   //         PARM='MAINT'


Important

Log Master does not require a working connection to Db2 to print the maintenance information.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*