Tuxedo Application Runtime for CICS and Batch 12cR1: TUXJES Does Not Take Care Jobs When /Q Is Unavailable
(Doc ID 1562924.1)
Last updated on MAY 07, 2020
Applies to:Oracle Tuxedo Application Runtime for CICS and Batch - Version 220.127.116.11 and later
Information in this document applies to any platform.
TuxJES system does not take care error handling if /Q is not available.
For example, if /Q process down when running job and if /Q can not recover after job end. The job status is "running" and never changed.
If we use MP configuration, /Q existing node is down, the status of running job on another node will be incorrect and can not recover.
Simple case to reproduce behavior:
tmboot -y for TuxJES
- submit simple job with sleep 30 (confirm it runs on backup master node,if MP domain)
- tmshutdown -g QUEGRP(/Q group) (or master node with /Q down)
- after 30 seconds tmboot -g QUEGRP(/Q group) or migg and boot /Q group on backup master node)
the job is gone, but still running
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