This section explains the exit program called when job nets end with Abended or Canceled.
[Windows]
If the job net ends in Abended or Canceled, the system searches for the jobschexitex.bat file first, and then the jobschexitex.exefile as the exit program. The exit program found in the search will be called up. If jobschexitex.bat is found, jobschexitex.exe 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 ends in Abended or Canceled, the system searches for and calls the jobschex.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.
The job net abended extended exit differs from the job net abended exit. This means if the job net of Job Execution Control attribute ends with Abended, the completion code passed to the exit program is the same with the value returned from Job Execution Control.
Parameters Passed to the Exit Program
The parameters passed to the exit program are as follows:
|
Information on each job in the job net is stored in the temporary file as shown below. The job name, completion code, and status are stored for each job.
Job name Completion code Status Job name Completion code Status .......... Job name Completion code Status
The following explanations describe each of the types of information shown above:
Depending on execution attributes, the following contents are stored:
This is a job name. If the job name is omitted, the string registered as a command will be stored.
This is a job workunit name.
This is a job workunit name.
This is a command name.
This is a job completion code. Completion code for unexecuted jobs is 0.
For a job net with the Job Execution Control attribute, completion code may exceed 256.
The job status can be specified using one of the following seven strings:
Indicates completed.
Indicates pseudo-normal completion.
Indicates abended.
Indicates canceled.
Indicates the job was not started.
Indicates the job has been paused.
Indicates the job has been disabled.
The temporary file is created in the following directories:
In the work directory under the database directory of Jobscheduler
The name of the file is created in NEXnnn.tmp (nnn is appended by the system) format.
/var/tmp directory
/tmp directory
Since the temporary file is not deleted on the Jobscheduler side, you must delete it from the exit program.
If the exit is not registered, the temporary file is not created.
About the Job in Passed Status
If the execution condition of the following job is specified in Condition concerning completion code of preceding job, the job that ends with the Passed status will be processed as follows:
The job status (waiting /disabled/paused) before being passed, will be passed as the job information.
The completion code is 0.
A job that is waiting using the OR condition and is then canceled because of the OR condition of the following job will be processed as follows:
The job status will be "canceled" regardless of whether the job was actually started.
The completion code is 248 or 249.
Exit Program Location
Windows | Systemwalker Operation Manager installation directory\MpWalker.JM\bin |
Solaris | /opt/FJSVJOBSC/bin |
HP-UX | /opt/FHPJOBSCH/bin |
AIX | /usr/FAIXJOBSC/bin |
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 abended extended exit:
[Windows]
/* When a job net abnormal completion occurs, sends the following messages to "MANAGEMENT"
server.
Job net name (group name) is abended !! code = completion code*/
#include <stdio.h>
#include <process.h>
main(int argc, char *argv[])
{
char cmdline[256];
sprintf_s(cmdline,sizeof(cmdline),
"NET SEND MANAGEMENT %s(%s) is abended !! code = %s",
argv[2], //job net name
argv[4], //group name
argv[5]); //completion code
system(cmdline);
_unlink(argv[9]); // temp file is deleted
exit(0);
}[UNIX]
/*
Example program for the job net abended extended exit (for UNIX) which outputs a job
net abnormal completion message with a group name, job net name, and completion code
on the console.
*/
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <syslog.h>
main(int argc, char **argv)
{
openlog ("jobsch", LOG_CONS, LOG_USER);
syslog (LOG_WARNING,
"WARNING: jobnet abnormal end. project=%s, group_name=%s, net_name=%s, net_comment=%s,
net_code=%s,
argv[1], argv[4], argv[2], argv[3], argv[5]);
closelog();
unlink (argv[9]);
exit(0);
}