Re: monmsg question

[Evan Harris <spanner@xxxxxxxxxx>]

Hi Rob

I've had many situations where I wanted to generate "stuff" using a 
CL where I wanted that "stuff" to hang around after the program had 
finished running and therefore I don't delete it when the program ends.

Deleting it before starting the next run is the easiest (laziest) way 
to ensure all subsequent steps can be simply coded to create what 
they need to create without having to think too much about things 
like *REPLACE VS *ADD in CPYF, etc

Also, I might have arrangements with users to delete the "stuff" 
after they have finished with it as it might not be needed until the 
next update is run, after next end of quarter for example, or when 
maybe other type of intermittently required but predictable data set 
is requested.

At the risk of finding out I have very bad habits it seems to me that 
this is a reasonable thing to do at the start of a program in certain 
circumstances.

I guess if I'm wrong about this being acceptable practice, then at 
least I'm going to get an education as to what I ought to be doing :)

Regards
Evan Harris

At 02:50 a.m. 23/11/2006, you wrote:

> Another point,
>
> Why do a delete before creation on a library other than QTEMP?  If the
> object already exists and it shouldn't, doesn't that mean that the
> previous run abnormally terminated and restart procedures should be used?
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com