Detailed below is a set of steps that can be used to diagnose an issue with one or more probes:
- On the LPAR: Cycle the Ironstream started task.
-
In ServiceNow, turn on logging
for the probes as follows:
- Under Ironstream Mainframe Discovery, click the Mainframe Probes, the screen will show a list of the Ironstream probes. These probes are organized under DB2, CICS, LPAR, IMS and MQ category and logging is turned off by default.
- On this Mainframe probes list, you can configure the logging of any probe to be true or false under the Logging column of the probe list. Only probes with the Logging option set to true will be included in the discovery logging process.
- Logged information can be found in System Logs -> Application Logs. All logged messages will be prefixed with the string "ET Logger".
-
On the LPAR: turn on the debug diagnostics on Ironstream Started Task Control using these commands:
F taskname,SHOW FLOW
F taskname,DEBUG TCP-0 3
F taskname,DEBUG SMF 3
F taskname,DEBUG CMD-0 3
- In ServiceNow: Run the Quick Discovery on the probes with their logging option set to true.
-
On the LPAR: perform this every 10 minutes:
F taskname,SHOW FLOW
- Wait for up to 30 minutes, if the discovery does not complete then cancel it.
-
On the LPAR: Turn off the debug diagnostics:
F taskname,SHOW FLOW
F taskname,DEBUG TCP-0 0
F taskname,DEBUG SMF 0
F taskname,DEBUG CMD-0 0
- On Service Now: turn off logging for the probes.
- On the LPAR: Cycle the started task.
-
Review this and send to Support if necessary:
- From ServiceNow Instance:
- ECC Queue Log
- Discovery Queue Log
- Log messages from the ServiceNow Application Log
- From the Ironstream Proxy Server:
- The contents of the log folder in the install path on (default location: C:\Program Files\EView Technology\EView390z).
- From the LPAR:
- Job log from the Ironstream STC from the mainframe used during the test.
- From ServiceNow Instance: