Issue: Lockedby codes reflect the state of CAPSYS Capture cases as they are processed. The Q_QUEUE table shows all cases and their Lockedby values. Understanding what happens with specific Lockedby values will help ensure a smooth process for each case.
Note: Capsys Software does not recommend directly editing the CAPSYS Capture Database, and is not responsible for any loss of data caused by doing so.
Resolution: Lockedby Codes drive specific processing or events for each case within the system.
Lockedby Code -97
EventID = xx, Lockedby = -97, MachineName = empty string
When an input module creates a new case, it is initially created as shown above. The EventID is the start event for the batch profile. If the server crashes at this point, the Input module will submit the case again on restart. If you see any rows like this when the servers are stopped, they can be deleted. The corresponding batch has already been resubmitted.
Lockedby Code -99
EventID = xx, Lockedby = -99, MachineName = empty string
This is a case that has been marked completed by the Web Client or ServerManager. When a server picks it up, the Lockedby will be changed to -100 and the MachineName will be changed to the name of the server processing the case. Cases that are being processed by a CAPSYS Capture Server will have the MachineName value set and the Lockedby set to -100 or -104. As soon as a case is picked up by the server (from an input module, from being completed in a queue or from an assembly event), the Lockedby is changed to -100 and the MachineName value is set. These columns will remain constant as the case moves through the map. The EventID and DateIn will be updated as the case moves from one event to the next. When the case reaches a queue, the Lockedby will be changed to -104. -104 indicates that a case is being routed into a queue. When the files have been copied to the DataStore, the Lockedby will be set to -1 and the MachineName will be set to an empty string.
Lockedby -101
EventID = xx, Lockedby = -101, MachineName = empty string
This is a case that has been marked for deletion by the ServerManager. When a server picks it up, the Lockedby will be changed to -102 and the MachineName will be changed to the name of the server processing the case. EventID = xx, Lockedby = -102, MachineName = yyyy This is a case that is being deleted by the server named yyyy. The files will be copied from the DataStore to the Server's Working Directory and then deleted. Then, the database records will be deleted and an AuditLog record will be created recording the deletion.
Lockedby Code -105
EventID = xx, Lockedby = -105, MachineName = empty string
This is a batch that has been released from a client workstation. The EventID is the start event of the batch profile. When a server picks up this case, the Lockedby will be changed to -106 until the batch backup is created. At that time, the Lockedby is changed to -100 and the batch is routed along the process map.
If the servers are stopped, there should be no cases with a -1 EventID or a Lockedby of -97.
Note:
** Cases being processed by a server will have a Lockedby value of -100, -102, -104 or -106 and the MachineName value equal to the network name of the server.
** Cases with a Lockedby value of -99, -101, and 105 are waiting for a server.
** If the servers are stopped, there should be no cases with a -1 EventID or a Lockedby code of -97.
0 Comments