-----------------------<snip>-------------------------
Ca. 1991, STORAGE did not allow disabled callers at all (this was changed
in SP 4.3.0 to allow STORAGE to be called disabled for common storage
subpools). So your only choice would have been GETMAIN
BRANCH=(YES,GLOBAL).
IGVVSM31 (the first GETMAIN module, not counting the glue routine)
checks the PSW for being disabled, but does not check super bits or locks.
The second GETMAIN module, IGVSMVRT does not (and never did) check any
such
thing. There is nothing (and never was) in VSM that checks super bits.
Since you called GETMAIN illegally disabled, when IGVVSM31 released
the VSMFIX lock, the SETLOCK RELEASE would have enabled. If nothing
else bad happened in the meantime due to being unexpectedly enabled, a
subsequent GETMAIN or FREEMAIN with BRANCH=(YES,GLOBAL) would get a
B78-40 abend due to being enabled. Setting the IOS super bit avoided
these unpleasantries, since then the SETLOCK RELEASE for the
VSMFIX lock did not enable.
-----------------------<unsnip>------------------------
Jim, now I'm confused. What are the "acceptable" methods of obtaining
storage while
"legally" disabled? One of the programs I use requires the use of a
rather large and
complex I/O Appendage, using start/stop mode terminals via a very old,
and reliable,
3705 controller running 270x emulation.
Don't even think of asking why. <G>
----------------------------------------------------------------------
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
