RE: BPCS 4.0.05CD

Paul, Chuck,...
No you're not alone.
We are in the middle of testing our Y2K Modified BPCS release 2.1
We are also moving to RISC in the process.

Getting the RISC code and keys from SSA has been a bad joke.
First order of the "RISC Pack" was sent to an address I never heard of.
Our company never had an address of any kind in the town they sent it
to.
Second "RISC Pack" arrived with instructions for use with a different
release.
Installed the second Pack, set up the libraries and tried to run.  Found
that
within the libraries they sent us at least two programs had level checks
against their display files. Fortunately, they were CL and I was able to
retrieve the source and recompile.

First temp key they gave me was incorrect and wouldn't apply,
second one worked. Had them FAX me the form to request a
permanent key which I filled out and sent back. They returned it,
turns out there was a second sheet they needed filled out with
check boxes for the products we have. Filled it out, sent it in,
and got a permanent key back.

Y2K testing was going on and we were ready to change the system date
to December 1999. (Yes this is on a test box.) Forgot to apply key
first, so when the date was changed the temp expired. Tried to
enter the perm and found out it was bad. Called SSA and explained
the problem. Two hours later, I called them back and asked how it
was going. They said they were working on it. I asked when would I
hear back from them and they said in a day or two. I told them I had
people I had brought in for testing who were unable to do any work.
They said they would make it a "priority one" call and that I would 
be called within four hours. Three hours later they called. Over the
next three hours on the phone with them we were able to apply the
permanent key but the system still wouldn't work.

Turned out that when they create the key they tell their program that
we are running on an S20, which is correct. When we apply it to our
system, the programs they gave us read the key and think it is for
a B20, identifies a violation and signs us off the system.

Their solution was to change the system date back to the current date
and enter a new temp key they gave us, then don't change the date.
I needed to change the system date for our testing. By this time
it was getting late and they wanted to go home, so they said they
couldn't help us but an Incident was logged. Almost a month later
I still haven't heard anything from them.

My solution, was a little different. Suffice to say, I changed the
system
date and we are testing.

What I've learned so far, (as though I didn't already know it) SSA's 
database(s) apparently not only cannot keep track of where our
company is they don't seem to know what we own. They will gladly
send you software that will not work until you fix it. If you have a
problem which stops you from working, don't be surprised if they
treat it with less urgency than you might like. When a flaw in their
software is found and an Incident is logged, don't expect any
fast fixes.

Sorry for going on so long, but it felt good to vent.
As my operator says, "relax, take deep cleansing breathes..."

 -steve cotes
 -cotess@data-io.com

> ----------
> From:         Paul[SMTP:kdcma@ix.netcom.com]
> Sent:         Tuesday, May 05, 1998 4:17 AM
> To:   BPCS-L@midrange.com
> Subject:      Re: BPCS 4.0.05CD
> 
> Chuck,
> 
> Always good to know your not alone! Thanks for the sympathies! Finally
> got the BASE
> CD product loaded and the key to apply. I had to download ANOTHER fix
> from their FTP
> site and put it up. Not sure why I'm so different... But anyway, I get
> the base
> product loaded, which was on 5 1/4" cartridges, then I dig out the PTF
> tapes which
> is on 6 1/4" cartridges (that's right, 6 - one more than the whole
> product) and
> proceed to install it. What do you know, it is done after tape 3. I
> call the
> helpline back and they don't know if it should have taken more tapes,
> nor can they
> tell me if the 394 objects restored to BPCSCDPTF1 is the correct # of
> objects or
> not! It's really quite comical, if not pathetic, wouldn't you agree?
> 
> Paul
> 
> Chuck Lewis wrote:
> 
> > Paul,
> >
> > SSA (and their "alliance partners") have got to be the WORST when it
> comes to
> > keys... I don't fault the folks that answer the phone, it's whoever
> came up with
> > the STUPID way they do things. I won't EVEN get into, if PC vendors
> have gotten
> > away from this garbage, SSA still feels a need (but they aren't
> alone there). I
> > just WISH they could write a program that would be part of there
> base library
> > that would include a "master key" that through a secure database
> would know
> > about ALL alliance products and that there would be a way (say
> through ECS or
> > something) to enable different modules. When we went from CISC to
> RISC 2 years
> > ago, the RSS people had to provide THREE keys because theirs are
> DATE sensitive
> > and we were not sure what day (Saturday, Sunday or Monday) are
> upgrade from a
> > BIG 320 to a BIGGER 530 would be ready to start loading RISC
> application
> > "upgrades". Then I don't know HOW many times we have been told we
> are getting a
> > PERMANENT key and it ends up expiring...
> >
> > OK, I taken a deep breath and will be OK now <BG> you have my
> sympathies !!!
> >
> > Paul wrote:
> >
> > > I'm in the middle of a migration and we're having a hard time
> getting a
> > > temporary key to work on my RISC box just to unlock the software!!
> It's very
> > > frustrating because you play telephone tag with SSA helpline and
> you usually
> > > end up with a "try this and if it doesn't work call me back." That
> cycle can
> > > take a day sometimes!
> > >
> > > Paul
> > >
> > > Mario La Rosa wrote:
> > >
> > > > Does anyone know of any companies that are actually live and
> using BPCS
> > > > 4.0.05CD in production??
> > > > +---
> 
+---
| 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
+---