AnsweredAssumed Answered

Ca7 Log Dump

Question asked by Nair_Vin on Feb 18, 2016
Latest reply on Feb 18, 2016 by Marysue

I have noticed that the automatic LOG dump switching is not happening in our test Ca7 instance. Currently Operator get a WTOR in console whenever the LOG files are full and has to manually respond.

 

I can see that the DBASE definition in the test Ca7 looks fine and the LOG jobs are defined in Ca7.

DBASE,JOB=CA07LTSP,PROCLOAD=CA7LOADT,RSRC=YES,DEFAULTJOB=DEFAULTS  

ALOG1,DSN=SYSV.CA7.TEST.R11L3.LOGP                                 

ALOG2,DSN=SYSV.CA7.TEST.R11L3.LOGS                                 

 

I have also tried to issue /SWAP command to check the function however the below WTOR is coming in console while issuing the /SWAP

CA-7.200 - AWAITING REPLY: LOGP, LOGS, OR CANCEL

 

I tried to manually demand both LOG jobs and that too not working.

DEMANDH,JOB=CA07LTSP,SCHID=1                                 

SPO7-12  REQUEST INVALID -- PRIMARY LOG FILE IS ACTIVE      

REQUEST COMPLETED AT 22:57:36 ON 16.048.     

 

DEMANDH,JOB=CA07LTSS,SCHID=1                                

SPO7-11  SCHEDULE SCAN POSTED TO DUMP SECONDARY LOG FILE   

REQUEST COMPLETED AT 22:58:15 ON 16.048.

 

I was expecting CA07LTSS to be in request queue but haven't seen any instances.

Do anyone knows what would be the reason for this? Is there any user exists which cancel the LOG jobs before comes in Ca7?

Outcomes