Datacom 15.1 DB01933I and DB01904I messages

Products

• Datacom
• DATACOM - AD
• Datacom/DB

Issue/Introduction

After upgrade to CA Datacom/AD 15.1, the Datacom Multi-User Facility (MUF) shows new start up messages.

Why are some startup options that I coded for previous versions of datacom now show as obsolete or forced?

DB00215I - CA Datacom/DB Version 15.1                                                          
DB00249I - DBSIDPR  2020/09/18 15.32 SVC=000 TOGROUP=         CCISYS=          PC=PROD
DB00253I - TARGET_MUF_LIST=P1MUF1                                                     
DB00254I - SIMPLIFY_MODE=YES CXXNAME=P1MUF1   DSN_XXX=SYS3PDAT.P.P1MUF1.???           
DB01900I - *-------------------*VARIABLE START-UP PARMS FOR AXDATIN1 --------------   
DB01900I - DATAPOOL   8K,2000,16K,2         DATA BUFFER SIZE,# OF BUFFERS,            
DB01900I - *                              LARGE DATA BUFFER SIZE,# OF LARGE BUFFERS   
DB01900I - LOGPEND    500                 LOG PEND                                    
DB01933I - VALUE(S) NOW INVALID, SET TO - LOGPEND 5000                                
DB01900I - LOGRCV     NEVER               LOG RECOVERY FILE AVAILABLE                 
DB01900I - LOGSPILL   70,90,25,30,20     LOG %FULL MSG,%FORCE CKP,%FORCE SPILL,       
DB01900I - *                                   %FORCE SCAN,%FORCE REDO                
DB01900I - *MESSAGE YES,DB00133           USER JOB INFORMATION    

.......

DB01900I - DATETIME   ISO,ISO             SQL DATE, TIME FORMATS                    
DB01900I - DICTIONARY 2,15                DICTIONARY DBID, DDD DBID                 
DB01900I - DYNAMIC_EXTEND_MSGS  TRK       OLD/TRK/CYL  1701,1703 -- 1705 1706       
DB01900I - EXCTLNO    0                   EXCLUSIVE CTL MAX RECS                    
DB01900I - FORCE_ABEND_FULL_SNAPER NO     FORCE BOTH SNAPER AND SYSUDUMP            
DB01900I - FORCE_NO_64BIT    NO           FORCE DATASPACE INSTEAD OF 64 BIT         
DB01904I - OPTION IS OBSOLETE AND IGNORED                                           
DB01900I - IOTASK     0,0                MAXMIMUM AND CURRENT IO TASKS              
DB01933I - VALUE(S) NOW INVALID, SET TO - IOTASK 2 SRB                              
DB01900I - LOG_RECORD_FORMAT 1           LXX COMPRESSION                            
DB01900I - LOGOPTION  NO                 DO NOT LOG OPEN/CLOSE WHEN NO MAINTENANCE  
DB01900I - LOGPOOL    2                   # OF LOG BUFFERS FOR ROLLBACK                                

 

Environment

Release : 15.1

Component : CA Datacom/AD

 

Cause

Datacom PTF SO09683

 

Title: ENHANCEMENT: MUF STARTUP OPTIONS CHANGES


ENHANCEMENT DESCRIPTION:
This product enhancement delivers updated code which includes the
the following changes:

1. Some existing, obsolete CA Datacom/DB Multi-User Facility (MUF)
startup options will now be ignored. In these cases the desired
behavior will be forced by MUF.

2. Some defaults for MUF options which are not coded have been
modernized.

3. A few of MUF's internal behaviors have been changed regardless of
the option selected. In such cases the desired behavior will be forced
by MUF.

4. A few options will now be forced from one setting to another,
especially in cases where the old behavior is less than optimal or inferior.

Resolution

The CA Datacom R&D team knows from existing Datacom MUF environments what the best value should be for some DBMUFPR startup options.

Options where the recommended value has been forced are marked by message DB01933I. Options that are obsolete are marked by message DB01904I.

Error/info messages always follow, or are after, the startup option in question.

 

Messages DB01933I and DB01904I are given as a result of this enhancement  PTF.
DB01933I talks about MUF SMPTASK/BREAK and LOGPEND. 

To see what option is obsolete in version 15.1 and what value has been forced,look at the Datacom MUF startup messages in the MUF log .

The message is written just after that startup option.

Remove Obsolete options to avoid this DB01904I message.