Application programming for a user-maintained data table

CICS® handles a user-maintained data table and its source data set as separate entities. When loading is complete, all file control commands that access the filename are performed only on the data table.

There are some restrictions on which commands and options can be used. There are also some exceptional conditions that are unique to user-maintained data tables. These restrictions and conditions are described below.

The following commands are not supported; they return the INVREQ condition and a value of 44 in the EIBRESP2 field:

The following commands are supported (using cross-memory services for remote accesses):

The following commands are supported (using function shipping for remote requests):

Using a user-maintained data table during loading

A user-maintained data table can be accessed only by the FOR during loading. All remote requests are function shipped to the FOR, which processes them in the same way as for a local request described below.

While a user-maintained data table is being loaded, you can use only non-update read requests with precise keys. If the record has already been loaded, processing the request is handled in the normal way. If the record has not yet been loaded, the record is read from the source data set and submitted to the user exit XDTRD (if activated):

The LOADING condition is returned for other requests that would have been valid had loading been complete.

Related concepts
Application programming for data tables
Application programming for a CICS-maintained data table
Use of cross-memory services for shared data tables
Differences between function shipping and cross-memory services
Differences between shared data tables services and VSAM
[[ Contents Previous Page | Next Page Index ]]