After completing the common steps above, proceed as follows:
- If you want to use an SFS directory as the work space
for the P696234K top directory, include the following in the P696234K
directory entry. This change requires the directory to be rebuilt
and placed online.
Directory Statement |
Explanation |
IPL CMS PARM FILEPOOL VMSYS
|
This directory statement allows automatic access
to the P696234K's top directory as file mode A. |
- Place the new directory online using VM⁄Directory Maintenance
(DIRMAINT) or an equivalent CP directory maintenance method.
- Use the number of 4K blocks calculated from Table 1.
- If you are installing all the default HLASM Toolkit Feature SFS
directories, the block requirements are summarized in the table.
- If you are selectively installing SFS directories, calculate the
number of 4K blocks your installation requires by adding up the storage
required by each of the directories you plan to install.
- From a user ID that is an administrator for the VMSYS filepool,
issue the following command:
Command |
Explanation |
enroll user P696234K vmsys: (blocks blocks
|
|
This command enrolls the user P696234K in the VMSYS filepool. VMSYS is
the default filepool. |
Options: - blocks
- The number of 4K blocks that you calculated previously.
This makes available
a top directory of VMSYS:P696234K. to the user.
- Compare your storage needs to the amount of storage available
in the filepool.
Command |
Explanation |
query filepool status vmsys:
|
Command to get a list of directories in the filepool
and the number of free blocks. VMSYS is
the default filepool ID. |
If
the number of free blocks is smaller than the number of blocks you
need to install HLASM Toolkit Feature (which you calculated in step 3, above), you need to add space to the
filepool.
For instructions on adding space to a filepool,
see z/VM: CMS File Pool Planning, Administration,
and Operation.
- Create the necessary vmsys:P696234K.HLASMTL subdirectories
used in the P696234K PLANINFO file.
Command |
Explanation |
set filepool vmsys:
create directory dirid
|
Commands to create subdirectories |
Options: - dirid
- The name of the SFS directory you are creating.
Examples of the command
above include:
create directory vmsys:P696234K.HLASMTL
create directory vmsys:P696234K.HLASMTL.object
⋮
A
complete list of default HLASM Toolkit Feature SFS directories is
provided in
Table 1. For information
about the CREATE DIRECTORY command, see
z/VM: CMS Commands and Utilities Reference.
There
is no need to create the top directory (VMSYS:P696234K.) as this has
been implicitly created by the ENROLL command.
- Give the MAINT user ID READ
authority to the general-use test build directory, using the GRANT
AUTHORITY command.
Command |
Explanation |
grant auth vmsys:P696234K.HLASMTL.TESTPROD to MAINT (read newread
|
|
The GRANT command permits copying files to MAINT's 19E production
disk. |
Options:
- read
- Gives the user read authority on a file or directory.
- newread
- Indicates that the users automatically receive read authority
for any new files added to the directory.
For more information
about the GRANT AUTHORITY command, see z/VM: CMS Commands and Utilities Reference.
Go to Step 3: Install HLASM Toolkit Feature.