27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

13. The STABLE <strong>and</strong> EXCLUSIVE modes cannot be used in a mixed CSE<br />

complex when any of the systems are at a release earlier than <strong>VM</strong>/ESA ®<br />

Release 1.1.<br />

14. Messages are given to the user if:<br />

a. A WRITE link exists to the requested disk or<br />

b. A READ link exists to the disk <strong>and</strong> you are linking with mode WR, M, MR,<br />

or MW.<br />

No messages are given if no other links exist, or a READ link exists, <strong>and</strong> you<br />

are linking with mode R or RR.<br />

15. LINK response #2 is issued when <strong>CP</strong> does the link. If you issue the LINK<br />

comm<strong>and</strong> from CMS mode then no response is issued. If you issue LINK from<br />

<strong>CP</strong> READ mode, response #2 is issued. Also, if you issue #<strong>CP</strong> LINK, from<br />

either mode, response #2 is issued.<br />

16. An informational response is not always generated after a read link is<br />

established.<br />

17. LINK is used to obtain access directly to another user’s minidisk, or to obtain<br />

access indirectly, through linking to another user’s LINK or MDISK directory<br />

statement (LINKS to LINKS). Up to 50 of these indirect links (LINK<br />

indirections) are allowed. For example:<br />

USER0<br />

MDISK 393 3390 1 10 USRVOL ALL ALL ALL<br />

USER1<br />

LINK USER0 393 393 RR<br />

USER2<br />

LINK USER1 393 393 RR<br />

USER3<br />

LINK USER2 393 393 RR<br />

Since USER1 has had to first access the 393 minidisk through a direct link to<br />

USER0, USER2’s link to the 393 minidisk is considered an indirect link.<br />

USER3’s link to the 393 minidisk through USER2 is thus also an indirect link.<br />

Up to 50 of these indirect links are allowed before the following message is<br />

issued:<br />

H<strong>CP</strong>109E<br />

userid vdev not linked; excessive LINK indirections<br />

Note: This limit of 50 indirect links includes the original link. (In the example,<br />

USER1 to USER0.)<br />

18. State change interrupts will not be reflected to guests who dynamically link to<br />

any full-pack minidisk. To receive state change interrupts for full-pack<br />

minidisks, a static link should be defined in the user directory followed by the<br />

DASDOPT statement specifying DEVCTL or SYSCTL level of control.<br />

19. The link allowed by the LINK comm<strong>and</strong> to the vdev1 device belonging to<br />

userid is summarized in the tables that follow.<br />

Table 11. Linking to a Device in READ Mode<br />

Link<br />

Mode You<br />

Entered<br />

R No<br />

Yes<br />

Yes<br />

Yes<br />

READ Password<br />

Specified in the<br />

System Directory?<br />

Any Other Links to this Device? Link Type You Will<br />

Establish<br />

Not applicable<br />

No<br />

Yes—READ, stable READ<br />

Yes—WRITE, stable WRITE,<br />

exclusive (READ or WRITE)<br />

None<br />

READ<br />

READ<br />

None<br />

LINK<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 513

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!