|
I copied your cl (now called RMVDELREC) (many thanks BTW) from>
http://www.ke9nr.net/iseries/faqs/reorgpf.shtml
and ran it this weekend on a bunch of test libraries from a mother CL. I ran into one that halted the process because a library did not have any *PF files (shotgun approach).
Here's a joblog fragment from your CL:
CALL PGM(RMVDELREC) PARM('LAWPGMPKD' '*ALL') 5700 - DSPFD FILE(LAWPGMPKD/*ALL) TYPE(*MBRLIST) OUTPUT(*OUTFILE) FILEATR(*PF) OUTFILE(QTEMP/REORGPF) 8400 - RCVMSG MSGTYPE(*ANY) RMV(*YES) MSGDTA(&MSGDTA) MSGID(&MSGID) RTNTYPE(&RTNTYPE) MSGF(&MSGF) SNDMSGFLIB(&SNDMSGFLIB) 10800 - SNDPGMMSG MSGID(CPF3020) MSGF(QSYS/QCPFMSG) MSGDTA('*ALL LAWPGMPKD') MSGTYPE('*ESCAPE') No files in *ALL in LAWPGMPKD have the specified FILEATR.
It jumps from the DSPFD to the MSGLOOP to a SNDPGMMSG in your CL. This is in
line with your note 2: If an error occurs on the DSPFD command, the associated
messages sent to the calling program and no files are reorganized.
In the mother process I put a monmsg after each call to the daughter process and
it continues past the library with no *PF objects. Is this what you would
recommend?
CALL PGM(RMVDELREC) PARM('LAWDBFPKD' '*ALL')
MONMSG MSGID(CPF0000)
CALL PGM(RMVDELREC) PARM('LAWPGMPKD' '*ALL')>
MONMSG MSGID(CPF0000)
CALL PGM(RMVDELREC) PARM('JDRAPER' '*ALL')>
MONMSG MSGID(CPF0000)
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.