This section explains the exit program used if the job net registered in Jobscheduler is not activated when the scheduled time arrives.
[Windows]
If the job net is not activated when the scheduled time arrives, the system searches for the startlateexit.bat file first, and then the startlateexit.exe file as the exit program. The exit program found will be used. If the startlateexit.bat file is found, startlateexit.exe will not be called up even if it exists.
For a job net whose start time is set in [Scheduled start time] with [Once in a day] checked in [Start only when message event has occurred], if no message event occurs when the scheduled startup time arrives for the job net or it is in the disabled status at the scheduled startup time, this exit program will be also called up.
If you want to use this exit to perform custom processing, create an exit program with the same name and store it in the following directory:
<Systemwalker installation directory>\MpWalker.JM\bin |
[UNIX]
If the job net is not activated when the scheduled time arrives, the system searches for and calls the startlate.exit file as the exit program.
For a job net whose start time is set in [Scheduled start time] with [Once in a day] checked in [Start only when message event has occurred], if no message event occurs when the scheduled startup time arrives for the job net or it is in the disabled status at the scheduled startup time, this exit program will be also called up.
If you want to use this exit to perform custom processing, create an exit program with the same name and store it in the following directory:
Solaris/Linux:
/opt/FJSVJOBSC/bin |
HP-UX:
/opt/FHPJOBSCH/bin |
AIX:
/usr/FAIXJOBSC/bin |
Appropriate execution privileges are required to execute the exit program. If relevant privileges are not set, the exit program will not be called.
Parameters Passed to the Exit Program
The parameters passed to the exit program are as follows:
|
In Systemwalker Operation Manager EE, the number of parameters is five.
This parameter is used in Systemwalker Operation Manager EE.
Cautions
Prevent time-consuming process because it may cause delay of execution for job nets and groups.
The execution user at the exit is the logon account of the Jobscheduler service. [Windows]
The execution user at the exit is a root account. [UNIX]
Program Example
Below is an example program for the job net start delay exit:
[Windows]
/* When the activation of the job net delays, sends the following messages to "MANAGEMENT" server. Job net name is delayed */ #include <stdio.h> #include <process.h> main(int argc, char *argv[]) { char cmdline[256]; sprintf(cmdline, "NET SEND MANAGEMENT %s is delayed", argv[2]); //job net name system(cmdline); exit (0); }
[Solaris]
/* Example program for the job net start delay exit (for UNIX), which outputs a job net start delay message with a project name and job net name to the console. */ #include <syslog.h> #include <stdio.h> main(int argc, char **argv) { openlog("jobsch", LOG_CONS, LOG_USER); syslog(LOG_WARNING, "WARNING: %s %s is delayed.", argv[1], argv[2]); closelog(); exit(0); }