How could App Server LOGS directory set to a shared directory and have COBOL remote call run success
On Unix host "A", we have set up the app server's LOGS directory to some directory on Unix host "B".
Everything works (i.e. logs are created on Unix host "B") except COBOL remote call test (from PeopleTools Test Utilities).
Below is the error message:
"Could not open connect file <LOGS directory on Unix host "B">/rmtcall_conn.8459 for child program connect string (2,-1)"
If we set the LOGS directory back to Unix host "A", the error disappears.
Anyone knows how to fix this issue?
Everything works (i.e. logs are created on Unix host "B") except COBOL remote call test (from PeopleTools Test Utilities).
Below is the error message:
"Could not open connect file <LOGS directory on Unix host "B">/rmtcall_conn.8459 for child program connect string (2,-1)"
If we set the LOGS directory back to Unix host "A", the error disappears.
Anyone knows how to fix this issue?
0