Re: Nightly saves

[Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx>]

The lock problem only applies to files open for update and we don't 
allow anything other than read access through FTP and ODBC.

Jones, John (US) wrote:
> For those who are ending QINTER, what are you doing about the other ways
> that data can be accessed (FTP, ODBC, etc.)?
>
> If we need to shut off access, we ENDTCPIFC on the only IP address the
> users know about.  There's a second IP address on the box that IT can
> use and for which there is no DNS entry. 
>
>
> 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 Cyndi Bradberry
> Sent: Monday, October 16, 2006 2:10 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Nightly saves
>
> We wrote our own version of Go SAVE 23. This runs on weeknights, from a
> queue of jobs, all single threaded. We do a SAVSECDATA, SAVLIB, and
> SAVDLO, taking 30 minutes to an Ultrium tape library. Currently, we have
> nearly 140G in use. QINTER is shutdown prior to backup, no messages. No
> one should be on-line at midnight except for IT staff (if necessary) and
> we have our own SBS.
>
> A full SAVSYS is done whenever PTF's are applied.
>
> Cyndi B.
> Boise, ID
>
> --
> 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 the future then please respond to the sender to this effect.