Explain MDUOLL CANNOT BE ACCESSED error

Products

• Datacom
• DATACOM - AD

Issue/Introduction

When I sign into DDOL on a test CICS system, I get this error:

T009 *****  START OF DDO   ERROR LOG ON 03/13/18  AT  13:19:41  *****
T009 1-ICSCMSGP03T -  INTERR: MESSAGE LIBRARY MDUOLL   CANNOT BE ACCESSED 1-DDOL0000
T009 SRVC=VLS FUNC=INIT     RC=008    PGM=SC00MSGP14.0 -12D8                   
T009 CALPGM=SC00MSGP14.0 -1882 CURACT=   ACTTYP=  USER=JMG ERRID=              
T009 SYS=    ENTTYP=    ENTNAM=                ENTVER=    ENTSTAT=             
T009 LIB=MDUOLL   MEM=$DDOMSGE                                                 
T009 *****    END OF DDO   ERROR LOG ON 03/13/18  AT  13:19:41  *****

What is the problem here, and how do I correct it?

Environment

Release:
Component: DD

Resolution

This error message means that you cannot access the MDUOLL file from within the CICS region. The two most likely causes are:

1. The physical file referred to by the MDUOLL File entry is missing, or
2. There is no FCT entry for the MDUOLL file in this CICS region. 

You can issue CICS Transaction
CEMT I FI(MDUOLL)
to confirm that the file or the FCT is missing.

If the file is missing, you will need to recreate the file ending with DDMAP. Please refer to your INSTJCL for jobs to create and load this file.
If the FCT is missing, and because this is a BDAM file (along with DDOFILE and DDOFIL2), you have to assemble these entries into your existing FCT entries.The information you need is found in the CABDSAMP(ADFCT) member.

Additional Information

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