topic [HELP]Schedule job was triggered unexpected in Operating System - OpenVMS

[HELP]Schedule job was triggered unexpected

zheng_fei — Thu, 10 Apr 2014 03:32:20 GMT

Hi,

There is a schedule job on our server which should be triggered twice a day. Somehow it was triggered more than twice recently.

Is there a way to track by whom or which procedure the schedule job was triggered?

I have pulled out the event report of this job but got no findings.

>run NSCHED$:VSS_REPORTS.EXE

Job Management Manager
LOG FILE
READER/REPORTER

1) Event Report

2) Job Elapsed Time Report

Option <EXIT>? 1

Logfile file specification <NSCHED$:VERMONT_CREAMERY.LOG>?

Indicate the reporting time window you are interested in by specifying both
begin and end dates. (You can narrow the time window further by entering
more complete dates and times in the format "dd-mmm-yyyy hh:mm:ss")

Begin date <10-APR-2014>? 9-apr-2014

End date <10-APR-2014>?

Display Job Management Events, Job Events or Both [S,J,B] <B>? b

Enter a comma-separated list of the numbers below which correspond to the
classes of events you would like displayed in the report.

1) Job Events 7) Broadcast Messages
2) Normal Job Management Events 8) Timer Settings
3) Abnormal Job Management Events 9) Database Checks
4) Job Management Deaths 10) Job Management Error Traps
5) User-Interface Events 11) Job State Changes
6) Mailbox Messages

Event classes to display <ALL>? 1

You can select which jobs will be printed in the report by specifying
Job Name, Group Name, Job Type and Username below. Full wildcarding
(using "%" or "*") is supported.

Job Name <*>? XXXXXX_OMCLICK_IFFM

Group Name <*>?

Job Type <*>?

Username <*>?

Report file name <EVENT.RPT>?

>ty EVENT.RPT

EVENT REPORT 10-Apr-14
Page 1

JOB EVENT EXIT
DATE AND TIME NUMBER TYPE NODE PID STATUS ADDITIONAL INFORMATION
-------------------- ------ ------------ ------ -------- -------- ----------------------------------------------------------

9-APR-2014 17:10:58 1168 JOB START NODE1A 209835AD
9-APR-2014 17:10:59 1168 JOB FINISH NODE1A 209835AD Success
9-APR-2014 17:21:18 1168 JOB START NODE1A 20980DD6
9-APR-2014 17:21:19 1168 JOB FINISH NODE1A 20980DD6 Success
9-APR-2014 19:20:19 1168 JOB START NODE1A 209840A9
9-APR-2014 19:20:20 1168 JOB FINISH NODE1A 209840A9 Success

Re: [HELP]Schedule job was triggered unexpected

labadie_1 — Thu, 10 Apr 2014 11:10:10 GMT

Hello

So you are using Dec Sched.

In order to help you, one would need a lot more informations, about the user, the jobs, the rules applied...

Do you use "special days" ?

sched sh job xxx/ful

and all related information would be useful

does a

sched sh scheduled_runs

shows a normal or not expected job execution for the next days ?

It may be "normal" or not.

Re: [HELP]Schedule job was triggered unexpected

zheng_fei — Fri, 11 Apr 2014 10:00:07 GMT

Hi labadie_1,

Thanks for the reply. Below is the full information of the job.

Job Name Entry User_name State Next Run Time
-------- ----- --------- ----- -------------
MY_JOB_NAME
1168 ZF Scheduled Never
VMS_Command :
Group : MY_GROUP Type : FM
Last Start Time : 10-APR-2014 19:19
Last Finish Time : 10-APR-2014 19:19 Last Exit Status : SUCCESS
Schedule Interval : None Mode : Detached
Mail to : ZF (No Mail)
Days : None
Output File : MY$DIR:MY_JOB_NAME.LOG
Cluster_CPU : MY_CPU User not notified on completion
Load Balance Group: (none)
Run Priority : Default
Max_Time Warning : None Job Always retained
Stall Notify : None No Retry on Error
Success Count : 305 Failure Count : 3
Owner UIC : [130,2] Restart on Crash
Write Identifier : SCHED$WRITE
Send Opcom Completion Message
Pre Function : @OMN$COM:SCHED_PRE_FUNCTION, Last Exit Status : SUCCESS
Post Function : @OMN$COM:SCHED_POST_FUNCTION, Last Exit Status : SUCCESS
No local jobs depend upon this job.
This job has no Dependencies on other jobs

As you can see, the job status is NEVER. It can only be triggered by another procedure at particular time. By right the trigger time should be around 17:10 and 17:20 GMT every day. But now it runs again at 19:19.

I checked trigger procedure and had no findings. Trying to find out if there is another source triggering this job.

Re: [HELP]Schedule job was triggered unexpected

MarkOfAus — Sat, 12 Apr 2014 06:29:27 GMT

Perhaps, can you start it up in debug mode?

Edit of SYS$STARTUP:SCHEDULER$STARTUP.COM set SCHED SET DEBUG ON

Do that before it triggers, see if it gives you clues.