VMSCHED stopped running some jobs. Next run date showed in the past.

book

Article ID: 191954

calendar_today

Updated On:

Products

CA VM:Schedule

Issue/Introduction

Looked at the status of the jobs and saw something very odd:

vmsched q ( user jabatch

REQUEST      EXECUTION STATUS        LAST DATE/TIME            NEXT DATE/TIME          USERID   
--------              ------------------                      ---------------------                ---------------------              --------       
RAWDATAE    EXECUTION COMPLETE  FRI 05/29/20 04:57:23    *FRI 05/29/20 00:15:00   JABATCH  
RAWDATAF    EXECUTION COMPLETE  FRI 05/29/20 04:57:35    *FRI 05/29/20 00:20:00   JABATCH  
LNXLIST         EXECUTION COMPLETE  WED 05/27/20 23:00:00  THU 05/28/20 23:00:00  JABATCH  
RAWDATA6    EXECUTION COMPLETE  FRI 05/29/20 04:57:46    *FRI 05/29/20 00:20:00   JABATCH  
JADASD         EXECUTION COMPLETE  WED 05/27/20 23:45:00  THU 05/28/20 23:45:00  JABATCH  

This command was run Saturday night 5/30/2020. 

I've search the console logs and come up with nothing.
My resolution was to back out of RSU-1901 and go back to the old version of VMSCHED (CA VM:Schedule (TM) Version 02.0 RS1510).

Environment

Release : 2.0

Component : VM:Schedule

Resolution

PTF SO11328 fixes this problem.

Apply the PTF, deploy, and recycle VMSCHED to pick up the updated code. The schedule will fix itself when VMSCHED is initialized.

After applying/deploying the PTF and recycle of VMSCHED, the schedule should be correct with correct “NEXT RUN DATE” based on the date/time/within that are specified for the event.