|
Bill Hopkins wrote: > ... > I would love to use ExtProc( 'system' ) instead of ExtPgm('QCMDEXC'). But to > the staff here > QCMDEXC just looks familiar to them. It was hard enough to get them to let > me 'prototype for a call' > instead of calling QCMDEXC each time. One person was voting always CL. So > as I weep for them and also wish for their early retirement, I'm stuck > cause in the end right or wrong the CLIENT IS ALWAYS RIGHT. I can't force > them to learn. > Bill, I think using ExtPgm('QCMDEXC') with an (E) extender on the CALLP is better than system() anyway, especially when debugging, but also when something unexpected happens. If a command done by system() ends in error, all you can get is the message id without any replacement values, since system() removes the exception message from the joblog. But system() doesn't do a complete cleanup - it only removes the last message related to a command - if the command generated multiple exceptions or diagnostics, those will still be in the joblog. This makes the joblog very confusing, since you have diagnostic messages but no final exception message to explain them.
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.