× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2020

RE: RUNRMTCMD Spool File

Confirm 2 items.
1) OVRPRTF is executed before the QSYSPRT spoolfile is opened. Check joblog.
2) that the QSYSPRT spoolfile is actually being created by the same job. Check job number.

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rich Loeber
Sent: Tuesday, January 07, 2020 11:28 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: RUNRMTCMD Spool File

A good thought, but this produces the same results.  Just tried it.

Rich

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



On 1/7/2020 11:24 AM, Steinmetz, Paul via MIDRANGE-L wrote:
Rich,

On your OVRPRTF, try adding Override scope . . . . . . . . . > *JOB

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rich Loeber
Sent: Tuesday, January 07, 2020 11:15 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RUNRMTCMD Spool File

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

--
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 ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.