GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-23
Extended Segments for Trace Files
10007 maxDCBpool or previous pools too large
10008 maxLDCBpool or previous pools too large
10009 maxLINEpool or previous pools too large
10010 maxPCBpool or previous pools too large
10011 Sum of all max***pools are > 16777216d
10012 Sum of final EXT. MEM size > 16777216d
For example, if the TCB and IOCB pool sizes have been calculated, and the total
requirement for the TCB and IOCB pools, the extended buffer pool, and the extended
message pool exceeds 16,777,216 bytes, the following error message is sent to the home
terminal:
10003 maxIOCBpool or previous pools too large
If the total calculated for all the control block pools, the extended buffer pool, the
extended message pool, and the checkpoint buffer exceeds 16,777,216 bytes, error
message 10011 is sent to the home terminal. If the total calculated for all the areas to be
allocated in the extended segment exceeds 16,777,216 bytes, error message 10012 is
sent to the home terminal.
The configured control block pool sizes may be displayed by issuing the following SCF
command at the SCF prompt:
-> INFO PROCESS $GDSX-process-name, DETAIL
where is the name you gave to the GDSX process.
Extended Segments for Trace Files
When the trace facility is turned on in the primary GDSX process, TSCODE allocates an
extended segment with segment ID 1025, a default size of 64 pages, and the default file
name TRACEP under the default subvolume. The SCF TRACE command may be used
to specify a different file name, and the USER^OPEN^TRACE^FILE procedure may be
used to specify a different file size. (For other information regarding the trace facility,
see "Tracing GDSX" on page 2-76.)
When the trace facility is turned on in the backup process, TSCODE allocates an
extended segment with segment ID 1025, a default size of 64 pages, and the file name
TRACEB under the default subvolume.
If the specified trace file does not exist, the GDSX process creates and uses the file. If
the default subvolume already has a file with the name specified and the file has not
been opened by another process, the GDSX process opens the file. If the specified trace
file is in use by any other process, the GDSX process will not initiate the trace.
Memory Pools
Because the working stack images of tasks are swapped to and from an extended data
segment during I/O operations, I/O must be performed to and from global buffers. To
facilitate buffer allocation and deallocation, TSCODE provides users with two local
memory pools within the user data segment—the buffer pool and the message pool—
and two pools in an extended segment (by default, segment ID 1024)—the shared
extended pool and the private extended pool—along with procedures to allocate and