Within the context of the 7526 DCT, an event describes an action that requires some response or servicing by the DCT. Usually, events are serviced by initiating a transaction program.
An example of an event being initiated is an operator pressing a function key or scanning a badge.
Any of the following DCT devices can generate an event:
File 0 may have up to 65 records (0-64), depending on the function specified (7525 compatibility or enhanced mode), containing entries that determine basic terminal operating characteristics and transaction programs.
Each record must be terminated by a record separator (RS). When the last record is defined which is not a No Operation (NO-OP) transaction, the remainder of the file (composed entirely of NO-OP transactions) need not be supplied by the terminal controller. Up to this point, however, a NO-OP command code must be supplied for all events that are ignored.
Note:
Initialization of File 0 must specify the total number of bytes for the entire file with all the NO-OPs included.l.The following table describes the organization of file 0.
Table 4. File 0 Organization
+===========+======================+======================+==================+ | Record | Description | Function ID, 7525 | Function ID, | | Number(s) | | Compatibility Mode | Enhanced Mode | +===========+======================+======================+==================+ | 0 | General Parameters | N/A | N/A | +-----------+----------------------+----------------------+------------------+ | 1-28 | Programs 1-28 | 0-27 Dec | 01-1C Hex | | | (F1-F28) | | | +-----------+----------------------+----------------------+------------------+ | 29 | Badge Initiated | 30 Dec | 1D Hex | | | Program | | | +-----------+----------------------+----------------------+------------------+ | 30 | Fast Clock Program | 29 Dec | 1E Hex | +-----------+----------------------+----------------------+------------------+ | 31-42 | PF Key-Initiated | N/A | 1F-2A Hex | | | Transactions | | | | | (Not accessible by a | | | | | physical key stroke) | | | +-----------+----------------------+----------------------+------------------+ | 43-54 | Shifted PF | N/A | 2B-36 Hex | | | Key-Initiated | | | | | Transactions | | | | | (Not accessible by a | | | | | physical key stroke) | | | +-----------+----------------------+----------------------+------------------+ | 55-56 | RS-232 serial ports | N/A | 37-38 Hex | | | 1 and 2-Initiated | | | | | (initiated by | | | | | incoming data on | | | | | optional serial | | | | | ports) | | | +-----------+----------------------+----------------------+------------------+ | 57-64 | DI Initiated | N/A | 39-40 Hex | | | Transactions | | | +-----------+----------------------+----------------------+------------------+ | N/A | Date/Time | 28 Dec | 79 Hex | +-----------+----------------------+----------------------+------------------+ | N/A | Command D | 31/81 Dec | FC Hex | +-----------+----------------------+----------------------+------------------+
Notes:
- In the 7525 Compatibility mode, this table indicates function IDs of buffered transactions on the 7526 DCT. For the Enhanced mode a B in the byte preceding the function ID indicates buffered.
- Interactive transactions (7525 compatibility mode) add "50" to function ID. The 7526 DCT places the letter I in the byte preceding the function ID for enhanced mode.
- Records 31-56 require sending :9
if DI initiated transaction (records 57-64) are to be active. - DI initiated transactions are not active in the 7526 compatibility mode.
- When using validation on data input, remember that Files 2-7 are always located in the 7526 memory, and the files A&mdash.Z, and a&mdash.z are always located remotely, on the terminal controller.