IBM Support

JR31670: INFORMATION SERVER 801: NODE MAP CONSTRAINTS SET IN THE SURROGATE KEY GENERATOR STAGE ARE IGNORED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Information Server 801:  I have a parallel job that with the
    Surrogate Key Generator stage and I defined a Node Map
    constraint on node1, but when I run the job the Node Map
    constraint is ignored.
    
    Looking at the osh I see the nodemap set to node1:
    
    ################################################################
    #
    #### STAGE: Surrogate_Key_Generator_1
    ## Operator
    surrogatekey
    ## Operator options
    -sk_id '/tmp/mrl_surr_key_test4.sf'
    -output_key 'SURR_KEY'
    ## General options
    [ident('Surrogate_Key_Generator_1');
    jobmon_ident('Surrogate_Key_Generator_1'); nodemap ( node1 ) ;
    nocombine]
    ## Inputs
    0< [] 'Row_Generator_0:DSLink2.v'
    ## Outputs
    0> [] 'Surrogate_Key_Generator_1:DSLink4.v'
    ;
    
    
    But dumpscore shows it is using all 4 nodes:
    
    main_program: This step has 4 datasets:
    ds0: {op0[1p] (sequential Row_Generator_0)
          eAny<>eCollectAny
          op2[4p] (parallel buffer(0))}
    ds1: {op1[1p] (sequential APT_KeyStateProcessOp in
    Surrogate_Key_Generator_1)
          eOther(APT_ModulusPartitioner {})<>eCollectAny
          op3[4p] (parallel APT_KeyGenerator in
    Surrogate_Key_Generator_1)}
    ds2: {op2[4p] (parallel buffer(0))
          eSame=>eCollectAny
          op3[4p] (parallel APT_KeyGenerator in
    Surrogate_Key_Generator_1)}
    ds3: {op3[4p] (parallel APT_KeyGenerator in
    Surrogate_Key_Generator_1)
          [pp] >>eCollectAny
          op4[1p] (sequential APT_RealFileExportOperator in
    Sequential_File_3)}
    It has 5 operators:
    op0[1p] {(sequential Row_Generator_0)
        on nodes (
          node1[op0,p0]
        )}
    op1[1p] {(sequential APT_KeyStateProcessOp in
    Surrogate_Key_Generator_1)
        on nodes (
          node2[op1,p0]
        )}
    op2[4p] {(parallel buffer(0))
        on nodes (
          node1[op2,p0]
          node2[op2,p1]
          node3[op2,p2]
          node4[op2,p3]
        )}
    op3[4p] {(parallel APT_KeyGenerator in
    Surrogate_Key_Generator_1)
        on nodes (
          node1[op3,p0]
          node2[op3,p1]
          node3[op3,p2]
          node4[op3,p3]
        )}
    op4[1p] {(sequential APT_RealFileExportOperator in
    Sequential_File_3)
        on nodes (
          node2[op4,p0]
        )}
    

Local fix

  • Workaround is to constrain on a Node Pool.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Datastage
    ****************************************************************
    PROBLEM DESCRIPTION:
    some minor issue on code and was corrected
    ****************************************************************
    RECOMMENDATION:
    801
    This change is included in 8.1 Fix Pack 1.
    ****************************************************************
    

Problem conclusion

  • fix is available on 801Fp1
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31670

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-14

  • Closed date

    2009-04-21

  • Last modified date

    2009-12-18

  • 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

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R801 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":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
18 December 2009