Submitting a batched repository-update (BATCHREP) job

You can create, update, remove, or review multiple definitions in the data repository by submitting a batched repository-update (BATCHREP) job in CICS Explorer®.

Before you begin

Before submitting a BATCHREP job, you must have an input file and a data set or partitioned data set member to contain it. See Submitting a batched repository-update (BATCHREP) job in CICS® TS documentation.

You must connect to a WUI server of a CICSplex through a CMCI connection. Single CICS region (SMSS) or SM Data connections are not supported. To apply updates to a particular data repository, ensure that your WUI server is connected to the CMAS that is associated with the data repository you want to update.

Procedure

  1. Open the Perform Operation dialog in either of the following ways:
    • In the SM Administration perspective, click Definitions > Submit Batched Repository-Update Job from the menu.
    • In the CICS SM perspective, navigate to the CICSplex Repositories view and click the Submit Batched Repository-Update Job icon (Submit BATCHREP Job icon) on the toolbar.
  2. In the Perform Operation dialog, enter the following information:
    Data Set Name
    Specify the name of the sequential or partitioned data set (PDS) containing the input to the batched repository-update job. The drop-down list stores the last 10 values submitted.
    Member Name
    When using a PDS, specify the name of the member that contains the input to the batched repository-update job. If your CICS Explorer is connected to a z/OS® connection, the drop-down list shows available members for the specified data set, prioritizing any that you previously used. If your CICS Explorer does not have a z/OS connection already, you can connect to or define one in the Connection field: The Connection field in the Perform Operation dialog.
    Print Class
    Optional. Specify a 1-character class designation. If not specified, class A is used.
    Print Node
    Specify the 8-character identifier of a designation node that the system spooler is to use to route the file.
    Destination User ID
    Specify the 8-character identifier of the eventual writer program or of the user who will process the report for spooled records that are intended for the printer. The report will carry this identifier, which will be used to select the report at its destination.
  3. If you want to check the command format of all the input statements of the batched repository-update job instead of executing it, select the Dry run checkbox.
  4. Click OK to submit the job.