Is RMOATHTB needed if using external security for Deliver access?

Products

• Deliver
• View

Issue/Introduction

As the Deliver RMOATHTB authority table has been used for security for a long time, if a client is converting to external security, is the table still being used?

The RMOATHTB authority table, regardless of use of external security, is necessary because the RMODBASE utility requires a default security table.

RMOATHTB is used to provide the security information for processes like the RMODBASE ADDDS and MAKECKPT commands, to create the database and checkpoint file.

Deliver is shipped with a plain-vanilla RMOATHTB, so that all users are able to perform RMODBASE UPDATE procedures. The type of security to be used is kept as part of the database Master Control record (MCR). RMODBASE cannot determine whether to use internal or external security if the database does not exist yet. If a RMODBA15 message is generated from running RMODBASE ADDDS, then there is a limitation in the client's external security (ACF2, Top Secret, RACF) stopping the function. Look for the following:

• A S306 condition indicates that the load library being used is not APF-authorized. The library should be authorized if it is not.
  
  
• If an RMODBA15 error still occurs, that is a result of external security that it is either not allowing that high-level qualifier to be created on the specified packs or that it is not allowing your UserID to create the database.

Resolution

CR24-VV