Re: BPCS 4.05 CD Bugs CST270 CST900

You might not consider this to be a buggy situation.

Additional description lines of CST270 are treated as reportable lines (report unreadable unless modified) and if you have a lot of lines in a lot of shop orders, at time of purge, this will "blow up" your spool file.

There is some ceiling on how many print lines you can have in a report before an AS/400 error message asking what you want to do about report filling up ... depending on how much stuff on a page, it is around 10,000 pages.

CST270 is embedded in the CST900 job stream. In a typical CST900 for us, we get around 30,000 pages.

We dealt with this several ways.
1. We have a modified version of CST270 which eliminates the ridiculus stuff that does not belong on the report, and we created some other reports structure to get at the spirit of the info.
2. We told the CST900 jobstream to make it NOMAX on # of pages & we delete them all at end of jobstream.

Also note that if your system can be quiet (no other users) running SYS120 before CST900 is great for performance.

SYS120 takes about 3/4 hour on our system.
CST900 takes maybe 4-5 hours if no SYS120.
CST900 takes maybe 2-3 hours if SYS120 ran first
All this if system quiet. System goes slow on steroids if people trying to access the same stuff that reorg purge trying to clean up.

Other people on this list, in past posts, have made some disparaging remarks about the quality of data on this CST270 report, and there are issues of report navigation.

CST900 update run also has some of the rounding "problems" I mentioned in an earlier "bugs" post.

Al Mac
BPCS 400 jack of all trades, master of not enough

> > If you know of any similar bugs in BPCS 4.05 CD PTF1 please let me
> > know.
> >
> > Peter Lunde
> > Manager, IT
> > WellSpring Pharmaceutical Canada Corp