PARAM SAVE-ENVIRONMENT ON
makes HP COBOL-programs save environment variables (which they receive as messages at startup from Guardian) for future calls to getenv()
from C modules.
Actually, the library I'm using tries to open stderr
because it can't read environment variables. One solution is to set the PARAM SAVE-ENVIRONMENT
to ON
, so getenv()
will properly function again. This has to be done in each TACL session.
Unless: you use the ?SAVE STARTUP
- or ?SAVE ALL
-directive in your COBOL program to achieve the same effect.
Lessons learned:
- Don't mix COBOL and C.
- Don't use COBOL at all.