Active Workstation Direct Connect Reference

GoTo

• Utilizing the Kermit Connection on QSR
• Example: Using the Connection and Getting FILELIST.FDC from the Mark 8

Overview

When Active Workstation QSR is started, it typically launches a Kermit 95 session over the serial port defined for that store (see Store Profile, under AWS Setup & Tools in the navigation frame).

It is important to understand that during normal QSR operation, Kermit 95 is always running.  When AWS QSR is started, it does one of three things relative to the direct connect session:

• It starts Kermit 95 in visible mode, where Kermit 95 shows up as a task in the taskbar of Windows 95/98
• It starts Kermit 95 in hidden mode, where Kermit 95 is started, but does not show up as a task in the taskbar
• It does not start Kermit 95.

The direct connect option is set in Store Profile (see graphic below):

The example above shows the setting for connecting in hidden mode.  If Kermit is started visible, you can tell by noting the task in the taskbar as shown below.

Remember that under normal conditions,  if AWS QSR is running, so it Kermit.   If Kermit is started hidden, the method to confirm it is running is by looking at the Windows task list (CTRL - ALT - DELETE).  If not, check the task list.  This is done by CTRL - ALT - DELETE after which the task list is shown.  If you note K95 in the list, then Kermit 95 is running.

What Happens when Kermit Direct is Started

When AWS QSR starts and it is configured to start Kermit in either visible or hidden mode, Kermit starts and is running.  During this time, Kermit has been programmed to look for things to do every second.  Every second, Kermit will look for a command file of Kermit commands.  Those command files are located in the port directory which has been setup in advance.  This is found in Store Profile (see graphic below):

The command files are simple text files known as Kermit TAKE files.  The filenaming convention is:

command#.ksc

When Active Workstation needs to get or send information to or from the POS system, it constructs these command files on the fly. 

You can take advantage of this by constructing command files manually, then placing those files in the port directory.   This is no different than constructing TAKE files you would use after starting Kermit manually, and issuing a TAKE command.

You do not need to start another session of Kermit 95.

Example: Getting FILELIST.FDC from the Mark 8

For example, if QSR is running and it has started the direct connect session, you can utilize this connection for other purposes.   Say you wish to retrieve the FILELIST.FDC file from Mark 8 flash memory.  Since getting and sending files to flash is done with Kermit, you can use the QSR Kermit session to do this.

This is done by creating a text file (in Notepad or WordPad) containing the necessary Kermit commands to retrieve the file above. 

1. Start Notepad or WordPad
2. Start a new file in a temporary directory
3. Type the following lines in the file

REM LOGIN RAIS
GET FILELIST.FDC

4. Save the file to command{#}.ksc (where # is a number 0 - 9)
5. Copy this file to c:\aws\k95\port{#} (where # is the port number of the direct connect session

Within a second of copying the command#.ksc file, Kermit will execute the commands in the file.  In this example, you should see a FILELIST.FDC file in the port directory.

You can also use this to get the database save files and send files too.  The command#.ksc will automatically get deleted once the Kermit session completes it.  If you wish to retain it, be sure to make a copy prior to copying it to the port directory.