3.10.2 Processing when signals are received (UNIX only)
This subsection explains the processing that occurs when the job controller has received signals during normal execution and during debug execution.
- Organization of this subsection
(1) During normal execution
This subsection explains for the SIGTERM signal and for other signals the processing that occurs when the job controller has received signals during normal execution.
(a) SIGTERM
The processing that occurs when SIGTERM has been received depends on the specified TRAP_ACTION_SIGTERM environment setting parameter.
When an operation is not defined with the trap command |
When an operation is defined with the trap command |
---|---|
|
Operation cannot be defined with the trap command.#3 |
When an operation is not defined with the trap command |
When an operation is defined the trap command |
---|---|
|
|
Job start method |
When an operation is not defined with the trap command |
When an operation is defined with the trap command |
---|---|---|
Started from JP1/AJS (Started from a custom job or with TERM set in the AJS_BJEX_STOP environment variable) |
The job definition script is not run and the job terminates with an error (error during environment file analysis). |
|
Started using a method that does not involve JP1/AJS (Started with a method other than the above) |
|
|
Job start method |
When an operation is not defined with the trap command |
When an operation is defined with the trap command |
---|---|---|
Started from JP1/AJS (Started from a custom job or with TERM set in the AJS_BJEX_STOP environment variable) |
Same processing as when TERM is specified |
|
Started using a method that does not involve JP1/AJS (Started with a method other than the above) |
Same processing as when CONT is specified |
(b) Other than SIGTERM
Type of signal |
When an operation is not defined with the trap command |
When an operation is defined the trap command |
|
---|---|---|---|
Termination request signal |
SIGHUP, SIGINT, SIGXCPU, SIGXFSZ, SIGQUIT, SIGUSR1, SIGUSR2, SIGPIPE, SIGALRM, SIGVTALRM, SIGPROF |
|
|
SIGMSG, SIGDANGER, SIGMIGRATE, SIGPRE, SIGVIRT, SIGALRM1, SIGRECONFIG, SIGCPUFAIL, SIGGRANT, SIGRETRACT, SIGSOUND |
Same as above. (AIX only) |
Same as above. (AIX only) |
|
SIGLOST |
Same as above. (HP-UX and Solaris only) |
Same as above. (HP-UX and Solaris only) |
|
Error notification signal |
SIGILL, SIGTRAP, SIGABRT, SIGFPE, SIGBUS, SIGSEGV, SIGSYS |
|
|
SIGIOT, SIGEMT |
Same as above. (AIX, HP-UX, and Solaris only) |
Same as above. (AIX, HP-UX, and Solaris only) |
|
SIGLOST |
Same as above. (AIX only) |
Same as above. (AIX only) |
|
Other |
|
|
- Important note
-
If you set - for the operation when you are using the trap command, the operation to be performed when signals are received is reset to the default.
With some signals, the operation during debug execution differs from that described in the tables. For details about the differences in signal processing depending on whether an operation is defined with the trap command, see (2) During debug execution.
(2) During debug execution
Type of signal |
When an operation is not defined with the trap command |
When an operation is defined with the trap command |
---|---|---|
SIGINT |
The debugger terminates execution of the job definition script and then waits for entry of a command.# |
The debugger terminates execution of the job definition script and then waits for entry of a command.# The processing depends on the operation defined by the trap command. |
SIGCHLD, SIGTSTP, SIGTTOU, SIGURG, SIGWINCH, SIGIO, SIGPWR |
Performs the next processing. |
The processing depends on the operation defined by the trap command. |
SIGSTKFLT (Linux only) |
||
SIGWAITING, SIGLWP, SIGFREEZE, SIGTHAW, SIGCANCEL, SIGXRES, SIGJVM1, SIGJVM2 (Solaris only) |
||
Real-time signal (HP-UX, Linux, and Solaris only) |