RE: ending jobs normally -- MIDRANGE-L

Al

I faced this at one site I managed. My strategy was to list the jobs still 
active in the QINTER subystem to a file, then disable the profiles - I had 
previously agreed this with managers around the place (its never their 
staff causing the problems is it ?) and they all agreed to having users 
leaving screens signed on locked out of the system. Our policy at the time 
was that managers needed to request having user profiles re-enabled - so... 
to cut a long story short, the managers got VERY involved in making sure 
their staff signed off as it caused them a heap of work.

Of course, this only worked because we had individual profiles for everyone.

Cheers
Evan Harris

>I have also been giving the bosses lists of the people who do this all the
>time.  That sometimes seems to cut down on the volume for a short time.  The
>reality is that no one cares about this until they have to face their data
>messed up & rarely is there a mental connection between the garbage data &
>the human actions responsible.
>
>Our Job Scheduler GO CMDSCDE has a message that goes out to everyone who is
>currently signed on, approx 1/2 hour before end-day Fridays that there is
>little point to having their work station consuming electricity all week end
>& it would be appreciated if they powered it off after signing it off when
>they are done for this evening.  This has had a dramatic positive effect on
>the volume of sessions left open, but there are still a few users who are
>brain dead on the topic of end of work day should mean end of open sessions.
>For those of them who are involved in updating batches, as opposed to general
>inquiry, I am tempted to give them more frequent personalized GO CMDSCDE
>reminders.
>
>Subj:    RE: ending jobs normally
>Date:   09/19/2000 9:38:07 AM Central Daylight Time
>From:   ddetz@zinccorp.com
>
>JDE was contacted on this problem 7 months, 3 JDE employee's and one boss
>(mine) ago.  I gave up that it was a JDE problem cuz NO ONE knew.  I think I
>asked the JDE World list also a looonng time ago.  But while scanning
>through the logs and seeing the same msg's over and over of "ended
>abnormally" right when our subsystems go down and reallizing they were
>probably staying signed on ... It clicked.  It took me so long to figure it
>out cuz it was SO inconsistant.  Obviously cuz SOMETIMES they were in a
>batch and sometimes they weren't.  It is hard to keep track of the users cuz
>we are in a large manufacturing plant environment and they are about a mile
>down the river.  I'm making the trip today w/ a pair of sizzors to cut come
>fingers....  thanks for the help.
>
>-----Original Message-----
>From: Richard Jackson [mailto:richardjackson@richardjackson.net]
>
>The "batch in use" error arises because opening the batch sets a flag in a
>record in the batch header database file - F0011 maybe?  Whatever technique
>you use has to "un-set" that flag.  The standard way is for the display
>record to time out and the time out is detected by the program.  The program
>ends politely.  The problem with unsetting the flag is that the user may
>have modifying the batch part way and not be finished.  Turning off the flag
>on an uncompleted batch could be more hazardous than what you are doing now.
>In other words, I can figure out how to turn off the flag but I promise you
>that the database integrity for GL batches will be worthless.
>
>Used to be that JDE did the record time out themselves.  Do you have a
>really old version?  Did you turn off this feature?  Have you contacted JDE
>response line for a hint?  If you get no help from response line, drop me a
>note off line and I might be able to help.
>
>
>Richard Jackson
>mailto:richardjackson@richardjackson.net
><mailto:richardjackson@richardjackson.net>
>http://www.richardjacksonltd.com <http://www.richardjacksonltd.com/>
>Voice: 1 (303) 808-8058
>Fax:   1 (303) 663-4325
>
>-----Original Message-----
>On Behalf Of ddetz@zinccorp.com
>
>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
>
>
>Al Macintyre  ���
>MIS Manager Green Screen Programmer & Computer Janitor of BPCS 405 CD Rel-02
>running on AS/400 V4R3 http://www.cen-elec.com Central Industries of
>Indiana--->Quality manufacturer of wire harnesses and electrical
>sub-assemblies
>+---
>| 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
+---