Latest News

Performance Improvements at Point Of Sale - A Guide to Getting the most out of your 4690 System.

It is clear that many of the IBM 4690 POS applications could use an overhaul. But who has the time? And where would one start?

Learn more.

When using InSight UI how much history is available?

It’s not based on time.  The terminal agent has a fixed-size memory buffer for each device.  For keystrokes, it’s more like ' the buffer will hold typically nn keystrokes.'    The current value is approximately 50 keystrokes 

Additional notes:

The controller agent also has a per-device memory buffer and this buffer may be a different size than the terminal buffer.  The controller agent puts keystrokes into its buffer when a terminal is being monitored.  If a 2nd client comes up and wants to monitor a terminal, the 2nd client will be given history from the controller agent instead of the terminal agent (in order to minimize POS loop/lan traffic).  The controller agent's buffer is flushed when there are no more clients.

We are likely to end up with a couple of versions of the terminal agent:  small and normal.  The small version may have smaller history buffers than the normal version.

We may make the terminal device history buffer sizes configurable if it seems like default sizes can’t meet the needs of different customers.

We will likely have an optional feature in future versions that allows keystrokes and other device history to be saved on the controller.  For example, 'save past n days worth of device history for all terminals for these devices.’

Bottom line is that there is some minimum but what the user actually sees can vary based on several factors.

Some other current defaults for device history buff sizes:

  • 40 2x20 display lines
  • 10 cashdrawer open commands
  • 30 receipt lines (38 chars each)
  • 50 vdisplay display lines (80 chars/attrs each)
 
© 2012 QVS Software, Inc.