001

01

Y

N

The Multi-User Facility could not
sign on a user for external security.

Collect all documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.

002

02

Y

N

The Multi-User Facility encountered
an error while signing off a user
with external security.

Collect all documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.

003

03

Y

N

The Multi-User Facility encountered
an internal error while attempting to validate a resource against external security.

Collect all documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.

004

04

Y

N

An internal security check was done with no security active.

Collect all documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.

005

05

N

N

DBINFPR could not extract a user
from an external security product.

Collect all documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.

006

06

Y

N

CA Datacom/DB was unable to load module DBSMNPR during run time.

Check for a message providing the load return code and pursue the documentation for that message.

076

4C

Y

N

One of the following occurred.
See the corresponding action.

• DBUTLTY security environment error.
• You attempted to run Single
  User against a secured Directory
  and were denied access.
• An internal security request was made for a Multi-User which is not externally secured.

Perform the following action for the corresponding reason.

• Contact CA Support.

For information about contacting CA Support, see Troubleshooting.

• Either do not run Single User or use the DBUTLTY CXXMAINT ALTER function to allow Single User to run in a secured environment.
• Contact CA Support

184

B8

N

N

One of the following occurred.
See the corresponding action.

• An internal security call was
  issued with no security active.
• Internal error.
• Cannot open SIT table for an
  SQL security check.

Perform the following action for the corresponding reason.

• Contact CA Support.

For information about contacting CA Support, see Troubleshooting.

• Contact CA Support.

For information about contacting CA Support, see Troubleshooting.

• Pursue the cause of the open error. The open error happend asynchronously with this error. Check the console messages for another error message and the PXX dumps that show the open error.