Using CMCI to update a resource definition

Update a BAS or CSD resource definition using the CICS Management Client Interface (CMCI).

Before you begin

You must have a connection with the CMCI; for more information, see Setting up access for CICS Explorer.

About this task

Complete the following steps to update a resource definition using the CMCI:

Procedure

  1. Use a PUT request to update a resource definition.
    For more information about PUT requests, see CICS management client interface PUT requests.
  2. Specify the URI for the request.
    • If you are updating a BAS resource and you specify a SCOPE in the URI, it is ignored.
    • If you are updating a CSD resource, specify the SCOPE and PARAMETER=CSDGROUP(value) in the URI.
    For more information about specifying the URI for a PUT request, see CICS management client interface PUT request URI.
  3. Add an XML body containing the parameters and attributes for the resource.
    The XML body comprises an <update> element inside a <request> element.
    • If you are updating a BAS resource, you must include a defver attribute in the XML body.
    • If you are updating a CSD resource, you must specify a CSD group attribute in the XML body. Do not include a defver attribute if you are creating a CSD resource.

Example

The following example shows you what to specify to update a BAS transaction definition. In this example, the value of the program name for transaction definition, TRN1, is updated to PRGM2.
PUT http://exampledomain.com:12345/CICSSystemManagement/
    CICSDefinitionTransaction/<CONTEXT>/
    ?CRITERIA=NAME%3TRN1

<request>
   <update>
      <attributes program="PRGM2"/>
   </update>
</request>
The following example shows an update request for a CSD transaction definition. In this example, the program name of the resource called TRN1, in resource group GRP1, is updated to PRGM2. Note that PARAMETER=CSDGROUP is added to the URI and that the defver attribute is excluded.
PUT http://exampledomain.com:12345/CICSSystemManagement/
    CICSDefinitionTransaction/<CONTEXT>/<SCOPE>/
    ?CRITERIA=NAME%3DAAAA&PARAMETER=CSDGROUP%28GRP1%29 

<request>
   <update>
      <attributes program="PRGM2"/>
   </update>
</request>
Both the examples, updating a resource definition and updating a CSD resource definition, return a similar output when they complete successfully. A successful update returns a CICSPlex SM API response message that contains api_response1="1024" and api_response1_alt="OK" as shown:
<response xmlns:...>
   <resultsummary api_response1="1024" api_response1_alt="OK".. />
   <records>
         ...
   </records>
</response>