Thanks Ek and James!
Right on the head both of you!
Just in case anybody's interested,
here's what i get after copying /usr/OV/service/reset_ci
to qwe (my favourite junk-name, easy to type)
and running just the (new) Tivoli part with set -x
[tolkien@NMSSR2:/home/root]> qwe
+ + objcall 0.0.0 get_oserv
OSERV=1712420541.1.2
+ [ 0 -ne 0 ]
+ + tr .
+ objcall 1712420541.1.2 query whoami
SEARCH_KEY=1712420541.1
+ P1=.
+ SEARCH_KEY=1712420541.1.
+ + grep 1712420541.1.
+ wlookup -ar ManagedNode
MNL=NMSSR2 1712420541.1.348#TMF_ManagedNode::Managed_Node#
+ + echo NMSSR2 1712420541.1.348#TMF_ManagedNode::Managed_Node#
+ awk {print $1}
LABEL=NMSSR2
+ + awk {print $2}
+ echo NMSSR2 1712420541.1.348#TMF_ManagedNode::Managed_Node#
MNOID=1712420541.1.348#TMF_ManagedNode::Managed_Node#
+ + cat /usr/OV/conf/NetViewServerOID
NV=1052361177.1.572#NetView::Server#
+ idlcall 1052361177.1.572#NetView::Server# _set_mannode NMSSR2
{ SYSTEM_EXCEPTION StExcep::INV_OBJREF { 28 NO }}+ basename qwe
+ echo \nqwe finished\n
qwe finished
[tolkien@NMSSR2:/home/root]>
Conclusion: As long as NetView does it's job
(which it does perfectly alright), i won't start
worrying about the Framework part.
Thanks again, Ralph.
-----Ursprüngliche Nachricht-----
Von: Ek C. [SMTP:ek@RALEIGH.IBM.COM]
Gesendet am: Freitag, 05. März 1999 19:19
An: NV-L@UCSBVM.ucsb.edu; Schiffinger Ralph 2100
Betreff: Re: reset_ci
Ralph,
You remind me to check the file reset_ci. Fortunately, it is a shell
script. It seems that the error you got
come from the line "idlcall ..." at the end of the file.
This idlcall is used to set the mannode attribute of the NetViewServer
object which should be the same
as the name of the NetViewServer. If this field is incorrectly set, you
may not be able to use your desktop
to manage the netviewserver because it will look for the NetViewServer
object at the wrong managed node.
You may need to run idlattr command to reset the mannode attribute to
the right value if you found it
incorrectly set by reset_ci.
Hope this could help...Ek
-----Ursprüngliche Nachricht-----
Von: James_Shanks@TIVOLI.COM [SMTP:James_Shanks@TIVOLI.COM]
Gesendet am: Freitag, 05. März 1999 19:02
An: NV-L@UCSBVM.ucsb.edu; Schiffinger Ralph 2100
Betreff: Re: reset_ci
reset_ci is a script and you can trace what it does if you like.
I think you are getting a failure trying to talk to the oserv. That code
was put into NetView V5 (or 5.1 -- don't remember which) by some
well-meaning soul who thought he should try to fix your oserv problems too.
But it only works I am told if you installed in the standard way -- your
box is the TMR server and there is a root admin with permissions to do
anything -- the sort of thing you'd get if you installed Framework just to
run NetView. Anything fancier than that will probably fail. Anyway, I
believe there was an APAR and a fix in 5.1.1 about this.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Schiffinger Ralph 2100 wrote:
> Hi, group!
> This is what i'm getting from /usr/OV/service/reset_ci
>
> Start of reset_ci, after successful completion
> you will receive a reset_ci finished message.
> Reregistering /usr/OV/lrf/ovesmd.lrf...
> ovaddobj - Static Registration Utility
> Successful Completion
> Reregistering /usr/OV/lrf/ovelmd.lrf...
> ovaddobj - Static Registration Utility
> Successful Completion
> { SYSTEM_EXCEPTION StExcep::INV_OBJREF { 28 NO }}
> reset_ci finished
>
> Anyone seen something like that?
> Any ideas what it could mean?
> As long as it says: reset-ci finished...
> Well, just wondering...
> Regards, Ralph.
> iT-AUSTRIA / OE2100 / TK-NET
> Tel. +43 1 21717 58948
> FAX +43 1 21717 58979
> Mobil 0664 1908469
> Mailto:Ralph.Schiffinger@erstebank.at
|