Debugging Endevor with IDz CARMA session
Article ID: 373375
Updated On:
Products
Issue/Introduction
IDz user could list elements and connect to Endevor but when trying to edit an element in stage for example P, the Environment drop down in IDZ where you select which environment to edit the element in only contained corresponding environment for example PROD.
The other environments are missing in the drop down list.
How to debug this issue and what logs could be collected when a problem happens in IBM Developer for z/OS (IDz) and its integration with Endevor?
Environment
Components: Endevor, IBM IDz CARMA.
Version: All
Resolution
Collect sysouts and traces from the user IDz session:
-> Check guideline from IBM Article "What are the mustgather for IDz when integrating with CA Endevor® SCM"
Here is what needs to be collected and the instructions to collect:
From IDz client Interface:
- Start IDz and Select menu Window > Preferences > Tracing and set the following properties to FINEST: carma.endevor.ui, com.ibm.carma.client, com.ibm.carma.ui, com.ibm.carma.ui.ftt
- Reproduce the problem
- Send to the support team the file <your workspace>\.metadata\.trace
From Server on z/OS:
Note:
Trace level needs to be enabled on the IDz client CARMA connection. Warning -> Level can be changed only when disconnected
Right-click on your CARMA connection
Select menu Properties and select Trace level "Debug"
Both the CARMALOG and the MSG3FILE is very important to help with those issues, make sure they are both allocated and output to dataset or sysout.
- The CARMALOG shows the invocation of the Endevor API, but it does not show the command that was sent to the API.
- The MSG3FILE shows what API calls were made to Endevor.
- The MSG3FILE is produced by Endevor and the CARMALOG is produced by CARMA.
If you need further assistance to identify the root cause of issue, open a case to Broadcom support.
Additional Information
Feedback
