press ENTER. You will then see the UPDATE LINK screen
that defines the link giving the user
SAMPLE
read/only
access to the 100 minidisk owned by user CMS. This
minidisk
is
also known to the SAMPLE virtual machine as
100. The user SAMPLE will not be able to write
on
his 100
disk since it
is
read/only. This
is
the CMS System disk,
which contains the
CMS commands, programs, macro
libraries, etc. ALL
CMS USERS SHOULD
HAVE
THIS
LINK.
If
you go back and look at the minidisks owned by
SAMPLE, you will see that SAMPLE has a
read/write
101
disk and a
read/write
102 disk. The 101 disk is his private
storage disk, typically accessed mode
"A"
by CMS and
commonly called the
"A
Disk." The access mode
of
his 1 02
disk
is
not automatically assigned.
Disk Allocation and Checking
When the END function
is
selected, (Function 6
on
the
FUNCTION
MENU), the Configurator will test for the
existence of all of the required system files. These file names
were supplied on the
SYSTEM CONFIGURATION screen.
You will see a message if a required system file cannot be
found.
Next the Configurator will look at all the changes and
additions
to
the minidisks.
If
the minidisk does
not
exist
on
the designated
PC
disk drive, it will be allocated.
If
the
minidisk has been enlarged, the minidisk file will
be
enlarged
to
match the specification.
Remember that
CMS will
not
take advantage of the
additional space until the
CMS FORMAT command with the
RECOMP
option
is
used
to
recompute the minidisk size.
If
FORMAT
is
used without the
RECOMP
option, the new
minidisk size will
be
computed, but all of the
data
previously
on
the minidisk will be lost.
If
the size of the minidisk is reduced, the Configurator will
warn you, but will
not
decrease the size of the allocated
space. When the size
of
a minidisk
is
reduced, you run the
risk of losing data.
3-18
VM/PC
Users
Guide
To Next Page
Loading...
Need help?
General
