Process control

The INPUTDEF file is used to control the translation of the CSV file into Application Definitions.

The INPUTDEF file contains keywords with the format KEYWORD(VALUE) KEYWORD(VALUE) KEYWORD(VALUE)

Each keyword has the value specified within parenthesis and separated from the next keyword by a space.

MAP(field,field,field)

Defines which columns of the CSV file relate to details within an operation.

JOBN

The job name you want to search.

PRED

The predecessors, multiple predecessors must be contained within the same “cell” separated by spaces.

FORM

The form number.

HIGHRC

The Highest Return Code.

WSID

The Workstation.

DURATION

The estimated duration in seconds.

<period>

A period is used as a placeholder for columns that do not contain information pertinent to the creation of the Application.

The following example shows the Job name being in column 2, highest return code in 3, workstation in 4, form number in 5 and duration in 7:

MAP(.,JOBN,HIGHRC,WSID,FORM,.,DURATION)

POLICY(op<total,op<total,op)

Defines the Operation Interval policy. Each level of the POLICY defines the operation number to use when the total number of operations in the CSVFILE is less than a specified threshold, with a “catch all” interval at the end.

The following example uses an interval of 10 for less than 26 operations, and interval of 5 for less than 51 operations and an interval of 3 for anything higher:

POLICY(10<26,5<51,3)

POLICY(5) simply sets the catch all at 5, meaning that the interval is 5 regardless of the number of operations in the CSVFILE.

SKIP(n)

Specifies the number of rows to skip at the beginning of the file before starting processing, to account for header rows in spreadsheets that are used to generate the CSV files. For example, SKIP(3) skips 3 rows and start processing with row 4.

UPDATE(Y|N)

Specifies whether the generated Batch Loader is to update the HCL Workload Automation for Z database (Y) or simply output the Batch Loader to OUTBL (N).

ADID(application-name)

Defines the Application name to create. If the number of operations results in more than one Application being generated, the names are suffixed with a numeric count. If the Application name and the numeric suffix would exceed 16 characters, the numeric suffix will overlay the end of the application name.

For example, ADID(ABCDAILY) will create ABCDAILY if only one application is needed, or ABCDAILY1, ABCDAILY2 etc if a split occurs.

<Batch-Loader-Token>(value)

Any Batch Loader tokens for ADOP (for details, see HCL Workload Automation for Z: Managing the Workload) can be used to set defaults for the mapped columns that have no values. For example, FORM(DD0001) creates a default value of DD0001 for any operation that does not have a value in the mapped column for form number.

They can also be used to create lookup tables to translate input values by suffixing the keyword name with a hyphen and a lookup value, with the replacement value being specified within parenthesis. In the following example, you use DD0001 as the form number for any column that contains MY.FIRST.JCLLIB and DD0002 for any column that contains MY.SECOND.JCLLIB:

FORM-MY.FIRST.JCLLIB(DD0001)
FORM-MY.SECOND.JCLLIB(DD0002)

This technique can be used for any of the mapped columns.

FIRST(1) FIRSTWS(NONR) FIRSTJOB(START) 
LAST(255) LASTWS(NONR) LASTJOB(END)