The AOPBATCH JCL procedure accepts these standard DD statements:
STDENV
Specifies environment variables that the transform command uses.
You can specify the environment variables in-stream in the JCL, 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 that is 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 these 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:
To obtain MVS return
codes (0, 4, 8) instead of the default UNIX exit
values (0, 1), set the AOP_MVS_RETURN_CODES=yes environment variable.
For information, see AOP_MVS_RETURN_CODES environment variable.
AOPBATCH sets the HOME environment variable to the user's home
directory and sets the LOGIN variable to the user ID.
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 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.
Rules:
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.
If you have not added the Language Environment® run-time
library (CEE.SCEERUN) or the C++ run-time library (CBC.SCLBDLL) to
the system LNKLST, specify these data sets in a STEPLIB DD statement.
The PDF to AFP and
the PostScript to AFP
transforms cannot transform concatenated input files. If you want
to transform more than one PDF or PostScript file
in the same job, create a separate step to transform each file. (The
PCL to AFP transform
can transform concatenated input files.) See AOPBATCH examples for
an example of how to transform and print multiple PDF files in the
same job.
If you want to write the AFP data stream to an MVS data
set, you must allocate and catalog the MVS data
set before you run AOPBATCH or include a DD statement in the AOPBATCH
job to allocate the data set. Allocate a data set with these characteristics:
Record format: VBM.
Record length: 8192 (8K) or larger.
Disposition: SHR or OLD overwrites any existing data in the data
set; MOD appends the output to any existing data. MOD is the default.
Allocate an MVS data set that is large enough to
hold the AFP data stream. The
size of the AFP data stream
depends on the size and complexity of the document, the type of image
compression, and the resolution of the image. Typically, the PCL to AFP, PDF to AFP, and PostScript to AFP transforms create an output AFP data stream
that is several times as large as the input data stream. For more
information about the size of the AFP data stream, see Calculating the size of the AFP data stream.
Note: If you specify
an MVS output data set that does
not exist, the transform creates the data set; however, the data set
does not have the correct record format and record length. If you
attempt to print the data set, PSF for z/OS® writes
message APS114I.