IBM Support

PM77745: EXTERNALLY SUBMITTED JOB MAY BE INCORRECTLY TRACKED AGAINST TWO SEPARATE SCHEDULED OCCURRENCES (FIN APAR PM56377)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • The following problem was originally reported against TWSz 8.5.1
    by APAR PM56377 (CLOSED FIN).  This APAR is created as the means
    to implement a fix for this problem in releases V8R6M0 and up.
    .
    When a TWSz-scheduled job defined with SUBMIT=NO is submitted
    outside of TWSz, it may be incorrectly tracked twice, against
    two separate scheduled occurrences, under the following
    conditions:
    1. An occurrence of the application containing this job is in
       the current plan in READY status
    2. A CP EXTEND process starts
    3. While the CP EXTEND is running, the job is submitted.
    4. The CP EXTEND adds another occurrence of the same
       with a LATEST START TIME *EARLIER* than the pre-existing
       occurrence.
    5. The original application occurrence must not complete before
       the new current plan is brought into production.
    When this happens, the job is tracked "real time" against the
    originally scheduled occurrence, allowing that operation's
    SUCCESSORS to start. But then, when the new plan is brought into
    production and is brought up to date by applying the updates
    logged in the JTLogs while the CP was being created, the re-
    apply of JT events incorrectly associates the job with the NEWLY
    SCHEDULED occurrence.
    .
    The problem can be avoided by making certain that the LATEST
    START TIMES for operations tracking externally submitted jobs
    are always in INPUT ARRIVAL sequence.  This can most easily
    be accomplished by assigning a valid operation-level deadline
    to the operation.
    .
    JT REAPPLY TURNOVER CATCHUP
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL TWS for z/OS 8.6.0 and 9.1.0 USERs       *
    *                                                              *
    *                 FUNCTION=EM,NMM                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Externally submitted jobs may have      *
    *                      JT events incorrectly reapplied         *
    *                      if they run during the CP turn over.    *
    ****************************************************************
    * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
    ****************************************************************
    Externally submitted jobs may have JT events incorrectly
    reapplied if they run during the CP turn over
    

Problem conclusion

Temporary fix

Comments

  • A new JT record (TRL 55) has been created to correctly track
    externally submitted jobs. This implementation
    affects operations already belonging to the CP  that are
    externally submitted, It does not apply to ETT.
    
    
                             - - -
     THE FOLLOWING TWS FOR ZOS PUBLICATION(S) WILL BE UPDATED:
                             - - -
    
    +------------------------------------------------------------
    |                                                C32-1261-07
    |                                                C32-1261-08
    |                                                C32-1261-09
    |TITLE:  TWS for z/OS Diagnosis Guide and Reference
    |
    |
    |Chapter 5. Data Areas
    |
    |
    |Paragraph "TRL - Job-tracking and audit record"
    |
    |Add the following new trl record:
    |
    |Offsets  Type      Length Name       Description
    |52  (34) STRUCTURE 42     TRLDBY55   Record Data
    |52  (34) CHARACTER 16     TRLADI55   ADID
    |68  (44) CHARACTER 10     TRLIA55    IA
    |78  (4E) SIGNED     2     TRLOPNUM55 Operation number
    |80  (50) CHARACTER  8     TRLJOBID55 Job ID
    |88  (58) CHARACTER  6     *          Free
    |
    +------------------------------------------------------------
    

APAR Information

  • APAR number

    PM77745

  • Reported component name

    TIV WRKLD SCHD

  • Reported component ID

    5697WSZ01

  • Reported release

    602

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-11-26

  • Closed date

    2014-04-15

  • Last modified date

    2016-04-22

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

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

    UI17085 UI17086 UI17087 UI17088 UI17089 UI17090

Modules/Macros

  • EQQAUDIT EQQEMJNA EQQEMMAT EQQNMEXT EQQNMRST JWSZ602J JWSZ912J
    JWSZ922J
    

Publications Referenced
SC32126107SC32126108SC32126109  

Fix information

  • Fixed component name

    TIV WRKLD SCHD

  • Fixed component ID

    5697WSZ01

Applicable component levels

  • R600 PSN

       UP

  • R602 PSY UI17088

       UP14/06/20 P F406

  • R910 PSN

       UP

  • R912 PSY UI17089

       UP14/06/20 P F406

  • R920 PSN

       UP

  • R922 PSY UI17090

       UP14/06/20 P F406

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"602","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"602","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
22 April 2016