Re: eveventf

We USED to separate production and development with library lists when we
only had one partition. Now, the person responsable for the deployment will
transfer the development library to the production partition and a hand
made application will transfer the source to production libraries and
compile. I realise that some of you don't keep source at all in production,
but don't know how that is managed. That's probably not a subject for this
list, though. I think we'll just delete all the EVEVENTF at the end of each
day.

2012/6/5 Vern Hamberg <vhamberg@xxxxxxxxxxx>

Jim

Yeah, I understand that - but Dave said they are being pushed to the
production partition - so I assumed they are different ones - of course,
we all know.......

The exclusion method we both presented seems the best way to go, eh?

Vern

On 6/5/2012 7:58 AM, Jim Oberholtzer wrote:

Vern,

The vast majority of shops separate development and production with
library lists and have both on the same partition. While you and I (and
most folks) would agree that this is not the optimal solution, often
times it's simply not possible to separate them.

Dave:

Is is possible in your back up routines to exclude those files from the
save? If you use BRMS (or Robot/Save for that matter) it's easy to do.
If you use IBM base save commands you can alter your back up CL to
exclude them as well. They would not be needed in the event of a
disaster recovery anyway so why back them up at all? Now you aren't
messing around with them, just not putting them to tape. You could
create a separate back up routine for the development portion of the
system and run that after the production save as well.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 6/5/2012 7:50 AM, Vern Hamberg wrote:

Well, first of all, what are developer libraries doing on a production
partition? Yes, maybe for debugging - but change the procedure so that
you bring over source only when you need it, only for 1 or 2 programs.

Second, you can exclude objects from the saves - you might have to
retrieve and modify the source for the option 21 save - or one of the
others - but once done, it's taken care of.

These files are used only to display the results of the last compile in
RDP - I don't know of another usage - they could be deleted every night,
I suppose, but maybe just clear the members - there's a member for each
object that was compiled.

I rather like excluding the files myself - it is less intrusive and
invasive.

Vern

On 6/5/2012 4:15 AM, Dave wrote:

Hi,

Management complains that the development libraries are becoming

far too

heavy since more developpers switched to RDP and we started

generating the

EVEVENTF. These libraries are being saved every night, get pushed

onto the

production partition where they are also saved along with

everything else.

Is anyone using any kind of procedure for cleaning up these

unwanted files

after use?

Thanks

--

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.