z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Starting OAM

z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
SC23-6866-00

Before starting OAM for object storage, initialize DB2.

Tip: The system programmer can update the SMS entry in the IGDSMSxx member of PARMLIB to automatically start OAM during MVS IPL.

To start the OAM address space manually, or to restart the OAM address space after it has terminated, enter the MVS START command. The following syntax of the MVS START command starts OAM:

Read syntax diagramSkip visual syntax diagram
>>-+-START-+--+-OAM------+--+-------------+--+------------------+-><
   '-S-----'  '-procname-'  '-.identifier-'  '-,parameter=value-'   

OAM
Name of the IBM-supplied cataloged procedure that invokes OAM.
procname
Name of the user-written cataloged procedure that invokes OAM.
identifier
User-determined name that identifies the OAM address space. If you do not specify an identifier, the system automatically uses the procname as the identifier.

Recommendation: You can include any parameter of the OAM procedure statement in this command to modify the parameter upon activation of the OAM address space. An example of modifying these parameters follows:

START OAM,OAM=XX,OSMC=YES,REST=NO,MAXS=10,EJECT=LRM 

Where xx is the CBROAMxx member of PARMLIB that you wish to have OAM use during initialization.

For details on these parameters, see the discussion concerning modifying and running the CBRAPROC SAMPLIB member in 5h Updating the PROCLIB.

Note: REUSASID=YES must not be specified when starting OAM for object support.
When initializing OAM with OSMC, the system issues the following messages:
CBR0001I OAM initialization starting.
 
CBR0016I Successful processing of the OAMXCF commands in CBROAMxx member of PARMLIB. Initialization continues.
 
CBR0070I OAM XCF member xcf-member-name is the first member defined to
         OAM XCF group xcf-group-name, group successfully defined to
         XCF and member created.
 
CBR0016I Successful processing of the SETOAM commands in CBROAMxx member of PARMLIB. Initialization continues.
 
CBR0016I Successful processing of the SETOPT commands in CBROAMxx member of PARMLIB. Initialization continues.

CBR0016I Successful processing of the SETOSMC commands in CBROAMxx member of PARMLIB. Initialization continues.

CBR0016I Successful processing of the SETTLIB commands in CBROAMxx
member of PARMLIB. Initialization continues. 

CBR0016I Successful processing of the SETDISK commands in CBROAMxx
member of PARMLIB. Initialization continues.

CBR0016I Successful processing of the ONLYIF commands in CBROAMxx member 
of PARMLIB. Initialization continues.
 
CBR9000I OSMC initialization starting.
 
CBR9001I OSMC initialization completed.
 
CBR0002I OAM initialization completed.
Notes about starting OAM:
  1. CBR0016I displays only if OAM=xx is indicated.
  2. If you use a CBROAMxx PARMLIB member to initialize OAM, OAM displays CBR03xxI messages that might be normal for your environment.
  3. You must restart OAM to recognize any changes that were made to the CBROAMxx member of PARMLIB. Additionally, to dynamically change the SETOAM, SETOPT, or SETOSMC parameters, use the UPDATE command. See Using the UPDATE command to set SETOAM, SETOSMC, and SETOPT values for more information.

When initializing OAM without OSMC, the system issues the same messages as when initializing with OSMC, with the exception of messages CBR9000I and CBR9001I.

For further information on these messages, see MVS System Messages.

Related reading:

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014