Don,
In true 20/20 hindsight :), what we should do next time is check if the
facility is still locked when you answer the message in the morning.
Check file ZMF field MFULCK (I hope I spelled that correctly) for the
facility you ran in MRP. If the field is blank, then whatever was locking
the facility has already completed normally, and you don't need to run the
reset. If not blank, then you'll know whose job it is and can look to see
what is running.
The danger in running the reset is that, unless something ended abnormally,
whatever caused the lock is still active and the lock is legitimate.
Master Schedule Generation (MRP500) and Capacity Requirements (CAP600) are
both possibilities. If you allow more than one active job for the
subsystem, or if you submit to different subsystems, the jobs could have
overlapped and caused the conflict.
Kevin Harper
Waterfall Data Solutions, Inc.
----------------------------------------
Return-Path: <bpcs-l-bounces+kharper=waterfalldata.com@xxxxxxxxxxxx>
Received: from mailout.midrange.com (mailout.midrange.com [69.3.23.26]) by
maila23.webcontrolcenter.com with SMTP;
Thu, 8 Apr 2010 06:57:34 -0700
Received: from rivendell.midrange.com (localhost [127.0.0.1])
by mailout.midrange.com (8.14.3/8.14.3) with ESMTP id o38DvbFq015862
for <kharper@xxxxxxxxxxxxxxxxx>; Thu, 8 Apr 2010 08:57:40 -0500
X-DomainKeys: Sendmail DomainKeys Filter v1.0.0 mailout.midrange.com
o38DvbFq015862
DomainKey-Signature: a=rsa-sha1; s=dk; d=midrange.com; c=simple; q=dns;
b=YiOP1Tv4I0evkwADxeYEWClyvq3XOpjBfSq21OJa0ItP46iMxBo57EkUsbYjy6Nmu
m8zBE9E7XzzDMyV1LMnnA==
X-DKIM: Sendmail DKIM Filter v2.8.3 mailout.midrange.com o38DvbFq015862
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=midrange.com;
s=midrange; t=1270735060;
bh=/lSeJ7AzVjP5ODow666tfuhXhVxyUcp1BweXdasRYzM=;
h=MIME-Version:Date:Message-ID:References:From:To:Cc:Subject:
Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:
List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender;
b=ruSALzN6QLeP+ktjU9Q+LVNb3YdpAw+xJCpjS9zKyLRHEdeBvWxF25HQMXpGFL1Sa
IFJ0kS72JqWPvWdvKAAKoetO2Ts0EFqvZ4VoiPP8swdoaWO0QJ73NX1/UsJ2ghdORO
CgmBFtthSFBK4B7+yHZ+A1KIKx3o42xavpT19+kA=
Received: from amerkiel-nhw.amerequip.com (amerkiel-nhw.amerequip.com
[209.103.237.18])
by mailout.midrange.com (8.14.3/8.14.3) with ESMTP id o38Duig5015491
for <bpcs-l@xxxxxxxxxxxx>; Thu, 8 Apr 2010 08:56:50 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 8 Apr 2010 08:56:35 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID:
<B06F8E8D4C33474D86CF132FEA1CB0CB013CB007@xxxxxxxxxxxxxxxxxxxxxxxx>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BPCS-L] User has Facility LOCKED for processing ?
thread-index: AcrXIl5nJ+fewiz6Q5GESn5lrv4pVgAANjww
References:
<B06F8E8D4C33474D86CF132FEA1CB0CB013CAF8C@xxxxxxxxxxxxxxxxxxxxxxxx><8CCA5290
461D674-1E10-136D@xxxxxxxxxxxxxxxxxxxxxxxxxxx><B06F8E8D4C33474D86CF132FEA1CB
0CB013CAFB9@xxxxxxxxxxxxxxxxxxxxxxxx>
<362073.98154.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
From: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
To: "BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
X-Virus-Scanned: clamav-milter 0.96 at rivendell.midrange.com
X-Virus-Status: Clean
Cc: Melissa Lefeber <mlefeber@xxxxxxxxxxxxx>
Subject: Re: [BPCS-L] User has Facility LOCKED for processing ?
X-BeenThere: bpcs-l@xxxxxxxxxxxx
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
List-Id: BPCS ERP System <bpcs-l.midrange.com>
Auto-Submitted: auto-generated
List-Unsubscribe: <
http://lists.midrange.com/mailman/listinfo/bpcs-l>,
<mailto:bpcs-l-request@xxxxxxxxxxxx?subject=unsubscribe>
List-Archive: <
http://archive.midrange.com/bpcs-l>
List-Post: <mailto:bpcs-l@xxxxxxxxxxxx>
List-Help: <mailto:bpcs-l-request@xxxxxxxxxxxx?subject=help>
List-Subscribe: <
http://lists.midrange.com/mailman/listinfo/bpcs-l>,
<mailto:bpcs-l-request@xxxxxxxxxxxx?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: bpcs-l-bounces+kharper=waterfalldata.com@xxxxxxxxxxxx
Errors-To: bpcs-l-bounces+kharper=waterfalldata.com@xxxxxxxxxxxx
X-Rcpt-To: <kharper@xxxxxxxxxxxxxxxxx>
X-SmarterMail-Spam: Commtouch 0 [value: Unknown], SPF_Pass, DK_Pass,
DKIM_Pass
X-CTCH-RefId: str=0001.0A090206.4BBDE0F0.0173:SCFSTAT10360365,ss=1,fgs=0
X-SmarterMail-TotalSpamWeight: 0 (Trusted Sender)
Les - what if Capacity was running at the time the MRP kicked off?
-----Original Message-----
From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf Of
Les Mittman
Sent: Thursday, April 08, 2010 8:47 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] User has Facility LOCKED for processing ?
Hi Don,
Kevin is correct that the Reset Facility Locks option must be run to allow
MPS/MRP to run again. I believe you are on V4.05CD. On that version, the
option can be found on Menu SYS, Option 23 for System Reorgs Menu, Option
25 for Reset Facility Locks.
When MPS, MRP, or DRP generations run, BPCS places the UserID into the
Facility Master (ZMF) file in a field that indicates the Facility is
currently being planned. The reason is that for proper planning results,
you must run the planning jobs in a specific sequence. BPCS does not want
to allow conflicting planning for the same Facility to run simultaneously.
When your job terminated, it left a value in the ZMF file. The Reset
option will clear that value and it will also set a flag to tell MPS/MRP to
clean up workfiles from the prior run.
So, by running the Reset, you will again be able to run planning.
This addresses the problem, but it does not address why the program hung
originally.
What other jobs were running at the time? Was there another planning job
that was in process?
I hope this information help. If you have additional questions, please let
me know.
Thanks.
Les Mittman
847-858-5235
BPCS Consultant for over 20 years.
________________________________
From: Don Cavaiani <dcavaiani@xxxxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Thu, April 8, 2010 7:28:45 AM
Subject: Re: [BPCS-L] User has Facility LOCKED for processing ?
Hi Kevin,
I'll take a look at that - BUT - how could that be 'triggered' to lock ?
Thanks,
Don
-----Original Message-----
From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf Of
washburnccinc@xxxxxxx
Sent: Thursday, April 08, 2010 6:52 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] User has Facility LOCKED for processing ?
Hi Don,
Try the program for
Reset Facility Locks SYS996D
I think it is on the SYS01 menu.
Kevin Washburn
Washburn Computer Consulting, Inc.
www.washburnccinc.com
Milwaukee Area: 414-587-9098
Waukesha Area: 262-363-9098
Fox Valley Area: 920-787-1996
-----Original Message-----
From: Don Cavaiani <dcavaiani@xxxxxxxxxxxxx>
To: bpcs-l@xxxxxxxxxxxx
Sent: Thu, Apr 8, 2010 6:23 am
Subject: [BPCS-L] User has Facility LOCKED for processing ?
During the MRP run last night, the job hung with the above message.
Where do I o to clear that up? I entered a "C" to cancel the job.
Don F. Cavaiani
T Manager
merequip Corp.
20-894-7063
It's amazing what you can accomplish if you don't care who gets the
credit." arry S. Truman
--
his is the BPCS ERP System (BPCS-L) mailing list o post a message email:
BPCS-L@xxxxxxxxxxxx o subscribe, unsubscribe, or change list options,
isit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
r email: BPCS-L-request@xxxxxxxxxxxx
efore posting, please take a moment to review the archives t
http://archive.midrange.com/bpcs-l.
Delivered-To: WASHBURNCCINC@xxxxxxx
--
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: lmittman@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: dcavaiani@xxxxxxxxxxxxx
midrange.com
