People come up with the dumbest requests.
Users access a specific system using a product called Switch. Every night the active users log off at about 23:30 and operations cycles the task to bounce any users that forgot to log off to free up all the connections.
So now someone came up with the brilliant idea that instead of cycling the task the active users could still log off and then we could display all the active connections and then just cycle any connection that shows active with a session.
I just displayed the current active connections and see 285 thus turning a task that is performed by a single command (that completes in about 1 minute) to an automated routine that could consist of up to 570 separate commands which will take a hell of a lot longer that 1 minute because each inactivate command has to be issued individually, wait for it to go inactive then you can issue the activate command again.
Users access a specific system using a product called Switch. Every night the active users log off at about 23:30 and operations cycles the task to bounce any users that forgot to log off to free up all the connections.
So now someone came up with the brilliant idea that instead of cycling the task the active users could still log off and then we could display all the active connections and then just cycle any connection that shows active with a session.
I just displayed the current active connections and see 285 thus turning a task that is performed by a single command (that completes in about 1 minute) to an automated routine that could consist of up to 570 separate commands which will take a hell of a lot longer that 1 minute because each inactivate command has to be issued individually, wait for it to go inactive then you can issue the activate command again.