Catalogs, or enables, the user-defined commands (UDCs) in a
specified catalog file at the user, account, or system level.
You can also use this command to disable all UDCs on the system.
If you enter the SETCATALOG command without specifying a catalog
file name, all UDCs are disabled (deleted from the UDC directory)
regardless of whether or not you use the ;DELETE option.
Use only MPE/iX flat files as UDC files. If you issue the
SETCATALOG command for any other type of file, you will get
catfilename The name of a file containing User Defined Commands
to be cataloged. Commands within the file must be
separated from each other by a line whose first
character is an asterisk (*).
SHOW Specifies a listing of the User Defined Commands as
the UDC files are cataloged. Error messages are
printed for command lines that contain any errors.
This parameter is useful for locating errors in UDC files.
ACCOUNT Specifies cataloging of the file at the account
level. Using this parameter requires Account
Manager (AM) capability.
SYSTEM Specifies cataloging of the file at the system
level. Using this parameter requires System Manager
USER Allows users who have AM capability to change the
UDC catalog set for users in their account. Users
having SM capabilities can change the UDC catalog
set for any user. This does not rebuild the
executing UDC Directory the user must log on after
the command has been invoked.
RESET Causes the file(s) being cataloged to replace all
files that are already cataloged. Thus, specifying
one or more files with SETCATALOG and using the
RESET option functions the way SETCATALOG did with
a list of one or more files in MPE V/E. RESET is
the default if no option is specified.
APPEND Permits the user to add UDCs to the Directory. This
option causes the file(s) being cataloged to be
appended to the existing catalog. It also finds and
makes adjustments for any logon UDCs if appropriate.
DELETE Deletes the file(s) from the existing UDC Directory.
This permits the user to delete individual files
from the catalog directory. The original order of
the catalog is maintained. It also finds and makes
adjustments for logon UDCs. The ACCOUNT and SYSTEM
options allow the user to delete the cataloged file
at the account or system levels. The default is
The SETCATALOG command allows you to catalog user-defined
commands. You must have lock access and either read or execute
access to the UDC file that you specify on the command line.
When you set your own UDCs, the change takes place in your
UDC catalog immediately. If you specify ;ACCOUNT or
;SYSTEM, your UDC catalog is changed immediately, but other
users in your account or system must log on again in order
to have those changes available to them.
If you set a UDC and specify another user (;USER=), that
user must log on again in order to have the changes available.
The ability to delete or append files is particularly useful
because, although most UDC files do not change, new UDC
commands are frequently added or modified. Using ;DELETE
and ;APPEND allows you to make changes without incurring the
overhead of recataloging the entire Directory for every
change. Grouping UDC files into functions will further
reduce the work involved in modifying UDCs.
The RECURSION option now available in UDCs relieves the user
of having to define a particular command more than once in a
catalog set, and from having to maintain a particular order
for commands within a catalog set.
If SETCATALOG is used in a UDC, all valid commands through
and including the SETCATALOG command will execute. But
execution of the UDC will terminate after the execution of
the SETCATALOG command. Commands that follow will not
execute. The SETCATALOG command does not have this effect
when executed in a command file.
You may invoke the SETCATALOG command only from the logon
Command Interpreter (user main), where it is passed through the
scanner/parser. You cannot invoke SETCATALOG from
any other program (any child process).
This command is available in a session, job, or in
Break. It is not available from a program. Pressing [Break] has
no effect on this command.
SETCATALOG udca; USER=john.workers
This sets the UDC Directory for the user john.workers with
the commands in the file named udca. The USER option cannot
be specified with the ACCOUNT or SYSTEM options. Attempting
to do so will produce an error.
The following two command sequences are equivalent
SETCATALOG udca, udcb
SETCATALOG udcb ;append
In the first example, the command has an implied RESET, and
thus overwrites the previous file set in the Directory. In
the second example, udca is entered into the Directory, and
then udcb is appended to the Directory without affecting
udca. It also finds new logon commands if appropriate.
SETCATALOG udca ;delete ;account
This command deletes udca from the Directory at the account
level, provided it was cataloged at the account level. If
other account level UDCs reside in the Directory along with
udca, they remain undisturbed by this deletion. When
appropriate, a new logon UDC will be set up.
It is not good practice to create UDCs that have the same name
as other files, especially command files or any other files your
users may confuse with UDCs. MPE/iX first interprets the file
name as a UDC and will attempt to execute it. For example, if
there is a UDC named COMM and a user enters
COMM.GROUP.ACCT at the CI prompt, MPE/iX will execute
the COMM UDC and pass .GROUP.ACCT as the first parameter.
Manuals : System Startup, Configuration, and Shutdown Reference
Using the 900 Series HP 3000: Advanced Skills Course