Resolving Ideal authorization Error IDAETERR64E
search cancel

Resolving Ideal authorization Error IDAETERR64E


Article ID: 262954


Updated On:


Ideal Datacom


While trying to use the "DEBUG" function on a Prod status IDEAL Program, the user is getting the below error:

IDAETERR64E - User Not Authorized for Program. 

We would like to know what caused this error and what the resolution is.


Release : 15.1

Component : Ideal


The user running the DEBUG commands did not have the necessary privilege to debug PROD status programs.


According to the "Commands" section of the Symbolic Debugger documentation, running the Debugger in general requires that the user must have UPDATE access to the Ideal system containing the programs being tested. Further, to run Debug against Prod status programs, the user must also have Ideal Administrator privileges (this assumes that the default authorizations have not been changed).

To determine the level of access for the user and the level of access needed, you can do the following:

1. For Debug processing levels, an Ideal Administrator will need to issue the command D ATZ (Display Authorizations). Then, find the entries for DEBUG-PROD, DEBUG-TEST, and the relevant RUN* authorizations. For example,a to run a Prod status program, the authorization for RUN-PROD, RUN-PROD-USING-PANEL, or RUN-PROD-USING-PROGRAM will be used. By default, DEBUG-TEST requires UPDATE access to the Ideal system containing the programs being tested. DEBUG-PROD is used to test PROD status programs and therefore requires Ideal Administrator access.

2. Once the levels that are needed have been identified, the Ideal Administrator will display the user's profile, and determine if they have the proper access to the Ideal System (to be able to run the program and to execute the Debug commands (for non-Prod versions). If trying to Debug a Prod status program, they will need to determine if the user has Ideal Administrator privileges (based on the default settings).

Since granting Ideal Administrator access just to Debug Prod status programs has significant security ramifications, we would recommend that the Prod status programs be copied (DUP PGM) to a new, Test status version, and then the user can run Debug against that version to recreate the problem. Once the Debug activity is done, you can either delete those test versions, or make your corrections to them and promote them as usual.

Additional Information

For more information on using the Ideal Debug processing and the security levels needed, please review the documentation for the Symbolic Debugger.

For more information about Ideal authorizations, please see the Ideal Administration documentation for the Authorization Table and Maintaining Authorizations.

As always, please contact Broadcom support for Datacom if you have further questions.