We've come to the conclusion that when batch printing tickets, the APPLICATION_TIMEOUT causes the batch to become irrevocably locked to the user on the client side. The DBA has to manually unlock the batch in the background. A simple response is "So just have someone watch the batch while it prints and to cancel the timeout", but some batches apparently are so large they have to be left overnight to print. Is there some way to make this a background process or have it be "immune" to the timeout for the sake of printing these ticket batches?
Matt,
You can override the default APPLICATION_TIMEOUT at the workstation level by adding an APPLICATION_TIMEOUT into the local .ini file for that user. Whatever is in the [Defaults] section of the ini for APPLICATION_TIMEOUT will override what is in T_DEFAULTS for that user.
Of course making this value greater than 900 seconds (15 Minutes) would not be PCI compliant unless you locked the windows screen after 15 minutes of inactivity.Dale