to you as if the files and disks were locally attached.
Some of the fields in the internal file system tables ADT
and
AFT
are used differently when the minidisk or file
is
located remotely.
•
NUCXLOAD
Command
The
NUCXLOAD
command in
VM/PC
is
different
from that of
VM/SP
Release
2.
The
VM/PC
command
is
located in the CMS nucleus, and supports the loading
of modules which are adcon free and those which have
their RLD information saved with the module, through
the use
of
the 'RLDSA VE' option of LOAD and
INCLUDE. Also, the
NUCXLOAD command doesn't
support loading of modules from
OS
LOADLIBs, as this
support does not exist in
VM/PC.
XEDIT and
EXECIO
Initialization
Both XEDIT and
EXECIO are initialized differently in
VM/PC
than in
VM/SP
Release
2.
Both programs make
use of the capabilities of the
NUCXLOAD command to
load the programs as nucleus extensions. After the first
invocation of these commands, the nucleus extension will
normally be used when you invoke the command. In
addition,
OS Simulation uses of this capability to load
the
OSSIM module into your virtual storage to provide
the capabilities of
OS
Simulation in your CMS
environment.
XEDIT
In
addition
to
the difference in the initialization of
XEDIT, the messages and screen format
of
XEDIT use
mixed case to facilitate the reading of information. Also,
the default
PF
keys for XEDIT set the
PFI
key to 'TOP'
rather than
'HELP',
since the
HELP
facility does not
exist
on
VM/PC.
Appendix C. Comparison
of
VM/PC
and
VM/SP
C-5
To Next Page
Loading...
Need help?
General
