Hi Jeff,

I really think it is too restrictive not to be able to qualify a function
name.  It is certainly unlike command files.

I suggest that there be some kind of escaping mechanism for the function
name:

  f()
  "f.b.a"()
  "/A/B/F"()

Quotes might not be the best escape character.  I'm not sure.

You asked for an example.  Our installation scripts are command files that
run on customer systems.  They reside in the LPS account and are run from
the SYS account, so we fully qualify the names of other command files that
are in the LPS account.  We would want to do the same for CI functions that
we might use.

Yes, we could put the name of the group containing our command files at the
head of the HPPATH list, and it would work.  But we shouldn't HAVE to do it
that way, one should be able to name a function anywhere on the system
without having to have the HPPATH variable point to its location.  Where
else in MPE must a file be on the path in order to use it?

Thanks.

Jim

Jim Kramer
Director of Research and Development
Lund Performance Solutions
Phone: (541) 812-7600 | Email: [log in to unmask]
Fax:   (541) 812-7612 | Web:   www.lund.com
Yahoo: jhkramer_1     | AOL:   jh kramer 1

NOTICE:  This communication may contain privileged or other confidential
information.  If you are not the intended recipient or believe that you may
have received this communication in error, please reply to the sender
indicating that fact and delete the copy you received.  In addition, you
should not print, copy, retransmit, disseminate, or otherwise use the
information.  Thank you.

> -----Original Message-----
> From: VANCE,JEFF (HP-Cupertino,ex1) [mailto:[log in to unmask]]
> Sent: Wednesday, December 17, 2003 4:04 PM
> To: 'Jim Kramer'; [log in to unmask]
> Subject: RE: CI functions clarification
>
>
> > 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