|
Jim wrote
I should also state that everything was working correctlyuntil 2 day ago when this happened, so dont know if a job ended abnormally in mid stream or something.
If you suspect that, try running SYS993 for her work station id with option 6 (Customer Order Picking)
which is one of the programs I copied from SYS/23 to our FXSHowever, that would not explain same work station working for some people but not for others, since vanilla BPCS (unless Y"all modified it) keeps track of stuff using combination of beginning characters of work station id and a few letters designating type of work being done.
Some of that stuff ends up in object type *DTAARA in your primary BPCS files library, which OS/400 permits us to access only one at a time. I have a program stream to dump all via DSPOBDJ into an *OUTFILE which an RPG then tries to analyse, comparing one line to the next to identify any time bombs from unreported abnormal terminations.
The other place to look is what members are in the E* files. Beware ... there are a few specialized ones unrelated to work station tracking. I earlier wrote
You are talking about a modification here, since in vanilla BPCS the IWM warehouse does not specify OUTQ.
Perhaps I could have phrased that better.This is one of those places in BPCS that is setup for something but is not working, so that someone who has not read what passes for standard documentation, or been involved in the testing when BPCS first installed, may not know what stuff is in BPCS, that your version of BPCS ignores.
In this case you need something more than WRKMBRPDM file BPCSDOC library *LIBL position to SSALOG00 - Al Macintyre http://www.ryze.com/go/Al9Mac BPCS/400 Computer Janitor ... see http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.