Re: About BPCS V6.1.01 MM -- BPCS-L

Hello,

I have to take issue with Dean's postings of late such as:

>>I don't mean to be ugly, but >>>
>> WHY DO YOUR PROGRAMS
> _LEAVE_ RECORDS IN THE WORK FILES IN THE FIRST PLACE???  Don't give me
that
> "the client crashed" excuse, either.  I haven't had enough clients crash
> within a week of clearing the files to generate 13K+ records.  etc.......

Can we get some facts about these problems please?

First of all, what release and cumulative level of BPCS was this problem
about work files even in regards to? And what application are we speaking
about here? Was this 2 years ago - there was definitely a bug back then in
Order Entry COM which caused work files to fill as a program when into a
loop --- long since fixed. You posted back that you don't use this program
anymore. If you re-wrote the offending application, when when was this work
done - last week or last year or two years ago? How do you know what current
code in BPCS is doing to those work files if you aren't even running it
anymore?

I also wonder why your statement "Then again, all serious BPCS work seems to
have ceased since Gores took over. " is based on experience with 1 BMR not
getting completed? Dennis Dompke from SSA GT asked for a BMR number so that
he could research the problem. You mentioned this could not be determined
because OGS was down when you checked.

In fact, OGS is not down today, nor yesterday. I verified with our web
master that the system has not been down for quite some time now (several
months) since we upgraded the search engine on the site (this was the cause
of previous downtime). The BMR search utility is up and working.  Maybe the
problem is with your user ID or firewall - have you checked with the
Helpline about why you are unable to access OGS?

You said the BMR which was escalated but not being worked on was about an
SSATCP job sending bad parameters to BIL. SSATCP jobs only run COM, CEA or
OLM jobs. Some COM jobs update billing file records, but BIL programs are
run through the thin client  (NEWI) interface, so SSATCP would not pass them
any parameters directly. Pro-forma invoices in COM are generated via some
calls to SYS programs which then later call BIL programs in batch to do
printing. Can you mention what BIL program this was in regards to and a
basic outline of the problem? I can look up the BMR by its description for
you on OGS if you give more details about the problem.

If anyone doubts that serious coding work is occurring at SSA Global
Technologies and want to see what work __IS__ being done on BMRs, I suggest
checking out OGS Online.

If you have paid for OGS support, you can see on the OGS site a listing of
Recently Passed BMRs which is updated on a daily basis, and shows all new
code fixes which have been passed for each release of BPCS in the prior 30
days to the inquiry date. This can be searched on by release and priority
code, so that customers can use this as a pro-active tool to obtain the
latest code fixes for products they use on their system and release level.

Currently (as of today) it shows 33 pages of BMR objects which have been
completed on various releases of BPCS in the past 30 days. Additionally,
several people on this mailing list have mentioned hearing our announcements
to customers about a planned new release of the product. This doesn't seem
to bear out the accusation that serious work has stopped at SSA Global
Technologies since the takeover.

I would suggest that Dean take more seriously the idea that he is the
(neutral) moderator of this mail listing, as recent posts seem to treat
facts rather like the US presidential debates have done!

Thanks

Genyphyr Novak
SSA Global Technologies






----- Original Message -----
>
> You know Clare, you're the second or third SSA staff member to suggest I
> clear the work files.  I don't mean to be ugly, but WHY DO YOUR PROGRAMS
> _LEAVE_ RECORDS IN THE WORK FILES IN THE FIRST PLACE???  Don't give me
that
> "the client crashed" excuse, either.  I haven't had enough clients crash
> within a week of clearing the files to generate 13K+ records.  There is
> something _seriously wrong_ with BPCS, which should be quite easy to
correct.
>  Then again, all serious BPCS work seems to have ceased since Gores took
> over.  We reported an occasional problem with the SSATCP jobs sending the
> wrong number of parameters to a BIL program over six months ago and have
yet
> to receive a fix.  Is this the level of support to be expected for BPCS
under
> the Gores regime?
>
> Regards,
>
> Dean Asmussen
> Enterprise Systems Consulting, Inc.
> Fuquay-Varina, NC  USA
> E-mail:  DAsmussen@aol.com
>
> "I put instant coffee in the microwave and almost went back in time." --
> Steven Wright
> +---
> | This is the BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---
>

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---