IBM Tivoli Monitoring for Applications: mySAP.com tasks fail with 4.1.1-TMF-0090 and 4.1.1-TMF-0085

Flash (Alert)


This document applies only to the following language version(s):

English

Abstract

After installing 4.1.1-TMF-0090 or 4.1.1-TMF-0085, Configure Remote Function Call and Server Status tasks fail. mySAP Application Server icon shows unknown state, a yellow triangle with a "?"

Content

Diagnosing: The values of the AMS_INSTANCE_OID and INSTANCE_OID variables in the task logs will be equal to "oid##taskname#". For example:

+ idlcall 1788621172.1.5167##MSM_moa03/Configure Remote Function Call# update_context "ABH_Client=100"
+ CLIENT_OK=0
+ [ 0 -ne 0 ]
+ USER_ID=0
+ idlcall 1788621172.1.5167##MSM_moa03/Configure Remote Function Call# update_context "ABH_Userid=TME"
+ [ 1 -ne 0 ]
+ USER_ID=1
+ diagmsg LOGYES sap_config_rfc.sh idlcall 1788621172.1.5167##MSM_moa03/Configure Remote Function Call# userid

Cause: This failure is a result of installing 4.1.1-TMF-0085 or 4.1.1-TMF-0090. These include changes to the run_task method which break mySAP PAC tasks. Future TMF patches for TMR servers, managed nodes, and gateways could also introduce this problem.

Resolving: ITM Component Services 5.1.3 Interim Fix 15 (5.1.3-TIV-ITM_ICS-IF0015) was released in July 2007 with a fix for APAR IY99695: AMS_INSTANCE_OID contains task name causing run task failure on the TMR or endpoint.


Related information

5.1.3-TIV-ITM_ICS-IF0015

Product Alias/Synonym

mySAP PAC
mySAP.com PAC

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Monitoring for Applications
IBM Tivoli Monitoring for Applications mySAP.com

Software version:

5.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1289519

Modified date:

2010-04-26

Translate my page

Machine Translation

Content navigation