5 replies to this topic

[bschroder]

I'm working now with Pro-IV kernel 4.6 r518.
On older versions, I was able to use the reserved word XFERIN to pass parameters when starting up a pro-iv session.

Example:
something.piv -P SYS MDC VAR1 VAR2 VAR3 VAR4

Then, in the pro-iv function:

XFERIN(VAR1, VAR2, VAR3, VAR4)

But, using 4.6 r518, when I do the same thing, all I get is:

VAR1 = Pro32
VAR2, VAR3, VAR4 = blank

Is there a different command to pick up those passed variables or has this changed somehow? Any help would be appreciated.

Thank you.

[Chris Pepper]

Which platform are you running on? Unix works OK.

[Phil]

Here are some transparent parameters ;












Hope that helps.

[bschroder]

I am trying this on a Windows platform (Windows 2000 Server sp4).
It works fine using kernel 4.6 r218 on Windows NT 4.
Thanks.

[Anthony Downey]

Hi,

We are after upgrading from PROIV 4.6 to 5.5 and from Win NT to Win2003.

A transparent login that was working previously now no longer works.

The function that executes with the transparent login uses the XREFIN command.

The format of the command is
XREFIN($VAR1, $VAR2, $VAR3, $VAR4)

As per Brett's original post it appears that $VAR1 is assigned a value of 'Pro32'.

If anyone has come across this issue or has any advice about the use of XREFIN I'd be very happy to hear it.

Maybe the command and it's usage have changed between releases although the 'Logic' documentation is the same for 4.6 and 5.5.

Regards,

Anthony

[Joseph Bove]

bschroder,

In our transparent logins we had to do the following:

PROIV.EXE C:\ATC\TEMP\%1.PIV /PNOTHING NOTHING %1

Parameters 1 and 2 seem to disappear into some black hole.

I forget exactly when we had to make this change, but it was somewhere in the 4.6 development cycle.

hth,

Joseph