My Oracle Support Banner

Tuxedo Application Runtime for CICS and Batch 12cR1 (12.1.1.0): WAITING JOB DOES NOT PROCESS AFTER REBOOT (Doc ID 1540414.1)

Last updated on NOVEMBER 14, 2023

Applies to:

Oracle Tuxedo Application Runtime for CICS and Batch - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms

When executing JOB, If the machine has been crashed and  after recovering machine, that job
status will be INDOUBT status, and WAITING job should be processed continously.

However, if jesconfig has not defined as DUPL_JOB=NODELAY, WAITING job will not be started after recovering machine.
It stayed DELAYEXEC queue. If same JOB has submit and finished , then WAITING job will be processed.

normal status

JOB001   00000178 *           9 B     EXECUTING
JOB001   00000179 *           9 B     WAITING
JOB001   00000180 *           9 B     WAITING

machine down and reboot

 JOB001   00000178 *           9 B     INDOUBT
 JOB001   00000179 *           9 B     WAITING <----- not start here
 JOB001   00000180 *           9 B     WAITING

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.