7526 DCT Reference

Transaction Programming

Transaction programs define the sequence of operator prompts, data input fields, data verification, control of outputs (beeper, indicators, DO points), and logging of data which are to occur as part of a data collection process. For example, one transaction program may handle a operator clocking-in, while another transaction program handles tracking of work coming into the area.

The transaction programs are loaded into the terminal as individual records in RAM file-0, and also may be sent for immediate execution with host command "D". The loaded transaction programs are initiated by events at the terminal:

Pressing of a function key while the terminal is in the idle state. Each function key is a separate event which may initiate a unique transaction program.
Reading of a bar code or magnetic stripe when the terminal is in the idle state. Upon entry to the transaction program, the data read to initiate the event is already present in user variable 0.
Note:
There are separate transaction programs for regular badge-initiated transactions and for transactions initiated during a fast-clocking period.
.
Changing the state of a digital input point. If the terminal is not idle when the DI point changes, the terminal executes the transaction associated with the point as soon as it returns to the idle state. Each of the 8 DI points may have a unique transaction program assigned to it. DI-initiated transactions are available in the enhanced mode only.

User Variables

Within the transaction programs, there are up to 999 user variables available for storage of data for future use. The 7526's configuration file is used to specify how many user variables are required, and the length of the user variables. User variables 0 through 4 are always 255 characters in length, and variables 5 to 998 may be specified with any length from 1 to 999 bytes. There is a limit of 65,535 bytes available for the aggregate size of user variables 1 through 998, including two (2) bytes of overhead associated with each variable defined.

Note:

With 7526 microcode level 1.01, there are always four (4) user variables.
All transaction programs have access to the user variables, and the variables retain their values between execution of the various transaction programs which may be loaded into the 7526. Thus, the variables may be used to pass data to subsequently-run transaction programs. For example, a transaction could be used for a operator to indicate that a new lot of sub-assemblies is now being used to assemble the product. The lot number could be stored in a user variable, and then used repeatedly as part of subsequent transactions where the operator collects data on which serial-numbered final products receive the sub-assembly with that lot number.
The data collection controller may also set the contents or read the contents of any user variable at any time, using host commands I and Q, respectively.
Note:
Command Q (Read Terminal User Variable) is only available on machines with microcode level 1.02 or higher.
Whenever an input command is executed, the data read is placed in user variable 0. From there, it may be copied to other user variables, passed as data to a Custom Function Routine, sent to the host, or otherwise processed.