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

Thanks, I'll check this out

On 9/7/2024 1:03 PM, Jim Franz wrote:

check the config of the outq - the *PASTHR mentions the hold

Create Output Queue (CRTOUTQ)
...........................................................................
: Remote system (RMTSYS) - Help
:
: Specifies the remote system to send files to when a remote writer is
: started (using the STRRMTWTR command) to the output queue. This is
: referred to as the "address" by SNADS, and the "host" by TCP/IP.
:
: *NONE
: The output queue is used only for local printing. The STRRMTWTR
: command cannot be used when this output queue is specified on the
: OUTQ parameter.
:
: *PASTHR
: The system a user passed through (using the STRPASTHR command) is
: used when sending spooled files created by the user job. If a
: spooled file was not created by a job that had passed through from
: another system, the spooled file will be held (HLD status).

Jim Franz

On Fri, Sep 6, 2024 at 11:37 AM Justin Taylor<jtaylor.0ab@xxxxxxxxx> wrote:

Have you checked the job log for the writer?


date: Thu, 5 Sep 2024 21:40:26 -0400

from: Gavin Inman<midrangelist@xxxxxxxxxxxxxx>
subject: Why is the system putting my spooled file on Hold?

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.