Forwarded for Roger Smith.... [JK]
-----------------------------------------------------------------
The enclosed mail file has been identified as a delivery error for list
HP3000-L because it was sent to the reserved 'owner-hp3000-l' mailbox.
------------------------------ Message in error ---------------------
From: ROGER SMITH <[log in to unmask]>
Subject: Re: Getting The XL= string from a program
Date: Fri, 18 Oct 96 13:57:00 PDT

On 16 Oct 96 at 14:09, Michael J. Lorengo wrote:

> I have a COBOL program that creates a son process using the
> CreateProcess Intrinsic.  The CreateProcess intrinsic allows me to
> specify the XL string that is to be used with the newly created
> process.  What I would like to do is pass the XL string that the
> parent process was called with:
>
> RUN MONITOR.PROGRAM.PROD;XL="XLV250.XL.PROD"
>
> What I want to be able to do is get the XLV250.XL.PROD string inside
> the MONITOR program and pass it to the son process in the
> CreateProcess intrinsic.
>
> I know I can do the following:
>
> RUN MONITOR.PROGRAM.PROD;XL="XLV250.XL.PROD";INFO="XL=XLV250.XL.PROD"
> and then use the GETINFO intrinsic and parse out the string, however
> this just seems stupid that I would have to do this.  I've looke in
> the Intrinsic manual but couldn't find a 'GETXL' or similar beast.

I don't have my laserrom running right now, but if you are only going
to have one XL listed, you can call "HPGETFIRSTLIBRARY" (or something
like this).  It will return the name of the first library listed in the
XL= string.  There's probably a way to get all of them, but this is off
the top of my head.

Larry Boyd    <[log in to unmask]>
"Those who respect the law and love sausage should never be
      around when either is made."
(These opinions are my own and not those of Hewlett-Packard.)

 ------------------------------------------------
Michael,

We place our XLs with SETVAR in our logonudcs.
SETVAR ASKPATH "XL.MPUB.MMV080,XL.FPUB.MMV080"
SETVAR ADDPATH "XL.PUB.DISC"

Our run command looks like this.
RUN SYSMAN.PUB.MMV080;XL="!ASKPATH,!ADDPATH";INFO="MG"

You can call HPCIGETVAR from inside the parent program before the
CREATEPROCESS Intrinsic.  This way your XL paths are in one place.
There is
no need to recompile a program it the path is changed.

roger