DB00308I not issued when % reaches 70%

Products

• CA 7 Workload Automation

Issue/Introduction

  CA-7 was recently migrated to Release 12.1.

  Automation was set up via  CA Ops to  launch AL2DBSPL as soon as the message DB00308I  is generated.

 

 The Status_log is being monitored :- 

                              
00.00.00 STC02787  CA7DATA:DB00133I - JOB OPEN CA7ONL 10000 STCPRIV STC01234  
00.00.00 STC02787  CA7DATA:DB00133I - JOB OPEN CA7ONL 10001 STCPRIV STC01234  
00.00.00 STC02787  CA7DATA:DB00133I - JOB OPEN CA7ONL 10002 STCPRIV STC01234    
00.00.00 STC02787  CA7DATA:DB00102I - ENDED   JOB-CA7ONL   NUMBER-51298         
11.10.43 STC02787  CA7DATA:DB01311I - STATUS_LOG                                
11.10.43 STC02787  CA7DATA:DB00322I - LOG LXX LRSN-55,606 LBSN-1,944 WRAP-0 SGMNT-0 RSTRB-N SPILLING-N %FULL-71
        1 //CA7DATA  JOB MSGLEVEL=1                            STC01234                   

 

Noticed that no DB00308I has been displayed, which is the message being monitored to  trigger the AL2DBSPL job...

 

The Threshold is definately set at 70%:

 

  Display  Filter  View  Print  Options  Search  Help                          
-------------------------------------------------------------------------------
SDSF OUTPUT DISPLAY CA7DATA  STC02787  DSID     3 LINE  CHARS 'CUSMAC' FOUND   
COMMAND INPUT ===>                                            SCROLL ===> CSR 
      19 XXSYSIN  DD  DSN=YOUR.DATACOM.CUST.CUSMAC(AXDATIN1),                  
         XX         DISP=SHR                                                   
      20 XX       DD  DSN=YOUR.DATACOM.CUST.CUSMAC(AXDATIN2),                  
         XX         DISP=SHR                                                   
STMT NO. MESSAGE                                                               

 

and

   File  Edit  Edit_Settings  Menu  Utilities  Compilers  Test  Help            
 sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
 VIEW       YOUR.DATACOM.CUST.CUSMAC(AXDATIN1) - 01.00      Columns 00001 00072
 Command ===>                                                  Scroll ===> CSR 
 ****** ***************************** Top of Data ******************************
 000001 *-------------------*VARIABLE START-UP PARMS FOR AXDATIN1 --------------
 000002 DATAPOOL   8K,2000,16K,2         DATA BUFFER SIZE,# OF BUFFERS,         
 000003 *                              LARGE DATA BUFFER SIZE,# OF LARGE BUFFERS
 000004 LOGPEND    500                 LOG PEND                                 
 000005 LOGRCV     NEVER               LOG RECOVERY FILE AVAILABLE              
 000006 LOGSPILL   70,90,25,30,20     LOG %FULL MSG,%FORCE CKP,%FORCE SPILL,    
 000007 *                                   %FORCE SCAN,%FORCE REDO             
 000008 MESSAGE YES,DB00133           USER JOB INFORMATION                      
 000009 MESSAGE YES,DB00135      INF/INR CONNECT MESSAGE WHEN MUF               
 000010 MESSAGE YES,DB00136      INF/INR DISCONNECT MESSAGE WHEN MUF            
 000011 MUF  *,99,NO             LOGICAL NAME OF THIS MUF,#EXTRA RUNUNITS,      
 000012 *                                  ENDED NOMAINT.                       
 000013 RXXROLLBACK NO                 ROLLBACK ACTION IN CASE OF FORCE SPILL   
 000014 SYSPOOL    10,100,800,4096,64  CXX BUFFERS, IXX BUFFERS,DXX BUFFERS,    
 000015 *                                  INDEX BUFFER SIZE,31 OR 64 BIT MEMORY
 000016 SYSOUT    0,5M,1M,3M,1M,1M    CLASS,ML,CBS,SQL,DD,DST                   

 

 

Why is  message DB00308I not generated .

 

 

 

 

 

 

 

 

 

Environment

Release : 12.1

Component : CA 7

Cause

LOGRCV NEVER was coded. This means that you use a wraparound Logging file and NO Spill message is generated.

 

Resolution

 

LOGRCV NO needs to be coded as documented in the CA 7 Documentation  Configure Datacom/AD for Use with CA 7 -- Datacom/AD MUF Startup Options for CA 7