On Wed, 13 Sep 2006 15:56:12 -0400 Michael Donovan said: >EXECLOAD first determines what type of EXEC or XEDITmacro is being loaded. >If the object being loaded is REXX or "alternate" (read: compiled REXX), >then storage to load the object is obtained as LOC=ANY. If your virtual >machine is larger than 16M and there is available storage above 16M, the >object will be loaded there. If the object being loaded is EXEC-1 or >EXEC-2, then storage to load the object is obtained LOC=BELOW and the >object will reside below the 16M line. There is no user control of this >other than setting the size of your virtual machine.
Which is unfortunate that the user has no control. EXECLOAD can also load files into memory, but unless the file starts with /*, it is loaded below the 16M line. Prior to VDISK, it could be an easy file in memory function. I'll also add one of my favorite features of EXECLOAD is that the resulting execname doesn't have to be a valid CMS filename. For example, if you had an exec named HELP EXEC, you could do EXECLOAD HELP EXEC * ? EXEC and typing ? at the ready prompt will invoke the HELP exec. Try that on someone some time. > >Mike Donovan > /ahw
