Re: MONMSG CPF2130 was: CL program

[Booth Martin <booth@xxxxxxxxxxxx>]

If one chooses to put the monmsg at the top of the CL program, doesn't 
that do it for the entire CL program?  No need to write it after every 
CRTDUPOBJ?


rob@xxxxxxxxx wrote:
> Yes you can CRTDUPOBJ more than one file.  You can do it a couple of ways.
>
> 1 - Use generics and one command.
> CRTDUPOBJ OBJ(MYFILE*) FROMLIB(MYLIB) OBJTYPE(*FILE)
> MONMSG ...
>
> 2 - Or single string them.
> CRTDUPOBJ OBJ(MYFILE1) FROMLIB(MYLIB) OBJTYPE(*FILE)
> MONMSG ...
> CRTDUPOBJ OBJ(MYFILE2) FROMLIB(MYLIB) OBJTYPE(*FILE)
> MONMSG...
>
> They both have their pro's and con's.  You may like the latter method if 
> you only care that a particular object did not dup - and not why it didn't 
> dup.  But I suppose that same philosophy could be applied to the former. 
> Clean up of the objects that did dup in case of failure in the latter case 
> may be easier to handle.  Then again, if you're going to QTEMP a simple 
> CLRLIB QTEMP is quite succinct.
>
> Rob Berendt