JCL syntax for Z Data Tools batch jobs

To use a Z Data Tools function in a batch job, include the following EXEC statement:

You must supply a DD statement for SYSPRINT. You might also need a STEPLIB statement or other DD statements, depending on which Z Data Tools functions the batch job contains.

When you code Z Data Tools control statements, you must:
  • Begin each control statement with $$FILEM in columns 1 to 7, followed by a blank in column 8, followed by the command name, followed by the first parameter (if any).
  • Specify parameters and their values separated by an equal sign, like this:
  • Follow each parameter (except the last one) immediately with a comma.

Comment statements, which begin with an asterisk (*), are also allowed.

To continue a control statement onto the next line, end the first line with a comma and begin the next line with $$FILEM and a blank.

To continue a parameter that does not fit onto one line, do not use a continuation character. Instead, split the parameter into more than one line, enclosing each part in apostrophes. For example:
$$FILEM DSNIN='u/test/this is a regular HFS file ',
$$FILEM 'that has a v',
$$FILEM 'ery long name'
  1. If the control statement contains only the function name, there must be a space between the function name and the comma.
  2. To continue FIND and CHANGE commands in the FCH (Find/Change) utility, end the first line with a comma (the continuation line does not contain $$FILEM).
  3. To change processing options in batch or to reset options to the installation default, use the SET function.


In HEX format, the following example shows a batch job that uses the DSP Z Data Tools function to print 20 records of a data set (starting at the record with key value 0001000):