IBM Support

OptiConnect/400 Debug Hints

Troubleshooting


Problem

The following are OptiConnect/400 debug hints.

Resolving The Problem

The following are OptiConnect/400 debug hints:


When looking for messages and/or status of connections, check both the client and the host systems.

Collect job logs for both the client job and its associated agent job on the server (host) system.

Identify the direction in which the failure occurs. It is helpful to know if there is a problem on the source system or a problem on the target system. Also determine if the bus owner or a satellite system is failing.



From an operating system command line, type the following:

WRKSBS

Press the Enter key.
Verify the QSOC subsystem is active.
Verify SOC Agent jobs are running - SOCAnnnnnn - (target/server).
If no agent jobs are running, prestart jobs are probably set to none.
Create a transaction, and see if an agent job appears.

On the operating system command line, type the following:

WRKJOB QSOC

Press the Enter key. Review the job log for any messages.

Verify that DDM over a communications line works correctly.

On the operating system command line, type the following (for OptiConnect Connection Manager messages):

DSPMSG QSYSOPR

Press the Enter key. This is a duplicate of the QSOC message queue in V3R1 and V3R6 systems.

On the operating system command line, type the following:

DSPMSG QSOC

Press the Enter key. (Use QSOC for V3R1 and V3R6. After V3R6, all messages go only to QSYSOPR.) Check for error messages.

On the operating system command line, type the following:

DSPLOG QHST MSGID(CPF9167)
MSGCPF9167

See APAR SA50764 for error code and function code meaning in second level help text for MSGCPF9167.

On the operating system command line, type the following:

DSPLOG QHST MSGID(xxxxxx)

where xxxxxx is one of the following message IDs:

MSGCPIADA0 OptiConnect connection manager started at &1.
MSGCPIADA2 OptiConnect connection manager shutdown started at &1.
MSGCPIADA3 OptiConnect connection manager shutdown completed at &1.
MSGCPIADA4 OptiConnect connected to &1 using &5 at &6.
MSGCPIADA5 OptiConnect disconnected from &1 using &5 at &6.

Press the Enter key. These are connection messages. Note the times and who connected to.

DSPLOG QHST MSGID(xxxxxx)

In R310 the messages were as follows:

MSGSOC0001 OptiConnect/400 connection manager started
MSGSOC0003 OptiConnect/400 shutdown started
MSGSOC0004 OptiConnect/400 shutdown complete
MSGSOC0005 OptiConnect/400 connection opened
MSGSOC0006 OptiConnect/400 connection closed

Check the error logs for SRCB60069C1 on the host or client. This entry is not a problem if encountered during an IPL of the host system or the client. If generated during normal operations, a connection was lost.

Check the error logs for SRCB6005209 17 SRC00000710. This SRC follows SRCB60069C1 on the satellite system indicating the host system has gone away. Word 17 indicates IOP 1 on bus 7 timed out on an IPL command. Search the satellite system for VL34000000. If found, save a copy of the LIC log and contact a member of the SLIC I/O development team. An IPL of the satellite system is required. If no matching VLOGs are found, follow OptiConnect data gathering procedures (include IOP OBJECT flight recorder information, if possible). A reset/re-IPL of the IOP from the Hardware Service Manager I/O Debug Screen can be attempted to bring back the satellite system without a re-IPL following the data collection. If the satellite system does not come back after 10 minutes following the re-IPL of the IOP, a system re-IPL of the satellite is required.

To display the resource names, type, status, and system names, on the operating system command line type the following:

WRKHDWRSC *CSA

Press the Enter key.

Use this command if you suspect something is wrong with the physical links (optical cables) between the systems and their adapters.

QSOC/DSPOPCLNK

Press the Enter key. (If the command not found on R310 system, original level of PRPQ is installed). Display the status of the optical links. The HELP for each column on the DSPOPCLNK panels explains how to troubleshoot with this command.

To display the SOC activity and SOC connection status, on the operating system command line type the following:

QSOC/WRKOPCACT

Press the Enter key. Vary On/Vary Off connections from this panel.

Note: There is no adapter RESET function for OptiConnect adapters. RESET is a Bus Manager function.

For R305 through R360, on the operating system command line, type the following:

CALL QSOC/SOCVRFY

Test the SOC connection to the target system pointed to under WRKDDMF (QSOC/SOCDDMF). Change the remote location to the system you want to test the connection to.

For R370, on the operating system command line, type the following:

QSOC/VFYOPCCNN

Command replacement for SOCVRFY. More automated and detects OptiMover systems in the network.
Question: How do I check the mode table entries loaded in the QYYCT MI object?

Answer: If OptiConnect jobs are not being submitted as expected, you can check the QYYCT MI object to see what mode table entries have been loaded. It is possible that the customer changed the mode table without reloading or made a change that requires SBS QSOC to be ended and restarted (for example, changing DFTUSR from *JOBD to *NONE). To determine what mode tables entries are loaded, do the following:
1.On the operating system command line, type the following:

STRSST

Press the Enter key.
2.Select Option 4, Display/Alter Dump, and press the Enter key.
3.Select Option 1, Display Alter Storage, and press the Enter key.
4.MI object
5.Select Option 25, Space, and press the Enter key.
6.Find the object by name.
7.Type . . . . . . . . . : (19) - Space                  
   Name . . . . . . . . . .   QYYCT                        
   Subtype  . . . . . . . .   34   00-FF


Context:
Name . . . . . . . . . .   QSOC                          
   Subtype  . . . . . . . .   01   00-FF
8.Press the Enter key to confirm.
9.Display unformatted data.
10.Type 200 on the control line, and press the PgDn key.
11.The first line should have a T in the column to the right of the hex data as shown:

0200    80000000 00000000      PEA4FC14 FF008260   T   * ...............- *
0210    00000000 00000000      00000000 00000000      * ................ *
0220    00000000 00000000      00000000 00000000      * ................ *
0230    00000000 00000000      00000000 00000000      * ................ *          

Type P  at offset 08  ( as shown in blue ), and press F10.

Note: Clear the control area of the 200.
12.This will bring you to the area where the mode table is loaded in storage. There will be an area reserved for every entry in the mode table. Browse through the eyecatcher area using the page up/down keys to check that the entries here are what is expected.

[{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Communications-SNA","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Historical Number

11781723

Document Information

Modified date:
18 December 2019

UID

nas8N1019701