Duane Percox ([log in to unmask]) wrote:
: 1. since the temp file you want to use is just that, who cares if it is
: named using hfs? Why not just create a regular old temp file and then use
: format #1 of your example: callci 'run someprog.pub;stdin=tmpfile'. This is
: offered with the understanding that I don't have 5.0 installed and don't
: know if this makes sense given posix rules and such!
 
This seems like a good idea, but you can't create them using the shell.  A
callci command can do it...  If that's a problem, consider creating your
file with a valid MPE name in the first place!  An example would be to
cat foo > /ACCT/GRP/FILE and then callci 'run x;stdin=file.grp.acct'.
 
: 2. when building files in this environment, consider using a unique id of
: the server process (like pin). build all files with the pin in the name,
like:
: si##### where ##### is the pin number.
 
The CI keeps the HPPIN variable for you, it's inherited into the POSIX
environment with the correct value (since it's an active function evaluated
in the current process).  Children of your shell will inherit the parent's
value since it's static once you're in the POSIX environment.
 
: 3. to avoid the single file equation 'thang', have the cobol programs open
: the file with 'select cgi-parm-file assign using my-file-name'. You can pass
: the server pin to the created son process (in parm=) or use the PROCINFO
: intrinsic to get the pin of your father (the server process). Imbed the pin
: in the file names.
 
This kind of information can easily be passed in the environment variables.
 
Steve