Troubleshooting and Best Practices

Authentication errors

Verify the credentials are correct, that your user ID is not revoked and your password has not expired, and that they are set at the right host or endpoint scope. Reset them and enter them again if needed.

A "not authorised" message for a dataset or resource comes from your own RACF, ACF2 or Top Secret access. Request access through your normal process.

Error statuses and codes

The published APIs tell these cases apart:

• 401: the sign-on failed (wrong password, revoked user ID or expired password), or no credentials were provided.
• 403: your security product refused access to the dataset or resource.
• 404: the record or dataset does not exist.

An error body carries error, a readable message, and for the common cases a stable code, such as RECORD_NOT_FOUND, DATASET_NOT_FOUND or KEY_METADATA_NOT_LOADED. Test the code in a client instead of the message text.

Connection failures

Confirm the host address, network reachability, endpoint port/path/protocol, and administrator configuration.

Operation failures

Read the error message, verify backend permissions and asset existence, and confirm the endpoint supports the selected operation. For persistent issues, ask an administrator to review endpoint configuration and backend logs.

Working safely

Use search to locate assets, keep related operations open in tabs, validate record layouts before approving them, review destructive actions in confirmation dialogs, and export data for external analysis when appropriate.