Systemwalker Operation Manager Reference Guide

17.8 Job Net End Delay Exit

This explains the exit program used if the job net registered in Jobscheduler does not end when the estimated end time arrives.

[Windows]

If the job net does not end when the estimated end time arrives, the system searches the endlateexit.bat file first, and then in the endlateexit.exe file as the exit program. The exit program found will be used. If the endlateexit.bat file is found, then endlateexit.exe file will not be called up even if it exists.

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 ended when the estimated end time arrives, the system searches for and calls the endlate.exit file as the exit program.

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:

argc :

Number of parameters (5) (Note1)

argv[0] :

Exit program name

argv[1] :

Name of project where the job net is registered

argv[2] :

Job net name

argv[3] :

Job net comment

argv[4] :

Job net status

argv[5] :

Subsystem number (character string) (Note2)

Note1:

In Systemwalker Operation Manager EE, the number of parameters is six.

Note2:

This parameter is used in Systemwalker Operation Manager EE.

The character strings stored in the fifth parameter "job net status" are as follow:

not_executed:

The job net is in Waiting.

executing:

The job net is in Executing.

warning:

The job net is in Warning.

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 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 end delay exit:

[Windows]

/* When the job net end 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 end delay exit (for UNIX) which outputs a job net end
  delay message with a project name and job net name on 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);
}