Data areas & message queues

A data area stores a small piece of data accessible through IBM i interfaces. Applications use it for configuration, control information, or legacy shared values. It differs from a queue because it represents a current value rather than a sequence of work entries.

Define who may read or change it, its exact layout, and whether readers cache it. For structured or transactional state with history and queries, a database table is often easier to govern and evolve.

The local data area is associated with a job and accessed using its special interface, rather than behaving like an ordinary named shared *DTAARA object. It is often used by legacy code to carry job-specific parameters or control values.

Do not expect unrelated jobs to observe the same local data area. Explicitly pass required context across submission boundaries and verify the relevant inheritance rules. For a new interface, typed parameters or a documented request record usually make dependencies clearer.

DSPDTAARA displays a data area, RTVDTAARA retrieves data into CL variables, and CHGDTAARA changes values. Other interfaces, including RPG operations and APIs, can access data areas with their own locking conventions.

Treat its layout as a contract. A change to offsets, length, or numeric representation can break old programs. Keep configuration changes auditable, and do not assume a read-modify-write sequence is atomic merely because the storage object is small.

Protect the entire read-modify-write critical section using the appropriate data-area locking protocol followed by reliable release. Without that protection, two jobs can read the same value and both write the same incremented result.

For new designs, consider a database identity, sequence, or transactional row update that better expresses the requirement. Define crash recovery and whether gaps are acceptable. A requirement for unique IDs is different from a requirement for gapless legal document numbering.

A message queue supports IBM i messages with types, identifiers, routing, and potentially replies. It is suited to operational and program messaging. A data queue transports application entries in a producer-consumer design.

Choose based on semantics. An operator inquiry belongs in a message workflow; a high-volume work stream needs an explicit transport and processing contract. Neither object automatically substitutes for a full transactional business ledger.

A shared switch can be read at different times or cached by different jobs. Changing it may cause some requests to use old behavior and others new behavior while a single business operation is still in progress.

Define when configuration is sampled and record its version with the run or request. For incompatible schema or interface changes, coordinate deployment rather than hoping a flag prevents mixed versions. Test a flag change during a long-running batch and specify the expected behavior.