IBM Support

IY94286: WHEN USING REMOTE DP'S THEY DO NOT RECONECT TO THE TARGET UA IF THE TARGET UA IS RESTARTED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the UA that is hosting a remote DP is restarte the remote
    DP does not reconnect once the host UA is available again. The
    remote DP has to be cycled to get the connection back.
    
    Action Taken : Recreated steps as follows :-
    
    1. copied files required for remote DP to work to separate
    directory on
    laptop. (see dir output on Ecurep for filelist.).
    
    
    2. Placed testping.mdl in metafiles directory and updated
    KUMPCNFG file.
    
    3. Installed and started UA on hubtems (my main TEMS.)
    
    4. Checked that UA worked properly.
    
    5. Setup batch file to point to UA.
    
    6. Started remote DP using batch file.
    
    7. Monitored using TEP client to see when DP showed up.
    
    8. Stopped main UA.
    
    9. Waited 1 minute then restarted UA.
    
    
    10. Wait for UA to show available on TEP client.
    
    11. Wait 15 minutes to see if remote DP returns, it doesn't.
    
    12. Restart remote DP, returns immediately.
    
    
    batch file and MDL are both on Ecurep in recreate directory
    under normal
    PMR path.
    

Local fix

Problem summary

  • UA supports use of running its data providers
    remotely, that is to run the data provider on host A when UA is
    running on host B.
    
    When UA is restarted and it is connecting to a remote DP the
    remote DP does not automatically reconnect to UA when UA is
    stopped and then restarted.  The remote DP has to be cycled to
    get the connection back.
    

Problem conclusion

  • The key logic change is in kumptwdo.c where
    the DP-->DCH socket connection occurs.  Added a while (Retry)
    loop that's mainly intended to allow a standalone DP to keep
    trying the socket connection until the UA/DCH has been restarted
    and re-initialized.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    | fix pack | 6.1.0-TIV-ITM-FP0007
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY94286

  • Reported component name

    UNIVERSAL AGENT

  • Reported component ID

    5724K1000

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-02-01

  • Closed date

    2008-04-30

  • Last modified date

    2008-04-30

  • 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

    UNIVERSAL AGENT

  • Fixed component ID

    5724K1000

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHL9","label":"Tivoli Universal Agent"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 April 2008