× 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.


  • Subject: RE: BPCS 3.0 Questions
  • From: Clark@xxxxxxxxxxxxxxxxxxx (Clark, Ruth)
  • Date: Wed, 06 May 1998 11:48:20 -0700
  • Organization: dotCom


Mark wrote (snipped):

>I've just started at a company that is using a heavily
>modified version of BPCS 3.0 on the AS/400.
>They have not carried on the software maintenance
>for years. My first task here is to bring the software
>up to Y2K compliance.

>I've encountered some non-observable programs (of
>course, also without source.)  They begin with a
>call to SYS900, which calls some programs in the
>SYS65x series. I understand that these are probably
>used for security and license purposes. What I need
>to know is how these programs will react on 1/1/2000,
>and secondly, if/when we move to RISC, what are our
>options (other than paying big $$$ to SSA?)

First of all, if you move to a RISC box you will most likely
have to pay an upgrade fee to SSA because BPCS license
fees are tied to the model number of your AS/400.  I don't
know if you'll be required to pay maintenance fees, though.
(Anyone want to chime in with an answer?)  Also, you will
need to get from SSA the RISC versions of the SYS programs
if you move to a RISC box.

I'm not positive from reading your post, but it sounds like
you're going to stay on V3.0 and make it Y2K compliant.
Since your system is heavily modified, converting is definitely
the best decision--there's not enough time to upgrade to
another version or go to another package if you're just starting
now.  Regarding the SYS900 and SYS65x programs, your
potential for date-related problems is directly dependent on
the approach you take for century conversion.  Almost all of
the Y2K tools out there will completely fail when dealing with
those BPCS programs, and the workaround is tremendously
time-consuming, because you can't get the source for those
SYS programs.

That's a good example of why it's so important to use a Y2K
solution that was specifically designed for BPCS.  (full disclosure--
I work for Nexgen, makers of Focus/2000.)  Focus/2000 knows
about all of the BPCS idiosyncracies, so it works fine with those
SYS programs, without interfering with the SSA security.

 --Ruth Clark
Nexgen



+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@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
+---


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-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.