IBM Support

JR30374: PX JOB WITH LOOKUP RUNNING ON MORE THAN 2 NODES FAILED WITH EXECUTION MODE SET TO SEQUENTIAL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PX Job with lookup running on more than 2 nodes failed with
    execution mode set to sequential. When checking osh dump, found:
    
    ======
    It has 5 operators:
    ...
    op2[1p] {(sequential APT_LUTCreateOp in Lookup_44)
        on nodes (
          node1[op2,p0]
        )}
    op3[1p] {(sequential APT_LUTProcessOp in Lookup_44)
        on nodes (
          node2[op3,p0]
        )}
    ...
    It runs 5 processes on 2 nodes.
    ======
    

Local fix

  • To workaround the issue, I had to force node map constraint to a
    single node, then I can see operators are assign to a single
    node and the job running happyly:
    
    ======
    It has 5 operators:
    ...
    op2[1p] {(sequential APT_LUTCreateOp in Lookup_44)
        on nodes (
          node1[op2,p0]
        )}
    op3[1p] {(sequential APT_LUTProcessOp in Lookup_44)
        on nodes (
          node1[op3,p0]
        )}
    ...
    It runs 5 processes on 1 node.
    ======
    
    
    
    
    This fix is included in 8.0.1 fixpack 3
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Customers running IS 8.3 or earlier
    ****************************************************************
    PROBLEM DESCRIPTION:
    Job execution failure when running on 2 or more physical nodes
    with a lookup operator in sequential mode.
    ****************************************************************
    RECOMMENDATION:
    This change is included in 8.1 Fix Pack 1.
    
    
    ****************************************************************
    

Problem conclusion

  • In IS versions after 8.3 lookup sub-operators will be forced
    onto the same node to avoid run time failure.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR30374

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-05

  • Closed date

    2009-01-20

  • Last modified date

    2010-12-09

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

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

Modules/Macros

  • SERVER
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R752 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
09 December 2010