RE: ending jobs normally -- MIDRANGE-L

Title: ending jobs normally

I can't tell if I did anything. Did I give you new information?

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax: 1 (303) 663-4325

-----Original Message-----
From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of ddetz@zinccorp.com
Sent: Tuesday, September 19, 2000 8:13 AM
To: MIDRANGE-L@midrange.com
Subject: RE: ending jobs normally

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]
Sent: Monday, September 18, 2000 6:58 PM
To: MIDRANGE-L@midrange.com
Subject: RE: ending jobs normally

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
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-----Original Message-----
From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of ddetz@zinccorp.com
Sent: Monday, September 18, 2000 1:02 PM
To: MIDRANGE-L@midrange.com
Subject: ending jobs normally

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