DSV00155E-LOGON=NO not permitted with secured MUF

Products

• Datacom
• Datacom/AD
• Datacom/Server

Issue/Introduction

After applying Datacom PTF LU04806, Datacom Server startup fails with this error message:

DSV00155E-LOGON=NO not permitted with secured MUF. Datacom Server terminating.

Datacom Server startup options specifies LOGON=NO      

Environment

z/OS

Cause

This new feature was introduced by PTF LU04086 in Datacom Server. It is documented in Datacom Server New and Enhanced Features

Datacom Server Using LOGON=NO with Secured MUF (PTF LU04086) z/OS

This PTF addresses the behavior of Datacom Server started with LOGON=NO and connected to an externally secured Datacom Multi-User Facility (MUF). When a Datacom Server using input parameter LOGON=NO is is connected to a secured MUF and neither SECEXIT nor CONEXIT is specified, then Datacom Server is terminated with the message DSV00155E.
A new message for this option is:
DSV00155E - LOGON=NO not permitted with secured MUF. Datacom Server terminating

When MUF security is enabled, this message will be issued at MUF startup:

DB00220I - EXTERNAL SECURITY ACTIVE FOR MUFXX   ON SQL SERVER WITH DRTABLE

Resolution

To resolve this error when MUF external security is enabled :

• Specify LOGON=YES in the Datacom Server options which will require users to logon to the server.
  
  or
  
  
• Specify LOGON=NO and CONEXIT=exit_name in the Server options and code a connection exit to allow access to the server. exit_name is the name of the load module of your connection exit. There is a sample connection exit in the CAYTMAC library (CAAXMAC for Datacom/AD) in member SVSXTPR. Modify the exit to supply a userid and password then assemble and link it into the CAYTLOAD library (CAAXLOAD for Datacom/AD). Use sample JCL in library CAYTMAC (CAAXMAC for Datacom/AD) member YTEXIT to do this. 

Additional Information

See documentation section Startup Options