os-command and no-console issues

Posted by LegacyUser on 08-Mar-2001 20:18

Hey all,

I am trying to run a batch process from within Progress. Basically we have some background tasks for scanning, verification scanners and printers. We would like these to be able to be run from a browse inside our main application. When we try to pass the -param it seems to strip all but the first parameter (setup like -param "xxx;xxx.xx.xx.xxx;x;x"). So I have been playing around with the idea of calling a sperate program (startup.p for example) and passing a single parameter into this, which then runs the appropriate program. It alls seems to be working fine (on my small test scale for now), but as soon as I put no-console on it basically dies. Can anyone explain this to me or better still how we can pass in multiple params?

For a better idea of what we are doing here is the format of how the OS-COMMAND is setup:

OS-COMMAND NO-WAIT 'dlc\bin\prowin32.exe -pf xxxxx -p xxxx.p -param "xxx;xxx.xx.xx.xxx;x;x"'.

Another little query is when I try to add our .ini file (eg -ini xxx.ini) I get a error message telling me that ProMsg was not found, any ideas?

Thanx to all who answer this query.

All Replies

Posted by LegacyUser on 08-Mar-2001 20:41

"wayne singh" wrote:

>

>Hey all,

>

>I am trying to run a batch process from within Progress.

Basically we have some background tasks for scanning,

>verification scanners and printers. We would like these

>to be able to be run from a browse inside our main application.

When we try to pass the -param it seems to strip all

>but the first parameter (setup like -param "xxx;xxx.xx.xx.xxx;x;x").

So I have been playing around with the idea of calling

>a sperate program (startup.p for example) and passing

>a single parameter into this, which

>then runs the appropriate program. It alls seems to be

>working fine (on my small test scale for now), but as

>soon as I put no-console on it basically dies. Can anyone

>explain this to me or better still how we can pass in

>multiple params?

>

>For a better idea of what we are doing here is the format

>of how the OS-COMMAND is setup:

>

>OS-COMMAND NO-WAIT 'dlc\bin\prowin32.exe -pf xxxxx -p

>xxxx.p -param "xxx;xxx.xx.xx.xxx;x;x"'.

>

>Another little query is when I try to add our .ini file

>(eg -ini xxx.ini) I get a error message telling me that

>ProMsg was not found, any ideas?

>

>Thanx to all who answer this query.

I have figured out why we only appear to be getting the first parameter. Because it is a character going in as a parmater and there appears to be no way to set the format for a parameter, it is only getting the first 8 chars.

Now I just have to either figure out to increase the amount of chars we can send in.

This thread is closed