Contains an entry for every z/OS
subsystem. Db2 adds one entry for Db2 and two entries for IRLM in the list. The second
IRLM entry, whose subsystem name is JRLM, simplifies adding a second IRLM to your system if the
first is damaged. You must provide your own procedure to add JRLM. Unique names must be used for
each entry.z/OS provides subsystem
entries for Db2 and IRLM in IEFSSN00.
Examine these entries to determine whether they are appropriate for your needs. Make sure that a
subsystem name appears only once in the subsystem name list.
Place the SMS line as the first line in an IEFSSNxx member. Place
the primary system's record (JES2 or JES3) record next. Other products might affect the position of
the entries during system initialization. The Db2 line should come after SMS, the JES subsystem,
and other vendor products.
The
Db2
entry has the following format:
SUBSYS SUBNAME(ssname) INITRTN(DSN3INI)
INITPARM('DSN3EPX,cmd-prefix<,scope<,group-attach<<,subgroup-attach>>>')
- ssname
- The Db2 subsystem name.
- DSN3INI
- The name of the Db2 load modulethat z/OS invokes during z/OS master scheduler initialization. This module must be located in a link list data set (or in SYS1.LINKLIB).
- DSN3EPX
- The name of the Db2 load module that
responds to Db2 requests that are received
from the z/OS® subsystem interface. (Db2 can be active or inactive when the requests are
received.) This module must be located in a link list data set (or in SYS1.LINKLIB).
- cmd-prefix
- The one- to eight-character command prefix.
The first character of the command prefix must be
one of the following characters: @ # . / ' ) * + - = ¢ < | & ! ; % _ ? : ". The remaining
characters of the command prefix must be one of the above characters, A-Z, or 0-9. Do not use the
JES2 backspace character or command prefix character. The default is the hyphen (-).
Do not assign a command prefix that is used by another subsystem or that can be interpreted as
belonging to more than one subsystem or z/OS
application. Specifically, do not specify a multiple-character command prefix that is a subset or a
superset of another command prefix beginning from the first character. For example, you cannot
assign '-' to one subsystem and '-Db2A' to another. Similarly, you also
cannot assign '?DB2' to one subsystem and '?DB2A' to
another. You can assign '-DB2A' and '-DB2B' to
different Db2 subsystems.
- scope
- The one-character scope for the command prefix. Db2 registers its command prefix with the operating
system. When this is done, the scope of the command prefix is controlled by the value you choose:
- S
- Started; and the prefix is registered with sysplex scope at Db2 startup instead of duringz/OS IPL. This is the default.
Recommendation: Choose S, which allows you to have a single
IEFSSNxx PARMLIB member that all z/OS systems in the sysplex can use. Choosing S also
simplifies the task of moving a Db2 from
one system to another; you can stop Db2 on
onez/OS and start it up on another without
having to re-IPL the system.
- M
- z/OS system scope; the prefix is
registered during z/OS IPL.
- X
- Sysplex scope; the prefix is registered during z/OS IPL. As a result, this Db2 cannot be restarted on another z/OS without changing the definitions and re-IPLing
both z/OS systems.
- group-attach
- The group attachment name, which is used for data sharing. You can specify this on installation
panel DSNTIPK.
- subgroup-attach
- is the name of the subgroup attachment, which is used in data sharing environments to provide
more control over how TSO, CAF, RRSAF, JDBC, ODBC, and Db2 utilities connections find active Db2 subsystems. You can specify this value by
entering a subgroup name in the SUBGRP ATTACH field on installation panel DSNTIPK.
Job DSNTIJMV updates IEAAPFxx to include the
Db2 program libraries
(prefix.SDSNEXIT, prefix.SDSNLOAD,
prefix.SDSNLOD2, prefix.SDXRRESL, and
prefix.SDSNLINK) as APF-authorized libraries.
If a program library that contains DFSORT or Db2 Sort for z/OS
is not already APF-authorized, you can edit DSNTIJMV to authorize it. To do this, you can include
the authorization either in this list or in LNKLSTxx. All libraries that are
concatenated with prefix.SDSNLOAD in STEPLIB and JOBLIB statements must be
APF-authorized. Ensure that the volume serial number in this member is the volume on which the data
set resides.
If you are using the PROGxx member instead of the IEAAPFxx
member, you must update the member manually—job DSNTIJMV does not edit it.
Job DSNTIJMV updates this member to include the Db2 load module library,
prefix.SDSNLINK. If you moved the modules from prefix.SDSNLINK
into another library, edit DSNTIJMV to include that library in the LNKLSTxx
member. If you have combined prefix.SDSNLINK and
prefix.SDSNLOAD into one library, edit DSNTIJMV to include the combined library
in the LNKLSTxx member.
Any data set that is added to the LNKLSTxx member must be cataloged in the
master catalog of the system. This is normally true of prefix.SDSNLINK; however,
if an alias points to a user catalog when you run DSNALLOC, prefix.SDSNLINK is
cataloged in a user catalog. In this case, you must either ensure that
prefix.SDSNLINK is also cataloged in the master catalog or give
prefix.SDSNLINK a high-level qualifier other than prefix, the
high-level qualifier for this release. You must give a high-level qualifier other than
prefix to all release-sensitive data sets that are placed in the
LNKLSTxx member.
If you do not include the DFSORT library, the Db2 Sort for z/OS library,
or both in the LNKLSTxx member, you must provide a JOBLIB or STEPLIB statement
for all utility jobs that include one of those libraries. You can accomplish this by placing a
STEPLIB statement in DSNUPROC, which appears later in this job. If you use customized modules and
exits, prefix.SDSNEXIT must precede prefix.SDSNLOAD in JOBLIB
and STEPLIB statements.
