That is correct, it is being called externally. The tec/onmibus server ssh/rsh
to the remedy server to executed the script. This is what I'm simulating,
running it local on server (commandline), which should do the stdout of
arerrors but this is not occurring with 7.5 runmacro, but does work wit
not returning the stdout error
7.5 filter logs does capture the error, but does not do the stdout nor log to
the arfork.log. " Error while performing filter action: Error 653258"
--
/* Thu Aug 09
2012 19:15:47.9647 */ Checking
"*FP-SM 340 SM Valid
7.5 filter logs does capture the error, but does not do the stdout nor log to
the arfork.log. " Error while performing filter action: Error 653258"
--
/* Thu Aug 09
2012 19:15:47.9647 */ Checking
"*FP-SM 340 SM Validate CPI 1" (340)
--> Failed
qualification
/* T
(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of D Dussie
Sent: Thursday, August 09, 2012 5:05 PM
To: arslist@ARSLIST.ORG
Subject: Re: Runmacro is not returning the stdout error
Exactly, using a data that should not return an error and execute to create a
incident ticket, this works fine for
Ok, found the protocol definition, its just defining the verison you are
running..
Protocol: Version
Protocol 11:6.3
Protocol 12:7.0.1
Protocol 13:7.1
Protocol 14:7.5
Protocol 17:7.6.03
Protocol 18:7.6.04
___
UNSUBSCRIB
Exactly, using a data that should not return an error and execute to create a
incident ticket, this works fine for both versions 6.3/7.5.
BMC is request recreating the macro in 7.5. vs the current which was created in
probably 6.3 version at max. However, since this is a flatfile , i'm waiting
)
[mailto:arslist@ARSLIST.ORG] On Behalf Of D Dussie
Sent: Thursday, August 09, 2012 1:40 PM
To: arslist@ARSLIST.ORG
Subject: Re: Runmacro is not returning the stdout error
Thank you for responding,
api.log shows the marco is being executed, however that stdout of the error is
not occuring,
w
Thank you for responding,
api.log shows the marco is being executed, however that stdout of the error is
not occuring,
when it registers "Unidentified Client" -- the stdout of the error occurs.
when it registers "runmacro" is fails..
What does it mean to be an Unidentified Client?
/* Thu
not returning the stdout error
Hello List,
Hoping someone can assist.
With further investigation, I have found that filters are not being executed
with 7.5 Runmacro executes. The errors are not being written to arfork.log.
With Runmacro 6.3,
Arfilter.log logs this entry, which is reflected
Hello List,
Hoping someone can assist.
With further investigation, I have found that filters are not being executed
with 7.5 Runmacro executes. The errors are not being written to arfork.log.
With Runmacro 6.3,
Arfilter.log logs this entry, which is reflected in the stdout error for
runma
Hello Everyone,
Environment,
AIX 6.1. with ARS 7.5P4 on 11g (local)
Websphere 6.1, MT 7.5P4 32bit install.
History, we have been using runmacro to create automated tickets for a long
time. So it is bridge between TEC/Ominbus and Remedy.
Occasionally and lately we have been experiencing
11 matches
Mail list logo
