Sheduled maintenance is no problem as we are aware of it and we shut down the services manually and everything is fine. However in events where the batch processing is running longer than usual, the subsystems are down and the services kick off and there you go….they become un responsive and needs a server restart to bring things back to normal.

So what we would do is grant the AS400 admin or operator admin rights to the W2K3 server. Then whenever AS400 maintenance was to be performed the admin would log onto the W2K3 box either interactively using a Remote Desktop Connection (RDC) from a PC.
Or Using the Admin Tools on a PC point to the W2k3 box and stop the necessary service before continuing on with the AS400 work.
Sometimes you cant’ talk your Windows admins into giving you full admin rights to use the RDC, but if you can get access to the services then that should be sufficient using the admin tools.

RDC
Read section: Connect your remote computer to the host computer

Admin Tools (Services)
Read section: How to Use Computer Management on a Remote Computer

Somehow I just finished writing Java program to check if any specific subsystem i down and if that is the case i would not fire up the authentication sevice on window.

Just thinking any other way to do this….suggestions???

To Slack400: Can you please elaborate “You can then use RDC or admin tools from your PC to shutdown the service before you kick off a opt 21″

thanks

I don’t miss the pain of shutting down subsystems for nightly’s.

Then you’re only down when you’re running full system saves (annually or more) Then you’ll have to schedule these outages with your windows server admin so they can kill this authentication service.

IF necessary they can give you admin rights to the windows services on that box.
You can then use RDC or admin tools from your PC to shutdown the service before you kick off a opt 21.

This link is a good reference for creating the VB script.