Have you tried VPUT / VGET to the PROFILE pool instead of the
application or shared pool? Just asking.
I wouldn't recommend it. Unlike the SHARED pool (which is dynamically
created and deleted during ISPF sessions), the PROFILE pool is kept
'forever'; i.e. it's saved on disk. And just like every other data set that
gets saved on disk, it can run out of space. In addition, each individual
PROFILE member has a fixed size (something like 64K). If this size is
exceeded, nasty things happen.
"VPUT PROFILE" should be used as sparingly as possible, and generally only
used when a variable needs to be available for use at some point in the
future (e.g. tomorrow or next week etc). To pass variables between programs,
I'd recommend using the SHARED pool or perhaps creating a temporary ISPF
table that other programs can read to find the values they need.
HTH,
Dave Salt
SimpList(tm) - The easiest, most powerful way to surf a mainframe!
http://www.mackinney.com/products/SIM/simplist.htm
_________________________________________________________________
Enter the "Telus Mobility Xbox a Day" contest for your chance to WIN! Telus
Mobility is giving away an Microsoft Xbox® 360 every day from November 20 to
December 31, 2006! Just download Windows Live (MSN) Messenger to your
IM-capable TELUS mobile phone, and you could be a winner!
http://www.telusmobility.com/msnxbox/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
