|
Bruce, > As you're intercepting the CRTBND* couldn't you just break this up into > individual CRTxxxMOD and CRTPGM steps. I could, but I'm trying to do something that won't require me to change the way things are currently done - we have a lot of OPM CL programs for which the source type has simply been changed from CLP to CLLE, so they're now compiled using CRTBNDCL rather than CRTCLPGM. I could try to get people to use PDM option 15 (and include a precompiler 'post-create' command to run the CRTPGM after the CRTCLMOD has completed), but it would require everyone to use a different option. Inertia, you know... I guess another option would be to do something like the following (these are example precompiler comment processing lines): /*O: MODULE(QTEMP/&N) DBGVIEW(*LIST) */ /*C: CHGOBJSRC OBJ(QTEMP/&N) OBJTYPE(&T) SRCLIB(&L/&F) SRCMBR(&M) */ /*C: CRTPGM PGM(&O/&N) MODULE(QTEMP/&N) ACTGRP(*CALLER) */ So the original compile command is overridden (the /*O: line) to create the module in QTEMP. Then (after the CRTCLMOD command has run) the module in QTEMP has its source changed (in the first /*C: 'command' line) to say it was created from the source member in the 'real source library. Finally (in the second /*C: 'command' line) a command runs to create the program in the final library from the module in QTEMP. CHGOBJSRC is simply a command which invokes the QLICOBJD API, obviously. Now I have to add this source into all the CL source members.... Rory
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.