We do things in different manners over here but I have been asking myself
the same question and I got a little break and looked at the manual. I
found this and even though I have not tried it, is worth it to test it:
EXEC_PATH
This path configuration statement identifies one or more directories that
Net.Data searches for an external program that is invoked by the EXEC
statement or an executable variable. If the program is found, the external
program name is appended to the path specification, resulting in a fully
qualified file name that is passed to the language environment for
execution.
Syntax:
EXEC_PATH [=] path1;path2;...;pathn
Example: The following example shows the EXEC PATH statement in the
initialization file and the EXEC statement in the macro that invokes an
external program.
If the file myFunction.mbr is found in the
/qsys.lib/rexx.lib/rexxpgms.file directory, the qualified name of the
program is /qsys.lib/rexx.lib/rexxpgms.file/myFunction.mbr.
If the file is not found in the directories specified in the EXEC_PATH
statement:
* If the specified path is absolute, Net.Data searches for the file in the
specified path. For example, if the following EXEC statement were
specified:
%EXEC{/qsys.lib/programs.lib/rpg1.pgm %}
Net.Data would search for the file rpg1.pgm in the /qsys.lib/programs.lib
directory.
* If the specified path is relative, Net.Data searches the current working
directory. For example, if the following EXEC statement were specified:
%EXEC { rpg1.pgm %}
then Net.Data would attempt to find the file rpg1.pgm in the current
working directory.
PETER VIDAL
MAPICS IT TECHNICAL SUPPORT TEAM / SR SYSTEM ANALYST
10540 Ridge Rd., Suite 203, New Port Richey, FL 34654-5111
WWW.PALL.COM
"There are qualities which one must possess to win: definitiveness of
purpose, knowledge of what one wants and a burning desire to posses it."
Anonymous
This communication may contain information that is confidential,
privileged and/or exempt from disclosure under applicable law.
If you are not the intended recipient, please notify the sender
immediately and delete the original, all attachments, and all
copies of this communication.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.