You could also look at Cosyn Software's Audit Trail;/400 solution.
That allows you to add a permanent or temporary audit trail , in minutes.



-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of bpcs-l-request@xxxxxxxxxxxx
Sent: Friday, 2 March 2012 7:00 a.m.
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 10, Issue 34

Send BPCS-L mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific than "Re: Contents of BPCS-L digest..."

*** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. mysterious/rogue updates to rate fields in LWK file (Milt)
2. Re: mysterious/rogue updates to rate fields in LWK file
3. Guidelines for BPCS-L mailing list (mailman@xxxxxxxxxxxx)


message: 1
date: Wed, 29 Feb 2012 12:23:59 -0600
from: "Milt" <mhabeck@xxxxxxxxxx>
subject: [BPCS-L] mysterious/rogue updates to rate fields in LWK file


Good morning,

Al Mac's comment is correct, Unbeaten Path does have tools "which can identify for you who is messing with what fields of what files, using what programs, when." If our 'NoExcuses HelpLine' guys were called on to figure out Ms. Reddy's mystery, we wouldn't waste time by plowing through tens of thousand of lines of code with our fingers crossed that we were looking at the culprit program. We'd simply install a temporary key for our Stitch-in-Time software and point it at the LWK file. It would capture the precise origin and nature of any prospective data accident. It's a very efficient debug approach ... especially for home-grown code.
[ www.unbeatenpath.com/software/sit/Stitch-in-Time.pdf ]

To get an email alert immediately when a data accident happens (e.g. movement from a numeric value to a blank), the approach is Needle in a Haystack software. That product uses artificial intelligence to learn what kinds of data changes are "normal" for a field. If it then spots something that falls outside the learned normal, a real-time email alert is sent to that file's guardian/business process owner. Immediate notification permits him/her to fix the accident before it messes up calculations (like CAP results in Ms.
Reddy's situation) and before it can be propagated into transactions.
[ www.unbeatenpath.com/software/needle/in-a-haystack.pdf ]

Peace to you,
Milt Habeck
Unbeaten Path
(888) 874-8008

From: chandrahasa reddy
Sent: Wednesday, February 29, 2012 6:57 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Reg: CAP100D2-02 Work Center Rate

Hi All,

For some of my work center's CAP100D1, rate fields LWK.WLRTE, LWK.WFOLR, LWK.WSSUR & LWK.WSMCR in CAP100D2-02 are getting cleared.
Can I know which program updates the above Work center rate fields & when does that happens?



message: 2
date: Wed, 29 Feb 2012 13:47:22 -0500
from: rob@xxxxxxxxx
subject: Re: [BPCS-L] mysterious/rogue updates to rate fields in LWK

First do this on your file
File is currently journaled . . . . . . . . : Yes
Current or last journal . . . . . . . . . . : BPCS_ALL
Library . . . . . . . . . . . . . . . . . : #MXJRN

We're a Mimix shop so it has to be journalled. If you start journalling on this file you can easily see who updated it, from what job, using what program.
Heck try it on your own test db somewhere.

Drawback, there's a whole discussion on journal receiver maintenance.
We've gone nuts with our journal receivers - they're so useful management wants to keep them for 100 days. So we tie up a TB or so with all the journalling we do. But what the heck, I have 1/2TB on my laptop.

Rob Berendt
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755


message: 3
date: Thu, 1 Mar 2012 06:30:38 -0600
from: mailman@xxxxxxxxxxxx
subject: [BPCS-L] Guidelines for BPCS-L mailing list

This is the BPCS list server. It is devoted to the discussion of topics
related to Infor's (formerly System Software Associates') Business
Planning and Control System (BPCS). We can generally concede that topics
involving AS/Set, ODW, and BPCS "bolt-ons" are acceptable. Discussion of
other software products as they relate to interfacing with BPCS is fine.
Discussion of hardware platforms as they relate to BPCS is fine as well,
but do not attempt to promote one platform over another. Discussion of
platform strengths and weaknesses is allowed.

Opinions are both welcome and encouraged, but longer threads should be
held "off line". Same for personal experiences. All versions and all
"flavors" of BPCS are welcome, as well as all hardware configurations.
Please contact the list moderator at bpcs-l-owner@xxxxxxxxxxxx if
you have any questions regarding appropriate content.

Questions regarding programming techniques as related to AS/Set or ODW are
allowed; however, native programming not specifically related to BPCS would
be better served on the midrange list server, MIDRANGE-L, or an appropriate
UNIX forum. Connectivity and AS/400 related questions, unless specific to
BPCS or CIMPath, would be better served by MIDRANGE-L as well.

While the participants of this list are happy to answer questions and
help solve problems, it is greatly appreciated if you do some of your
own research beforehand. Before posting a question for the first time,
please take a moment to review Eric Raymonds excellent FAQ "How to Ask
Questions the Smart Way" (http://www.catb.org/~esr/faqs/smart-questions.html).

Flames are ABSOLUTELY prohibited. We are all adults here, and can express
our discontent without childish remonstrations. Any person caught issuing a
flame will be immediately terminated from the list, or be forced to maintain
one of the "500" programs using screen arrays instead of subfiles and at
least twelve "dead" subroutines -- you decide which is worse.

Employment related discussions are off-topic in this technical discussion
forum. Please restrict abstract employment discussion to MIDRANGE-L and
specific employment discussion to MIDRANGE-JOBS.

When posting a long weblink (URL), consider using http://tinyurl.com to
shorten it. Some mail programs wrap long text and cause URL's to break.

By posting to this mailing list, you are granting MIDRANGE dot COM and
David Gibbs (david@xxxxxxxxxxxx) non-exclusive, unlimited, rights to
republish its contents.

PLEASE NOTE: When posting to the list, any personally identifying
information in your message will be included in the list. Email
addresses, however, are masked when being formatted for the list
archives. If you include a standard signature in all messages, consider
using the internet standard for signature separator (as defined in RFC
3676, http://tools.ietf.org/html/rfc3676) of '-- ' (that's dash dash
space). The list archiving software will automatically stop including
the message when it encounters the marker.

This list IS copyrighted as a compilation. Republication of this mailing
list, for anything other than personal use, without the explicit permission
of the list owner is a violation of U.S. Copyright Law and will be dealt
with as such.

Collecting or "Mining" of email address from this forum, or any related
web archive, is strictly and explicitly prohibited (not to mention that
it is extraordinarily unprofessional).

PLEASE do not report list messages to your mail providers abuse / spam
department. This results in a black mark against midrange.com and,
depending on the mail provider's policies, can cause mail delivery
delays for everyone who uses both midrange.com with that mail provider.
midrange.com does treat abuse reports very seriously and acts upon them
immediately. When abuse reports are received, and the reporting person
can be identified, they will be removed from all lists immediately ...
and then a follow-up email will be sent.

If you wish to be unsubscribed from a list and cannot do so through the
normal mechanisms (identified at the bottom of every list message),
please contact the list owner or support@xxxxxxxxxxxx for assistance.

Advertising products, repeated postings, etc, are strictly prohibited.
Also, if you have a solution that will specificly help another
participant, feel free to tell that person. And finally, if you are a
vendor, please identify yourself as such... do not try to pass yourself
off as a user of your own products (even if you are).

To subscribe, unsubscribe, or change mailing list options, please visit

The official language of the BPCS mailing list is English.

MIDRANGE dot COM, midrange.com, the owners and operators of this list are
in no way associated with Infor or International Business Machines (IBM).
The opinions expressed here are strictly those of their authors, and in
no way reflect the opinions or statements of direction of the
aforementioned companies.

MIDRANGE dot COM is a non-commercial organization dedicated to the free
exchange of ideas and information among computer users on the Internet.
For more information: Email support@xxxxxxxxxxxx.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.