|
On Friday 14 November 2003 22:17, Henrik Krebs wrote: [snip] > Not long ago I coded the lines: > > CALL PGM > IF 5 = 7 > CALL 'PGM1' > CALL 'PGM2' > CALL 'PGM3' > ENDIF > > Guess why? > > You're right: PGM1, -2 and -3 are included in DSPPGMREF. > Not nice really, cause the first line is ment to be flexible. Some day > the variable PGM might have a fourth value 'PGM4', but the DSPPGMREF > does not follow. I recently noticed that a DSPPGMREF had picked up a file for output from a CL, when that file wasn't on a DCLF. It had identified a file used on a command's OUTFILE parameter. The weird thing was that the command wasn't an IBM one, but one of my own. I'm presuming that it was the OUTFILE parm that was recognised. Are there any other tricks like this? Could you maybe create a dummy command DCLPGM PGM(*N) to get a PGM object appear in the references, instead of CALLs in a never entered IF block? Regards, Martin -- martin@xxxxxxxxxx AIM/Gaim: DBG400dotNet http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.