Reporting a problem to IBM
Before reporting a problem with CICS® Configuration Manager to IBM® support, gather the following information:
- Version, release, modification number, and details of applied
maintenance (such as PTF numbers) for:
- CICS Configuration Manager
- CICS Transaction Server
Typically, there are several instances of CICS Transaction Server involved:
- The instance running the CICS Configuration Manager server.
- The instances associated with the CICS configurations.
Figure 1. Example usage involving several instances of CICS Transaction ServerEach instance of CICS Transaction Server involved could be at a different release. For example, you could be using CICS Configuration Manager to migrate resource definitions between CICS configurations that are associated with different releases of CICS Transaction Server. And both of these could be at different releases than the CICS Transaction Server that is running the CICS Configuration Manager server. In this case, you need to gather the details for three instances of CICS Transaction Server.
- Which CICS Configuration Manager interface you were using (batch or ISPF)
- A brief description of what you were doing at the time of the
problem, including:
- The JCL for the batch command
or
- The ISPF panel that you were using (use the ISPF command PANELID to get the panel identifier), with input field values.
- The JCL for the batch command
- The keys (names) of the objects that you were working on. For
example:
- Resource definitions (names, types, and groups)
- CICS configurations Important: For each CICS configuration, note the associated CICS Transaction Server release level, and also whether the CICS configuration refers to a CSD file or a CICSPlex® SM context.
- Change packages
- Migration schemes
- Extracts from the following CICS Configuration
Manager server SYSOUT output
file ddnames:
- CCVLOG
- CICS Configuration Manager messages
- CCVPRINT (batch only)
- CICS Configuration Manager batch interface output
- JESMSGLG
- MVS™, VSAM, and RACF®
- CEEMSG
- Language Environment®
- If possible, the XML of the CICS Configuration
Manager API command and
response. Tip: To capture the XML that is transferred between the server and the ISPF dialog interface, open the pull-down menu and set XML print on.
- The effect of the problem on your workflow, including details of any workaround that you use.
- If available, a CICS system
dump. If you have a re-createable problem that either produces a CICS system
dump, or for which a CICS system dump can be captured,
please ensure SPECIAL tracing is enabled for transaction CCVA. Even
when CICS tracing is active, CICS suppresses trace records for
CCVA, so that the system dump is missing data vital to problem determination.
To activate special tracing:
- Sign on to CICS
- Run transaction CETR
- Press F5 (ter/trn)
- In the Transaction ID, enter CCVA
- In Transaction status, enter SPECIAL
- Press F3 to return to the CETR menu, but do not exit CETR (that would cancel the special trace request)
- Run the failing process and capture the system dump
- Now exit CETR