X'08' - Virtual Console Function".) The reason for this is that other CP mes­
sages can be mixed in with the command response, and therefore the program
cannot be assured of receiving its response in consecutive IUCV messages.
If the CP command response is to be typed on the programmable operator's
virtual machine console, the action routine should use a CMS function, such as
WRTERM, to write the lines in the program's CP command response buffer to
the terminal.
The Programmable Operator Facility 457

Auxiliary Directories
When a disk is accessed, each module that fits the description specified on the ACCESS command is included in the resident directory. An auxiliary directory
is an extension of the resident directory and contains the name and location of
certain CMS modules that are not included in the resident directory. These
modules, if added to the resident directory, would significantly increase its size,
thus increasing the search time and storage requirements. An auxiliary directo­
ry can reference modules that reside on the system (S) disk; or, if the proper
linkage is provided, reference modules that reside on any other read-only CMS disk. To take advantage of the saving in search time and storage, modules that
are referenced via an auxiliary directory should never be in the resident directo­
ry. The disk on which these modules reside should be accessed in a way that
excludes these modules.
How To Add an Auxiliary Directory
To add an auxiliary directory to CMS, the system programmer must generate
the directory, initialize it, and establish the proper linkage. Only when all three
tasks are completed, can a module described in an auxiliary directory be proper­
ly located.
Generation of the Auxiliary Directory
An auxiliary directory TEXT deck is generated by assembling a set of DMSFST macros, one for each module name. The format of the DMSFST macro is: DMSFST where:
l
filename l
(filename [,filetype]) [ ,aliasname [ , FORM=E] ,MODULE filename, filetype is the name of the module whose File Status Table (FST) information is to be copied.
aliasname is another name by which the module is to be known. FORM=E specifies that 64-byte FST entries are to be generated
rather than 40-byte entries. Either length FST entry
will operate correctly on basic CMS. However, the 40-byte form will not contain such information as
date/time after initialization by GENDIRT.
Initializing the Auxiliary Directory
458 VM/SP System Programmer's Guide
After the auxiliary directory is generated via the DMSFST macro, it must be
initialized. The CMS GENDIRT command initializes the auxiliary directory
with the name and location of the modules to reside in an auxiliary directory.
By using the GENDIRT command, the file entries for a given module are
loaded only when the module is invoked. The format of the GENDIRT com- . mand is: