Kbase 13698: Common problems running Progress under X-windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Common problems running Progress under X-windows
Common problems running Progress under X-windows:
Note: _prox is the Version 6 exe for X-windows
_promtf is the Version 7 exe
Also note that in some older versions of Progress, there may be no
windows exe provided and the user may have to use PROBUILD to create
one. Remember when doing a probuild, the resultant exe could have
a different name than the default progress exe.
1) Entering pro or mpro with -ws option and gets error
-ws is not supported by this executable. (1610)
Check the pro and mpro scripts. By default, these scripts call
the _progres executable or whatever exe is pointed to by the
environment variable PROEXE. _progres does not support the -ws
startup option. The x-windows exe is _prox and does support
-ws. Either modify the scripts to use _prox or define the
environment variable. Version 7 has a script prowin which calls
the version 7 exe, _promtf.
2) Trying to access database using _prox and gets error
Cannot find or open file <file-name>, errno = 13. (43)
Errno 13 is a permissions problem. Make sure that the _prox
executable has correct privileges (ie the same as _progres:
-rwsrwxrwx, see kbase 12538 for more information on setting
protections in the Unix environment.)
3) No errors when starting _prox, but nothing seems to happen.
Check to see if the environment variable DISPLAY is set and
what it is set to. Sometimes the _prox is started on a
different host than the local station and if DISPLAY is not set
to hostname:0.0, progress will try to try to open window on the
local machine which may not be the same output device as the local
workstation. When run locally, DISPLAY can be set to :0.0
Examples: Hostname = orange
Local $DISPLAY :0.0
Remote $DISPLAY orange:0.0
4) Can't run _prox procedures in background.
Even though we're not running in the foreground, DISPLAY still
needs to be set. This is because X requires an X server be
identified to execute an application (Xclient, .exe, etc),
regardless of whether the application is running in foreground
or background.
In version 7, you can also use the Progress startup parameter
Windows Attributes (-Wa) to specify the X display name
(-display) on which to run the application. For example, you
could specify the display in this manner:
$DLC/bin/prowin -b -p compile.p -Wa -display :0.0 >log.err 2>&1 &
Progress Software Technical Support Note # 13698