Guardian Procedure Calls Reference Manual

SEGMENT_SEGID4
Invalid segment-id.
SEGMENT_SEGSIZE5
Invalid segment-size.
SEGMENT_NOSEGSPACE6
Unable to allocate segment space.
SEGMENT_NOPAGETABLE7
Unable to allocate segment page table space.
SEGMENT_SECURITY8
Security violation when attempting to share segment.
SEGMENT_INVALIDPIN9
pin does not exist.
SEGMENT_NOTOWNED10
pin does not have the segment allocated.
SEGMENT_INCEST11
Caller is trying to share segment with self.
SEGMENT_UNSHARABLE12
One of three conditions: (1) The requested segment is a shared selectable segment, but the allocated segment
is a flat segment. (2) The requested segment is a shared flat segment, but the allocated segment is a selectable
segment. (3) The segment is being resized.
SEGMENT_ALREADYALLOC13
A segment with ID segment-id is already allocated by this process.
SEGMENT_NOPST14
Unable to allocate process segment table (PST).
SEGMENT_RANGE_ALLOCD15
Part or all of the requested address range has already been allocated. This error is returned if bit 15 of the
alloc-options parameter is set to 1 and a flat segment cannot be allocated. This error can also occur
when bit 15 is not set, but either a flat segment cannot be shared due to address-range overlap with another
segment or a flat segment cannot be allocated as there is no unallocated address range large enough to hold
the requested size. This error is returned only on native processors.
SEGMENT_BASE_ALIGN16
The caller has specified the base-address for a 64-bit segment that does not satisfy the alignment
requirements. Those requirements are described in SEGMENT_GET_MIN_ALIGN_ Procedure (page 1282).
Considerations
NOTE: There are additional considerations for privileged callers.
• Preventing automatic temporary file purge
SEGMENT_ALLOCATE[64]_ opens the swap file for read/write/protected access. A process
can prevent the automatic file purge of a temporary swap file by opening the file for
read-only/shared access before the segment is deallocated.
• Nonexisting temporary swap file
A caller requesting allocation of a temporary swap file can obtain the actual file name used
by making a subsequent call to the SEGMENT_GETINFOSTRUCT_ Procedure (page 1291) or
SEGMENT_GETINFO[64]_ Procedures (Superseded by SEGMENT_GETINFOSTRUCT_
Procedure) (page 1287).
1268 Guardian Procedure Calls (S)