Dwayne,

there are three levels of UDCs:

* user one's,
* account one's, and
* system one's.

User's UDCs are valid only to the user,
Account's UDCs are valid for all users in the account, and
System's UDCs are valid for all logons on the system.

The command SETCATALOG is the right one. Especially options ;APPEND or ;DELETE are
very useful.

The structure of an UDC file is easy:
UDC_command [parms]
MPE_command(s)
******

But: UDCs are always loaded into the memory! Since MPE/iX it is better to set a
Path to a common used area of useful command files instead of having UDCs.
Such an entry in a system wide UDCs (probably the only one) could look like:
SETVAR HPPATH "!!HPGROUP,PUB,PUB.SYS,XECMD.SYS"
so the search for an unknown command will start in the current (logon) group, and
is continued in
PUB of current account, in PUB.SYS, and in the special group (we use XECMD.SYS).

An example:
T filename
could invoke TDP to edit the file filename.

S could show you all session, because S.XECMD.SYS looks like
SHOWJOB JOB=@S

and so on.

If you're interested in more, please let me know!

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 06/26/98 12:59:34 AM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/HI/CSC)
Subject:  UDCs




I am new to the world of HP3000s.  I have been hired to run one and have
spent the past several weeks learning commands to make the system work.  I
would like to set up some of my own UDCs to manipulate and control the
print jobs and where they are going.  I just need to know how to actually
write new ones or edit existing UDCs.
Thanks!
Dwayne Stewart