Troubleshooting
Problem
This document will describe how SNADS may fail with a CPFAF95 rc4 and CPF9A8C rc11.
Resolving The Problem
This document will describe how SNADS may fail with a CPFAF95 rc4 and CPF9A8C rc11.
Objects sent using SNADS commands (SNDNETMSG, SNDNETSPLF, SNDNETF) do not reach the distribution queue of the sending (source) system. The system posts message CPFAF95, Reason Code 4, and message CPF9A8C, Reason Code 11.
In order for SNADS to route objects to the appropriate distribution queue, at least one QMSF job must be active under subsystem QSYSWRK. If the STRMSF command fails to allow the QMSF job to go active, the above error messages will be posted, indicating the STRMSF command failed.
One option (and probably the quickest) to allow the QMSF job to start after the errors occurred, is to simply use the option STRMSF MSGOPT(*CLEAR). Using this option will clear the existing mail, network messages, network files and network spooled files that are still on the MSF queue. These will have to be sent again.
Another option, if the system currently has little IBM OfficeVision or SNADS activity, issue the following commands:
Note: Sign on with the profile QSECOFR to enter the following commands.
| 1. | WRKOBJLCK OBJ(QAOKL03A) OBJTYPE(*FILE), and issue the ENDJOB *IMMED command for each job that has a lock on this file. *note: This may end jobs that are needed for in other activity such as POP or EMAIL servers and HOST servers that may cause IFS connectivity. Doing these command, may be done in a restricted state, to minimize unintended disruptions. |
| 2. | CHGSYSDIRA ALWSCH(*NO) |
| 3. | CHGSYSDIRA ALWSCH(*YES) |
| 4. | ENDSBS SBS(QSNADS) |
| 5. | STRSBS SBS(QSNADS) |
| 6. | STRMSF MSGOPT(*CLEAR) |
Historical Number
23930246
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1017284