Saving interim changes to a permanent data object

Window services allows you to save interim changes you make to a permanent object. You must have previously requested a scroll area for the object, however. You request a scroll area when you call CSRIDAC to gain access to the object. Window services saves changes by replacing blocks in the scroll area with corresponding changed blocks from a window. Saving changes in the scroll area does not alter the object on DASD.

After you have a view of the object and have made changes in the window, you can save those changes in the scroll area. To save changes in the scroll area, call CSRSCOT. For a description of the CSRSCOT parameters and return codes, see CSRSCOT — Save object changes in a scroll area.

To identify the object, you must supply an object identifier for object_id. The value supplied for object_id must be the same value CSRIDAC returned in object_id when you requested access to the object.

To identify the blocks in the object that you want to update, use offset and span. The values assigned to offset and span, together, define a contiguous string of blocks in the object:

The value assigned to offset specifies the relative block at which to start. An offset of 0 means the first block; an offset of 1 means the second block; an offset of 2 means the third block, and so forth.
The value assigned to span specifies the number of blocks to save. A span of 1 means one block; a span of 2 means two blocks, and so forth. A span of 0 has special meaning: it requests that window services save all changed blocks to which a window is mapped.

Window services replaces each block within the range specified by offset and span providing the block has changed and a window is mapped to the block.