MustGather Reference Guide for SNADS

Resolving The Problem

Note: Before proceeding with the actual troubleshooting steps below, verify that all the basic requirements for normal SNADS operation described below have been met.

SNADS Requirements

For SNADS to operate properly, it requires the following on the operating system:

o	Communications line, controller, and device descriptions configured for APPC or APPN support. For more information about configuring line, controller, and device descriptions for APPC, see the APPC Programming manual. For more information about APPN configuration, refer to the APPN Support manual.
o	The IBM-supplied subsystem QSNADS must be active. To start this subsystem, on the operating system command line type the following: STRSBS SBSD(QSNADS) Press the Enter key.
o	The IBM-supplied subsystem QSYSWRK must be active. To start this subsystem, on the operating system command line type the following: STRSBS SBSD(QSYSWRK) Press the Enter key.
o	The Mail Server Framework job QMSF found under subsystem QSYSWRK must be active. To start this job, on the operating system command line type the following: STRMSF Press the Enter key.
o	The Object Distribution job QNFTP found under subsystem QSNADS must be active. This job should automatically start when the subsystem QSNADS is started. If it is not started, try ending and then starting subsystem QSNADS. If problems persist, call the IBM Support Center, and report a SNADS problem.
o	There must be a successful communications link test between the two systems you plan to set up SNADS for. Before configuring SNADS, test the communications link by starting a display station pass-through session from the source system to the target system. To test the communications link, start a display station pass-through session using the same RMTLOCNAME, LCLLOCNAME, MODE, and RMTNETID parameters you plan to use when configuring your Distribution Queue for SNADS. In other words, use the same RMTLOCNAME, LCLLOCNAME, MODE, and RMTNETID parameters in your test as you plan to use with SNADS. For example, a user may start a Display Station Pass-Through session by typing the following on the operating system command line: STRPASTHR RMTLOCNAME(SYSB) MODE(BLANK) LCLLOCNAME(SYSA) RMTNETID(APPN) (Refer to Note 1.) Press the Enter key. If pass-through works with the selected parameters, this user is ready to configure SNADS and should use these parameter values when configuring the distribution queue. If pass-through does not work with the selected parameter values, call the IBM Support Center, and report a display station pass-through problem. Notes: 1. The parameters cited in the example above (RMTLOCNAME, MODE, LCLLOCNAME, and RMTNETID) may be different for each operating system connection. The operating system connection might not match the parameters described above. To verify the actual RMTLOCNAME, MODE, LCLLOCNAME, and RMTNETID parameters, display the device description you plan to use for SNADS. 2. For more information about configuring display station pass-through, see the Remote Work Station Support manual.

Basic Troubleshooting Steps

Below, you will find some basic steps in troubleshooting SNADS:

The QSNADS journal, also known as the Distribution Services Log, contains useful entries that track SNADS operations that were performed on both the source and target systems (sending, routing, receiving, and so on. Although not all SNADS processes log entries in the Distribution Services Log, correct problem analysis and problem determination can be made for many common problems by reviewing the entries in the Distribution Services Log.

Entries on the Distribution Services Log can be reviewed by running command DSPDSTLOG and pressing Enter. When troubleshooting a SNADS problem, it is recommended that you prompt the command DSPDSTLOG with a F4, and use the Beginning Time, Beginning Date, Ending Time, Ending Date and Originator User ID parameters and attempt to single out an individual distribution that has been sent from the source system and has not arrived at the target system.

o

The Originator User ID parameter in the "Display Distribution Log (DSPDSTLOG)" screen specifies the originating user ID (user who sent the distribution) and address of logged distributions. This parameter allows you to display or print only those entries logged because of distributions originated by a user with the specified ID or address. Therefore, if a user is having difficulties with distributions not arriving at its destination, this user can specify his/her User Profile in the Originator User ID parameter to review only the QSNADS journal entries pertaining to him/her.

The Display Distribution Services Log screen describes various SNADS functions and whether these functions were performed normally or in error. The Function Type column describes the SNADS function that was being performed when the QSNADS journal entry was made. The Entry Type column describes whether the function listed under the Function Type column was performed normally (*NRM) or in error (*ERR). Finally, notice the column named Seq Nbr (Sequence Number). The Seq Nbr column describes the number that was assigned to all functions related to an individual distribution. When a distribution is sent or received, all QSNADS journal entries related to this distribution will have the same Seq Nbr (sequence number). The sequence numbers from the source system and the target will not necessarily match. As the name indicates, these are sequential numbers and they will rarely match between the Distribution Services Log in the source and in the target.

o	The following are QSNADS journal entries a user should see when displaying the Distribution Services Log in the source system for a distribution that was sent and has successfully left the source system. On the Source System: Function Entry . . . Seq Type Type . . . Nbr *ORG *NRM . . . 0001 *RTR *NRM . . . 0001 *SND *NRM . . . 0001
o	The following are QSNADS journal entries a user should see when displaying the Distribution Services Log in the target system for a distribution that was been successfully received on the target system. On the Target System: Function Entry . . . Seq Type Type . . . Nbr *RCV *NRM . . . 0010 *RTR *NRM . . . 0010 *ARV *NRM . . . 0010

Troubleshooting Basic Problems

1.	On the operating system command line of the source system, type command DSPDSTLOG and prompt it with the function key F4. Use the Beginning Time, Beginning Date, Ending Time, Ending Date and Originator User ID parameters to attempt to single out either a time period or an individual distribution that has been sent from the source system and has not arrived at the target system. Press the Enter key. You should be at the Display Distribution Services Log screen.
2.	Notice the Seq Nbr column. On the source system, verify that for every sequence number listed in the Distribution Services Log, there is an entry of Function Type *ORG and of Entry Type *NRM. If you found an entry of Function Type *ORG and of Entry Type *NRM for every sequence number listed in the Distribution Services Log, proceed to Step 3. However, if you do not have an entry of Function Type *ORG or the entry that you have is an Entry Type *ERR, refer to the possible causes below. Possible Causes: 1 Ensure that the Beginning Time, Beginning Date, Ending Time, Ending Date or any other parameter specified in the DSPDSTLOG command did not prevent the entry you are looking for from being displayed. 2 Verify that all the basic requirements for normal SNADS operation described above under SNADS Requirements have been met. 3 Verify that your Local System Distribution Directory Entry is correct and it follows the requirements described in section 1, Adding a Local System Directory Entry, of document N1018347, Configure SNADS and Setting Up SNA Distribution Services. 4 Verify that your Remote System Distribution Directory Entry exists and the Address field of your remote entry matches the Address field value used when sending the distribution to the remote system. For guidelines on creating a remote entry, please refer to section 2, Adding a Remote System Distribution Directory Entry, of document N1018347, Configure SNADS and Setting Up SNA Distribution Services. 5 If none of the options above seem to fix your problem, call IBM Support Center and report a SNADS problem.
3.	On the source system, verify that for every sequence number listed in the Distribution Services Log, there is an entry of Function Type *RTR and of Entry Type *NRM. If you found an entry of Function Type *RTR and of Entry Type *NRM for every sequence number listed in the Distribution Services Log, proceed to Step 4. However, if you do not have an entry of Function Type *RTR or the entry that you have is an Entry Type *ERR, refer to the possible causes below. Possible Causes: 1 Ensure that the Beginning Time, Beginning Date, Ending Time, Ending Date or any other parameter specified in the DSPDSTLOG command did not prevent the entry you are looking for from being displayed. 2 Verify that all the basic requirements for normal SNADS operation described above under SNADS Requirements have been met. 3 Verify that the Mail Server Framework job QMSF found under subsystem QSYSWRK is active. 4 Verify that your Remote System Distribution Directory Entry exists and the System Name and Group fields of your remote entry matches a Routing Table Entry with the exact same System Name and Group field values. For guidelines on creating a remote entry, please refer to section 2, Adding a Remote System Distribution Directory Entry, of document N1018347, Configure SNADS and Setting Up SNA Distribution Services. 5 If none of the options above seem to fix your problem, call IBM Support Center and report a SNADS problem.
4.	On the source system, verify that for every sequence number listed in the Distribution Services Log, there is an entry of Function Type *SND and of Entry Type *NRM. If you found an entry of Function Type *SND and of Entry Type *NRM for every sequence number listed in the Distribution Services Log, proceed to Step 5. However, if you do not have an entry of Function Type *SND or the entry that you have is an Entry Type *ERR, refer to the possible causes below. Possible Causes: 1 Ensure that the Beginning Time, Beginning Date, Ending Time, Ending Date or any other parameter specified in the DSPDSTLOG command did not prevent the entry you are looking for from being displayed. 2 Verify that all the basic requirements for normal SNADS operation described above under SNADS Requirements have been met. 3 Verify the status of the distribution queue in question. This can be accomplished with command WRKDSTQ. If the queue is HELD, release it by taking Option 6 from the Work with Distribution Queues screen. If the queue is in status of ERR-HELD, RETRY-FAIL, RETRY-WAIT or FAILED, try holding the distribution queue with Option 3 and then releasing it with Option 6. If the queue is in status of NOT-RDY, try sending the queue by taking Option 2 from the "Work with Distribution Queues" screen. 4 Verify that individual queue entries are not HELD. From the Work with Distribution Queues screen, take Option 5 next to the queue in question to work with queue entries. Verify that individual queue entries are not HELD or take appropriate action to release them. 5 Verify that your communications link is up. You may have had a communications failure. The line, controller and device descriptions pointing to the target system should be all ACTIVE. You should be able to test the communications link, by starting a Display Station Pass-Through session (command: STRPASTHR) from your source system to the target using the same RMTLOCNAME, LCLLOCNAME, MODE and RMTNETID parameters you specified in the distribution queue configuration. 6 If none of the options above seem to fix your problem, call IBM Support Center and report a SNADS problem.
5.	If you are in Step 5 of troubleshooting your SNADS problem, this means that 100% of the distribution has left the source system and that the problem most likely is in the target System. On the operating system command line of the target system, type command DSPDSTLOG and prompt it with the function key F4. Use the Beginning Time, Beginning Date, Ending Time, Ending Date and Originator User ID parameters to attempt to single out either a time period or an individual distribution that has been sent from the source system and has not arrived at the target system. Press the Enter key. You should be at the Display Distribution Services Log screen on the target system.
6.	On the target system, verify that for every sequence number listed in the Distribution Services Log, there is an entry of Function Type *RCV and of Entry Type *NRM. If you found an entry of Function Type *RCV and of Entry Type *NRM for every sequence number listed in the Distribution Services Log, proceed to Step 7. However, if you do not have an entry of Function Type *RCV or the entry that you have is an Entry Type *ERR, refer to the possible causes below. Possible Causes: 1 Ensure that the Beginning Time, Beginning Date, Ending Time, Ending Date or any other parameter specified in the DSPDSTLOG command did not prevent the entry you are looking for from being displayed. 2 Verify that all the basic requirements for normal SNADS operation described above in under SNADS Requirements have been met. 3 Verify that your communications link is up. You may have had a communications failure on the target system. The line, controller and device descriptions pointing to the source system should be all ACTIVE. You should be able to test the communications link, by starting a Display Station Pass-Through session (command: STRPASTHR) from your target system back to the source. 4 If none of the options above seem to fix your problem, call IBM Support Center and report a SNADS problem.
7.	On the target system, verify that for every sequence number listed in the Distribution Services Log, there is an entry of Function Type *RTR and of Entry Type *NRM. If you found an entry of Function Type *RTR and of Entry Type *NRM for every sequence number listed in the Distribution Services Log, proceed to Step 8. However, if you do not have an entry of Function Type *RTR or the entry that you have is an Entry Type *ERR, refer to the possible causes below. Possible Causes: 1 Ensure that the Beginning Time, Beginning Date, Ending Time, Ending Date or any other parameter specified in the DSPDSTLOG command did not prevent the entry you are looking for from being displayed. 2 Verify that all the basic requirements for normal SNADS operation described above under SNADS Requirements have been met. 3 Verify that the Mail Server Framework job QMSF found under subsystem QSYSWRK is active. 4 If none of the options above seem to fix your problem, call IBM Support Center and report a SNADS problem.
8.	On the target system, verify that for every sequence number listed in the Distribution Services Log, there is an entry of Function Type *ARV and of Entry Type *NRM. If you found an entry of Function Type *ARV and of Entry Type *NRM for every sequence number listed in the Distribution Services Log, proceed to Step 9. However, if you do not have an entry of Function Type *ARV or the entry that you have is an Entry Type *ERR, refer to the possible causes below. Possible Causes: 1. Ensure that the Beginning Time, Beginning Date, Ending Time, Ending Date or any other parameter specified in the DSPDSTLOG command did not prevent the entry you are looking for from being displayed. 2. Verify that all the basic requirements for normal SNADS operation described above under SNADS Requirements have been met. 3. Verify that your Local System Distribution Directory Entry is correct and it follows the requirements described in section 1, Adding a Local System Directory Entry, of document N1018347, Configure SNADS and Setting Up SNA Distribution Services. link at bottom 4. Verify that the Object Distribution job QNFTP found under subsystem QSNADS is active. 5. If none of the options above seem to fix your problem, call IBM Support Center and report a SNADS problem.
9.	If you are in Step 8, the distribution is most likely arrived in the target system. Now it is a matter of locating it or further processing it. If you sent a spooled file, verify that the spooled file is in the output queue (OUTQ) specified in the User Profile of the user you sent the distribution to. If you sent a network message, verify that the message is in the message queue (MSGQ) specified in the User Profile of the user you sent the distribution to. If you sent a Save file or a Physical File, you must receive the file and can do so with the WRKNETF command. If you sent a network job, you can view it at the target system with the WRKNETJOBE command. If all else fails, call IBM Support Center and report a SNADS problem.