×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I just finished another month's end fiscal.
Because we will be doing physical inventory at end of December, I tried to
clear out those locations whose inventory and requirements had gone to
zero, because each valid ILI record can become a printed physical inventory
tag, which I figure we only need on item-warehouse-location combinations
active in December.
It has been a while since I included this "zero purge" in end-fiscal,
because it takes a while to run.
I recognize that certain steps are only safe to run at certain points in an
end fiscal cycle.
100% of the update jobs were run from the main console with the system in
restricted state except for subsystems QBATCH and QSPL going ... I do it
this way to prevent any co-worker from signing on while I am in the midst
of critical stuff.
You see, except for people intimately involved in end-fiscal stuff, most
users are freed from needing to comprehend the implications of disobeying
"stay off until I tell you that you can get back on." So by doing it this
way, they are incapable of such disobedience, so I not have to worry about it.
This sandwiched between backup/400 GO SAVE 21 to different backup tapes
before and after the whole shebang.
Right after INV900 I ran INV970, pausing only to check record counts via DSPFD
IWI = 37,436 with none deleted
ILI = 62,618 with none deleted
that's in IBM file terms
before & after, none changed but audit trail says it found 10,218 ILI
records to be zero and claimed to delete them ... Oh they have record id LZ
not LI so they are coded for BPCS deletion but not actually gone
so I ran SYS120 expecting that to remove them, but it did not
and I was signed off while SYS120 was running (I was signed on with a
user-id that is not part of live environment to check to see when it got
done) since I have learned that the reorg skips any files in use when it
gets to them
Nothing else running concurrent with any of these steps
then I looked at INV973 code ... incidentally the program title is
misleading ... then ran it
that took us to
IWI = 27,131 records with 10,305 deleted in IBM terms
But we still have 62,618 ILI records with a sizeable volume coded LID = 'LZ'
I was getting fatigued ... I had been at this for many hours, partly
because we run a lot of end fiscal reports, and partly because I am looking
at results at various steps to see if stuff seems Ok ... so I continued on
to other steps
Later I plan to do SYS120 again to see if it removes any ILI whose related
IWI now gone.
Then if the ILI record count has not gone down, after another backup I plan
a later nite or weekend to do an IBM reorg where I tell RGZPFM to get rid
of all ILI where LID is LZ. I almost never touch RGZPFM since I consider
it extremely dangerous ... what if I make a keying error?
I suspect some of these LZ have been there from past deletion efforts.
Is this how it is supposed to work?
Am I missing something?
We are V5R1 AS/400 mixed mode BPCS 405 CD Rel 2 with mountain of Y2K BMRs.
-
Al Macintyre http://www.ryze.com/go/Al9Mac
Find BPCS Documentation Suppliers
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.