|
CarollaT@xxxxxxxxxxxxxx wrote: > ... > Which works marvelously - when the file exists, and is not locked, etc. > Inside my CL program, I could use the MONMSG command, and deal with those > situations as they arose. Is there a way to find out whether or not a > command completed successfully, and catch the message if it doesn't complete > successfully? It sure would be a shame to have to write a CL program with > just one CLRPFM command... > Not just one CLRPFM - sounds like a CLRPFM and a whole lot of MONMSG and recovery. If you have common processing for clearing files in several programs, you should probably put it in a callable routine anyway, so why not make it CL? But if you want to use RPG for this, you can use CALL(E) as John suggested, and get the message causing the failure from the PSDS pos 40-46.
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.
midrange.com
