We have a load of batch processes that currently run using prowin. They shouldn't because they don't actually need to be GUI so I'm trying to convert them to use _progres.exe. Except it's not finding the rcode to run. The first one works, the second doesn't. What am I missing?
start C:\Progress\OpenEdge\bin\prowin.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
start C:\Progress\OpenEdge\bin\_progres.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
"Unable to run Startup Procedure"
We have a load of batch processes that currently run using prowin. They shouldn't because they don't actually need to be GUI so I'm trying to convert them to use _progres.exe. Except it's not finding the rcode to run. The first one works, the second doesn't. What am I missing?
start C:\Progress\OpenEdge\bin\prowin.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
start C:\Progress\OpenEdge\bin\_progres.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
"Unable to run Startup Procedure"
Flag this post as spam/abuse.
_progres does support INI files. My guess is that PROPATH is set in the Startup section. It needs to be in the WinChar Startup section for _progres.exe.
We have a load of batch processes that currently run using prowin. They shouldn't because they don't actually need to be GUI so I'm trying to convert them to use _progres.exe. Except it's not finding the rcode to run. The first one works, the second doesn't. What am I missing?
start C:\Progress\OpenEdge\bin\prowin.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
start C:\Progress\OpenEdge\bin\_progres.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
"Unable to run Startup Procedure"
Flag this post as spam/abuse.
Flag this post as spam/abuse.
Reply by Peter JudgeI don't know whether _progress supports INI files.
I know that it doesn't work on non-Windows platforms, but haven't checked whether that's true on Windows with _progress.The first statement is the reason why I never use INI in anger (usually roll my own XML and/or INI).-- peter[collapse]From: James Palmer [mailto:bounce-jdpjamesp@community.progress.com]
Sent: Wednesday, 04 March, 2015 10:12
To: TU.OE.General@community.progress.com
Subject: [Technical Users - OE General] Issue with prowin.exe vs _progres.exeIssue with prowin.exe vs _progres.exeThread created by James PalmerWe have a load of batch processes that currently run using prowin. They shouldn't because they don't actually need to be GUI so I'm trying to convert them to use _progres.exe. Except it's not finding the rcode to run. The first one works, the second doesn't. What am I missing?
start C:\Progress\OpenEdge\bin\prowin.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
start C:\Progress\OpenEdge\bin\_progres.exe -basekey "INI" -ini e:\batch\MONTHEND\batch.ini -pf e:\batch\MONTHEND\ICMASliv.pf -p TeamTimeCost.p -b
"Unable to run Startup Procedure"
Stop receiving emails on this subject.Flag this post as spam/abuse.
Stop receiving emails on this subject.Flag this post as spam/abuse.
-- Tom Bascom 603 396 4886 tom@greenfieldtech.com[/collapse][/collapse]
The winchar startup works a treat. Thanks.