Setting up CMCI in a stand-alone CICS region
To use the CICS® management client interface (CMCI) in a stand-alone CICS region (SMSS) without using CICSPlex® SM, you must add the SEYUAUTH and SEYULOAD libraries to the startup JCL of your CICS region and then install URIMAP and TCPIPSERVICE resource definitions.
About this task
When CMCI is set up in a CICS region, you can use it to manage CICS operational resources and CICS definitional resources. See CICS management client interface resource names for a complete list of the operational resources that the interface can manage.
Sample resource definitions are provided for setting up the CICS management client interface. DFH$WUUR is a sample URIMAP definition and DFH$WUTC is a sample TCPIPSERVICE definition. The samples are included in the CICS system definition file (CSD) in group DFH$WU. You can install these resources as they are, or more typically you can copy and modify them to tailor them for your environment. However, you must always specify the URIMAP path as CICSSystemManagement/*. This procedure does not activate security on the interface. For more information about security settings, see Setting up CMCI in a CICS region with active security.
If security is not active, messages that are produced by auditing system programming interface commands contain the default user ID of the region.
Use the following procedure to set up the CICS management client interface by using the samples provided.
Procedure
What to do next
Use CICS Explorer or a browser to check that your setup works correctly.
- Check that the TCPIPSERVICE is OPEN and URIMAP is ENABLED on the stand-alone region. Confirm the port and that the URIMAP references the TCPIPSERVICE with the new name and not the old DFH$WUTC resource that you copied.
- Try to access the URL by using the following request in your browser.
If the browser returns a result, your setup is working as expected.
The CMCI URIMAP responds only to requests for URLs that begin as follows:
/CICSSystemManagement/: http://hostname:port/CICSSystemManagement/CICSTask/ - Check for any SMSS related messages on the region job log, for
example:
EYUXL0022I xxxxxxxx SMSS Phase I initialization complete EYUXL0007I xxxxxPhase II initialization complete EYUNL0099I xxxxxxxx SMSS LRT initialization complete - Check for any installation errors in both the job log and the MSGUSR log.
- Try to connect CICS Explorer to the CMCI port to check whether that connection works.
You must define the following transactions to RACF®, or an equivalent external security manager, and ensure that CMCI users are authorized to
access the transactions: CODB, COD0, COD1, COD2, COSH, COLU, CWWU, and CWXN.