IBM Support

JR32860: EXPORT/IMPORT FROM IS MANAGER .ISX FILE , ISTOOL or DSXIMPORTSERVICE REQUIRES RECOMPILE BEFORE JOB CAN RUN SUCCESSFULLY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Export/Import from IS Manager or istool .isx file requires
    recompile  before job can run successfully after import. The
    .isx file contains runtime data but the job fails until it is
    recompiled.
    
    Problem also shows using DSXImportService.sh or
    DSXImportService.bat to import .dsx files which contain job
    runtime.
    

Local fix

  • Workaround is to recompile the job. Alternatively for a dsx
    fileand  DSXImportService, use the Designer import function
        instead.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Information Server Manager export / import facilities,
    istool commandline tool and DSXImportService commandline tool
    ****************************************************************
    PROBLEM DESCRIPTION:
    Certain jobs imported with their runtime using the Information
    Server Manager or the istool and DSXImportService commandline
    tools give internal errors when run. The errors are resolved if
    the job is recompiled.
    
    It is difficult to anticipate the errors reported, but so far
    we have seen errors like "Parameter not resolvable:
    DSCAPIOP_...". Not all job runtime will be affected; this
    example is seen only when dscapiop / API stages are used in a
    parallel job.
    
    ****************************************************************
    RECOMMENDATION:
    Apply the patch to resolve the problem. Refer to readme file for
    required locations - client, server & domain. Re-export any
    istool or Information Server Manager files.
    
    This fix is included in 8.1 FP1.
    ****************************************************************
    

Problem conclusion

  • Resolved by correcting internal separator (mark character)
    handling in the Java infrastructure used by the affected
    components : export and import from istool and Information
    Server Manager, and import using DSXImportService.
    
    Customers experiencing this problem with information server
    manager or istool export files will have to re-export the
    affected components after applying the patch. DSX files which
    came from Designer GUI or similar components should not need
    re-exporting.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR32860

  • 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-05-01

  • Closed date

    2010-01-21

  • Last modified date

    2010-01-21

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

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

Modules/Macros

  • ALL
    

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":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
21 January 2010