Config updating and 'job not run' notifications

Products

• VM:Schedule

Issue/Introduction

When a job cannot be run because the userid is logged on (see below) - who gets the notification?

 

You can see from the info below that user PAMMIE gets sent a RDR file to notify me.

However I am not the only 'OPERATOR' defined in the config - why did the others not get a RDR file for notification as well? 

Bottom line is I want to keep my authority but I don't really want a notification if a job does not run - only if it is mine.

 

13:19:00 SCHEDMAN  7B1C VMDAUT0063I Request 'CARROT' for user 'SCHEDMAN' skipped because user was logged on.                                                  

13:19:00 SCHEDMAN 7B1C VMDAUT0068I Request 'CARROT' for user 'SCHEDMAN' next run: WED 11/10/21 AT 13:20:00.                                                  

 PUN FILE 5760 SENT TO   PAMMIE  RDR AS  5029 RECS 0005 CPY  001 A NOHOLD NOKEEP

 

 

Environment

Release : 2.0

Component : VM:Schedule

Resolution

The doc doesn't indicate to include ... [ SPOOL _UserID_ ] ... for the NOLOG option, but in this case you should:

VMSCHED CHANGE CARROT ( USER SCHEDMAN NOLOG

should be if you want to get rid of your ID

VMSCHED CHANGE CARROT ( USER  SCHEDMAN NOLOG SPOOL SCHEDMAN 

 

The doc is also not clear where it says "spool option is ignored when NOLOG is specified" ... It really means if the NOLOG option is in place, then the UserID specified for SPOOL TO is ignored ... because nothing is spooled with NOLOG in effect.

The "SPOOL TO" UserID (3rd 8-bytes in IRBDB) got changed to what I specified after NOLOG SPOOL ...