Basic troubleshooting procedure

If you encounter problems when using OptiConnect, follow this procedure to find out why you are having difficulties. In general, it may be helpful to try the same DDM transaction over a communication link (LAN, for example). If no error occurs, follow the steps below to determine where OptiConnect is failing. If the error still occurs, the problem is not likely to be OptiConnect.

If all OptiConnect DDM accesses are failing, check the following:

1. Check to ensure that the system-to-system connections are operational by using the Work with Hardware Resources (WRKHDWRSC) command. Enter:

   WRKHDWRSC TYPE(*CSA)

   For more information on this command, see Work with hardware resources (WRKHDWRSC).
2. Check to ensure the cables are operational using:

   DSPOPCLNK

3. Verify that QSOC subsystem is running on both the application systems and the database system by entering the following command on both:

   WRKACTJOB SBS(QSOC)

4. Verify that the SOCMGR job is running in the QSOC subsystem. If the QSOC subsystem is not running, start it. If the subsystem is running, but there is no SOCMGR job, either the SOCMGR job has been ended, or a software failure has occurred. Locate the job log that is associated with the SOCMGR job by entering:

   WRKJOB QSOC

   Display the log to determine why the SOCMGR job ended. Report software failures by contacting your service provider.
5. Verify that the OptiConnect Connection Manager has established communications between the source and target systems. Each time a connection is opened or closed, a message is sent to the system operator message queue. Connections are closed when the QSOC subsystem has ended, the SOCMGR job has ended, a system is powered off, or a failure occurs. To display the system operator messages, enter:

   DSPMSG MSGQ(*SYSOPR)

   Otherwise, use the following command to select a particular time period:

   DSPLOG LOG(QHST)

   Note:
   To see only QSOC messages, use DSPMSG QSOC.
6. Check to ensure that the QSOC job queue is not held. Enter:

   WRKJOBQ JOBQ(QSOC/QSOC)

7. Verify that the correct remote location name, device, and mode are defined in the DDM file used for OptiConnect. See Configure OptiConnect.

Follow these steps if you suspect a problem with a particular application:

1. Locate the failing job or job log on the source system.
2. Display the job log information and find this message:

   DDM JOB STARTED ON REMOTE SYSTEM

3. Use F1 to display the detailed message text. The detailed message text shows the OptiConnect agent job name.
4. Locate the agent job on the target system.
5. Inspect the job log information for both the application and agent jobs to locate any unexpected errors.
6. If MSGCPF9167 is encountered, see OptiConnect error messages for more information on communications messages.