cancel
Showing results for 
Search instead for 
Did you mean: 

DECSCHEDULER

 
Kevin Raven (UK)
Frequent Advisor

DECSCHEDULER

Where does scheduler get it's history data from ?
We have been running the following command for the last 3 years with no issues ..but now it fails with an ugly error message.
Is this an indication that scheduler database file , is about to go pop ?

$ ! get history of all job which ran in the last 24 hours
$ ! -----------------------------------------------------
$ minus1day = F$CVTIME("-1-00:00:00","ABSOLUTE")
$ SCHED SHOW HIST/GROUP=*/RECORD-
/OUT=RDTS_LOG:SCHED_200907102240.LIS-
/COMPLETION=ALL/USER=AUTO_OP/START_TIME="9-JUL-2009 22:40:05.34"
%NSCHED-I-NORUNREC, No specified run records found for job 6
%NSCHED-I-NORUNREC, No specified run records found for job 7
%NSCHED-I-NORUNREC, No specified run records found for job 41
%NSCHED-I-NORUNREC, No specified run records found for job 61
%NSCHED-I-NORUNREC, No specified run records found for job 33
%NSCHED-I-NORUNREC, No specified run records found for job 32
%NSCHED-I-NORUNREC, No specified run records found for job 31
%NSCHED-I-NORUNREC, No specified run records found for job 52
%NSCHED-I-NORUNREC, No specified run records found for job 35
%NSCHED-I-NORUNREC, No specified run records found for job 34
%NSCHED-I-NORUNREC, No specified run records found for job 55
%NSCHED-I-NORUNREC, No specified run records found for job 53
%NSCHED-I-NORUNREC, No specified run records found for job 27
%NSCHED-I-NORUNREC, No specified run records found for job 42
%NSCHED-I-NORUNREC, No specified run records found for job 62
%NSCHED-I-NORUNREC, No specified run records found for job 63
%NSCHED-I-NORUNREC, No specified run records found for job 43
%NSCHED-I-NORUNREC, No specified run records found for job 44
%NSCHED-I-NORUNREC, No specified run records found for job 38
%NSCHED-I-NORUNREC, No specified run records found for job 58
%NSCHED-I-NORUNREC, No specified run records found for job 40
%NSCHED-I-NORUNREC, No specified run records found for job 60
%NSCHED-I-NORUNREC, No specified run records found for job 54
%NSCHED-I-NORUNREC, No specified run records found for job 37
%NSCHED-I-NORUNREC, No specified run records found for job 39
%NSCHED-I-NORUNREC, No specified run records found for job 57
%NSCHED-I-NORUNREC, No specified run records found for job 59
%NSCHED-I-NORUNREC, No specified run records found for job 46
%NSCHED-I-NORUNREC, No specified run records found for job 65
%NSCHED-I-NORUNREC, No specified run records found for job 28
%NSCHED-I-NORUNREC, No specified run records found for job 45
%NSCHED-I-NORUNREC, No specified run records found for job 64
%NSCHED-I-NORUNREC, No specified run records found for job 36
%NSCHED-I-NORUNREC, No specified run records found for job 56
%NSCHED-I-NORUNREC, No specified run records found for job 29
%NSCHED-I-NORUNREC, No specified run records found for job 4
%NSCHED-I-NORUNREC, No specified run records found for job 5
%NSCHED-I-NORUNREC, No specified run records found for job 30
%NSCHED-I-NORUNREC, No specified run records found for job 49
%NSCHED-I-NORUNREC, No specified run records found for job 48
%NSCHED-I-NORUNREC, No specified run records found for job 51
%NSCHED-I-NORUNREC, No specified run records found for job 50
$
$ ! create a new log if necessary (every 90 DAYS)
$ DAYS_90 = F$CVTIME("-90-00:00:00","COMPARISON",)
$ schedlog_file = f$trnlnm("NSCHED$LOGFILE")
$ if f$search(schedlog_file) .nes. ""
$ then
$ if F$CVTIME(F$file(schedlog_file,"CDT"),"COMPARISON",) .les. DAYS_90
$ endif
$ endif
$
$
$ Above all works fine ...then it checks if the job is being run on a Friday and ....

$ SCHED SHO JOB GET_STATS_DATA_WKLY/SYM ! will set sched$type
$ if SCHED$TYPE .eqs. "OFFLINE" then - ! if offline job (fri)
SCHED SHOW HIST/GROUP=* /COMPLETION=ALL/USER=AUTO_OP/OUT=RDTS_LOG:SCHED_HIST_200907102240.LIS
SUB VSS$GET_HISTORY: Error 51 at line 29 ?Integer error or overflow
%SYSTEM-F-HPARITH, high performance arithmetic trap, Imask=00000000, Fmask=00000504, summary=12, PC=0000000000000003, PS=82B29380
-SYSTEM-F-FLTINV, floating invalid operation, PC=0000000000000003, PS=82B29380
-SYSTEM-F-FLTUND, arithmetic trap, floating underflow at PC=0000000000000003, PS=82B29380
$ L_ERROR:
$ My_status = $status
$ if My_status .eq. My_aborted then goto L_ABORTED
$ log "SCHED-E-GET_STATS_DATA_WKLY terminated. Error status : %X00000504"
19 REPLIES 19
Peter Elliott
Occasional Advisor

Re: DECSCHEDULER

Hi,
Not too sure about the actual error message you are receiving... But generally, I believe Scheduler writes History records to a Default logfile of NSCHED$:.log
This also requires the logical NSCHED$DEFAULT_LOG to be set up in the Scheduler startup routine (normally to 5)
I've always found most scheduler issues can be fixed by running NSCHED$:DB_UTILITY and compressing the Database.
(Try the command: Sched Show Delete - to see how many deleted record there are in the DB)
Also - if you haven't already - maybe look to upgrade to the latest version provided by CA: http://supportconnectw.ca.com/public/unijobmgtopenvms/unijobmgtopenvms_supp.asp

Hope this helps...

Peter.
Peter Elliott
Occasional Advisor

Re: DECSCHEDULER

Sorry - the link I sent is probably not the best - The data sheets on the following link are better:

http://www.ca.com/us/products/product.aspx?id=1485#documents
Kevin Raven (UK)
Frequent Advisor

Re: DECSCHEDULER

We rebuild the DB on a regular basis ...once every 6 months ....
Do the historystats come from the VSS.DAT ?
We have a record of jobs from 2006 when the history command is run on another system (mirror of production , that has the issue).


(LNM$SYSTEM_TABLE)

"NSCHED$" = "NSCHED$DATA"
= "NSCHED$COM"
= "NSCHED$EXE"
"NSCHED$CLEAR_RESTART_PARAM" = "TRUE"
"NSCHED$COM" = "SYS$COMMON:[NSCHED.COM]"
"NSCHED$DATA" = "SYS$COMMON:[NSCHED.DATA]"
"NSCHED$DEFAULT_JOB_MAX" = "10"
"NSCHED$EXE" = "SYS$COMMON:[NSCHED.EXE]"
"NSCHED$LBAL$CPU_WEIGHT" = "0.5"
"NSCHED$LBAL$INTERVAL" = "0 00:00:30"
"NSCHED$LBAL$MEMORY_WEIGHT" = "0.5"
"NSCHED$LOGFILE" = "SYS$COMMON:[NSCHED]DECSCHEDULER.LOG"
"NSCHED$MAILBOX" = "_MBA58:"
"NSCHED$REMOTE_SUPPORT_ENABLED" = "TRUE"
"NSCHED$TERM_MAILBOX" = "_MBA63:"
"NSCHED$UID" = "NSCHED$:SCHEDULER$MOTIF.UID"
"NSCHED_DEFAULT_SD_ACTION" = "SKIP"
"RDTS_SCHED" = "SYS_SYSTEM:[OMN$SCHED]"
"RDTS_SCHEDULER_REPORTS" = "SYS_STATS:[RDTS.REPORTS.SCHEDULER]"
"SCHED$FLAG" = "OMN$FLG"
"SCHED$LBAL_GROUP_HOST" = "RDTSC RDTSD"
"SCHEDULER$NODE" = "RDTSC::"
"SCHED_RTL" = "NSCHED$:SCHED_RTL.EXE"
"SCHED_RTL_TV" = "NSCHED$:SCHED_RTL.EXE"
"SCHED_SHUTDOWN" = "AUTO-RESTART"

(LNM$SYSCLUSTER_TABLE)

(SYSMAN$NODE_TABLE)
$ $ DIR NSCHED$:*.LOG/SIZE/DATE

Directory SYS$COMMON:[NSCHED.DATA]

RDTSA.LOG;2 3 14-NOV-2006 10:40:01.45
RDTSA_REMOTE_EXECUTOR.LOG;2
1 14-NOV-2006 10:40:02.35
RDTSB.LOG;2 3 14-NOV-2006 10:41:40.16
RDTSB_REMOTE_EXECUTOR.LOG;2
1 14-NOV-2006 10:41:40.18
RDTSC.LOG;35 4 22-NOV-2006 15:29:09.19
RDTSC_REMOTE_EXECUTOR.LOG;34
1 22-NOV-2006 15:29:09.27
RDTSD.LOG;21 3 22-NOV-2006 15:29:10.52
RDTSD_REMOTE_EXECUTOR.LOG;21
1 22-NOV-2006 15:29:10.58
SCHED$ERR.LOG;1 0 10-NOV-2006 11:58:45.84
VERMONT_CREAMERY.LOG;1
288 10-NOV-2006 11:40:47.78

Total of 10 files, 305 blocks.

Directory SYS$COMMON:[NSCHED.EXE]

SCHED$ERR.LOG;1 0 13-NOV-2006 16:10:35.21

Total of 1 file, 0 blocks.

Grand total of 2 directories, 11 files, 305 blocks.
$

The log file gets rolled over every 90 days see below ....
$ DIR SYS$COMMON:[NSCHED]DECSCHEDULER.LOG/SIZE/DATE

Directory SYS$COMMON:[NSCHED]

DECSCHEDULER.LOG;1 9744 4-MAY-2009 21:24:59.96

Total of 1 file, 9744 blocks.
$

What is the VERMONT_CREAMERY.LOG;1 file used for ???? Funny name .....lol



Peter Elliott
Occasional Advisor

Re: DECSCHEDULER

I think (having read up some more), unless you specify otherwise - the Default Logfile which contains Job History is Vermont_Creamery.log (I believe they were the first company to run Scheduler).
There are also suggestions that on some older versions - Event history was sometimes written to the Vermont_cremery.old file instead of the .log

What version of scheduler are you running ?
($Sched show stat)
marsh_1
Honored Contributor

Re: DECSCHEDULER

hi,

vermont creamery - thats where they started with it , well thats the story they gave us when we had decscheduler when digital still had it.

fwiw