text
| - Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
- Instruct users to perform the following action:
-- Ensure that the openlink.sh and openlink.csh files are executable.;
-- Run . ./openlink.sh in a Bourne and/or a Bash shell. ;
-- Run source openlink.csh in a C shell, if the problem persists. ;
-- Set the variables--contained within the shell scripts--manually, if the problem persists.
Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .
However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .
When in doubt, consult the man pages or another Unix reference.
|