Troubleshooting
This troubleshooting information can help you diagnose some common installation problems. For most situations, start troubleshooting by running the procedures in Milestone-7-Verify-Product-Installation and checking the log for any diagnostic messages describing errors.
Typical Errors
U123 Abend Encountered
Indicates the VTAM release is not supported by Performance Test Global Record.
Suggestions
Either go to BMC Support Center or contact BMC Customer Solutions to determine if there is a PTF available for Performance Test to support the VTAM release.
If the VTAM release is not GA, contact BMC Support.
S047 Abend Encountered
The Performance Test load library, SQQFLOAD, in not APF authorized.
Suggestion
Make the Performance Test load library, SQQFLOAD, APF authorized.
Error Message “SVMAN388E NOT LICENSED FOR MQSERIES SUPPORT” or “SVMAN389E NOT LICENSED FOR TCP-IP SUPPORT” in Global Record Started Task
Indicates that the installation is not licensed to record MQ and/or TCP/IP data.
Suggestions
- Either remove or comment out the MQ_QUEUE_MANAGER_NAME and/or TCPIP_JOBNAMES in the PARMLIB member for Performance Test. Refresh PARMLIB and restart the global record started task.
- Ensure that the licenses for Performance Test for WebSphere MQ and/or Performance Test for Mainframe Servers have been added to LMS subsystem for the LPAR.
Informational Messages “SVMAN601I GLOBAL RECORD SUBSYSTEM IS ALREADY ACTIVE” and “SVMAN602I IT MUST BE SHUTDOWN FOR A START UP TO TAKE PLACE”
There can only be one global record started task running at a time on an LPAR. This can happen when there are production and test global record started tasks.
Suggestion
To avoid this error, add the following to all global record started tasks in the LPAR:
//ENQUEUE DD DSN=MY.EMPTY.DATASET,DISP=OLDThis will provide an exclusive lock on the data set MY.EMPTY.DATASET. If one of the global records is running, the other global record job will not run until the one currently running has been brought down.
Global Record Shuts Down Immediately
This can occur when either there are errors on the initial refresh of the Performance Test PARMLIB member or Performance Test is not configured to record any technology.
Suggestions
- Ensure there are no errors with any of the parameters in the Performance Test PARMLIB member by checking the output of the CMSC job. Correct any issues and refresh the Performance Test PARMLIB member.
- Edit the PARMLIB member for Performance Test. Ensure that at least one of the following is in the PARMLIB member:
- TCPIP_JOBNAMES
- MQ_QUEUE_MANAGER_NAME
- ENABLE_3270=YES
- ENABLE_APPC=YES
- ENABLE_LU0=YES
Message “VTAM SETUP PROBLEM” in Domain Traveler
Domain traveler could not connect to the domain destination.
Suggestions
- Correct the LU name value on the Session Options panel.
- Ensure the value for VIRTUAL_TERMINAL_PREFIX is correct in the Performance Test PARMLIB member. Correct any errors and refresh the Performance Test PARMLIB member.
- Ensure the virtual terminal is defined (or can be autoinstalled) to the domain destination being connected.
Changes to Performance Test PARMLIB Member Not Taking Effect
Suggestions
- Perform a refresh on the Performance Test PARMLIB member in the CMSC job.
- Check the CMSC job to ensure there were no errors during the refresh. Correct any errors and refresh the Performance Test PARMLIB member.