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

The stdenv file consists of one or more records, where record is defined as a
string terminated with a character (X'15') in an z/OS UNIX file, or a
fixed or variable (nonspanned) format record in an MVS data set. Other MVS
record formats are not supported for stdenv. The following rules apply to the
specification of environment variables in stdenv files:
v Only one environment variable can be specified per record.
v Each environment variable is specified as variable=value.
v Environment variable names must begin in column 1, unless names
beginning with blanks are used.
v Environment variable records should not be terminated with null characters
(X'00'). BPXBATCH automatically appends a null character to the end of
each environment variable, and the lengths of environment variables as
seen by the program include the null characters.
v Trailing blanks (X'40') are truncated for MVS SYSIN data sets, but are not
truncated for any other type of file.
v Be careful that sequence numbers are not present in MVS data sets,
because they will be treated as part of the environment variables. ISPF edit
users should always set number mode off when creating environment
variables, including JCL data sets with environment variables specified as
SYSIN.
Some environment variables are release-dependent. If BPXBATCH is executed
on a system that does not support the environment variable, you will not get an
error message and the variable will be ignored. Use the uname shell
command to determine the release number of the operating system that
BPXBATCH is running on.
Environment variables (including PATH) are established at the start of the
executable program, not for BPXBATCH itself. Thus, PATH is not searched to
locate the program, but instead is used if the program invokes other
executable programs. In the following example, someprogram may be found
only in the initial working directory defined by the user’s profile, not by the
PATH environment variable:
//jobname JOB ...
//stepname EXEC PGM=BPXBATCH,PARM=’PGM someprogram parm1 parm2’
//STDOUT DD PATH=’/tmp/pgmout’,PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=SIRWXU
//STDENV DD *
PATH=/bin:/u/usr/joeuser
STEPLIB=SYS1.JOE.STEPLIB
/*
12. BPXBATCH uses two more environment variables for execution that are
specified by STDENV:
v _BPX_BATCH_UMASK=0755
v _BPX_BATCH_SPAWN=YES|NO
BPXBATCH
_BPX_BATCH_UMASK allows the user the flexibility of modifying the
permission bits on newly created files instead of using the default mask (when
PGM is specified).
Note: This variable will be overridden by umask (usually set from within
/etc/profile) if BPXBATCH is invoked with the ’SH’ option (SH is the
default). SH causes BPXBATCH to execute a login shell which runs the
/etc/profile script (and runs the user’s .profile) and which may set the
umask before execution of the intended program.
Appendix D. Running shell scripts or executable files under MVS environments 897