IBM Support

JR34257: RE-IMPORTING WITH ISTOOL -REPLACE FAILS AFTER A JOB RUNNING ONCE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • [ Problem ]
    Re-importing with istool -replace fails after a job running
    once.
    
    
    [ Detail ]
    On customer site. a very strange phenomenon related to istool
    -replace occurs.
    Re-importing a job with istool -replace sometimes fails.
    Customer does not have a clear simple test case.
    
    I tried to reproduce in house.
    I was able to reproduce a re-import error with below error
    messages.
    -----
    Beginning import
     [1/1]  IRITA_31538/takuk01/JOB/P00800/pp00800trans.pjb
    ignored
     The asset has no design-time information
     Unexpected error importing runtime. See the log in the Web
    Console for more details.
    Elapsed time: 00:00:02
    Imported 0 assets
     -----
    

Local fix

  • slibclean before importing again.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    AIX users re-importing jobs using istools
    ****************************************************************
    PROBLEM DESCRIPTION:
    This problem occurs on an AIX system where an existing job,
    that contains at least one transformer has been run. After the
    job has been run, if an attempt is made to re-import the job
    using istools, then that re-import will fail. An import of a
    non existing job is OK.
         The cause is the AIX
    shared library cache, where running the    job has caused the
    transformer shared library to be loaded into that cache. Because
    AIX has it stored in the cache, that shared library cannot be
    overwritten on import and so the import fails.
    ****************************************************************
    RECOMMENDATION:
    The job should be deleted before the re-import is attempted.
    Alternatively the AIX command 'slibclean' can be run that will
    empty the AIX shared library cache which will enable the job to
    be re-imported successfully. This must be run by an
    administrator.
    
    Alternatively: install patch_JR34257_server_aix_8100.tar on the
    server system.
    ****************************************************************
    

Problem conclusion

  • Changed the import code so that if it cannot overwrite a binary
    file, it deletes it and creates a new one instead.
    This means that if patch_JR34257_server_aix_8100.tar is
    installed, the workarounds mentioned below are not necessary.
    

Temporary fix

  • The job should be deleted before the re-import is attempted.
    Alternatively the AIX command 'slibclean' can be run that will
    empty the AIX shared library cache which will enable the job to
    be re-imported successfully. This must be run by an
    administrator.
    

Comments

APAR Information

  • APAR number

    JR34257

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-14

  • Closed date

    2009-11-13

  • Last modified date

    2009-11-13

  • 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

  • R810 PSY

       UP

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

Document Information

Modified date:
11 October 2021