The scenario I’ve seen with the 4SHUT causing the process to shutdown is when the engine has sent a message to INVISION, but prior to INVISION issuing the ACK, a 4SHUT message is sent from INVISION because the system is being brought down for dayend, etc. Since the engine is in reply mode (i.e. waiting on the reply) it processes this 4SHUT in the reply context; in the tcl procs there is a command to shutdown the process if a 4SHUT is rec’d as a REPLY. Then this message gets ‘bound in tcl’ and is in the recovery database at state 1. Every time you start the process it gets shutdown because this message gets pulled in from the recovery database and causes the script to run the shutdown again. You ultimately have to delete the 4SHUT message from the recovery database to get things back up and running.
INVISION will send a 4SHUT whenever communications is being shutdown due to a downtime; normally the engine just ignores these if it’s not expecting a REPLY.
Hope this helps.
Jim Cobane
Henry Ford Health
Author
Replies
Viewing 0 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.
.
.