BCM Data Collection
Please provide the following information.
1 Describe what the user is trying to accomplish.
2 Provide the TSO error messages.
- We need a screen copy of the error messages.
- If there is more than one screen, we need a screen copy of each screen.
- If ISPF is used, it might be possible to display an error message from a previous command from the Exception Message Panel.
3 Describe the steps the user has completed so far.
- Extremely important is a copy of EVERY screen before pressing enter to process the data typed into the screen.
- One way to get a copy of the screen activity is to get the ISPF log dataset.
- Examples of functional steps include DADID definition, route list, Copy group definition, Command Device definition etc.
4 Provide the hardware configuration that the user is trying to define.
- A diagram showing the data flow and the PORTS will be very helpful. The diagram should include the command devices.
- We need the software configuration. We need to know if the user is using SI, TC, TCA, UR, etc.
- If CASCADE is being used, we need to know the relationship of the software being cascaded.
- Is the Remote DKC Function being used?
- What are the volume pairs defined in each one of the software being used?
5 Provide the ISPF log file. ISPF should save the ISPF log to a dataset (ISPF option 0).
6 Provide the BCM log. The method to collect the log depends on the user's installation option.
- If the BCM log is in a user dataset, we need the formatted logs.
- If the BCM log routed to the SYSLOG, we need a copy of the SYSLOG with the BCM messages.
- If BCM is run as a Batch job, we need the JOBLOGS.
7 Provide a list of all the BCM control and XML configuration files for the user prefix. There are six possible types of BCM XML files.
- . prefix.GRP.*
- . prefix.DSK.*.*
- . prefix.ROUTE.*
- . prefix.CDEV.*
- . prefix.PATH.*
- . prefix.CCENTRAL.LICENSE or prefix.user_license_file