If it's simple fast access, perhaps something as easy as virtual disk in 
storage would work?  They format INSTANTLY.  I/O is awesome. 

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



"Alan Altmark" <[EMAIL PROTECTED]> 

Sent by: "VM/ESA and z/VM Discussions" <[email protected]>
01/13/2006 09:21 AM
Please respond to
"VM/ESA and z/VM Discussions" <[email protected]>



To
[email protected]
cc

Subject
Re: VM maclib reference






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




 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited.

Reply via email to