RE: DTACPR(*HIGH)

["Jones, John \(US\)" <John.Jones@xxxxxxxxxx>]

Rob,

Have you benchmarked the save operations that you're thinking about?
I'm curious about the added CPU time and space saving of each option.  I
normally specify *YES or *MEDIUM as it seems to do wonders for DASD
consumed but doesn't appear to add much to the overall CPU time spent
doing the save.  I admit, though, I've not done any benchmarking and am
going by casual observation.

We aren't concerned about deleted records either; we've turned on reuse
deleted in all of the major JDE files.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, October 10, 2006 7:05 AM
To: midrange-l@xxxxxxxxxxxx
Subject: DTACPR(*HIGH)

We use a lot of save files for saving of data (not our normal backup
stuff though).  I am thinking of changing the command defaults to
DTACPR(*HIGH). 
 Then on all tape backup programs put in DTACPR(*DEV).  Leaving concerns
about what if, instead of our special program, someone does a GO SAVE -
21.

One concern we can ignore is that we do not employ the old trick of
saving a file to a save file so that one can see deleted records.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.