Kbase P124764: How to troubleshoot Progress error 156?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/20/2008 |
|
Status: Unverified
GOAL:
How to troubleshoot Progress error 156?
GOAL:
Redirection or piping of stdin or stdout is allowed only with -b. (156)
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
If the error (156) is displayed when trying to start a Progress session, check the following to see if the problem can be resolved.
Possible causes:
1. Attempting to run the wrong Progress binaries for the operating system.
To confirm operating system, type: "uname -a <CR>" on most systems. If what binaries have been received from Progress cannot be confirmed, please call Technical Support with serial number ready. This also may be caused if you are running a version of the O/S that is older than the version we used to compile the Progress binaries.
2. There may not be any tty associated with this terminal session.
If there is no tty associated with the session, then Progress will assume you are trying to run in batch mode where no I/O is allowed. For this reason the error is generated. To test to see if there is a tty associated with your session, type: "tty <CR>" at your O/S prompt. It should return with the name of the tty device that your session is using. If it returns with something else or a message that no tty is available, check with your hardware vendor to find out why.
3. The permissions on the tty device may not be set properly.
To check the permissions, first type: "tty <CR>" to determine your tty, for this example we will assume what is returned is /dev/ttyp1. Then type: "ls -l /dev/ttyp1 <CR>". The permissions for your device should have read/write privileges enabled for all groups like this:
crw-rw-rw- 1 root 20, 1 Mar 8 10:06 /dev/ttyp1
If you don't have read/write permissions for your tty device then this will cause error 156 because Progress cannot allow I/O to the screen.
4. Your terminal may not be large enough to run an interactive Progress session.
If your terminal does not support a minimum of 80 columns, Progress will stop and display error 156. We require a minimum of 80 columns to run an interactive session.
5. If your sessions worked at one time and stopped working and are now resulting in error 156, check to see if anyone has made any changes to the getty file. The getty file is responsible for opening and initializing a tty line, reading a login name and invoking a login. If changes were made to this file improperly this may cause a problem in creating a tty. Consult with your system administrator if this is the problem.
6. This error will also result if you try to run a Progress session in the background without using the -b startup parameter.
For example, if you type:
mpro demo -p program.p &
Error 156 will result, indicating that you need to add the -b startup parameter:
mpro demo -p program.p -b &
... or you can use the mbpro or bpro startup scripts that are provided by Progress that add the -b startup option for you.
7. This error will occur on SCO OpenServer with Progress 9.0, if you have not installed the OSRCompat BCM for SCO OpenServer. For more information, please refer to solution 19212, "Error 7113 on SCO OpenServer 5.0.5" and 19513, "Version 9, SCO OpenServer and the OSRCompat BCM".