CA Dynam for VSE User Guide

Dynamic File Sorting
CA SRAM normally uses the upper unused portion of the partition to allocate
storage for each task and its own overhead. If this procedure conflicts with the
user program (for example, PL/I and RPG II also dynamically use partition
storage), a CA SRAM SRTCORE call must be issued. CA Dynam/FI obtains the
necessary storage from the partition GETVIS area and issues the SRTCORE call
based on the size you have indicated for the specific sorting task (using
SRTCORE on the xLBL statement) and/or what you have requested as a total
amount of storage (using SORTCORE on the SET statement).
Note that the SET SORTCORE statement indicates the total amount of storage
you want CA Dynam/FI to request for all sorting tasks. The SRTCORE
parameter on the xLBL statement indicates the amount of storage requested
for a particular task.
For more information on the CA Dynam/FI SET statement, see Controlling
System Actions. The CA SRAM documentation set provides instructions for
calculating storage sizes.
Examples
Sort the file TAPEOUT on output. The sort key record shows that the sorted
field starts at the first position, has a length of 20, is character data, and will
be sorted in descending order. The file name of the work file is WORK1 and is
on logical unit SYS040. 40000 bytes of GETVIS storage have been requested
for the sort and its overhead.
// TLBL TAPEOUT,'OUTPUT.FILE',,SORTOUT=(1,20,C,D), X
SORTWRK=(WORK1,SYS040),SRTCORE=40000
If a cataloged sort key name (KEY1) and sort work file defaults (WORK1 on
SYS001) were used, and no SRTCORE call were needed, the above example
could be rewritten as:
// TLBL TAPEOUT,'OUTPUT.FILE',,SORTOUT=KEY1
Sort the file FILEOUT on output. Since PL1001 is a user-written PL/I program,
a SET SORTCORE statement precedes execution of the program. 50000 bytes
of storage have been requested for all sorting tasks in this job and 30000
bytes have been requested for the task for FILEOUT.
Chapter 6: Controlling File Independence 6–9