Recent content by jrsimmo

Shubbas - Check to see if you may be running out of file descriptors on the box. Also if you are running ITM 5.0 there was a time when the ITM was hitting the epmgr several times a second. Are you seeing a core file? How large of an endpoint environment do you have? Have you run the wepmgr...

You may want to install this using the command line wpatch or winstall commands and then trace the error. This will give you a clue as to who the system is trying to autheticate with. This will lead you to the source of the problem that the install is seeing. to trace: odadmin trace objcalls...

When looking to migrate to newer software, this question comes up quite a bit. The answer is always yes. New software with new capabilities and fixes to old problems and of course, compatibility and supportability. Older software becomes less likely to be supported as the software levels...

To kill the processes on the TMR Server you would issue a kill -9 1818734 2236484 2277464 The authentication package on the ManagedNode is a dll file so the box will have to be rebooted to pick up the new authentication. Regards, Jim Simmons Tivoli

It is recommended that you install new ManagedNodes and that you migrate existing endpoints to the new gateways. They do not need to be server boxes, but certainly a box with disk space and memory will serve the purpose just fine. The manuals on Installation and Implementation and the Release...

Are all endpoints failing? or just certain ones that are in some migrating state? Check to see what the RIM handler is doing. Did you recycle the oserv on the box that has the RIM handler? Maybe even run a wrimtrace on that box. Regards, -Jim

No information available. Looks like it is not a supported configuration. May be able to do something like this with multiple TMR servers. Just IMHO. Regards, -Jim

The -N option here refers to a proxy endpoint when using the winstlcf command to install to windows type boxes. This windows endpoint must be installed locally (using setup.exe) and then it can become the proxy endpoint. Look at the lcfd.log file from the Windows proxy endpoint for more error...

Another command that is useful is the wgateway command. If used without any options, will show what endpoints are associated with what gateway. Regards, -Jim

The error is more likely to show up in an odtrace log. If you run the wtrace -jHk $DBDIR command and pipe it out to a file along with the odstat -v piped out to a file then you should be able to see what it is actually looking for. You might also add this line to your SWD user's .profile...

There are several questions here. RedHat 8 is not a supported version for Framework. RedHat 7.2 and Enterprise versions 2.1 and 3.0 are the current RedHat supported versions. "Destination unavailable" is usually a communication type problem. Either network, name resolution, or the TMR...

Should be an easy upgrade. Tivoli has really worked to get this upgrade thing correct. Any reason not to go to 4.1.1? It is the better version and has better patches. Regards, -Jim

zaianeimed - Most of the time when the Desktop for Windows is used to access Tivoli and it fails, there is some authentication/password issue. You should be able to bring the desktop up from the command line by sourcing the Tivoli environment...

Jasonbasis - Can you install the endpoint via the winstlcf? Are you using a proxy endpoint to push the endpoint code? (I asume that these are Windows endpoints) The endpoint proxy must be able to connect to the $C share on the "new endpoint" and be able to create directories. Regards, -Jim...

it means that for some reason the person who submitted the job can't access the jobs database. usual causes are: 1. Not on the master domain manager or 2. Permissions issue for the user running conman Thanks, Jim Simmons Technical User