Creating and maintaining CICSPlex SM definitions

To create, update, remove, or review CICSPlex SM definitions in the data repository, use one or more control statements.

Control statements take the form:

   command object keyword1(value) keyword2

where:

command

Is the name of a batched repository-update facility command, in uppercase letters. Specify one of the following:

CREATE

To create a record and add it to the data repository associated with the local CMAS.

UPDATE

To update an existing record in the data repository.

Note: You cannot update LNKSxSCG records using the batched repository-update facility, although you can do so through the WUI.

REMOVE

To remove an existing record from the data repository.

When you remove a record, all associations between that record and other records in the data repository are lost. For example, if you remove a CICS® system definition, associations between that CICS system and any CICS system groups or component specifications are also removed.

When removing BAS definitions the DEFVER( ) keyword must be specified.

LIST

To list a record from the data repository.

DUMP

To list a record from the data repository and insert a CREATE control statement in front of it.

You can use the output resulting from a DUMP command as input to another batched repository-update job that creates definitions. The output of a DUMP command is formatted as follows:

Data lines are broken at column 72
Continuation characters are placed in column 1.

By default, the output is written to a spool file and must be extracted from the spool, and edited, before it can be used as input to the batched repository-update facility. The extracted records contain ANS control characters in column 1, therefore you must shift the records one character to the left to align the data for processing by CICSPlex SM. You must also remove all the page header information from the data set. For an example of a listing, see Figure 1. However, you can use the OUTPUT command to write the output in the correct format, direct to a data set. For details, see Creating a data set for re-input to the batched repository-update facility.

CICSPlex SM requires certain definitions to exist before others can be created. Therefore, you should adhere to the following guidelines when dumping data repository records:

Always dump CICS system (CSYSDEF) and CICS system group (CSYSGRP) records first.
Dump basic CICSPlex SM definition records (such as, xxxDEF, xxxGROUP, and xxxSPEC) before association records (such as, LNKxxxxx, xxxINGRP, or xxxINSPC).
For Business Application Services:
- Dump RESGROUP records before RESDESC and RASGNDEF records.
- Dump RESDESC and RASGNDEF records before RESINDSC and RASINDSC records.
- Dump resource definition records (such as FILEDEF) before xxxINGRP records (such as FILINGRP).
- Dump CONNDEF, SESSDEF, IPCONDEF, and TCPDEF records before SYSLINK records.

If you follow these guidelines, the output from a DUMP command is in the correct order for the batched repository-update facility to create new definitions. For an example of using the DUMP command output to create new definitions, see Examples of managing records in the data repository.

Note: Output from the DUMP and LIST commands contains a visible record of any passwords associated with CICS resources (such as connections or files). To prevent possible security exposures, you should restrict access to such output.

object

Is one of the resource table names shown in Table 1.

keyword1(value)

Is the name of a field in the specified resource table and the data that is appropriate for that field, in uppercase letters. The required input for the various commands is as follows:

CREATE: Provide all of the information required to define the resource, for example the same type of information as required by the equivalent WUI Create view.
You can derive the input to the CREATE statement from the output of a DFHCSDUP EXTRACT or BATCHREP DUMP request. See Creating a data set for re-input to the batched repository-update facility, Example 6 - Dumping records as input to create new records for further information. If you do not create your input in this way, you must specify all the required attributes.
Note: For some definition records you should not specify certain operands; for example, for CPLEXDEF, do not specify the STATUS operand.
UPDATE: Identify the specific record to be updated. For CICS resource definitions created as part of business application services (BAS), this must include the version (DEFVER) of the resource. Specify the attributes that will be updated.
REMOVE: Identify the specific record to be removed. For CICS resource definitions created as part of business application services (BAS), this must include the version (DEFVER) of the resource.
LIST and DUMP: Provide a specific or generic record name, where generic names can contain the plus sign (+), asterisk (*), or both.

keyword2

Indicate how the creation or removal of a specification-to-CICS system group link record (LNKSxSCG) should affect the current members of the CICS system group. The keywords for the CREATE and REMOVE commands must be entered in uppercase letters and are as follows:

CREATE

Specify one of the following:

FORCE: All current members of the CICS system group should have implicit links established to the named specification. When a link already exists, it is replaced with the newly CREATEd link.
NULL: Current members of the CICS system group should have implicit links established to the named specification only if no link already exists.
NONE: No implicit links should be established.

When you use the CREATE command, the default value for keyword2 is NONE

REMOVE

Specify one of the following:

KEEP: All implicit links are to be converted to explicit links.
NONE: No implicit links are to be converted to explicit links.

There is no default value for keyword2 when you use the REMOVE command; you must specify a value.

When you submit the batched repository-update job, the syntax of each command is checked for validity. If multiple commands are being issued, syntax checking can have the following results:

When a LIST, DUMP, MAPLEFT or MAPRIGHT command is invalid, that command is not executed; processing of all subsequent commands continues .
When a modification command (CREATE, UPDATE, or REMOVE) is invalid, that command is not executed. All subsequent modification commands are checked for validity; however, no subsequent modification commands are executed.