Skip to Content
Nov 20, 2016 at 07:51 PM

IDES developer key is not validated

300 Views Last edit Nov 20, 2016 at 07:53 PM 2 rev

Hi, dear experts

the problem is that I had fair and fully-functional developer key for my IDES installation, which worked just fine, but due to certain circumstances my user was locked and invalidated ("valid to" date has expired) and I lost ability to create new Z-programs.

After time, user was renewed but now the system constantly prompts me to enter developer key when I try to create something. Also I lost the key itself as it was sent to me long long ago, and my message box has self-cleaning policy. All my colleagues from the training group work as before and their keys are still functional.

What can I do in such situation? My BASIS guy is a total newbie and has no idea what to do in that case. And I has no direct access to OSS.

I checked DEVACCESS table and dev-key maintained against my user is still there, but it is invalid when I try to enter it in a prompt window. How that cold be? It was perfectly functional before and the user is still the same. How the validation is made?

I read dozens of old threads and the question is raised in a couple of them (for example here and here) but nowhere have been given an answer.

I have basic idea about the issue:

1. I know that validation is made via system call CHECK_DEVELOPER_KEY, as stated here, and this call is made in FM CHECK_DEVELOPER_KEY.

2. I know that developer keys are stored in DEVACCESS table and this table is checked when any Z-changes are made.

3. I know that the developer keys are generated using Installation number and User ID as input parameters. And if these values haven't changed, the key should be valid.

In my case all these prerequisites are met (installation number and user ID left unchanged) but the key now is not approved by system. Why?

Is this assumption about encryption of DEVACCESS table correct?