Parmlib concatenation allows concatenation of up to 10 libraries
to data set SYS1.PARMLIB. It also provides message IEE252I in syslog
to show in which data set a member resides.
When XRC is started by the XSTART command, XRC looks for member
ANTXIN00 in the parmlib concatenation. Any of the parameters that
are described in Table 1 can
be included. The parameters that are unique to ANTXIN00 are processed
first so that XRC knows which libraries and members to use to finish
parmlib processing. These parameters (hlq, mhlq, parmlib, global and session)
are found in the NAMES and STARTUP categories.
It is possible to change the parameters in the NAMES and STARTUP
categories in the ANTXIN00 member. The following parameters describe
some of the changes that you might want to make:
- Parameter hlq provides the high-level qualifier for all
XRC data sets. The default is SYS1, but you can override this value
with the hlq parameter that is specified on the XSTART command.
- Parameter parmlib allows you to specify
which parmlib to use for the processing that follows. If XCOPY is
specified (the default), data set hlq.XCOPY.PARMLIB is used.
If you specify SYS1, the parmlib concatenation is used. If the parmlib
concatenation is used, any messages that include the parmlib data
set name display SYS1.PARMLIB+.
- Parameter global allows you to specify
a single member containing XRC parmlib values that are applied to
all XRC sessions.
- Parameter session allows you to specify
a single member for each XRC session. Each member contains XRC parmlib
values which are applied to the associated XRC session.
When you issue the XSTART command, XRC performs the following:
- Searches for member ANTXIN00 in the parmlib concatenation. If
ANTXIN00 is not found, the defaults of hlq(SYS1), mhlq(SYS1), parmlib(XCOPY),
and global(ALL) are used. In addition,
the default member used for a session is the member having the same
name as the session_id.
- Processes the parameters found in ANTXIN00. XRC processes the
parameters for hlq, mhlq, parmlib, global,
and session. These parameters are processed
only if they are found in ANTXIN00 during XRC XSTART processing. You
can choose to not have any other XRC parmlib members, in which case
you might provide additional XRC parmlib values in the ANTXIN00 member;
these additional parameters are also processed at this time.
- Searches for the member specified on the global parameter.
XRC parmlib values specified in this member are applied to all XRC
sessions. If the Global parameter member was not specified , member
ALL is searched for, and if found, XRC parmlib values in this member
are processed.
- Searches for the member specified on the session parameter
for the session being started. The Session parameter might contain
multiple pairs of names: the first name in a pair is the session_id name
and the second name in the pair is the member name containing the
XRC parmlib values that will be used for the session. If a matching session_id name
is found, the associated member is searched for. If the associated
member is found, the parmlib values specified in this member are processed.
If the session_id is not in the Session
parameter, the member with the name of session_id is
searched, and if found, XRC parmlib values are processed from this
member.
The general format of the SESSION parameter is as follows:
Session(session_id1 member1 session_id2 member2)
The following example represents approved coding for
the Session parameter:
In this example, the session_id of
started sessions DBACKS and ANGELS is specified on the Session parameter,
and XRC processes parmlib member BIGUNIT for session DBACKS and parmlib
member SMALUNIT for session ANGELS.
SESSION(DBACKS BIGUNIT ANGELS SMALUNIT)
NOTE: If the same parameter value appears more than
once in a parmlib member or in more that one parmlib member, XRC uses
the value it processes last. For the Session parameter, if a session_id is
specified more than once, only the XRC parmlib values for the last
member found is applied.
It is possible for errors to occur as the parameters process. If
XRC finds an error, it issues an error message to the operator console
describing the error. When ANTAS000 starts up and errors are found,
the system issues message ANTI1030E and processing continues. When
an ANTAS00n address space starts up because of an XSTART command
and errors are present, the processing of the XSTART command ends
with return code 4119.
For information about the allocation specifications of hlq.XCOPY.PARMLIB,
refer to Creating a PARMLIB data set.
For additional information about parmlib concatenation, refer to z/OS MVS Initialization and Tuning Reference.