The CMS ACCESS command, takes a /extension argument for making a disk a read-only extension of another.
I've never understood this, and have only used it when I wish to make a disk r/o. I certainly does not work for making a disk appear elsewhere in the CMS search order, which is what I would
On 6/28/07, Ian S. Worthington [EMAIL PROTECTED] wrote:
I've never understood this, and have only used it when I wish to make a disk
r/o. I certainly does not work for making a disk appear elsewhere in the
CMS search order, which is what I would really like it to do (when I have to
squeeze a
@LISTSERV.UARK.EDU
Subject: Re: ACCESS /extension
On 6/28/07, Ian S. Worthington [EMAIL PROTECTED] wrote:
I've never understood this, and have only used it when I wish to make a disk
r/o. I certainly does not work for making a disk appear elsewhere in the
CMS search order, which
When CMS is searching for something executable, it does not search
extensions before intervening disks.
However, you could EXECLOAD your exec - that will find it according to
the extension rules. Not maximally convenient, I know...
Ray Mansell
Ian S. Worthington wrote:
Hmmm. That's what
/servlet/pbi.wss?CTY=US
http://www.vm.ibm.com/library/
http://www.vm.ibm.com/pubs/redbooks/
To answer your question about the access extension and search order more
directly, read:
z/VM: CMS User's Guide (SC24-6137), Chapter 5, How File Mode Letters
Are Used (which explains extensions
