5 replies to this topic

[Rob Fantini]

Hello
10 years ago I remember reading in a document that it was possible to run a pro4 pgm from linux command line.

we use : Version : 4.6000 Revision : 2.1.3 Jul 20, 00 Bootstrap Rev : 4.6M

Could someone point me in the direction to do this?

thanks
Rob Fantini

[Wim Soutendijk]

Hi Rob,

there are multiple possibilities:
- you could setup a specific operator code with transparant logon and start function as the program you want and startup a proiv session passing on the co/div and operator code
- you could register all the keystrokes in a text file and run pro with a redirect input from that file
- you could setup a task to run your programm, and call the task directly from the operating system.

hope this gets you started

Wim

Edited by Wim Soutendijk, 01 February 2011 - 08:47 AM.

[Rick Young]

Just a personal $0.01 opinion - I would go with either of Wim's first two suggestions, as I seem to recall B&T being a tad "flaky" under 4.6.....

Note I'm making this comment with zero onhand evidence to back it up - so please just consider a personal opinion.

[Richard Bassett]

I'd add my 0.01 to Rick's and say don't try to use B&T unless that kind of functionality is specifically what you're looking for.

You can start a ProIV green-screen session just with transparent logon (flag in $OPR) as Wim says eg:

pro OPR CDV ..more..arguments..

It still links to the operator's logon function and you can pick up extra arguments using XFERIN() in logic.


If in fact you want something to behave more like a 'real' command-line command, it's tricky, because you can't stop ProIV generating full-screen-oriented output on the standard output stream (stdout) as far as I know.

In theory you could try to discard that output and, say, write the output you want to see onto the standard error stream (stderr), eg:

pro OPR CDV ..more..arguments.. >/dev/null

I have used this technique with a ProIV kernel extended to write to stderr using LINK(), but as far as I know, regular ProIV gives you no way to write to the standard error stream.

[Richard Bassett]

>> regular ProIV gives you no way to write to the standard error stream

Although, since you're on Linux, you could probably use a report and send the output to the /dev/stderr 'file'..

[Rob Fantini]

thank you for the replies...

Using transparant log on is the way I'll go.