Datacom DB00205E - MULTI-USER ERROR

Products

Datacom DATACOM - AD Datacom/DB Datacom/AD

Issue/Introduction

After upgrading to Datacom 15.1 from version 15.0, the 15.1 MUF startup terminated with:

DB00205E - MULTI-USER ERROR - 1078                                       
DB00239I - MUF TERMINATION, START PROGRAM ABEND                          
CCSR010E DBMUFPR U0004 at 0DF50310 LMOD DBSSPPR CSECT DBSSPPR +006310

This can also happen when implementing external security for the first time in the MUF.

Environment

Release: 15.1

Cause

From the Datacom Messages for DB00205E - MULTI-USER ERROR - 1078

DB00205E MULTI-USER... ERROR - nnnn [optional-text]

Reason:
An error occurred while initiating the Multi-User Facility. The text varies by specific code containing addition information to usually avoid manual lookup of the Explanation and User Response.

1078 More than one option was allowed by the Security Administrator for DBxxRAT, but none was coded on the SECURITY MUF startup option.

Action: Code an allowed value for this parameter.

This means external security has been enabled for a Datacom path and class but the Datacom 15.1 MUF startup options member is missing the SECURITY option.

Note the informational message in the MUF startup indicating the external security was active:

DB00231I - EXTERNAL SECURITY LEVEL 05 ACTIVE

Resolution

Ensure that the MUF startup options includes the SECURITY option. If upgrading to 15.1 include the statements used in Version 15.0.

The SECURITY statements are:

SECURITY DBDxSSR,DBDxRAT,DBDxSCI,DBDxRSR,DBDxSQL,DBDxRCI
SECURITY DBDxSCQ,DBDxRCQ,DBDxRAQ,DBDxSQQ

Note that the "x" in the above values represents the resource class DxTABLE created in your ESM. For example, if you use class DCTABLE, the SECURITY values would be DBDCSSR, DBDCRAT, etc. If you use class DTTABLE, then these SECURITY values would be DBDTSSR, DBDTRAT, etc.

To externally secure a path and class, a DTSYSTEM resource class needs to be defined for each path and class and permission denied to the MUF userid. The resource name is cxxname.path-and-class.

For class DTSYSTEM the security definitions are needed for each of the path and class combinations specified in the SECURITY card, DBDCSCI, ,DBDCSCQ etc. In this case 10 security rules are needed.

Note, the resource class names used for RACF is DT@YSTEM instead of DTSYSTEM and Dx@ABLE instead of DxTABLE.

Sample definitions:

RACF

RDEFINE DT@YSTEM cxxname.DBDCRAT UACC(NONE)

ACF2

$KEY(cxxname) TYPE(DTS)
DBDCRAT UID(*) PREVENT

Top Secret

TSS PER(ALL) DTSYSTEM(cxxname.DBDCRAT) ACCESS(NONE)

Alternatively, a generic resource rule to secure all paths and classes could be defined like this:

RACF

RDEFINE DT@YSTEM cxxname.DBDC* UACC(NONE)

ACF2

$KEY(cxxname) TYPE(DTS) 
DBDC- UID(*) PREVENT

Top Secret

TSS PER(ALL) DTSYSTEM(cxxname.DBDC*) ACCESS(NONE)

Additional Information

See Datacom documentation sections Using the DTSYSTEM and Table Classes.