pos-D100.htm

SYSTEM INFRASTRUCTURE
This document describes the infrastructure used to run the POS-2200 software. It covers file folders, shortcuts, data files, backups, etc.

SYSTEM INSTALATION

POS-2200 runs as a Microsoft Windows application. It runs 32 bit code, is totally compliant with all Windows rules, and is very well behaved.

The system does NOT, however, use a Windows install procedure. Rather the software and data is designed to be installed in a simple directory structure and is executed by making a shortcut to the primary program.

This approach means that the system is very easy to backup, to execute, to move, and to manage. There is no concern about lost DLL's, left over registery entries, unexpected Windows interference and all the other irritants that plague too many Windows applications.

FILE FOLDERS

There are two common organizations for an POS-2200 installation. The first places virtually all data files and executable programs in a single folder. That folder is typically located at the root of the drive where it resides.

The second organization, and the one now recommended, uses a master folder with two folders inside. The first inner folder contains all of the data, the second contains the executable programs.

The advantage of the second organization is that it offers a simply way to control versions of the software. By simply renaming folders, a newer or older version of the software can be run agains the same data sets.

The recommended structure is: 
   POS-2200       root level folder
      POS-DATA      folder for all data files
      POS-SYS       folder for all executable programs and DLL's


DATABASE ID (System ID)

All POS-2200 data files are prefixed with a three character database identifier. This is usually your store's initials. The ID is created by MMCC when your system is built. Examples include: The database ID is the first thing asked when you load the software. When you enter the ID and tab, or tap enter, or click log in, the software looks for the database using the 3 byte prefix. If the system configuration file is found the software begins to initialize using that ID as the prefix for all files.

Note that you can store the database ID in a port's INI file (described below). If you do that the software will pre-load it on the screen and you don't have to remember or type it.

BACKUP PROCEDURES

Making frequent backups of your data and system is ESSENTIAL. Do NOT let it slide!

Keeping the entire system in one or two folders makes backups simple. The easiest approach is to just burn a CD, or DVD, of the master folder. That gets all of the data and all of the programs.

Some clients opt to use more universal backups such as tapes, off site services, secondary servers and other products or methods. That's great and should definitely considered as a master backup, but MMCC recommends using the CD or DVD burning method.

If you use some other backup method or product, be sure you understand how it works. There can be issues:
The advantage of a CD or DVD is that the backup is a total image. Everything is there and requires no special recovery software to be read. You can send the backup CD to MMCC, for example, where it can be loaded to a testing computer and used to diagnose problems or to test new software features.

CD's and DVD's also allow an infinite number of backup generations. Burn the CD, write the date and time on it, and put it in storage. The real benefit of using a CD is that the files are immediately usable. If you need to check the actual data from six months or six years ago you just find the CD for that date and use it.

In some cases you can read the data directly from the CD. In most cases you would drag and drop the entire folder onto another machine and run the software there. It's like you were in a time machine! This is frequently used for testing and for support. A client will send a CD to MMCC where the data will be loaded to a testing computer to replicate the exact conditions from another time.

GOTCHA!       The software that comes with most CD drives usually has a "backup" option. This is a solution like the ones mentioned above. Typically this produces a managed, compressed backup file. The backup CD CANNOT be easliy moved to another system. You have to use the same software that burned the backup CD to extract the backup onto another computer.

MMCC recomends AGAINST using the CD drive software's "backup" option. It's much better to just plain burn the data to CD.

If your database grows to the point of filling one CD, you can split the burn manually to use two or more CD's. It's a bit of a pain, but the result is very effective. A better solution would be to change to a DVD burner, which holds several times the amount of a CD. External CD and DVD drives plug into a USB port. They are cheap and easy to use and can easily be moved from one computer to another.

In summary, make a backup by simply copying the entire folder structure to a CD.

(MMCC does not recommend using re-writable CD's or DVD's. These were once a significant cost saving measure when blank CD's were expensive. But today CD's are cheap. Re-writables have a finite life and it's sometimes not easy to tell when one is worn out. You may make a backup only to find later that it won't read!)

NETWORK IMPLEMENTATION

POS-2200 is fully network compliant. It will run on most Windows network implementations. With additional runtime support software the system can be run in a number of client server scenarios, even across the internet.

GOTCHA! Windows supports the concept of "named drives". That is, you can locate files, folders and programs using something like "\\SERVER01\c:\folder\file". Although this works, it has been shown to cause some unpredictable results in certain cases. Mapped drive letters seem to work better (more below).

The best way to configure your network is create a "mapped drive letter" on each work station. Generally you create a mapped drive like this. By using this procedure, the workstation will now have a drive letter that points to the POS-2200 main folder. MMCC typically uses drive "P:". Each time the workstation is started, that drive letter will be connected to the server.

DESKTOP SHORTCUT

The preferred way to run POS-2200 is to make a desktop "shortcut" on each workstation where the system is to be run.

Before making the shortcut, you should create a "permanently mapped drive letter" on each work station as described above.

The easy way to create the shortcut is to explore (browse) to the POS-2200 startup program and work from there. Follow this procedure: You've now made a desktop icon to run the POS-2200 system.

You can close your windows explorer window BUT YOU'RE NOT DONE...

Now you need to change a few properties on the shortcut you just created. RIGHT CLICK on the desktop shortcut and select PROPERTIES from the menu. Change the following: Now you're almost ready to run. You just have to make a port INI as named in the target line. That's described below.

PORT INI FILES

The shortcut shown above names a port INI file to be used for the port. This file identifies the specific port. That's important. All transactions are time, user and port stamped. Transactions are also stored in the daily transaction file based on port number.

        Each port needs that unique number.

You can store an INI file for every port in the data folder. These files are typically named with your system prefix and the port's number: 
    HSP-P01.ini
    HSP-P02.ini
    HSP-P03.ini
... etc
 The INI files are all identical except that the port number is unique. The file contents are: ---> 
[environment]
PLB_TERM=ansi
PLB_SYSTEM={path to software i.e. P:\POS-2200\POS-sys}
PLB_PATH={path to other software i.e. P:\POS-2200\POD-sys}
PLBWIN_ICON={icon file or bitmap}
[shop-sys]
shop_sys=BCM
shop_port=02
shop_supervisor=S
shop_filepath=[
shop_histpath=[
shop_histdrive=[
shop_picpath=[
shop_picdrive=[
shop_diag=N
Note the following:

USER LOGIN

The POS-2200 security system is a standard part of the system but you are not required to use it. When the system is first installed there are no users defined. When you run the software it will ask for a "Database ID". That's the three byte code that identifies all of your data files.

When you enter the ID, the software will look at the security files to determine if you have turned on the feature. If security is not turned on the program loads and gives you the first menu.

If security has been turned on you will be prompted for a User ID. Every user must have a User ID.

Users are NOT required to have a password. When you set up a user they have no password and can log in with just their User ID. On the menu you'll find a button for "Change PW". The user is responsible for his own password.

Some company policies require a new user to be given an initial password. If so, after setting up the new user the administrator would just log in as that user and change the password.

INDEX FILES

All POS-2200 data is stored in flat text files with the file extension of .TXT. Most files have one or more associated "index" files that have an extension of .ISI. That means that files are at generally paired such as: 
HSP-HC00.TXT       data file
HSP-HC00.ISI       index file
Some files have multiple indexes such as: 
HSP-AL00.TXT       data file
HSP-AL00.ISI       primary index file
HSP-AA00.ISI       secondary index file
HSP-AC00.ISI       secondary index file
HSP-AP00.ISI       secondary index file
The TXT files are the most important files. That's where your data is. The index files can be recreated at any time from the txt files.

The index files are self balancing and almost never need attention. On the other hand, hardware issues have been known to damage index files. Generally the software will just keep right on working unless you access the specific damaged record. If needed, an index procedure is available in the files menu and can be used to re-create any index file.

NOTE: If you think that you need to rebuild an index it is best to talk to MMCC first. We want to know why the re-index is needed.