Troubleshooting
Problem
This document will describe when the SNADS receiver job fails with a CPF4059 rc08640000.
Resolving The Problem
Problem:
SNADS from one system to another does not work. Distribution queue at the source goes to RETRY-WAIT (or RETRY-FAIL) status.
Action Taken:
| 1. | HOLD the distribution queue at the source system. At an OS/400 command line, type WRKDSTQ, and select Option 3 next to the distribution queue in status of RETRY-WAIT (or RETRY-FAIL). |
| 2. | From the Work with Distribution Queues screen, select Option F10. From the Configure Distribution Queues screen, select Option 5 to display the distribution that is in a RETRY status. Copy down the Remote Location parameter. |
| 3. | At an operating system command line type, WRKACTJOB SBS(QSNADS) and search for the SNADS sender job. It will have the same name as the Remote Location parameter copied in Step 2. From the Work with Active Jobs screen, select Option 4 to end the sender job and press F4. End the SNADS sender job with *IMMED option. |
| 4. | Release the distribution queue. From an operating system command line, type WRKDSTQ, and select Option 6 to release the distribution queue. If the distribution queue goes to a RETRY-WAIT status again, hold the distribution queue back up and continue at the next step. |
| 5. | At the source system, run the WRKACTJOB SBS(QSNADS) command, and search for the SNADS sender job. Select Option 5 to work with the job, and select Option 10 to display the job log. The following messages were found in the SNADS sender job job log: MSGCPF5283 RC08640000, MSGCPI8805 RC22, MSGCPI8816 RC22. |
| 6. | At the target system, search for the SNADS receiver job. The SNADS receiver job at the target system will have the same name as the APPC device used to connect the target system to the source system. Use command DSPJOB JOB(APPCDEVNAME) to display the SNADS receiver job. The job should be in an OUTQ status, and the user should be QSNADS. The following messages were found in the SNADS receiver job job log: MSGCPF1124 followed by MSGCPF4059 RC08640000. |
| 7. | Read the entire message text for the message CPF1124. Verify that the SNADS receiver job is being started in subsystem QCMN or some other user-defined communications subsystem that is designed to handle Program Start Requests. If the subsystem described in the message CPF1124 is not QCMN, copy down the subsystem name. |
| 8. | Display the subsystem description (DSPSBSD) for the subsystem copied in Step 7. From the Display Subsystem Description screen, select Option 7 to display Routing Entries. You should compare the Routing Entries you have in the subsystem copied in Step 7 with the Routing Entries found in subsystem QCMN. If they are not the same, this subsystem is not configured to handle certain Program Start Requests. For whatever reason, the APPC device connecting the target system to the source system is getting allocated to the subsystem copied in Step 7 rather than an appropriate subsystem with appropriate Routing Entries such as QCMN. |
| 9. | To correct this problem, select Option 8 from screen Display Subsystem Description to display the Communications Entries. Verify if the APPC device that connects the target system to the source system is specified under column, 'Device'. If the APPC device is found in column 'Device', this communications entry will either have to be removed or the appropriate routing entries (such as the ones found in QCMN) must be added to this subsystem. If the APPC device is not found in column 'Device', press F12 to return to the previous screen, and select Option 9 to Display Remote Location Name Entries. Is there an entry found? Does the entry found have the same Remote Location as the Remote Location parameter found in the APPC device that connects the target system to the source system? If so, this remote location entry will either have to be removed (RMVCMNE) or the appropriate routing entries (such as the ones found in QCMN) must be added to this subsystem. If no remote location entries are found, press F12 to return to the previous screen, and select Option 5 to Display Communication Entries again. If you are this far, that means that all the communications entries have an '*' before them (such as *APPC or *ALL). If such entries exist, they must be removed from this subsystem or the appropriate routing entries (such as the ones found in QCMN) must be added to this subsystem. |
| 10. | Once the appropriate changes were made in Step 9, the APPC device on the target system that connects the target system to the source system will have to be varied off and varied back on using command VRYCFG. This is necessary so that the APPC device gets allocated to the problem subsystem. Once this is done, use command DSPJOB to display the job log for the subsystem and verify that it was allocated accordingly. You should find message CPF1273. For example, DSPJOB JOB(QCMN). |
| 11. | Go back to the source system, and release the distribution queue. |
[{"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
14693235
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1018167