AOPBATCH DD statements

The AOPBATCH JCL procedure accepts these standard DD statements:

STDENV

Specifies environment variables for use by the transform. You can specify the environment variables in-stream in the STDENV DD statement, in an MVS™ data set, or in a UNIX file. Specify the environment variables in the format variable=value, with one environment variable per line or record. Sequence numbers in columns 73-80 in data specified with the STDENV DD statement are ignored and not treated as part of the data.

If you omit the STDENV DD statement or do not specify one of the environment variables, AOPBATCH sets these default values, which are suitable for running Infoprint Server programs if your installation installed Infoprint Server files in the default directories:

PATH=/usr/lpp/Printsrv/bin:/bin:/usr/bin
LIBPATH=/usr/lpp/Printsrv/lib:/lib:/usr/lib
NLSPATH=/usr/lpp/Printsrv/%L/%N:/usr/lpp/Printsrv/En_US/%N:/usr/lib/nls/msg/%L/%N

AOPBATCH also sets the HOME environment variable to the user's home directory and sets the LOGIN variable to the user ID.

Tip:

The lp command and some transform commands return MVS return codes (0, 4, 8) instead of UNIX exit values (0, 1) when you set the AOP_MVS_RETURN_CODES=YES environment variable.

Note:

Do not specify the _BPX_SHAREAS environment variable. AOPBATCH sets it appropriately.

STDERR

Specifies the system output data set where error messages are to be written. The data set can be an MVS data set or a UNIX file. The transforms from AFP (AFP to PCL, AFP to PDF, and AFP to PostScript) do not write messages related to errors in the input data stream in this data set. Instead, the transforms write these messages at the end of the output document.

STDOUT

Specifies the system output data set where informational messages are to be written. The data set can be an MVS data set or a UNIX file.

You can also include DD statements to specify MVS data sets that contain input data to be transformed, the transformed output, or job attributes that are input to the transform. Do not use DD names STDIN, STDOUT, or STDERR to specify the transform input and output data sets. Instead, use other DD names, such as INPUT and OUTPUT, which are used in the examples.

Rules:

• If the output data set is an MVS data set, these requirements apply:
  • You must either allocate and catalog the data set before you run AOPBATCH, or include a DD statement in the AOPBATCH job to allocate the data set.
  • The MVS output data set must be large enough to hold the output data stream. The size of the output data stream depends on the complexity of the document and the type of the image compression. Typically, an output AFP data stream is several times as large as the input data stream.
  • If the output data set is to contain an AFP data stream, allocate a data set with these characteristics:
    • Record format: VBM
    • Record length: 8017 bytes or larger
    Notes:

    1. For InfoPrint Transform Manager for Linux, if you do not use the -pragma afpdsrecordlength option, allocate the data set with a record length that is at least 32017 bytes. By default, the transforms to AFP create AFP records that are 32000 bytes. To request that the transforms create AFP records that are a smaller maximum length, you can use the -pragma afpdsrecordlength option. Valid values for the option are 8000 - 32000. The default is 32000. For example, to set the maximum number of bytes in a record to 8000, specify:

       -j "filter-options='-pragma afpdsrecordlength=8000'"

    2. For the Infoprint Transforms to AFP for z/OS®, allocate the data set with a record length that is at least 17 bytes larger than the record length specified in the AOP_RECLEN environment variable. AOP_RECLEN is specified in units of kilobytes. Valid values are 8 - 32. The default is 8.
  • If the output data set is to contain a PCL, PDF, or PostScript data stream, allocate a data set with these characteristics:
    • Record format: VB
    • Record length: 1024 or larger is suggested
  • Specify a disposition of SHR or OLD if you want the transform to overwrite any existing data. Otherwise, specify a disposition of MOD to append the output to any existing data. If you do not specify any disposition, the transform overwrites any existing data.
• If you have not added the Language Environment® run-time libraries (CEE.SCEERUN and CEE.SCEERUN2) and the C++ run-time library (CBC.SCLBDLL) to the system LNKLST, specify these data sets in a STEPLIB DD statement.
• You can concatenate input data sets that have the same data format; for example, PostScript data or AFP data. However, you cannot concatenate data sets that contain PDF data.