QVS Software, Inc. - How to install QConnect on a 4690 Controller

Newsflash

QVS is Moving - On June 1, 2010, QVS will move to a new office location at 5950 Six Forks Road, Raleigh, NC 27609. The phone numbers stay the same as the main number is 919.676.1991. Click here for the release.

Main Menu

Home

Using Applied Software Maintenance (ASM) to install QCONNECT

The 4690 OS system provides the capability to install and track code modifications, features, etc and allow them to be distributed to other stores. QCONNECT can be installed on a 4690 controller via ASM.

Note: Installation of this ASM is not necessary if you intend to run IBM terminals using QCONNECT. Loading of those terminals occurs using imbedded code under 4690 OS.

Installing the QCONNECT ASM

Place the QCONNECT ASM diskette in drive A: of the 4690 OS Master Controller.

From a 4690 command prompt, type: a:install
When the program completes, go to the main 4690 menu screen and execute the following steps:

choose Installation and Updates (option 4)
choose Apply Software Maintenance (option 5)
Place an X by the QVS QCONNECT 7052/7450 option
choose Transfer Maintenance from Diskette (option 1)
When this operation completes, choose Activate Maintenance (option 2)
choose the accept option for the QVS QCONNECT 7052/7450 option (3)
Reboot machine when prompted.

Updating QCONNECT code which was loaded via the ASM

Most likely, some updates to the ASM code may have to be made. An easy way to do this is to copy each file to its proper directory and distribute the file if multiple controllers are used. You will probabbly update the following files:

adx_udt1:cdifile.000
adx_udt1:cdifile.xxx where xxx represents any specialized configuration files
adx_udt1:keymap.000
adx_udt1:keymap.xxx where xxx represents any specialized configuration files
adx_udt1:dynakey.000 needed only if a dynakey display is attached
adx_udt1:dynakey.xxx where xxx represents any specialized configuration files.
adx_udt1:load7452.bbk (updates, if needed)
adx_udt1:ncrload1.slf (updates, if needed)

When these files have been copied to the controller, their distribution characteristics should be modified from 1 (local) to 5 (compound). To do this, execute the following steps:

go to the main 4690 menu screen
choose File Utilities (option 3)
choose Distributed File Utilities (option 3)
choose Modify Distribution Type (option 3)
Type in file name to be modified. Example: adx_udt1:load7452.bbk
Choose Compound file, distribute at close (option 5)
Continue in this manner until all modified files have been converted to compound files.
If you have an Alternate Master Controller defined on your system, copy the following files from the Master Controller to the Alternate Master Controller: (These files are local files)

adx_udt1:term.ini
adx_udt1:group.ini
adx_udt1:groupdir.ini

continue to the next section

Please skip to the Setting Up Background Tasks section for further instructions

Copying QCONNECT code directly onto your Master Controller

There are two major ways to do this. It can be done manually or it can be done with an automated bat file available in .ZIP form from QVS

Copying using an automated copy

Obtain the most current copy of QINSTALB (copy file for 7452 installations) or QINSTALS (copy file for 7052 installations) from QVS.
Unzip the file onto a diskette.
Type: a:install
Follow on-screen instructions

Copying manually

In order to properly install QCONNECT on a 4690 Master controller, the following files must be copied to the specified directory:

adx_udt1:cdifile.000
adx_udt1:cdifile.xxx where xxx represents any specialized configuration files
adx_udt1:keymap.000
adx_udt1:keymap.xxx where xxx represents any specialized configuration files
adx_udt1:dynakey.000 needed only if a dynakey display is attached
adx_udt1:dynakey.xxx where xxx represents any specialized configuration files.
adx_udt1:load7452.bbk (745x only)
adx_udt1:ncrload1.slf (7052 only)
adx_udt1:groupdir.ini (745x only)
adx_udt1:group.ini (745x only)
adx_udt1:term.ini (745x only)
adx_udt1:loader.ini (7052 only)
adx_udt1:qldr7450.ini (745x only)
adx_upgm:qether.286
adx_upgm:qlanload.286 (7052 only)
adx_upgm:udv0.286
adx_upgm:qldr7450.286 (745x only)

Note 1: None of the xxxxx.ini files need to be modified unless you intend to load two different types of NCR terminals in the same store. If this is the case, please see the help document, How to Load More Than One BBK in a Store. This document can be found on the QVS web site (www.qvssoftware.com).

Note 2: Instructions for modification of KEYMAP.XXX, DYNAKEY.XXX, and CDIFILE.XXX can be found on other help files on the QVS web site (www.qvssoftware.com)

If you do not plan to attach an Alternate Master controller, please skip to the Setting Up Background Tasks section. If you install the QCONNECT code on a 4690 System that has Multiple Controllers (a Master AND and Alternate Master controller), you must also modify the file distribution type on some of the files you have copied. The distribution type should be changed from local to compound file, distribute at close. To do this, execute the following steps:

go to the main 4690 menu screen
choose File Utilities (option 3)
choose Distributed File Utilities (option 3)
choose Modify Distribution Type (option 3)
choose Type in file name. Example: adx_udt1:load7452.bbk
choose "Compound file, distribute at close (option 5) and hit Enter
The following list of files should have their distribution types modified:

adx_udt1:cdifile.000
adx_udt1:cdifile.xxx where xxx represents any specialized configuration files
adx_udt1:keymap.000
adx_udt1:keymap.xxx where xxx represents any specialized configuration files
adx_udt1:dynakey.000 needed only if a dynakey display is attached
adx_udt1:dynakey.xxx where xxx represents any specialized configuration files.
adx_udt1:load7452.bbk (if used)
adx_udt1:ncrload1.slf (if used)
adx_udt1:loader.ini
adx_upgm:qether.286
adx_upgm:qlanload.286
adx_upgm:udv0.286
adx_upgm:qldr7450.286
adx_udt1:qldr7450.ini

The following files should REMAIN local files:

adx_udt1:term.ini
adx_udt1:group.ini
adx_udt1:groupdir.ini

Copy these local files over to the Alternate Master Controller:

adx_udt1:term.ini
adx_udt1:group.ini
adx_udt1:groupdir.ini

go to the next section, Setting Up Background Tasks

Setting Up Background Tasks

If you are using the NCR 7052 series of terminals, go to the Setting Up to Load 7052 Terminals section. Otherwise, go to the Setting Up to Load 745x Terminals section.

Setting Up to Load 7052 Terminals

Make sure that the file, adx_idt1:ncrload1.slf, contains the latest code from QVS. Configure a background job to run only on the Master Controller. If you have an alternate controller, a similar background task should also be configured, but should not be configured to autostart. To do so, execute the following steps:

Go to the main 4690 menu screen
choose Installation and Update Aids (option 4)
choose Change Configuration Data (option 1)
choose Controller Configuration (option 2)
Using the enter key, step through the screens until you can choose configuration of the Master Controller
Place an X by the Background Application option
choose Define a Background Application
Type in for an initial message, Loader for 7052 Terminals
Tab to the next field (Program Name) and type, adx_upgm:qlanload.286
Tab to the next field (Parameter List) and type, adx_udt1:qlanload.ini
Page down and type Y in the following fields (all other fields should be "N"):

Start when Master
Start when Not Master

Press Enter
If the screen now allows you to choose another controller to configure, highlight the Alternate Master controller and hit Enter. Otherwise, skip to the Activate Controller Configuration section
Place an X by the Background Application option
choose Define a Background Application
Type in for an initial message, Loader for 7052 Terminals
Tab to the next field (Program Name) and type, adx_upgm:qlanload.286
Tab to the next field (Parameter List) and type, adx_udt1:qlanload.ini
Page down and type Y in the following fields (all other fields should be "N"):

Start when Master
Start when Not Master

Press Enter
Skip to the Activate Controller Configuration section

Note: The loader executes on the alternate controller only if it is manually started.

Setting Up to Load 745x Terminals

Make sure that the file, adx_idt1:load7452.bbk, contains the latest code from QVS. Configure a background job to run on the Master Controller. If you have an alternate controller, a similar background task should also be configured. To do so, execute the following steps:

Go to the main 4690 menu screen
choose Installation and Update Aids (option 4)
choose Change Configuration Data (option 1)
choose Controller Configuration (option 2)
Using the enter key, step through the screens until you can choose configuration of the Master Controller
Place an X by the Background Application option
choose Define a Background Application
Type in for an initial message, Loader for 745x Terminals
Tab to the next field (Program Name) and type, adx_upgm:qldr7450.286
Tab to the next field (Parameter List) and type, qldr7450.ini
Page down and type Y in the following fields (all other fields should be "N"):

Start when Master
Start when Not Master

Press Enter
If the screen now allows you to choose another controller to configure, highlight the Alternate Master controller and hit Enter. Otherwise, skip to the Activating Controller Configuration section
Place an X by the Background Application option
choose Define a Background Application
Type in for an initial message, Loader for 7052 Terminals
Tab to the next field (Program Name) and type, adx_upgm:qldr7450.286
Tab to the next field (Parameter List) and type, qldr7450.ini
Page down and type Y in the following fields (all other fields should be "N"):

Start when Master
Start when Not Master

Press Enter
Go to the next section, Activating Controller Configuration

Activating Controller Configuration

Press F3 several times until you return to the 4690 OS Main Menu
choose Installation and Update Aids (option 4)
choose Change Configuration Data (option 1)
choose Activate Configuration (option 4)
choose Controller Configuration (option 2)
Wait until processing completes without error, then reboot the controller(s)
Test to see if the terminal loads and runs correctly

Note: This completes the installation and configuration procedure for QCONNECT.

Verifying other 4690 parms are set correctly

The following items must be checked to verify their correct installation:

Ethernet must be chosen as the LAN type for TCC communications (Controller Configuration)
LAN terminal configuration must be run for the terminal numbers you intend to use (System Configuration, LAN configuration)
Ethernet protocol must use the automatic resume option (Controller Configuration, Controller Characteristics)
Each terminal ID you want to use for QCONNECT must be defined with the correct terminal application specified (Terminal Configuration, Load Definition)

Once any of the above configuration options are completed, those changes must be activated. Controller or System configuration changes require a Controller reboot in order to initiate the changes.

< Prev		Next >