Top
NetCOBOL V11.0 NetCOBOL Studio User's Guide
FUJITSU Software
Chapter 9 Remote Development Function > 9.2 Work on server side > 9.2.2 Setting up the user environment on the server
PreviousNext

9.2.2 Setting up the user environment on the server

9.2.2.1 On a Solaris server, Linux(64) or Linux(Itanium) server

For code conversion

When the code conversion is done with Interstage Charset Manager on the server side in the sending and receiving of the resource, the following environment variables are set.

For build

Note

If the LC_ALL environment variable is required, use the same value as that used in the LANG environment variable.

Examples of shell scripts for setting environment variables

In the examples shown below, the environment variables are assumed to be set as follows:

On a Solaris server

For remote development using a Solaris server, csh must be used as the login shell. Edit .cshrc that is found in the home directory used by each developer, and add the text shown below.

In the following example, .cshrc is modified for a Solaris server.

## COBOL environment setting
source /opt/FJSVcbl/config/cobol.csh
## Environment setting for Interstage Charset Manager
if(${?LD_LIBRARY_PATH}) then
setenv LD_LIBRARY_PATH /opt/FSUNiconv/lib:${LD_LIBRARY_PATH}
else
setenv LD_LIBRARY_PATH /opt/FSUNiconv/lib
endif
## Setting for compilation and link that is common to developers
setenv COBOLOPTS "-dp ../list"
setenv COBCOPY ../COPYLIB:${COBCOPY}
## Character code set used by the program to be developed
setenv LANG en_US.UTF-8
On a Linux(Itanium) or Linux(64) server

For remote development using a Linux server, csh or bash can be used as the login shell.

To use csh as the login shell, edit .cshrc that is found in the home directory used by each developer, and add the text shown below.

## COBOL environment setting
source /opt/FJSVcbl/config/cobol.csh
## Environment setting for Interstage Charset Manager
if(${?LD_LIBRARY_PATH}) then
setenv LD_LIBRARY_PATH /opt/FSUNiconv/lib:${LD_LIBRARY_PATH}
else
setenv LD_LIBRARY_PATH /opt/FSUNiconv/lib
endif
## Setting for compilation and link that is common to developers
setenv COBOLOPTS "-dp ../list"
setenv COBCOPY ../COPYLIB:${COBCOPY}
## Character code set used by the program to be developed
setenv LANG en_US.UTF-8

To use bash as the login shell, edit .bashrc that is found in the home directory used by each developer, and add the text shown below.

## COBOL environment setting
source /opt/FJSVcbl/config/cobol.sh
## Environment setting for Interstage Charset Manager
if  ${LD_LIBRARY_PATH:-""} = ""  ; then
LD_LIBRARY_PATH=/opt/FSUNiconv/lib; export LD_LIBRARY_PATH
else
LD_LIBRARY_PATH=/opt/FSUNiconv/lib:${LD_LIBRARY_PATH};export LD_LIBRARY_PATH
fi
## Setting for compilation and link that is common to developers
COBOLOPTS="-dp ../list";export COBOLOPTS
COBCOPY=../COPYLIB:${COBCOPY}; export COBCOPY
## Character code set used by the program to be developed
LANG=en_US.UTF-8; export LANG

9.2.2.2 On a Windows server

For remote development using a Windows server, a user account for the server environment is used to perform development work. Unless remote development work is performed with an existing user account, a new user account for remote development work must be created in the server environment. When creating a user account, consult the server administrator.

Generally, to add a local user account to the server machine, log on to the server with an administrator account. Then, select "Apps" > "Control Panel" > "System and Security" > "Administrative Tools" > " Computer Management" from the Start menu to display "Computer Management" window, and use"Local Users and Groups" .If an additional environment setting must be made for remote development work, add the setting to the environment of the relevant user account.

Note

When registering a user account, register it as a member of a user group. Its password cannot be changed while the associated local personal computer is connected to the server. Therefore, when making settings for the user account, do not set a password change while the local personal computer is connected to the server.

Note

There are two types of environment variables: user environment variables and system environment variables. The user environment variables are generally used . However, for PATH environment variables, the system environment variables are used.

When giving priority to an original path, the COB_RDENV_X64 environment variable is used.

When a file is specified for the COB_RDENV_X64 environment variable, the file is considered to be a batch file.

A NetCOBOL remote build executes the file first by the CALL batch command.

COB_RDENV_X64=C:\MyTools\myenv.bat
Content of"C:\MyTools\myenv.bat"
path C:\MyCommand;%PATH%

As a result, "C:\MyCommand" is given a higher priority than the path of the system environment variable in a remote build.

Windows(Itanium)

SDK information must be set in the environment variables of each user account. SDK information varies according to which SDK is used.

Note

CPU architecture according to bit rate of the server, IA64 of the folder name becomes x64 or amd64. Set it after confirming the software development installation folder.

Windows(64)

The environment variable "PATH" will be set to the folder name of the user account at the installation destination of NetCOBOL. Remote Build is executed in the same environment as the "NetCOBOL command prompt" on the NetCOBOL server side.

PreviousNext
Copyright 2011-2015 FUJITSU LIMITED