IBM Support

JR39415: An ISD import fails if the agent name specified in the data file is not configured on the target system.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ISD import command will fail to import a file exported
    from another system if the target system does not have same
    Agent (host) specified as what is stored in the export file.
    

Local fix

  • 1) create an Agent with same name on the target system
    2) import application
    3) change Agent for the imported application on target system
    4) delete the temporary agent created in step # 1
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users importing runtime applications on one system that were
    exported from another system that had a different agent.
    ****************************************************************
    PROBLEM DESCRIPTION:
    1)  Export an application from the runtime section of ISD on one
    system (e.g. VMWIN08)
    2)  Import the application to the runtime section of a different
    system (e.g. VMWIN06)
    
    The import fails because the Agent configured on the system
    being exported from does not exist on the system being imported
    to.  This causes an AgentNotConfiguredException.
    ****************************************************************
    RECOMMENDATION:
    Install this patch.  Note that a bundled patch containing this
    and other fixes is being prepared.  When available, that will
    supersede this patch and must be installed instead.
    ****************************************************************
    

Problem conclusion

  • The AgentNotConfiguredException that is thrown when an attempt
    is made to enable the provider on the missing agent is ignored
    on import (unless enableProvider was explicitly specified on
    the import).
    
    It should be noted that after the import is done, any attempt to
    enable the application will result in an exception until the
    agent name has been updated to a valid agent.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR39415

  • Reported component name

    WS INFORM. SRVC

  • Reported component ID

    5724Q3600

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-15

  • Closed date

    2011-05-10

  • Last modified date

    2011-10-12

  • 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

    WS INFORM. SRVC

  • Fixed component ID

    5724Q3600

Applicable component levels

  • R850 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSZJMP","label":"InfoSphere Information Services Director"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5"}]

Document Information

Modified date:
06 October 2021