Terminal Concentrator FAQs

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.

Terminal Concentrator FAQs

What are the memory and disk requirements of TC?

The following numbers are not exact but are meant to give an idea of TC requirements. Without knowing a lot of details about a potential system, it isn't possible to be exact.

Disk space:

TC/Windows – 64 terminals

TC/Windows XL Version – 80 terminals

TC/4690 – 60 terminals

What are the technical differences between the various TC versions?

The differences can be broken down into the following categories:

Where TC is relative to the 4690 controller and files.

Whether or not and how other applications running in the concentrator interact with TC or the sales application.

Method of I/O device emulation or access.

If I/O device access is provided by the TC Remote Peripheral Access Method (RPAM), the type of communication that is used between the client terminal and the TC server.

If I/O device access is provide by RPAM, the terminal type of the client.

For additional information, see Knowledge Base Article “Terminal Concentrator Technical Differences (KB000107)”

What are some examples of how TC is used in customer environments?

Handheld terminals: Self shopping or price checker or line busting applications where there is a desire to have the price generated by the customer's standard IBM SA/GSA terminal sales application.

Non-IBM traditional POS terminals: when customer wants to use non-IBM, (typically older), hardware but run IBM SA/GSA sales applications.

Older IBM terminals that are low on memory and can no longer hold an application that has grown in size.

How do I do a terminal concentrator trace in a 4690 environment?

Note: For complete diagnostic information, QVS may also need "client-side" diagnostic logs. This means that your code must enable client-side logging. This is not necessary if you are running Terminal Concentrator with a standard IBM terminal. In order to obtain traces of Terminal Concentrator execution do the the following steps:
Read more...

How do I do a terminal concentrator trace in a windows environment?

Note: For complete diagnostic information, QVS may also need any generated "client-side" diagnostic logs. This means that your code must enable client-side logging. If you are using either a "COM RPAM" or "Java" client, these logs are created when the following command is issued from your client code: Java: Set RPAMApp.setTracing(true) COM RPAM: Set CRPAMApp->put_Tracing(1);
Read more...