Hmmm. That's what I was hoping for, but with EXECs. Maybe those are found differently. When my VM's available I'll test it again.
Thanks,
ian
...
------ Original Message ------
Received: Thu, 28 Jun 2007 03:49:07 PM BST
From: Rob van der Heij <[EMAIL PROTECTED]>
To: [email protected]
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 is what I would really like it to do (when I have to
> squeeze a disk in where there isn't a hole).
It does not affect LISTFILE for example, but it does silently take the
file from the R/O extension if it does not exist yet on the disk where
you asked for it.
Like this (showing a file does not exist on my A disk, but can be read
when J/A )
acc 100 j
DMSACC724I 100 replaces J (100)
DMSACP723I J (100) R/O
Ready; T=0.01/0.01 10:47:39
pipe < esasys history a | count bytes | cons
FPLDSR146E File "ESASYS HISTORY A1" does not exist
FPLSCA003I ... Issued from stage 1 of pipeline 1
FPLSCA001I ... Running "< esasys history a"
Ready(00146); T=0.01/0.01 10:47:42
acc 100 j/a
DMSACC724I 100 replaces J (100)
DMSACP723I J (100) R/O
Ready; T=0.01/0.01 10:48:10
pipe < esasys history a | count bytes | cons
399648
Ready; T=0.01/0.01 10:48:12
