RE: backups on AS/400, objects

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Try just ending QINTER subsystem and any other subsystem you may have
created for interactive jobs.  Also sounds as if you software has no built
in safe guards.  Critical jobs with multiple steps should have a data area
or something that controls access.  IE
1 job step1 submitted
2 job step1 started
3 job step1 completed
4 job step2 submitted ....


Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: MacWheel99@aol.com [mailto:MacWheel99@aol.com]
Sent: Tuesday, May 29, 2001 12:05 PM
To: MIDRANGE-L@midrange.com
Subject: Re: backups on AS/400, objects


Well of course system history helps us identify who was on when, if we want 
to take the trouble to dig, but what I seek is a corporate policy of 
cooperation with what they want MIS to do, that is economical.

The original poster in this thread had a somewhat different interest I 
believe.

It is not economical for me to be doing long distance phone calls to remote 
sites to try to determine if the people are really there or gone home & left

their work stations in the middle of update programs.

I do send message, but unfortunately we do have novice users not yet able to

recognize messages, let alone repond to them.  Fortunately not many of those

people doing update programs.

This is one of the reasons I take the whole system down for backup.
Just imagine if we were doing some other kind of save & people signed on in 
middle of it.

I have hard enough time with my boss during EOM ... there are some jobs that

need only ONE user on running this or that job step, until it is done ... 
second user locks up the job & guess who ... most of the lockups are within 
the same department that knows this & supposed to enforce only one user
until 
those jobs completed.

We have had a bunch of crashes with inventory transactions to general ledger

& every single one of them traced to the people who do that work being 
impatient & going to next step before first step completed.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---