Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (S)
Guardian Procedure Calls Reference Manual—522629-013
14-24
SEGMENT_DEALLOCATE_ Procedure
segment-id input
INT:value
specifies the segment ID of the segment to be deallocated. The segment ID was
assigned by the program in the call to SEGMENT_ALLOCATE_ that allocated the
segment.
flags input
INT:value
specifies whether dirty pages must be written to the swap file. A dirty page is a
page in memory that has been updated but not written to the swap file. Valid
values are:
<0:14> Reserved (specify 0)
<15> 1 Indicates that dirty pages in memory are not to be written to the swap
file.
0 Indicates that dirty pages in memory are to be written to the swap file.
This parameter is ignored if the swap space was allocated using the Kernel-
Managed Swap Facility (KMSF).
The default is 0.
error-detail output
INT .EXT:ref:1
returns additional information associated with some errors. See
error for details.
If
error is 4, error-detail returns one of the following values:
1
segment-id is out of range.
2
segment-id is in range but not allocated by the caller.
3 Segment is currently in use by the system. It might be in this state
because an outstanding nowait I/O operation using a buffer within the
segment has not been completed by a call to AWAITIOX.
30 No message-system control blocks are available.
Considerations
•
flags parameter
If the swap file associated with an extended data segment is neither a temporary
file nor managed by the Kernel-Managed Swap Facility (KMSF), all of the modified
pages of the segment are written to the file before it is closed by the last process
using it. This is also true for a swap file that was created as a temporary file but
was later renamed. (A program might use this method to keep its temporary file.)
However, if the extended segment is large and if there are a large number of