QSNADS help - how to trouble shoot
John Swartzendruber
I'm feeling a bit stumped.
We have 2 AS/400s, both at v3r2, that we use QSNADS for sending spool
files back and forth. For the most part it just works, but this weekend
it quit. Other times when it has stopped sending, it is usually because
the distribution queue has a problem, and holding/releasing it usually
clears things up. This time, the DSTQ seems fine; in fact on the
sending system everything looks normal, and it appears to get sent. I
have watched the DSTQ while something is being sent, and it shows up in
the queue, then shows a 'sending' status, then is gone. But it never
shows up on the target system. No errors in QSYSOPR or QHST. I believe
a QSNADS job starts and ends, but the job log is just job starting and
ending info.
I've run out of ideas on where to look. Does anybody have any
suggestions?
John Swartzendruber
Mennonite Mutual Aid, inc
Goshen, IN
joh...@mma-online.org
Francis Lapeyre
Are either of your machines at 90% DASD or greater (per WRKSYSSTS)? That
has, in the past, brought SNADS communication to a screeching halt on
our systems.
--
Francis Lapeyre flap...@communique.net
----------------------------------------------------------
Qui desiderat pacem præparet bellum (Who would desire
peace should be prepared for war).--Vegetius: Rei Militari
3, Prolog.
Opinions are my own. Otherwise, they are someone else's.
Helmut Salzer
Hi John,
when you have any problems with qsnads-dstq then look at the dst-log.
Try the cmd DSPDSTLOG. With this you can find all information- and
errormessages the dst has produced!
Greetings and good luck
--
Helmut Salzer
webmaster Profi Reifen Service Ges.m.b.H.
Office: pr...@profi-reifen.co.at
http://www.profi-reifen.co.at/profi/
Privat: salz...@ping.at
http://members.ping.at/salzer.h/as400.htm
John Swartzendruber <as4...@ibm.net> schrieb im Beitrag
<3319E9...@ibm.net>...
Ian
Check out your disk storage used. If it exceeds the threshold value set in
Service Tools (Default 90%) then it will not fly!
John Swartzendruber <as4...@ibm.net> wrote in article
Robert
John Swartzendruber <as4...@ibm.net> wrote in article
<3319E9...@ibm.net>...
> I'm feeling a bit stumped.
>
> We have 2 AS/400s, both at v3r2, that we use QSNADS for sending spool
> files back and forth. For the most part it just works, but this weekend
> it quit. Other times when it has stopped sending, it is usually because
> the distribution queue has a problem, and holding/releasing it usually
> clears things up. This time, the DSTQ seems fine; in fact on the
> sending system everything looks normal, and it appears to get sent. I
> have watched the DSTQ while something is being sent, and it shows up in
> the queue, then shows a 'sending' status, then is gone. But it never
> shows up on the target system. No errors in QSYSOPR or QHST. I believe
> a QSNADS job starts and ends, but the job log is just job starting and
> ending info.
>
> I've run out of ideas on where to look. Does anybody have any
> suggestions?
>
> John Swartzendruber
> Mennonite Mutual Aid, inc
> Goshen, IN
> joh...@mma-online.org
>
John,
Either your have reached your threshold on one of your machines or you
might want to try running this command. ENDMSF (end mail server Framework)
and then run STRMSF (to start Mail server Framework). I have found that
when I have problems that this seems to clear up the problem. let me know
if that helps
John Swartzendruber
Francis Lapeyre wrote:
>
> Are either of your machines at 90% DASD or greater (per WRKSYSSTS)? That
> has, in the past, brought SNADS communication to a screeching halt on
> our systems.
> --
> Francis Lapeyre flap...@communique.net
> ----------------------------------------------------------
No, that was the first thing I checked. I've got it working now, but
more by accident than anything else. We are doing a little work with
POP3 on the AS/400, and I noticed that not all the required jobs were
running there. When I ran the STRMSF command, all the QSNADS stuff
started coming across too. Guess there must be some connection there,
but it surprised me.
Thanks for the suggestion, but that wasn't it this time
John
Peter Levy
With V3R1 and V3R2 the most common reason I've found to explain
what you're experiencing is that the QSYSWRK subsystem on the
target system is down or if it's up then the QMSF jobs havn't
been started.
--
Peter...@Liz.COM
Scott A. Hoff
John Swartzendruber wrote:
>
> I'm feeling a bit stumped.
>
> We have 2 AS/400s, both at v3r2, that we use QSNADS for sending spool
> files back and forth. For the most part it just works, but this weekend
> it quit. Other times when it has stopped sending, it is usually because
> the distribution queue has a problem, and holding/releasing it usually
> clears things up. This time, the DSTQ seems fine; in fact on the
> sending system everything looks normal, and it appears to get sent. I
> have watched the DSTQ while something is being sent, and it shows up in
> the queue, then shows a 'sending' status, then is gone. But it never
> shows up on the target system. No errors in QSYSOPR or QHST. I believe
> a QSNADS job starts and ends, but the job log is just job starting and
> ending info.
>
> I've run out of ideas on where to look. Does anybody have any
> suggestions?
>
> John Swartzendruber
> Mennonite Mutual Aid, inc
> Goshen, IN
> joh...@mma-online.org
John,
be sure that the auxiliary storage threshold has not been exceeded
on either box. This will stop snads dead in its tracks...
Does passthru still work?
Scott
S. G.
Several things to check:
1. Make sure you're not jumping over the threshold while the
transmission is going on.
2. Make sure that QSNADS has at least *CHANGE to the APPC device.
3. Make sure nobody messed with the mode description in the network
attributes. I had a situation where the distribution queue
specified *NETATR for the mode description and some genius changed
the network attributes.
4. Make sure QSNADS and QCMN have not been changed.
5. Check the distribution log DSPDSTLOG.
6. Check message queue QSYSMSG.
7. Make sure QSYSWRK is up, including a STRMSF.
hth