RE: Temporary Key Problems

[rvera@xxxxxxxxxxxxxxxxxxxxxxxxxxxx]

I think Paul was joking...
The point is that the key keeps on working, we only need to reenter the same
key we received from SSA in order to continue working. Is like the key
registration file (or dtaara or whatever) gets corrupted and then is not
valid anymore...

Ramiro

****************************************************************************
*****

From: "Genyphyr Novak" <novakg@ssax.com>
Subject: Re: Temporary Key Problems

I quite doubt it, Paul, as that is impossible to do. There is no way to
magically cut a key to make it both apply successfully to the system, and
later suddenly stop working with this type of error (rather than a normal
expiration message).

I suggest Ramiro speak to the Keys Department (the ones who cut the keys for
you) to explain this error, and then when it happens, send a joblog from one
of these jobs to the Keys administrator at SSA GT. Perhaps they or the
Helpline could take a look and see if there is something else going on.

Program SYS670 can be called (without entering BPCS, but just by having the
BPCS libraries in your library list) to check whether or not the key is
applied properly, and what the expiration date is.

Thanks,

Genyphyr Novak
SSA GT

----- Original Message -----
From: "Paul LaFlamme" <laflammep@kennedydc.com>
To: "'SSA's BPCS ERP System'" <bpcs-l@midrange.com>
Sent: Wednesday, January 22, 2003 7:56 AM
Subject: RE: Temporary Key Problems


I suspect SSA is throwing you a bad key once in a while to get you to
resolve the contract! :)

Paul

-----Original Message-----
From: bpcs-l-bounces@midrange.com [mailto:bpcs-l-bounces@midrange.com]On
Behalf Of rvera@bai.boehringer-ingelheim.com
Sent: Wednesday, January 22, 2003 7:59 AM
To: bpcs-l@midrange.com
Subject: Temporary Key Problems


Hi, everybody

We are using BPCS 6.0.2 MM in a AS/400 and, due to a contractual problem, we
are using temporary keys, that are issued by SSA every 3 month.
The problem is that three o four times a month the key gets broken and the
users are not able to enter (they get an screen with two lines reporting
errors with numbers 9995 and 9996).
The solution for this problem is to reenter the key but we don't have a clue
about why this is happening...

?Is this happening to somebody else?

we will appreciate if some of you can help us

Thank you in advance

Ramiro Vera
Project Leader
Boehringer Ingelheim Argentina
_______________________________________________