We do a shutdown of QINTER while it (MRP) is running - I don't know if
that is necessity.
-----Original Message-----
From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf
Of Bryce Martin
Sent: Wednesday, September 29, 2010 7:20 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Not what did I do to MPR nightly run??
Don,
How did the MRP run do last night?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
"Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx> Sent by:
bpcs-l-bounces+bmartin=c-sgroup.com@xxxxxxxxxxxx
09/28/2010 11:58 AM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
To
"BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
cc
Subject
Re: [BPCS-L] Not what did I do to MPR nightly run??
Did not dump - just displayed the message
________________________________
From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx on behalf of
Bryce Martin
Sent: Tue 9/28/2010 10:42 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Not what did I do to MPR nightly run??
Did that item happen to be in the dump of MRP600? Or did you not dump
it?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
"Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
Sent by: bpcs-l-bounces+bmartin=c-sgroup.com@xxxxxxxxxxxx
09/28/2010 08:24 AM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
To
"BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
cc
Subject
Re: [BPCS-L] Not what did I do to MPR nightly run??
405cd. It looks like the error was around the Order Policy code/Period
order days - array related code. We noted that a user had changed a
part#, with an Item Type = c, to an order policy code = k yesterday.
That was the only item type C with a K order policy code in the file.
-----Original Message-----
From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf
Of Bryce Martin
Sent: Tuesday, September 28, 2010 7:15 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Not what did I do to MPR nightly run??
Don,
Did you rerun MRP600? Did it finish correctly? Is your MRP600 code in
AS/SET or is it out of the box and in RPG?
My suggestion would be to pull it out and put it into RPGLE, recompile
it into a special library, then put that library at the top of the list
for tonights run. Then you could possibly hunt down the error by the
statement number... This could be a tough one to run down. If you
dumped it you could check for an array index of less than 1 in the dump
and try to find the offending code which might reveal the offending
data. What version are you on?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
"Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx> Sent by:
bpcs-l-bounces+bmartin=c-sgroup.com@xxxxxxxxxxxx
09/28/2010 07:07 AM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
To
<bpcs-l@xxxxxxxxxxxx>
cc
Subject
[BPCS-L] Not what did I do to MPR nightly run??
After running w/o error for many years, maybe I have some bad data in a
file ??
Message . . . . : The MRP600 435400 array index is not valid (C G S D
F).
Cause . . . . . : The RPG program MRP600 in library BPCDREL02 tried to
use
the array index at statement 435400 which was less than one or greater
than
the number of elements in the array.
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: bmartin@xxxxxxxxxxxx
--- This message (including any attachments) is intended only for the
use of the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential,
and exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify us and
destroy this message immediately. ---
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: dcavaiani@xxxxxxxxxxxxx
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: bmartin@xxxxxxxxxxxx
--- This message (including any attachments) is intended only for the
use
of the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential,
and
exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited.
If
you have received this communication in error, please notify us and
destroy this message immediately. ---
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: dcavaiani@xxxxxxxxxxxxx
midrange.com
