Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Changing system libraries z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries SC23-6867-00 |
|
After using SMP/E to install z/OS, change the system libraries using the following procedures. 2 Update PARMLIB. 2a Update IGDSMSxx PARMLIB member. Update the IGDSMSxx PARMLIB member to include the following
OAM-related keywords:
These optional parameters are used when you want the OAM address space to start automatically as part of SMS initialization. "OAM" can be used as the procedure name, the task identifier, or both. Note: For examples of the OAM START command and more information concerning
the identifier parameter, see Starting OAM. For more information on the START command, see z/OS MVS System Commands. Also, for more details concerning
these optional parameters and other keywords associated with the IGDSMSxx PARMLIB member, see z/OS DFSMSdfp Storage Administration.
2b Update IEFSSNxx PARMLIB member. Add or update the OAM1 entry in the IEFSSNxx PARMLIB member.
where:
OAM1 is the name of the subsystem, and CBRINIT is the name of the initialization module executed at IPL time. Rule: The SMS subsystem
must be started before the OAM1 subsystem is started, therefore ensure
that the SMS entry precedes the BEGINPARALLEL keyword in the IEFSSNxx parmlib member. The OAM1 subsystem entry
in IEFSSNxx can then follow the BEGINPARALLEL
keyword. If the BEGINPARALLEL keyword is not being used, you must
still ensure that the SMS subsystem entry precedes the OAM1 subsystem
entry. The OAM1 entry defines the OAM1 subsystem. To prevent a possible
system abend, ensure that the subsystem name in the IEFSSNxx member is different from the name of the PROCLIB
member used to start OAM.
Note: You can add the OAM subsystem without re-IPLing the system by
using the SETSSI ADD,S=OAM1,I=CBRINIT command. After the OAM subsystem
is started, OAM will ignore any further updates made by subsequent
SETSSI commands. See z/OS MVS System Commands for information on using the SETSSI command.
2c Update CONSOLxx PARMLIB member. To define a library console to MVS that allows console name message
routing, perform the following steps:
See z/OS MVS System Commands and z/OS MVS Planning: Operations for further information regarding multiple console support (MCS) definitions. 2d Update DEVSUPxx PARMLIB member. Normally, when a scratch volume recorded in higher-level recording format is mounted on a drive that that supports the media type but not the higher-level recording format, the operating system rejects the mounted volume and asks for another volume to be mounted. This is because the data set labels on the volume cannot be read and validated. If you want the volume to be used, create a DEVSUPxx member of PARMLIB and specify VOLNSNS=YES. If you are partitioning an ATLDS, use the DEVSUPxx library partitioning-related parameters to change the system default category assignments. See z/OS MVS Initialization and Tuning Reference for more information regarding DEVSUPxx. To take advantage of nonspecific (scratch) mount performance in a Virtual Tape Server (VTS) or a Peer-to-Peer VTS, remember to set the Fast Ready attribute at the library manager for the scratch categories to be used. This includes the system default scratch categories and any user-defined scratch categories to be used for partitioning the library. For the capability to share MTL devices as stand-alone, see Manual tape library considerations for potential usage of the MTLSHARE keyword. 2e Create or update CBROAMxx PARMLIB member (optional; used with the SETTLIB command) You must perform this step if you intend to use the SETTLIB (set tape library) command statement in the CBROAMxx PARMLIB member to tune your tape library environment. Previously this PARMLIB member had only been used with OAM's object support. This CBROAMxx member is invoked using the OAM=xx parameter in the OAM member of PROCLIB and is processed during OAM address space initialization. You must create or update the CBROAMxx member to use the optional SETTLIB support. The CBROAMxx member may already be used with OAM's object support. If so, SETTLIB is an additional command statement that can be used for tape library processing. If you do not specify specific parameters, the defaults are used. You can include the CBROAMxx PARMLIB member in any data set that is specified in the concatenation list in SYS1.IPLPARM(LOADxx). For information about using the SETTLIB command in the CBROAMxx PARMLIB member, see SETTLIB statement for tape library settings and ONLYIF statements in a PLEX. SETTLIB statement for tape library settingsThe SETTLIB statement and its associated keywords of the CBROAMxx PARMLIB member can be used to override the default behavior for some of the main cartridge entry messages in a system managed tape library environment. The SETTLIB command statement and keywords are processed when the OAM address space is started and cannot be updated by operator command. The syntax for the SETTLIB statement follows. SETTLIB statement syntax >>-SETTLIB--+------------------------------+--------------------> '-ENTRYIGNOREMSGTYPE(msg_mode)-' >--+-------------------------------------+----------------------> '-ENTRYIGNOREMSGDEST(msg_destination)-' >--+--------------------------------------+-------------------->< '-ENTRYSUCCESSMSGDEST(msg_destination)-' SETTLIB statement keywords: The keywords for the SETTLIB
statement are:
ONLYIF statements in a PLEXThe ONLYIF statement can be used to specify whether or not specific statements within the CBROAMxx PARMLIB member are to be processed on a given system. The scope of the ONLYIF statement is in effect until the next ONLYIF is encountered. The syntax for the ONLYIF statement follows. ONLYIF statement syntax >>-+---------------------------------------+------------------->< '-ONLYIF-+----------------------------+-' | .-*ALL*-------. | '-SYSNAME(-+-system_name-+-)-'
|
Copyright IBM Corporation 1990, 2014
|