z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

BPXBATCH
The stdparm DD will allow either a z/OS UNIX file, or a MVS SYSIN PDS,
PDSE or Sequential data set. The following are characteristics of the
parameter data that can be supplied in the stdparm DD, if a z/OS UNIX file is
specified:
v It must be a text file defined with read access only
v Specify one argument per line
v The file cannot have sequence numbers in it.
Tip: If you use the ISPF editor to create the file, set the sequence numbers
off by typing number off on the command line before you begin typing data.
If sequence numbers already exist, type UNNUM to remove them and then
type number off.
If a MVS data set is specified:
v Specify one argument per line. If the parameter string for an argument
spans more than one line of a data set or file, this string will be divided into
two or more arguments that are passed to the corresponding shell script or
program.
v The maximum length of a single argument supplied to the program is
32,760, which is the same as the maximum LRECL for an unspanned
non-VSAM data set.
v The record format of the data set can fixed or variable (unspanned).
v The data set cannot have sequence numbers in it. If you use the ISPF
editor to edit the data set, set the sequence numbers off by typing number
off on the command line before you begin typing in the data. If sequence
numbers already exist, type UNNUM to remove them and set number mode
off.
v Trailing blanks are truncated for SYSIN and variable block data sets, but not
for fixed block data sets. For a fixed block data set, trailing blanks will be
included in the parameter text for a given argument up to the end of the
record.
8. BPXBATCH does not close file descriptors other than 0–2. Other file
descriptors that are open and not defined as “marked to be closed” remain
open when you call BPXBATCH and BPXBATCH runs the specified script or
executable file.
9. BPXBATCH uses write-to-operator (WTO) routing code 11 to write error
messages to either the JCL job log or your TSO/E terminal. Your TSO/E user
profile must specify WTPMSG so that messages can be displayed at the
terminal.
10. BPXBATCH (with the SH parameter) must not be used to run an executable
file, shell command, or shell script in the background (by specifying the shell &
symbol) unless the shell nohup command is also used. If the shell ampersand
(&) symbol is used without nohup, the results are unpredictable.
11. BPXBATCH, when used with the PGM parameter, sets up environment
variables for the program to be run. If the stdenv file is not allocated, the
HOME and LOGNAME environment variables are set. If stdenv is allocated,
the environment variables read from the file it represents are set, with HOME
or LOGNAME or both environment variables added if they are not specified in
the stdenv file. The following types of files can be allocated to stdenv:
v z/OS UNIX text file
v Sequential format MVS data set (including SYSIN data set)
v Member of a partitioned data set (PDS)
Other forms of MVS data sets, such as DUMMY, TERMINAL, SYSOUT, or
PDS/E, are not supported for stdenv.
896 z/OS V1R9.0 UNIX System Services Command Reference