Re: PDM Library List

Marv,

In my sordid past as a programmer <bg>  I ran into this restriction and coded
around it.  I made a CL wrapper program for the CRTxxxPGM commands that did
several things:
o It checked for the existance of a data area 'CRTLIBL' in the requested target
library.  If the DA is not there then the compile is aborted. (This means you 
are
trying to compile to a source or IBM library for example.)  If it does exist the
list of libraries in the DA is used to replace the jobs library list.
o It deleting spool output for succesfull compiles.
o It scanned the 'F' specs (for RPG at least) for special comments that cause
OVRDBFs to be executed before the compile.
o TO short circuit myself from bypassing my own 'safeguards' I changed the
CRTxxxPGM commands to only be allowed within a program.

This process almost completely eliminated Level Check errors.   BTW We also made
it shop policy to NEVER EVER MOVE a compiled program into a production library,
it was ALWAYS Compiled into production.  Not always practical but it worked for
us.

 - Larry

Marv Noltze wrote:
> 
> My method of operation on the AS400 is to use a stripped down library list
> without any of my production libraries in it. When I compile a program...
<snip>

-- 
Larry Bolhuis         |         What if it's True?
Arbor Solutions, Inc  |
(616) 451-2500        |  
(616) 451-2571 -fax   | 
lbolhui@ibm.net       |
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---