Running discovery and loading the system model
You can also use the CICS DA API to call the discovery function. For more information, see The CICS DA API.
Note: CICS DA saves a local copy of the model in the CICS Explorer workspace on your computer. This model contains information about your environment and your systems, and it is advised that you secure the information, according to your company's security procedures, to prevent unauthorized access.
About this task
When you initiate discovery, the CICS DA server starts a number of discovery tasks. The first discovery task is to identify all the MVS™ images in the sysplex. The discovery tasks then look at the regions that are running on each selected MVS image and identify supported releases of CICS, other running subsystems, and any Authorized Cross-Memory (AXM) servers. The discovered resources are then further analyzed, and any associated resources and logical system information, such as connections, are identified and the model is created in the server. The discovery might take a long time, depending on the number of MVS images in your sysplex and the number of subsystems discovered. However, you can continue to view a model that you previously loaded while the discovery tasks are running, but you cannot change the model.
When discovery runs on an MVS image, the names of the TCP/IP stacks are queried to obtain the primary IP address of those stacks. The z/OS UNIX System Services host service is used to query the domain name server and resolve the IP address to a name. If a name is returned, this name is passed to the CICS DA server. If no name is returned, then the IP address is not passed to the CICS DA server.
Because this part of the discovery process runs on the MVS image, the name for the primary IP address might be a locally administered name that is not visible to the client. If that is the case, then the client might need to have its TCP/IP configuration altered; for example, by altering the client hosts file, to allow the client to use the host names that the discovery process adds to the model.
For CICS regions that are run as started tasks, the CICS DA discovery operation attempts to generate a start policy. CICS DA does not attempt to generate a start policy for CICS regions that are run as batch jobs. The discovery operation must have read access to the JES output queue. If successful, the generated CICS region start policy is stored in the local model. This generated start model can then be displayed and used to start the CICS region.
- CICS Coupling Facility Data Table (CFDT) servers
- CICS named counter servers
- CICSplexes
- CICSPlex® SM WUI servers
- CICS regions (managed and unmanaged)
- CICS system groups
- CICS temporary storage servers
- CICS Transaction gateways
- CMAS networks
- CMASs
- DB2®
- IMS™
- MVS images
- RTA specifications
- WebSphere® MQ
- WLM specifications
- z/OS systems
This task initiates a discovery operation on the CICS DA server and loads the model into the CICS DA client. You must have an active CICS DA connection before you can initiate discovery.
Procedure
Results
If you have a local model, when you click Finish CICS DA deletes the local model. The new model is then loaded into your local workspace and is shown in the connection navigation tree in the DA Explorer view.
