queue specification(1) — Commands
Digital
NAME
QUEUE SPECIFICATION − associates a data type identifier with a record queue
SYNOPSIS
QUEUE SPECIFICATION <record-queue-name>
RECORD <data-type-identifier> ;
[ { KEY IS | KEYS ARE } <key-field-name> [ ,... ] ]
END QUEUE SPECIFICATION;
PARAMETERS
•record-queue-name
An unqualified external identifier giving the name of a record queue. The record queue name has a maximum limit of 17 characters; characters beyond 17 are truncated. The record queue name specified in the record queue specification and the name of a record queue created by ACMSxp management must match for record queuing to work.
•data-type-identifier
An unqualified external identifier giving the name of the data type definition that specifies the format and layout of the record queue.
The fields in the record to which this data type identifier refers must match the field names specified in the KEY clause.
•key-field-name
A qualified internal identifier giving the name of a field in the record layout that can be a key field in the record queue.
oA key field name must be a uniquely defined field in the data type definition associated with the data type identifier specified in the RECORD clause.
oThe key field names must match the field names specified in DEQUEUE RECORD BY KEY, READ QUEUE FIRST RECORD BY KEY, and READ QUEUE NEXT RECORD BY KEY statements in the task definition.
There is a limit of eight keys for each record queue specification.
DESCRIPTION
Use the ENQUEUE RECORD, READ QUEUE or DEQUEUE RECORD statements to define the record queuing operation within task definitions. A record queue provides reliable local storage of data records between various operations of an ACMSxp business solution.
Each record queue specification contains a single data type identifier for association with a data type definition. Multiple clients and servers can use the same record queue.
The record queue is created as follows:
1.Compile the queue specification.
You can supply one or more record queue specifications either within an input source file for the compile operation, or with the -q option flag to the stdl compiler command. If you supply the record queue specification within the input source file (either directly or with the #INCLUDE and #CINCLUDE directive), the record queue specification must precede the data type definition for which it specifies a record queue.
2.Link the .o file from the STDL compilation and the ACMSxp shareable library libtps.so provided with the ACMSxp software.
This creates an executable file with the same name as the record queue specified in the enqueue and dequeue operations.
3.Supply the executable file as input on the acmsadmin create directive. Refer to the acmsadmin help for the syntax of the directive and the procedures to follow.
This creates the record queue managed entity and record queue database. The managed entity ACL attribute allows you to control access to the record queue. The record queue database stores the individual records that your application processes.
The ACMSxp record queue server must be running with your application server for your application to perform ENQUEUE RECORD, READ QUEUE, and DEQUEUE RECORD operations. And you cannot start the record queue server until you have created at least one record queue.
RELATED INFORMATION
Commands: acmsadmin(1)
Syntax: dequeue_record(1), enqueue_record(1), read_queue, task_definition(1)