That happens after the spool file is created and there is a split second available where a spool writer could pick it up.  I'd really prefer that it be created on hold.

Rich

------------------------------------------------------------------------



On 1/7/2020 11:22 AM, Steve McKay wrote:
Rich -

Would HLDSPLF work for you?

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Tue, Jan 7, 2020 at 11:15 AM Rich Loeber <rich@xxxxxxxxx> wrote:

I have an application using RUNRMTCMD between two IBM i systems. The
application is running as expected and producing the desired results
with the exception that a QSYSPRT listing is being generated. I
understand that this is normal and I can successfully delete it after
the process runs, but I am trying to make sure that it never prints by
putting it on hold. I'm trying the OVRPRTF route, but regardless of how
I code it, the spool file always ends up in RDY status.

The suggestion at the IBM support website of using an OVRPRTF for *PRTF
does not seem to do anything.

Rich Loeber - @richloeber
Kisco Information Systems
http://www.kisco.com

--
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
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.