Specifying the DD statements
The following table describes the data sets that are allocated in JCL.
Defines the input data set that contains the Log Master batch syntax keywords and their values. Always specify this data set in the JCL. The record format must be fixed blocked (RECFM=FB) with a record length of 80 (LRECL=80). Columns 73-80 are reserved for sequence numbers, and Log Master ignores any characters in those columns. You can choose to enter Log Master syntax within the JCL itself (in-stream).
For more information about the Log Master syntax keywords and values, see Command and syntax reference.
Defines the output data set that contains Log Master messages. Always specify this data set in the JCL.
Defines the output data set that contains messages from the sort routine. Normally, you can specify this data set as SYSOUT=* .
(optional) Defines the output data set that contains a SNAP dump that Log Master might generate in response to internal errors. BMC recommends that you include this optional data set in your JCL as a troubleshooting aid.
(optional) Defines a data set that is used for system dumps that are produced when a system error occurs. BMC recommends that you include either SYSUDUMP or SYSMDUMP in your JCL as a troubleshooting aid.
(optional) Defines a data set that is used for system dumps that are produced when a system error occurs. Use either the SYSMDUMP data set or the SYSUDUMP data set.
For SYSMDUMP, Log Master produces a system dump that can be read by the IBM Interactive Problem Control System (IPCS) product. Specify the attributes of the SYSMDUMP data set as indicated in the appropriate JCL documentation.
BMC recommends that you include either SYSUDUMP or SYSMDUMP in your JCL as a troubleshooting aid
Defines a data set that is used by BMC Software Customer Support to diagnose row completion processing problems. Log Master dynamically allocates this data set as needed. You might be asked to provide this data set if your job displays BMC097461 messages.
(optional) Defines an input data set that contains specifications for handling SQL codes. As the product executes generated SQL, it uses these specifications to determine how to respond to the SQL codes.
The DD statement is required if your job executes generated SQL and you want to change the default actions. For more information about defining these specifications, see SQLCODES data set syntax, or the section on executing SQL in the Running SQL.
(optional) Defines an input data set that contains translation information. The product uses this information as it generates SQL. Using generated SQL and the translation information in this data set, you can migrate database changes that affect one set of objects to a similar set of objects with different names on another DBMS system.
(optional) Defines an output data set that the product uses as it executes generated SQL. The data set contains the results of SQL execution in the format that is generated by DSNTEP2 processing. If your job does not execute SQL, specify the data set as SYSOUT=*.
For more information, see SQLPRINT.