|
That's the mystery - it will fail when called with the same parameters that will generate a spool file during debug. -----Original Message----- From: Buck Calabro [mailto:Buck.Calabro@commsoft.net] Sent: Tuesday, February 05, 2002 9:17 AM To: rpg400-l@midrange.com Subject: RE: Case of the missing spool file Mike wrote: >>>I'm having a strange problems with some CL. If I >>>run it in debug, it runs fine. If I just call if >>>from strpdm, it fails to generate a spool file and >>>the cpysplf statement fails. >>>OVRPRTF FILE(OCFAXPRT) PAGESIZE(&PAGESIZE) + >>> OVRFLW(&OVRFLW) RPLUNPRT(*NO) OUTQ(&OUTQ) + >>> HOLD(*YES) OVRSCOPE(*JOB) >>> >>>CALL PGM(COR06A) PARM(&ORD &TYP &USER) >>> >>>CPYSPLF FILE(OCFAXPRT) TOFILE(&PF) + >>> SPLNBR(*LAST) >> Buck wondered: >>What message do you get? What's in the job log? Mike replied: >CPF3303 received by ACOR06A >File OCFAXPRT not found in job 502626/M1C/ACOR06A. Given that "it fails to generate a spool file" and the CPYSPLF can't find a file to copy, it appears that the RPG program is not doing any output to the printer file. Are the parameters and library list the same in debug and production? Does CORO6A always produce (at least) headings? If not, consider adding a page that says "Order xxx, type xxx, user xxx no report." Or you can add a MONMSG to the CPYSPLF to stop the hard halt. --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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.