IBM Support

IV59126: TWS SERVICE GOES DOWN IMMEDIATELY AFTER THE TWS IS RESTARTED ON WINDOWS 2012.

Direct links to fixes

9.1.0-TIV-TWS-WINDOWS_X86_64_AGENT-FP0002
9.1.0-TIV-TWS-WINDOWS_X86_64_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-DWC-README-FP0002
9.1.0-TIV-TWS-WINDOWS_AGENT-FP0002
9.1.0-TIV-TWS-WINDOWS_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-SOLARIS-FP0002
9.1.0-TIV-TWS-SOLARIS_I386-FP0002
9.1.0-TIV-TWS-SOLARIS_I386_AGENT-FP0002
9.1.0-TIV-TWS-SOLARIS_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUXPPC-FP0002
9.1.0-TIV-TWS-SOLARIS_I386_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-SOLARIS_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_X86_64-FP0002
9.1.0-TIV-TWS-LINUX_X86_64_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_X86_64_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX_S390_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_S390_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX_PPC_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_PPC_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX_I386_AGENT-FP0002
9.1.0-TIV-TWS-LINUX_I386_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-LINUX390-FP0002
9.1.0-TIV-TWS-IBM_I_AGENT-FP0002
9.1.0-TIV-TWS-IBM_I_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-HPIA64-FP0002
9.1.0-TIV-TWS-HPIA64_AGENT-FP0002
9.1.0-TIV-TWS-HPIA64_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-AIX-FP0002
9.1.0-TIV-TWS-AIX_AGENT-FP0002
9.1.0-TIV-TWS-AIX_AGENT_FOR_ZOS-FP0002
9.1.0-TIV-TWS-WINDOWS_X86_64-FP0002
9.2.0-TIV-TDWC-TWS-FP0001
9.2.0-TIV-TWS-AIX_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-AIX_AGENT-FP0001
9.2.0-TIV-TWS-HPIA64_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-HPIA64_AGENT-FP0001
9.2.0-TIV-TWS-IBM_I_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-IBM_I_AGENT-FP0001
9.2.0-TIV-TWS-LNX_I386_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-LNX_I386_AGENT-FP0001
9.2.0-TIV-TWS-LNX_PPC_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-LNX_PPC_AGENT-FP0001
9.2.0-TIV-TWS-LNX_S390_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-LNX_S390_AGENT-FP0001
9.2.0-TIV-TWS-LNX_X86_64_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS--LNX_X86_64_AGENT-FP0001
9.2.0-TIV-TWS-SOLARIS_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-SOLARIS_AGENT-FP0001
9.2.0-TIV-TWS-SOLARIS_I386_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-SOLARIS_I386_AGENT-FP0001
9.2.0-TIV-TWS-AIX-FP0001
9.2.0-TIV-TWS-HPIA64-FP0001
9.2.0-TIV-TWS-LINUX_X86_64-FP0001
9.2.0-TIV-TWS-LINUX390-FP0001
9.2.0-TIV-TWS-LINUXPPC-FP0001
9.2.0-TIV-TWS-SOLARIS_I386-FP0001
9.2.0-TIV-TWS-SOLARIS-FP0001
9.2.0-TIV-TWS-WINDOWS_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-WINDOWS_AGENT-FP0001
9.2.0-TIV-TWS-WINDOWS_X86_64_AGENT_FOR_ZOS-FP0001
9.2.0-TIV-TWS-WINDOWS_X86_64_AGENT-FP0001
9.2.0-TIV-TWS-WINDOWS_X86_64-FP0001

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After TWS service is restarted(i.e. FINAL jobstream, conman
    stop/start), the TWS service goes down immediately.
    
    The following message is outputted in TWSMERGE.log after
    restarted TWS downed.
    ----------------------------------------------------------------
    JOBMAN:AWSBDW015I Received command tQ for run number X from
    workstation XXXXXXXX.
    
    BATCHMAN:* AWSBHT087E Batchman has determined that jobman has
    failed with the following exit code: AWSDFD075I Stopped
    Normally.
    
    MAILMAN:+ AWSBCV001E Batchman has failed with an internal
    error, producing the following status code: AWSDFD075I Stopped
    Normally.
    

Local fix

Problem summary

  • This happens on Windows only. When conman stop is issued,
    batchman write a stop record in mailman msg queue: this record
    is processed by mailman that stops. During the stop phase
    also a windows stop event is generated to make sure all the
    process stops. Occasionally it may happens that
    stop event is received by mailman before the stop record is
    processed and this cause mailman to stop without the stop record
    has been processed. The side effect of this kind of stop is that
    the stop record remains into the mailman msg queue and is
    immediately processed after mailman restarts: after mailman
    restarts, the stop record is processed and the product stops.
    The problem has been fixed skipping stop records in mailman msg
    queue older than the mailman start date.
    

Problem conclusion

  • The problem will be fixed in TWS 8.6 fp05, TWS 9.1 fp02, TWS 9.2
    fp 01
    

Temporary fix

  • see local fix
    

Comments

APAR Information

  • APAR number

    IV59126

  • Reported component name

    TIV WKLD SCHDL

  • Reported component ID

    5698WKB91

  • Reported release

    9W1

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-04-11

  • Closed date

    2014-05-09

  • Last modified date

    2017-01-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TIV WKLD SCHDL

  • Fixed component ID

    5698WKB91

Applicable component levels

  • R9W1 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9W1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 January 2017