markjde
Active Member
When our ES is re-booted the administrator requires us to provide them with
either an automatic startup of all our subsystem jobs, or a script to allow
the administrator to start all subsystem jobs from the ES.
Basically what is happening is when the system is re-booted the pick slip
print subsystem job is ended, but when they restart the ES it isn't started.
As a result, we might go most of the day before we realize the problem. Has
anyone had any experience with this?
Thanks.
Mark
7332 SP 11.2, NT, SQL 7.0
either an automatic startup of all our subsystem jobs, or a script to allow
the administrator to start all subsystem jobs from the ES.
Basically what is happening is when the system is re-booted the pick slip
print subsystem job is ended, but when they restart the ES it isn't started.
As a result, we might go most of the day before we realize the problem. Has
anyone had any experience with this?
Thanks.
Mark
7332 SP 11.2, NT, SQL 7.0