Thanks. ok, what happens in the following two cases:
1) mdisks are accessed as previously mentioned. mdisk1 is A mdisk2 is B/A
I have the same program (module) on both A and B I want to run the module.
From which disk will the module be used?
2) I use the STATE/STATEW/ESTATE/ESTATEW. Same scenario as 1 above
Where will the program be found first and will the STATE command acknowledge/report
that I have the file on two mdisks?
Steve G.
| "Schuh, Richard" <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 09/12/2006 04:57 PM
|
To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: mdisk/extension search order question |
Be aware that not all commands search the search order in the same way. For example, if you have disks accessed as A and A/H, you will see that LISTFILE does not include the H disk when you
LIST * * A; however, in the commands TAPE DUMP * * A or COPYFILE * * A = = X, the files from the H disk will be included.
Regards,
Richard Schuh
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
> Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2006 8:27 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: mdisk/extension search order question
>
>
> H will be completely searched before going to I, which is the
> normal course of action. The I/H in this case forces R/o.
> -------------- Original message ----------------------
> From: Steve Gentry <[EMAIL PROTECTED]>
> > Hello. I've issued a Q DISK command and listed below is
> part of the
> > results:
> >
> > DSK4B0 4B0 H R/O 1625 3390 4096
> > DSK121 121 I/H R/O 900 3390 4096
> >
> > I issued a VMLINK command (could be ACCESS as well) to
> make the I disk an
> > extension of the H disk. What will the search order be?
> Will all of H
> > be searched first
> > and if file not found start searching the I disk or is the
> H and I disk
> > munged together
> > and searched concurrently?
> > Thanks,
> > Steve
> >
> Obsolescence is Just a Lack of Imagination
>
>
>
