|
Paul is referring to the Cleanup program, not the Startup program. Sysval qstruppgm will not do it. jim----- Original Message ----- From: "Zdenko Beks" <zdenko.beks@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Friday, January 19, 2007 7:34 AM Subject: RE: Question on QEZUSRCLNP
Hi Create Your own pgm in Your *LIB and change SYSVAL QSTRUPPGM with changed program LP Zdenko -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jonathan Mason Sent: Friday, January 19, 2007 1:28 PM To: 'Midrange Systems Technical Discussion' Subject: RE: Question on QEZUSRCLNP Hi PaulIn one of the recent releases of OS/400 (and it may well have been 5.3) IBMstarted qualifying their program and command calls with the library name, resulting in the effect you're having. I don't know of any solution other than renaming the original program in QSYS and compiling your program there, although I'd be reluctant to do it myself. All the best and good luck. Jonathan -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Tuohy Sent: 19 January 2007 12:18 To: 'Midrange Systems Technical Discussion' Subject: Question on QEZUSRCLNP Hi All, I am having a problem with the QEZUSRCLNP program that is used as part of the nightly cleanup. I did a RTVCLSRC of the QEZUSRCLNP program from QSYS, made my changes and compiled the program to a library that precedes QSYS in the library list. When I call the program it runs just fine but it is not called from the nightly cleanup - it seems to be running the original in QSYS. Should I compile to QSYS (eek!), am I missing a system value.? I am on V5R3 TIA Regards Paul Tuohy ComCon <http://www.comconadvisor.com> www.comconadvisor.com <http://www.systemideveloper.com> www.systemideveloper.com --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.