Use the NOLINK record to indicate which directory links are not to be mapped by CA VM:Director by identifying the target user ID and minidisk of a directory link to skip.
NOLINK userid [vaddr]
NOLINK is defined in the DASD CONFIG file.
Specifies a user ID that owns a frequently linked minidisk whose directory links you do not want mapped by CA VM:Director.
Specifies the virtual address of a specific minidisk owned by userid. If the virtual address is not specified, then directory links to all minidisks owned by the specified user ID are not mapped.
Not mapping directory links that are common to most user IDs (such as the CMS S‑ and Y‑disk links) reduces storage and processing overhead.
During CA VM:Director initialization, a table is created in virtual memory that is used to map the LINK statements from all directory entries. Each entry in this table represents a single LINK statement and is currently 40 bytes in length. A site with 5,000 user IDs, where each user ID has links to the CMS S‑ and Y‑disks, saves 400K of CA VM:Director virtual storage by not mapping these two disks.
Users who own minidisks that are specified on a NOLINK record cannot use Selection 8 on the User Selection Menu (Review or Remove Links By Other Users) to act on those directory links.
If you use the CA VM:Director ASSIGN, CHANGE, or TRANSFER command to change a user ID or minidisk that also appears on a NOLINK record, the directory links to that user’s minidisks are not automatically updated to refer to the new user ID.
Example
Add the following records to the DASD CONFIG file to prevent the links to MAINT’s 190 and 19E minidisks from being mapped:
NOLINK MAINT 190 NOLINK MAINT 19E
|
Copyright © 2014 CA.
All rights reserved.
|
|