Why is the system putting my spooled file on Hold? -- MIDRANGE-L

Subject: Why is the system putting my spooled file on Hold?
From: Gavin Inman <midrangelist@xxxxxxxxxxxxxx>
Date: Thu, 5 Sep 2024 21:40:26 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I have an interesting situation that is happening on only 1 out of about 50 remote output queues.
We have about Output queues on System A sending spooled files to System B.
The spooled files are in RLS status on system A, and they show up as RLS status on System B for all of them, except 1.

We are scratching our heads as to what is different on this One Queue.

I looked at the Spooled Audit Log and found the QSPLJOB job is putting it on Hold 2 seconds after it arrives on system B.
I don't know why.

Any Insight or ideas from the group?

Thanks,

Gavin Inman

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Why is the system putting my spooled file on Hold? , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.