C
carl.williams
Guest
Just so people are aware if they move to the new Appserver and shell out to Linux to run start say a batch progress task (mbpro) then the PROPATH environment is no longer setup in the Linux environment. Tech support say this is the expected behaviour and offer this possible work around below but instead we will be changing our application to pass the PROPATH to a script which will then run mbpro having setup the propath. "The PROPATH variable isn’t set in the environment because the PASOE does not use it. The reason for this is that a single PASOE instance can support multiple ABL applications with their own session manager and PROPATH. That said, you can get the PROPATH via the "oeprop" command. Execute the below command on oepas1 instance: /bin/oeprop.sh Appserver.Agent.oepas1.PROPATH, it should dump the PROPATH value. In your case, as the instance needs to find the ABL application on startup, you can create a *_setenv.bat/sh script that gets executed at startup. In this script you can set the PROPATH or you can call oeprop to extract the PROPATH value from openedge.properties and add it to the environment."
Continue reading...
Continue reading...