> Is there any way of having the ci execute a script in the HFS?  I.e.
> ./createjobq named file?

Yes.  Starting in release 5.0 express 3 ( see:
http://jazz.external.hp.com/papers/Communicator/5.0/exp3/ci_enhancements.htm
l )

command files can live in and be executed from the HFS.  As Donna correctly
mentioned you need to add a HFS directory name (can be /ACCT/GROUP) to your
HPPATH variable if you want the script name to be qualified via the HPPATH
mechanism.  However, if you want to execute a qualified HFS named script,
such as "/bin/foo.cf" or "./mybin/foo", HPPATH is ignored and thus does not
need an HFS element added.

As described in the Communicator article above, there are some ambiguous
cases, involving HPPATH qualification, where a script name can be considered
both an MPE name and an HFS name. In all cases the MPE interpretation has
precedence over the HFS interpretation. For example, a script named "a/b"
can be
considered an MPE name with an inline lockword, or an HFS named file "b" in
the
subdirectory "a".  Also, the script named "file.grp" can be an MPE file
("file")
in the group "grp" in the logon account, or it can be an HFS named file
"CWD/file.grp".

There are some other interesting(?) corner cases covered in the article.

regards,
 Jeff Vance, CSY