Performing an action against a resource

In addition to modifying individual attributes, you can also perform actions against many resources by using either of the PERFORM commands; PERFORM OBJECT or PERFORM SET.

The difference between these two commands is that PERFORM SET performs an action against the resource table records in an existing result set, while PERFORM OBJECT first creates a result set and then performs the requested action.

Some actions are self-contained and self-explanatory; specifying the action is enough to indicate the changes to be made to the resource. For example, you can discard a local file by issuing the DISCARD action against a LOCFILE resource table record.

Other actions require you to specify additional parameters. For these actions you might require a parameter expression to obtain the function you need. A parameter expression can be made up of one or more parm expressions in the form:
Read syntax diagramSkip visual syntax diagram
Parameter Expression

   .-------------------------.   
   V                         |   
>>-----| parm_expr |--+----.-+---------------------------------><

parm_expr:

|--+-| parm_name |--------+--+----------------------------------|
   '-.--| parm_value |--.-'      

where:
  • parm_name is the name of a parameter associated with the action.
  • parm_value is the value associated with the specified parameter name, if applicable.
Multiple instances of parm_exp should be delimited by spaces. The parameter expression buffer is terminated with a period (.).

Examples

  • To disable a local file (LOCFILE), you must indicate how to handle a file that is currently busy. To do that, you could specify the following parameter expression:
    PARM('BUSY(cvda).')
    where cvda is a valid CVDA value for the file busy condition, for example WAIT, NOWAIT or FORCE.
  • To request a dump of a CICS® region (CICSRGN) specifying the dump code and title of the dump, you could use the following parameter expression:
    PARM('DUMPCODE(PMR12345) TITLE('Doc for PMR12345').')
    Note that if the parm_value contains special characters such as spaces or periods, the value must be enclosed in single quotes. Also note that all parameter values are folded to upper case.

If you issue a PERFORM command against CICS systems that do not support the requested action, the request is ignored for those CICS systems. If your context and scope consist solely of CICS systems that do not support the action, you receive RESPONSE and REASON values of NOTAVAILABLE SCOPE.

The PERFORM OBJECT command does not require an existing result set, as it will effectively run a GET command followed be a PERFORM SET. In this case any parameter expression may be passed on the GET or PERFORM SET phase of the command depending on whether the parameter expression is valid on the GET or PERFORM SET as follows:
  • If the parameter expression is valid for GET it is used on the GET phase of the PERFORM OBJECT command
  • If the parameter expression is valid for PERFORM it is used on the PERFORM SET phase of the PERFORM OBJECT command.
  • If the parameter expression is valid for GET and PERFORM it is used on the GET and PERFORM SET phases of the PERFORM OBJECT command. This rule may mean that some actions are not possible via PERFORM OBJECT. Instead separate GET and PERFORM SET commands may be required to achieve the intended results.
  • If the parameter is not valid for GET or PERFORM, then an INVALIDPARM PARM condition will be raised.

For a list of the valid actions for each resource and their required parameters, see CICSPlex SM resource tables.



eyup1bg.html | Timestamp icon Last updated: Sunday, 4 June 2017