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 JUNE 26, 2013

Applies to:

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

Symptoms

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

  1. submit simple job with sleep 30 (confirm it runs on backup master node,if  MP domain)
  2. tmshutdown -g QUEGRP(/Q group) (or master node with /Q down)
  3. after 30 seconds tmboot -g QUEGRP(/Q group) or migg and boot /Q group on backup master node)
  4. artjesadmin/ptj

the job is gone, but still running

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms