|
> From: David Gibbs > > Why not just have OvrDbf format the command and call QCMDEXC itself? > > That way you've hidden the implementation and the invocation. As a first > level consumer, I don't care HOW something is done, I just care that it IS Because this is old RPG III code slowly being moved into the new world. If I wrote it from scratch, I'd probably go a level higher, and just pass in a an ID and a file type and let the called procedure determine the appropriate fields to use. Something like: callp OverrideFile('INFILE':PgmID:FileType) 'INFILE' is the name of the file in the program, PgmID is the identifier for the program, and FileType is the type of file to override to, such as original source, converted source, and so on. The procedure would use the PgmID to get the information about the program, and the FileType to determine which file I was overriding to. But I like your idea about burying the QCMDEXC call. Who knows, I may go through the code and do that at a later date. Joe
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.