If anybody's interested (that includes you, Steve...:-) I have a set of
HLL-callable Assembler routines for working with VM dataspaces. Free for
th asking.....
DJ
Alan Altmark wrote:
On Friday, 01/13/2006 at 08:16 EST, Steve Gentry
<[EMAIL PROTECTED]> wrote:
They will be updated as the program runs. When PGMA starts, all tables
are
empty (null, whatever). As the program runs, it starts filling up the
table
starting at the
beginning of the table. Data is continually added(or updated) to the
table
during the life of PGMA.
Can I correctly assumed that Shared Segments (or Saved Segments or NSS
or DCSS)
is not an option then?
An exclusive write no-data-saved (EN) DCSS will work. But if you need
more variability in the size of the segment (i.e. some users need bigger
segments) or its address, then I suggest looking at VM Dataspaces. You
will need to learn about access registers and the use of the ADRSPACE
macro in an XC mode virtual machine. See the CP Programming Services
book. (If the data needs to be written to disk, then the CP MAPMDISK
macro is available.)
I now understand that your table is simply a cache for data you generate
dynamically rather that static data tables resident in the program. That's
a horse of a different color.
Alan Altmark
z/VM Development
IBM Endicott
