RE: ending jobs normally

[Bryan Burns <burnsbm@xxxxxxxxxxxxxxxxxxxx>]

Perhaps the user's AS/400 connection is being broken when they are in the 
batch, through a power failure or network problem that is no fault of their 
own.  This will also keep the "batch in use flag" set.  It happens here 
occasionally and I really cannot blame the users...


Bryan Burns
System Operator
Echo, Inc.
Lake Zurich, IL
Burnsbm@echoincorporated.com
847-540-8400  x493



-----Original Message-----
From:   D.BALE@handleman.com [SMTP:D.BALE@handleman.com]
Sent:   Tuesday, September 19, 2000 3:59 PM
To:     MIDRANGE-L@midrange.com
Subject:        RE: ending jobs normally

Um, threaten to cut off their fingers?
Only kidding, of course.  But it amazes me that companies allow their users 
to
abandon their terminal without signing off.  What is so hard about this?
After the first time, your users know they've lost their batch and have to
rekey from the start.  Well, maybe not, if you're an "enabler".  ;-)

Don't think you're gonna find the magic command you asked for.  But I could 
be
wrong.

Technically, it is possible to modify the program to "wake up" after a 
certain
period of inactivity and take specific actions on such a "wake up", such as
run certain routines to close the batch, etc.  What do you do if there are
errors in the batch?  Personally, (and I realize I'm being spiteful  here) 
I'd
kill the batch and make them re-enter it first thing in the morning.  From
scratch.  Are you able and willing to modify this JDE application?

But, I will reiterate...  You do NOT need a technical solution here, you 
need
user training (and enforcement).  There is NO excuse for leaving your 
AS/400
session signed on when you leave for the day.  NONE!

Just my personal opinion!
Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

---------- Original Message ----------

We have a situation that users are leaving their terminals on while in JDE.
This is causing us to get a "Batch in Use" error.  To make a long story
short, we have to mannually go in and get these batches posted and deal w/
the GL etc. etc.

How do we get these users off "normally" before they get kicked off when 
our
backup starts at 02:00.  Our backup endsbs *immed so this ends their jobs 
w/
a code 50 - jobs ended abnormally.  This holds the last batch they were in
and keeps it "in use".

Is their some "kind" command to end their jobs w/o just cutting them off?

TIA

Dawn L. Detz
System Administrator
Zinc Corporation of America
300 Frankfort Road
Monaca, PA  15061-2295
ddetz@zinccorp.com
+---
| 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
+---

+---
| 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
+---