ray.wurlod wrote:If you set those users' inactivity timeout to, say, 60 minutes, then one hour after they leave their sessions idle they are cleanly logged out, nothing left locked.
Hahahaha. "Cleanly." Hahaha.
It took us 3 weeks to figure out what the heck was going on with the strange error messages. Once we realized that DataStage client was just disconnected from the server, we quickly increased the idle time to 12 hours.
As for archiving current resources, this is why I am so looking forward to Twister with its check in/out capability. It should allow for the administrator to archive the current version, disregardly of whether someone else is editing it or not.
A little tale, we use Tru-64, and we back up the actual diskspace where DataStage's Project folders are stored. Recently, a co-worker inadvertingly overwrote 4 day worth of work, so we called in the IS team to restore it from the backup the night before. It didn't work. Nor the night before. Nor the night before that...
Right now, we're looking into the reasons why the backup system failed. Teach ya to not trust backups too automatically.
-T.J.