working storage

Place the high-activity data elements at the beginning of each group of the WORKING STORAGE SECTION variables (COBOL).

This means the LRUDs split memory into a list of persistent pages and a list of working storage pages.

Thus, the system releases the working storage pages for the data of a process and stack when the process exits.

When a process exits, the system releases all of its private working storage pages.

When a program is invoked, the WORKING-STORAGE associated with the program is allocated.

The working storage pages for shared memory regions are not released until the shared memory region is deleted.

When modified working storage pages need to be paged out (moved from memory to the disk), they are written to paging space.

After the call is executed the working storage will have either the values retrieved from the Server program or either an error message.

For the duration of the run unit, WORKING-STORAGE items persist in their last-used state.

TE01W01 is our working storage record, a temporary data area defined for a program.

Working storage pages are never written to a file system.

It only supports doing this on working storage memory, not persistent storage.

You want it to favor working storage.

A working storage page is never marked as non-computational.

Working storage pages are pages that contain volatile data (in other words, data that is not preserved across a reboot).

So, in the above example, there are 188426 working storage pages mapped into memory.

Listing 3 provides the global working storage that is accessible by all functions defined in this program.

Of those 188426 working storage pages, 133537 of them are pinned (that is, can't be paged out).

Mine plans; underground working; storage and final deposition in mine workings

Data names in WORKING -STORAGE initialised with VALUE Clause