Specifying the DD statements

Defines the input data set that contains the BMC AMI 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 BMC AMI Log Master syntax within the JCL itself (in-stream).

For more information about the BMC AMI Log Master syntax keywords and values, see Command-and-syntax-reference.

Defines the output data set that contains BMC AMI Log Master messages. Always specify this data set in the JCL.

(optional) Defines the output data set that contains a SNAP dump that BMC AMI Log Master might generate in response to internal errors. We recommend 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. Use either the SYSMDUMP data set or the SYSUDUMP data set.

For SYSMDUMP, BMC AMI 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.

We recommend that you include either SYSUDUMP or SYSMDUMP in your JCL as a troubleshooting aid

Defines a data set that is used by BMC Support to diagnose row completion processing problems. BMC AMI 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.

For more information about translating Db2 object names, see SQLXLAT-data-set-syntax, or the section on defining the log scan step in the Defining-a-log-scan-step.