OPENMPE Archives

December 2003

OPENMPE@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Wed, 17 Dec 2003 16:04:05 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
> It sounds as though you are proposing that any CI functions
> must be in the logon group.  Is that correct?

This is not correct. All user defined functions (script files)
would need to be found via the existing HPPATH mechanism. If
your logon group was not specified in HPPATH (it is there by
default as !!HPGROUP) then the CI would not find any functions
there.

On the other hand, I have defined a group named SCRIPTS.SYS,
and I've seen customer systems with similar names like XEQ.SYS
or CMD.SYS, etc. This is the location for all of my (and other's)
command files.  It would be easy enough to place all of your
user defined functions in a group named FUNC.SYS, for instance,
and append FUNC.SYS to your existing HPPATH. Note, that since
POSIX names are acceptable in HPPATH, you could keep all/some
functions in the POSIX namespace.

Hope this helps clarify,

 Jeff

ATOM RSS1 RSS2