CPACCESS
Authorization
Privilege Class: A
Purpose
Use CPACCESS to identify a CMS-formatted minidisk to CP and to make the files on that minidisk available to CP by establishing a file mode letter for the files. Before you can tell CP to link a minidisk, you must have the authority to access that minidisk. You do not have to actually link to or access the minidisk; you only need the capability to do so without specifying a password.
You can also do this by using the CP_ACCESS statement in the system configuration file. For more information about the CP_ACCESS Statement, see z/VM®: CP Planning and Administration.
Operands
- userid
- specifies the user ID of the owner of the minidisk that you want to make available to CP.
- vdev
- is the virtual device number of the specified user's minidisk, as defined in the user's entry in the system directory. The address can be any hexadecimal number between X'0000' and X'FFFF'.
- fm
- is the file mode letter that you want to assign to all files on the specified minidisk. You can specify any letter from A to Z.
- mode
- is the access mode. Valid modes are:
- ER
- Exclusive read-only access. CP establishes read access unless a user has an existing access to this disk. CP denies all requests for access to a disk with an existing exclusive mode.
- EW
- Exclusive write access. CP establishes write access unless a user has an existing access (any
mode) to the disk. CP denies all requests for access to a disk with an existing exclusive mode
access. Note: An EXCLUSIVE access (ER, EW) is a stable access with the added restriction that no one else has, or can get access to, the specified minidisk until the access is released.
- M
- Multiple-write access. CP establishes write access unless a user has an existing write, stable, or exclusive mode access to the disk.
- MR
- Multiple-write access. CP establishes write access unless a user has an existing write, stable, or exclusive mode access to the disk. If a previous write or stable access exists, CP establishes read-only access. If an exclusive mode access exists, access is denied.
- MW
- Multiple-write access. CP establishes write access in all cases except when a user has an existing stable or exclusive mode access to the disk.
- R
- Read-only access. CP establishes read access unless a user has an existing write or exclusive mode access to the disk.
- RR
- Read-only access. CP establishes read access unless a user has an existing exclusive mode access.
- SM
- Stable multiple access. CP establishes write access unless a user holds a write, a stable, or an exclusive mode access to this disk. CP denies all requests for write access to a disk with an existing SM mode access.
- SR
- Stable read-only access. CP establishes read access unless a user has an existing write or exclusive mode access to this disk. CP denies all requests for write access to a disk with an existing SR mode access. SR is the default.
- SW
- Stable write access. CP establishes write access unless a user has an existing access (any mode)
to this disk. CP denies all requests for write access to a disk with an existing SW mode
access.Note: A stable access means that the user holding the (SR, SW, or SM) access can be assured that the disk remains stable, unchanged by others, until the access is released.
- W
- Write access. CP establishes write access unless a user has an existing access (any mode) to the disk.
- WR
- Write access. CP establishes write access unless a user has an existing access (any mode) to the disk. If write access is denied, CP establishes read access unless another user has an existing exclusive mode access for the disk.
- ASYNChronous
- tells CP to
schedule the command and lets you enter other commands before the CPACCESS command completes. When
the CPACCESS command completes, CP displays a 1-line response, such as:
ASYNCHRONOUS is the default.CPACCESS request for userid's vdev in mode mode completed
- SYNChronous
- tells CP to process the command immediately and does not allow you to enter any other commands until the CPACCESS command completes.
Usage Notes
- Even though CP may establish write access to a minidisk (for example, by using the link mode MW), CP itself does not write to the minidisk.
- When you enter the CPACCESS command and specify a file mode letter that CP is using for another minidisk, CP releases the first minidisk and accesses the minidisk you specified.
- If the specified minidisk contains files that will be used frequently, you should either:
- Issue the CPCACHE command to cache each file into storage.
- Create a CPCACHE FILES file on the minidisk before you enter the CPACCESS command. The CPCACHE FILES file should contain the file names and file types of the frequently used files.
- Use the CPRELEASE command to release a disk that you have accessed using the CPACCESS command. For more information, see CPRELEASE.
- Many users can link to a minidisk. We strongly recommend that you do not use the CPACCESS command to identify a minidisk to CP when some other user has write access to that minidisk. After accessing the minidisk, CP creates in storage a directory of all the files on that minidisk. If someone updates a file on that minidisk, CP is no longer maintaining a current directory and the results can be unpredictable. If you need to update a file on a disk that CP is accessing, use the CPRELEASE command to release the disk before you update the file.
- CPACCESS accesses a minidisk for CP to read from. If you need to change a file on that disk, you must link and access the disk first. The size of the minidisk that can be accessed by the CPACCESS command is limited to 65520 cylinders.
- If your virtual machine has privilege class A or E and can access a CP-accessed minidisk in read mode, you can use the CPTYPE command to look at the contents of a file on that disk. You do not have to link to the disk; you only need to have the capability to do so without a password. For more information, see CPTYPE.
- If the volume that contains the minidisk is under cross-system link protection (SSI cluster or XLINK), interpretation of the access mode takes into account all use of the minidisk by users on those systems.
- The use of the stable and exclusive link modes (SR, SW, SM, ER, EW) is controlled by the LNKSTABL and LNKEXCLU options on the OPTION directory statement. For more information about the OPTION Directory Statement, see z/VM: CP Planning and Administration.
- If you have an ESM installed and the LINK command is controlled, the ESM will be queried to determine LINK authorization. For further information about linking restrictions, see LINK.
Responses
Response 1:
If you specify the SYNCHRONOUS operand, you see something like:
cpaccess oper1 06dc b sr synchronous
OPER1's 06DC accessed in mode B
Ready;
Response 2:
If you specify the ASYNCHRONOUS operand or you choose it as the default by specifying nothing,
you see something like:
cpaccess oper1 06dc b sr
CPACCESS request for mode B scheduled
Ready;
CPACCESS request for OPER1's 06DC in mode B completed
Messages
- HCP002E Invalid operand - operand
- HCP003E Invalid option - command contains extra option(s) starting with operand
- HCP007E Invalid userid - userid
- HCP046E DASD rdev offline
- HCP101E DASD vdev forced R/O; R/O by {nnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}[; stable by {nnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}]
- HCP102E DASD vdev forced R/O; R/W by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}[; stable by {userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}]
- HCP103E DASD vdev forced R/O; R/W by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}, R/O by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}[; stable by {userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}]
- HCP104E userid vdev not linked; R/O by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname }[; stable by {nnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}|exclusive by {userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}]
- HCP105E userid vdev not linked; R/W by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}[; stable by {userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}|exclusive by {userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}]
- HCP106E userid vdev not linked; R/W by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}, R/O by {nnnnn users|userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname } [; stable by {userid|userid at sysname|userid ADJUNCT|userid ADJUNCT at sysname}]
- HCP107E userid vdev not linked; not in CP directory
- HCP108E userid vdev not linked; volid volid not mounted
- HCP109E userid vdev not linked; invalid link device
- HCP298E userid vdev not linked; request denied
- HCP475I Fatal I/O error trying to read directory from volid [for user userid]
- HCP1008E Device vdev is not a DASD
- HCP1150E DASD {rdev|vdev} is not a valid base exposure.
- HCP2880E userid vaddr is not linked, CSE LINK I/O error, code cc.
- HCP6525E Authorization request failed.
- HCP6640E userid vdev not linked. DASD is a VDISK and is already linked on system sysname.
- HCP6640E userid vdev not linked. DASD is a VDISK and is defined under a SUBCONFIG for another SSI member.
- HCP6640E userid vdev not linked. MDISK DEVNO parameter conflicts with minidisk linked by {userid|userid at sysname}.
- HCP6640E userid vdev not linked. Minidisk has been defined with the V mode suffix and is already linked by {userid|userid at sysname}.
- HCP6640E userid vdev not linked. Minidisk has been defined with WRKALLEG and is already linked by {userid|userid at sysname}.
- HCP6640E userid vdev not linked. Minidisk is already linked with the V mode suffix by {userid|userid at sysname}.
- HCP6640E userid vdev not linked. Minidisk is already linked with WRKALLEG in effect by {userid|userid at sysname}.
- HCP6640E userid vdev not linked. Minidisk is linked with the MDISK DEVNO parameter by {userid|userid at sysname}.
- HCP6640E userid vdev not linked. No EQID exists for RDEV rdev.
- HCP6640E userid vdev not linked. SSI cluster error, code code.
- HCP6645E userid vdev not linked; SSI cluster is in safe mode.
- HCP6648I MDISK vdev has virtual reserve/release support in effect.
- HCP6648I MDISK vdev has working allegiance simulation in effect.
- HCP6704E Missing token at end of line
- HCP6706E Invalid {device address|disk mode|access mode} - {vdev|fm|mode|string}
- HCP6731E {CPRELEASE|CPACCESS} request for mode mode already active.
- HCP6732I CPACCESS request for userid's vdev in mode fm completed.
- HCP6733E Disk contains invalid control information -- disk not accessed
- HCP6733E Disk is not CMS EDF formatted minidisk -- disk not accessed
- HCP6733E I/O error encountered attempting to access disk -- disk not accessed
- HCP6733E Unable to link requested disk -- it cannot be accessed by CP
- HCP6735I Error encountered attempting to cache files -- userid's vdev accessed in mode mode
- HCP6772E Not authorized to link disk without a password