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

BPXBATCH
Usage notes
and exec. BPXBATCH creates a process for the program to run in and then
calls the program. If you specify PGM, you must also specify
program_name.
All environment variables read from the stdenv file are set when the
program is run if stdenv was allocated. If the HOME and LOGNAME
variables are not specified in the stdenv file, or stdenv was not allocated,
then HOME and LOGNAME, if possible, are set when the program is run.
Refer to Usage notes for more information on environment variable
processing.
Note: When using PGM, the program_name cannot contain any shell
specific functions because they will not be resolved. If shell specific
functions must be specified, then SH should be used to avoid
possible errors or unpredictable results.
program_name
Specifies the shell command name or the z/OS UNIX path name for the shell
script or z/OS C executable file to be run. In addition, program_name can
contain option information.
The program_name is interpreted as case-sensitive.
Note: When PGM and program_name are specified and the specified program
name does not begin with a slash character (/), BPXBATCH prefixes the
user’s initial working directory information to the program path name.
1. BPXBATCH is an alias for the program BPXMBATC, which resides in the
SYS1.LINKLIB data set.
2. BPXBATCH must be invoked from a user address space running with a
program status word (PSW) key of 8.
3. BPXBATCH does not translate characters on the supplied parameter
information. You should supply parameter information, including z/OS UNIX
path names, using only the POSIX portable character set. For information on
the POSIX portable character set, see z/OS UNIX System Services
Programming Tools.
4. If your BPXBATCH job returns ABEND 4093 reason code 0000001c, you need
to expand the region size. For example:
//SHELLCMD EXEC PGM=BPXBATCH,REGION=8M,PARM=’SH shell_cmd’
5. BPXBATCH does not support any ddnames other than stdin, stdout, stderr,
stdenv or stdparm . Attempting to allocate or reference any other ddnames
will result in enqueue failures or unpredictable results. To use an MVS data set
in your batch UNIX application, use ″dynamic allocation″, such as SVC99 or
the TSO ALLOC command. Also, you must remove all ″static allocations″
(ddnames referring to the MVS data set in question) from all steps in the batch
job.
6. If you define an MVS data set for stdout or stderr consider the following:
894 z/OS V1R9.0 UNIX System Services Command Reference
v It must be a sequential data set, a partitioned data set (PDS) member, a
partitioned data set extended (PDSE) member, or SYSOUT.
v The data set must have a nonzero logical record length (LRECL) and a
defined record format (RECFM); otherwise, BPXBATCH will fail with error
message BPXM012I indicating an open failure for the affected ddname.