Start of change

Using the batched repository-update utility

The batched repository-update utility connects to a CMAS and submits batched repository updates to run in that CMAS. To make batched repository updates to a particular data repository, you need to run the utility so that it connects to, and submits batched updates to run in, the CMAS that is associated with the data repository you want to update.

In order to run the utility you need to prepare the necessary JCL and to define input parameters for the utility itself, such as the name of the CMAS associated with the data repository you want to update.

Here is an example of JCL to run the batched repository update utility:

  //jobname  JOB (acct),'name',CLASS=x,MSGCLASS=x
  //BTCHUPD EXEC PGM=EYU9XDBC,REGION=2048K
  //STEPLIB  DD  DSN=CICSTS31.CPSM.SEYUAUTH,DISP=SHR
  //         DD  DSN=CICSTS31.CPSM.SEYULOAD,DISP=SHR
  //SYSPRINT DD  SYSOUT=*
  //SYSABEND DD  SYSOUT=*  
  //SYSIN    DD  *
  CMASNAME(EYUCMS1A)                                         
  CHECK                                                      
  INPUTDSN(EXAMPLE.INPUT.DATASET)     
  INPUTMEMBER(MEMBER1)                                       
  OUTPUTUSER(EXUSER)   
  PRINTNODE(LOCAL)                                           
  /*

Here is an example of the output from the batched repository-update utility:

 CICSPlex/SM Batched Repository Update Utility                  Version 310  
                                                                          
        Parameters specified: 
                         
        CMASNAME(EYUCMS1A)                               
        CHECK                             
        INPUTDSN(EXAMPLE.INPUT.DATASET) 
        INPUTMEMBER(MEMBER1) 
        OUTPUTUSER(EXUSER) 
        PRINTNODE(LOCAL)
  
        
EYUXD0908I  A batched repository update has been submitted to run in CMAS EYUCMS1A. 

The output of the batched repository-update utility is a short report that lists the input parameters and a message to show the CMAS in which the batched updates have been submitted. You should review this output to verify the utility successfully submitted the batched updates in the CMAS.

The batched updates that run in the CMAS produce output using the standard CICS spooling facilities. You need to review this second output to verify batched updates have run successfully.

Start of change

Batched repository-update utility parameters

This section describes the input parameters that you must specify to use the batched repository update utility. These parameters must be supplied in the SYSIN data set.

The following syntax rules apply:

Read syntax diagramSkip visual syntax diagram>>-CMASNAME(data-value)--+-CHECK---+--INPUTDSN(data-value)------>
                         '-EXECUTE-'
 
>--+-------------------------+--+------------------------+------>
   '-INPUTMEMBER(data-value)-'  '-PRINTCLASS(data-value)-'
 
>--PRINTNODE(data-value)--OUTPUTUSER(data-value)---------------->
 
>--+------------+----------------------------------------------><
   +-DIAGNOSE---+
   '-NODIAGNOSE-'
 

The parameters can be specified as follows :

CMASNAME
specifies the 1-to-8 character name of a CMAS to which the utility is to connect and whose data repository is to be modified by the batched repository update processing. This parameter is mandatory. It is this CMAS in which batched repository update processing takes place and from which output is produced by the CICS spooling facilities.
CHECK or EXECUTE
must be specified for the type of run. CHECK specifies a syntax check of the input file and EXECUTE specifies the commands in the input file that must be executed. These keywords are mutually exclusive.
INPUTDSN
specifies a 1-to-44 character string for the dataset name of a sequential dataset or a PDS that contains the input to the batched repository update processing. The CMAS must have access to the dataset specified via the INPUTDSN parameter. This parameter is mandatory.
INPUTMEMBER
specifies a 1-to-8 character name of a member when using a PDS that contains the input file. This parameter is optional.
PRINTCLASS
specifies a 1-character print class identifier. This parameter is optional. The default is A.
PRINTNODE
specifies a 1-to-8 character print node identifier to be used by the system spooler for routing the job output. This parameter is mandatory.
OUTPUTUSER
specifies a 1-to-8 character user identifier to be associated with the spooled output. This parameter is mandatory.
DIAGNOSE
intended for use only under guidance by IBM service personnel.
NODIAGNOSE
intended for use only under guidance by IBM service personnel.
End of changeEnd of change [[ Contents Previous Page | Next Page Index ]]