To use remote development, the services required by this function must be operating at the server system side. Accordingly, these services must be installed and started.
The services that must be installed at the server side are determined by the server OS and NetCOBOL product version.
Server OS | NetCOBOL Product on Server | Service to start |
|---|---|---|
Windows(Itanium) | Windows(Itanium) 64bit NetCOBOL | NetCOBOL Remote Development Service (*1) |
Windows(64) | Windows 64bit NetCOBOL | |
Solaris | Solaris 32bit NetCOBOL V10 or earlier | rtpd/rexec service telnetd(*2) |
Linux(Itanium) | Linux(Itanium) 64bit NetCOBOL | rtpd/rexec service telnetd(*2) |
Linux(64) | Linux 64bit NetCOBOL | NetCOBOL Remote Development Service(*1) telnetd(*2) sshd(*3) |
*1: The remote development service is a service that NetCOBOL provides. Refer to the following for the service startup procedure.
For a Windows server
Refer to "9.2.1.1 NetCOBOL Remote Development Service".
For a Linux(64) server
Refer to "NetCOBOL User's Guide" of Linux 64bit NetCOBOL.
*2: This service is required in order to use the remote debug function.
*3: This service is required in order to encode communication contents by SSH port forwarding.
The NetCOBOL Remote Development Service (referred as "Remote Development Service" after in this chapter) must be run on the server side system to make use of the remote development functions from NetCOBOL Studio on the client side. The Remote Development Service accepts a request from NetCOBOL Studio, logs on the server side system with the specified account and performs tasks on the server side system with the account.
For security reasons, the Remote Development Service is not configured to start automatically in its installation. You must start the Remote Development Service before you use remote development functions.
Note
Security Notes
For security reasons, the Remote Development Service is not configured to start automatically in its installation.
In order to maintain security, make sure to disclose the Remote Development Service only for the limited period required. When the release of the Remote Development Service is stopped, restore the changes made in the firewall settings or Remote Development Service "Startup type".
Make sure to use remote development functions with the Remote Development Service only inside a safe network such as an intranet with security that is appropriately managed.
When you connect to the Linux(64) server to use Remote Development Service, you can encode communication contents by SSH port forwarding.
In this case, SSH must be running at the server system side, and you need to notify the NetCOBOL Studio user of the public key fingerprint used on the SSH server.
Information
Generally, execute the following command to get the public key fingerprint (typical md5).
ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub
For details, refer to the manual for ssh-keygen command.
This section explains how to start and stop the Remote Development Service.
Starting the Remote Development Service
To start the Remote Development Service, log on the server side system with an administrator account and take the following steps:
From the Windows start menu, select "Apps" > "Control Panel" > "System and Security" > "Administrative Tools" > "Services".
From the list of services, select "NetCOBOL Remote Development Services".
In the window menu, select "Action" > "Properties", and open the "NetCOBOL Remote Development Services Properties" dialog.
In the "NetCOBOL Remote Development Services Properties" dialog, select the "General" tab.
Click the "Start" button.
If you want the Remote Development Service to start automatically when the system is started, change the "Startup type" to "Automatic".
The Remote Development Service uses port 61999 by default, to disclose its services. If port 61999 is already being used in the system, the port number must be changed. Refer to the description of port setting in "9.2.1.1.4 Configuring the Remote Development Service" for details.
If the Windows Firewall or other firewall software is running on the server, you must configure it in a way that it does not block the port which is used by the Remote Development Service. The configuration method for the firewall differs according to the type of firewall software being used. Refer to the document on each firewall software.
Before starting the Remote Development Service, read "Security Notes "under "9.2.1.1 NetCOBOL Remote Development Service".
To stop the Remote Development Service, log on the server side system with an administrator account and take the following steps:
From the Windows start menu, select "Apps" > "Control Panel" > "System and Security" > "Administrative Tools" > "Services".
From the list of services, select "NetCOBOL Remote Development Services".
In the window menu, select "Action" > "Properties", and open the "NetCOBOL Remote Development Services Properties" dialog.
In the "NetCOBOL Remote Development Services Properties" dialog, select the "General" tab.
Click the "Stop" button.
If you do not want the Remote Development Service to start automatically when the system is started, change the "Startup type" to "Manual".
When Remote Development Service no longer needs to be disclosed, restore the settings changes that were made in the firewall software or so.
This section explains the log files output by the remote development service.
Contents of the Log file
The following information is recorded in the log file:
Connection start date and time
Client IP address
Account name
Whether or not log-on was successful
Connection end date and time
The commands executed under each user account after logon are not recorded.
The time output to the log file is Universal Time and Coordinated (UTC): coordinated universal time.
The path of the Log file
The path of the log file is as follows:
%ProgramData%\Fujitsu\NetCOBOL\RDS\Log\rds.log
%ProgramData% is a common application data folder for Windows.
You can change the folder to output the log file by configuration of the Remote Development Service. See the explanation for the logdir setting in "9.2.1.1.4 Configuring the Remote Development Service" for details.
You must log on with an administrative account to change or delete log files.
Generations of the Log file
When the size of a log file reaches the maximum size, a backup is made for that log file and a new log file is created.
You can change the maximum size of log files by configuration of the Remote Development Service. Refer to the explanation for the maxlogsize setting in "9.2.1.1.4 Configuring the Remote Development Service" for details.
Backup files are located in the same folder as the log file output folder and have the below name.
rds.<sequence number>.log
Where <sequence number> is a number starting at 001 and has a maximum value of 999. When new backup file is created, a new sequence number is allocated for it. This sequence number is the next sequence number of the backup file with the most recently updated time amongst the backup files in the same folder. If there is no backup file in the same folder, the sequence number 001 is allocated. 001 is also regarded as the next number of 999.
When a new backup file with sequence number n is created, only the backup files which have sequence number between (n - the number of backup generation + 1) and n are retained. All other backup files are deleted. For example, if the new backup file is rds.007.log and the number of backup generations is 3, all backup files are Deleted except for rds.005.log, rds.006.log, and rds.007.log.
You can change the number of backup generation by configuration of the Remote Development Service. See the explanation for the maxloggen setting in "9.2.1.1.4 Configuring the Remote Development Service" for details.
This section describes the Remote Development Service settings that can be changed and explains how to set them.
The following settings can be changed:
Port number to be used
The output folder, maximum size, and number of backup generations for log files
Specify the settings that you want to change as service start parameters. The Remote Development Service must then be restarted for the changes to take effect.
Changing setting of the Remote Development Service
To change setting of the Remote Development Service, log on the server side system with an administrator account and perform the following steps:
From the Windows start menu, select "Apps" > "Control Panel" > "System and Security" > "Administrative Tools" > "Services".
From the list of services, select "NetCOBOL Remote Development Services".
In the window menu, select "Action" > "Properties", and open the "NetCOBOL Remote Development Services Properties" dialog.
In the "NetCOBOL Remote Development Services Properties" dialog, select the "General" tab.
Enter the settings in the "Start parameters".
Note
To enter more than one setting in the "Start parameters", separate the settings with spaces.
To enter a setting that contains a space, enclose it in quotation marks (").
[Example] /port:61999 "/logdir:C:\log data" /maxlogsize:128 /maxloggen:2
The contents of "Start parameters" are not saved. If you configure the Remote Development Service to start automatically when the system is started, the Remote Development Service starts with default setting when the system is started next time.
Refer to the list below for the settings that can be entered in the "Start parameters".
Setting list of the Remote Development Service
The following table shows the settings that can be changed.
Setting name | Form to specify in start parameters | Default value | Explanation |
|---|---|---|---|
port | /port:<number> | 61999 | Specify the TCP/IP port number used by the Remote Development Service. In <number>, specify the port number in decimal form. |
logdir | /logdir:<path> | Windows shared application data folder (*) | Specify the folder to which remote development service log files are output. In <path>, specify the folder path. To use a path that contains spaces, enclose the start parameter in quotation marks ("). |
maxlogsize | /maxlogsize:<size> | 128 | Specify the maximum size of the Remote Development Service log file. In <size>, specify the maximum size in decimal form. Its unit is kilobytes. If 0 is specified, the Remote Development Service does not output log file |
maxloggen | /maxloggen:<number of generations> | 2 | Specify the number of generations of Remote Development Service log file backups to be retained. In <number of generations>, specify the number of generations in decimal form. If n is specified, n backups (rds.xxx.log) are retained. If a number greater than 999 is specified, 999 is considered to be specified. If 0 is specified, no backup is retained. |
*: This depends on the version of Windows. Refer to "The path of the log file" under "9.2.1.1.3 Log files of the Remote Development Service".
The ftpd services are installed with their default settings when the operating system is installed on the Solaris server, and always start automatically.
Note
No start setting for the rexec service are already configured when the Solaris operating system is installed. The following operations must be performed:
Checking the status
Execute the following command to check the status:
# svcs -a | grep rexec disabled 18:28:10 svc:/network/rexec:default
If "disabled" is displayed at the beginning of the execution results, start the rexec service.
Starting the rexec service
Execute the following command to start the rexec service:
# svcadm enable svc:/network/rexec:default
In most cases, to change the system settings of the Solaris server involves checking the contents of the setting file, and modifying them as necessary.
Check the service status.
inetd (Internet daemon) invokes the ftpd and rexec services on the Solaris server. Therefore, the contents of the following files should be checked:
/etc/services
/etc/inetd.conf
If valid descriptions of the ftpd and rexec services are found in /etc/services and /etc/inetd.conf, skip the remaining steps in this section. See the examples below. If the line in which ftpd or rexec or both are set is commented out ("#" is added at the beginning of the relevant line), then the remaining steps must be performed.
Example for /etc/services
# # Network services, Internet style # : ftp 21/tcp : ## UNIX specific services ## these are NOT officially assigned #
Example for /etc/inetd.conf
: # FTPD - FTP server daemon ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.ftpd -a : # REXECD - rexec daemon (BSD protocols) exec stream tcp nowait root /usr/sbin/in.rexecd in.rexecd exec stream tcp6 nowait root /usr/sbin/in.rexecd in.rexecd :
Change the settings of the services.
Modify /etc/services and /etc/inetd.conf.
Start the services.
Restart inetd because the ftpd and rexec services are started under the control of inetd.
Execute either the following command:
# kill -HUP `cat /var/run/inetd.pid`
Or execute the following:
# ps -ea | grep inetd inetd process id is displayed. # kill -HUP inetd process id D
The ftpd and rexec services may not be installed along with the operating system on the Linux server. Therefore, the first step is to determine if their packages are installed. A Linux system may provide tools with a GUI that can be used to configure system settings. Since there are considerable differences between the versions and individual system settings in differing GUI tools, a method for using commands to perform operations is presented below.
Check the packages.
Execute the rpm command in the following format to determine if the packages are installed:
# rpm -query package-name
Enter the following package names for ftpd and rexec:
ftpd : vsftpd
rexec : rsh and rsh-server
If the following information is displayed, the packages have been installed, and you can proceed to checking the service status.
# rpm -query vsftpd vsftpd-2.0.1-5 # rpm -query rsh rsh-0.17-17 # rpm -query rsh-server rsh-server0.17-17
If the package information is not displayed, one or more packages must be installed.
Note
The type of ftpd package used for the Linux system depends on the version and distribution. The following may be used:
wu-ftpd
proftpd
Install packages.
Execute the rpm command to install each package.
rpm -Uvh package-name
Check the service status.
Execute the /sbin/chkconfig command in the following format to determine if the services are configured to start when the system starts.
/sbin/chkconfig --list service-name
For example, if the following results are obtained, startup of ftpd (vsftpd) and rexec when system starts has been disabled using their respective settings.
# /sbin/chkconfig --list vsftpd vsftpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off # /sbin/chkconfig --list rexec rexec off
Change the setting for a service as necessary.
Execute the /sbin/chkconfig command in the following format to confirm that the service will start when the system starts:
/sbin/chkconfig [--level run-level] service-name on
In the following example, the setting is changed so that the service is started when the system starts, and the changed setting is checked:
# /sbin/chkconfig --level 5 vsftpd on # /sbin/chkconfig --list vsftpd vsftpd 0:off 1:off 2:off 3:off 4:off 5:on 6:off # /sbin/chkconfig rexec on # /sbin/chkconfig --list rexec rexec on
Start the services.
Execute the /sbin/service command in the format shown below to start the services. Since the rexec service is started under the control of xinetd, restart xinetd.
# /sbin/service vsftpd start vsftpd start: [ OK ] # /sbin/service xinetd stop xinetd stop: [ OK ] # /sbin/service xinetd start xinetd start: [ OK ]
