VCOM for i5, OpenVMS, Windows & Unix. Release Notes May 2013

Transcription

1 VCOM for i5, OpenVMS, Windows & Unix Release Notes May 2013 Please read the following Release Notes before installation and have also a check in for last minutes information. New Functionality IPv6 Support on UNIX and Windows Platforms VCOM now supports the IPv6 protocol on UNIX and Windows (Windows 7/Server 2008 R2) platforms. Both VCOM links and client/server connections will work over IPv6. Clients using the IPv4 protocol can connect to an IPv6 server provided that the host platform supports dual-stack (IPv4/IPv6) mode. IPv6 and VCOM Links In order make servers accept both IPv6 and IPv4 connections, the link driver's listening socket must be bound to an IPv6 local address, preferably the IPv6 wildcard address 0::0 in the Listen IP address configuration parameter. For example: Listen IP address : 0::0 If you, for some reason, want to restrict VCOM links to use only the IPv4 protocol, you can explicitly bind the server's listening port to an IPv4 address, preferably the wilcard address For example: Listen IP address : IPv6 and VCOM TCP API Servers In order make servers accept both IPv6 and IPv4 connections, the API server's listening socket must be bound to an IPv6 local address, preferably to the IPv6 wildcard address 0::0 by using the -b option. For example (UNIX): vcomservtcp x 200 -b 0::0 If you, for some reason, want to restrict VCOM servers to use only the IPv4 protocol, you can explicitly bind the server's listening port to an IPv4 address, preferably the wilcard address For example (UNIX): vcomservtcp x 200 -b

2 IPv6 Addresses within vcomhttp URL URLs use the colon character to separate host names and port numbers from each other. As IPv6 address notation includes colons, the numeric IPv6 address must be within brackets as specified by RFC IPv6 Addresses in the vcmaddrchk Plugin Configuration File The configuration file for the vcmaddrchk plugin now accepts IPv6 addresses and address ranges as well. vmu show client Display Format Changed In order to accommodate the longer IPv6 addresses some less important fields have been excluded from the one-line brief display. Full information can be obtained by using the new vmu show client full command. Dedicated API Servers In order to have the possibility to dedicate a TCP API server to certain clients the -x option is now introduced. This option then excludes this TCP/IP API server process from being part of the load balancing mechanism. When having a mix of both remote and local clients we strongly recommend to use it on UNIX and IBM i platforms in order to force the local applications to use the more efficient UNIX domain sockets communication. Better Performance for VCOM CS Service Several performance enhancements are made for the VCOM inter-process communications system and for the conversation service. Error Corrections API Server - vcomdsmon deadlock On some circumstances VCOM could hang due to a deadlock. This has now been corrected. VOA vping Failed Stricter check for operator command parameters introduced in VCOM version caused the voa vping command to fail. This has now been corrected. VCOM Common Logging Created Empty Files When collection of common logging events was enabled, VCOM created empty files when no events were collected. This has now been corrected.

3 Incorrect UTC offset in VCOM Common Logging Data UTC offset in common logging data timestamp had incorrect sign, for example -02:00 instead of +02:00 for central European daylight savings time. This has now been corrected. Translation table A7 corrected Duplicate of (euro) removed. Correction in translation A translation error could occur under some extremely rare conditions. Timeout on cssend Under heavy load cssend could return VCOM_RC_TIMEOUT (-31) although the data was sent successfully. When this occurred, a VE_PER_USE error was logged as well. This has now been corrected. Platform Specific Important Notes IBM i Replacing version that couldn't use UDS API servers. Performance improvements in conversations. OpenVMS New Functionality Support for Decnet ended Decnet is no longer supported as protocol for VCOM to VCOM communication. ApiServer If the installation procedure detects that no Api server is defined in vcom_udf:lineproc.dat, then an api server of type ICC will be configured. Error Corrections TRCMON not started The distr/conv trace process TRCMON is not started by default. Now corrected. Uncalled error from VCOMSERVICC

4 Message "Failed to delete logical name for host..." is removed from process VCOMSERVICC Inconsistency in dostart.com Starting a single process with DOSTART the priviledges will not be set correctly. When starting the attributes will be taken from but the corresponding VCOM_APPL:RUN_*.COM will be used. Also the priviledges will be set incorrectly. This inconsistent behavior is now corrected. Unix New Functionality Better Performance on DS Commits Committing written data to disk using fsync entails two disk operations, one for data and one for metadata. VCOM now uses fdatasync, which does not commit metadata to disk unless vital information (such as file size) has changed. Error Corrections Restrictive umask Settings Prevented Applications from Connecting to a Server Restrictive umask settings, for example 077, on VCOM's admistrator account prevented applications running on other user accounts from connecting to the VCOM server. This has now been corrected. Lost Wakeups in VCOM's Interprocess Communications Because of a non-atomic semaphore test/set operation, wakeups of VCOM processes could be lost. This typically caused a delay up to one VCOM clock tick. This has now been corrected. Linux / zlinux only Low UNIX Domain Datagram Queue Length may Slow Down VCOM Linux systems have low default value (10) for Unix domain sockets datagram queue length, which slows down VCOM under heavy load. You can increase this limit by the following command: # echo 2000 > /proc/sys/net/unix/max_dgram_qlen In order to make this change permanent, edit the /etc/sysctl.conf file and add the following line: net.unix.max_dgram_qlen = 2000

5 Windows IPv6 Support on Windows Support for dual stack (IPv4/IPv6) was introduced in Windows Vista and Windows Server This means that VCOM does not support IPv6 on Windows XP/Windows Server 2003 platforms. Error Corrections Common Logging did not Work on Windows If VCOM's log directory path contained spaces, the common logging files were no created correctly. This has now been corrected. Semaphore Timeout on API Server Sockets Receive from clients on Windows API server sometimes fails with error ERROR_SEM_TIMEOUT (121), which was treated as fatal and the client connection was terminated by the server. VCOM now treats this error as non-fatal and restarts the read operation. Fresh Install Before you begin Install notes for VCOM Server v5.5.2 on Unix As it is possible to run several VCOM servers on a UNIX host, we strongly recommend having a separate user for each VCOM node. Never install VCOM as root! On most UNIX platforms you can choose between 32 and 64-bits server. Which one to choose is not especially important because VCOM ships with both 32 and 64 bits libraries. Note the following: On 64-bits Linux platforms, 32-bits system libraries are not always installed by default. If your platform supports RAM disk, we recommend using it. Finally, you must decide the VCOM network and node names. Install procedure 1. Log on to the VCOM administrator's account. In this example we have logged on to the vcomt1 sccount. 2. Get the VCOM software distribution. 3. Unpack and extract the archive. In Linux you can unpack the gzipped tar archive using the following command: tar xzvpf vcom552_linux_x86.tar.gz vcom552/

6 vcom552/bin64/ vcom552/bin64/vcomopmon vcom552/bin64/vcompspl... vcom552/lib/libvcom64.so.3.0 vcom552/lib/libvcom64.so vcom552/lib/libvcom.so.3.0 vcom552/lib/libvcom.so On other UNIX platforms you need to uncompress the archive before extracting it. 4. We recommend to create a symbolic link and point it to the VCOM servers root directory. This will facilitate handling of future versions as described in the Migrate section later in this document. For example: ln -s vcom552 vcom ls -l lrwxrwxrwx 1 vcomt1 vcomt1 7 Apr 23 14:08 vcom -> vcom552 drwxr-xr-x 9 vcomt1 vcomt Apr 23 14:08 vcom Move to the VCOM server's root directory using the symbolic link. cd vcom pwd /home/vcomt1/vcom 6. Start installation./install.sh Retrieving system information. VCOM Installation Menu version Install No existing VCOM environment detected. If your intention is to migrate or upgrade an existing VCOM node exit this procedure, execute the VCOM login script (vcomdef.sh) and run install.sh again. 0. Exit Enter choice: 1Enter VCOM_NETWORK name to use (Max 8 characters): US Enter VCOM_NODE name to use (Max 8 characters) : AUSTIN Enter VCOM_ROOT: [/home/vcomadm/vcom]: <CR> (S)mall (M)edium or (L)arge VCOM installation:[medium]: S 32 or 64 bit VCOM:[64]: <CR> installation set to 64 bit mode Ramdisk found at /dev/shm. Using ramdisk may help to improve VCOM perfomance. Would you like VCOM to use ramdisk? [y/n]: y Generating vcomcsproc.dat... Generating vcomdsproc.dat file... Installation completed!

7 Please run ". /home/vcomdev/vcom/dat/vcomdef.sh" to set new VCOM environment. Installing and Migrating Settings from an Existing VCOM Node Typical setup for this installation is like the following: ls -l total 8 lrwxrwxrwx 1 vcomdev spp 7 Jan 7 13:53 vcom -> vcom406 drwxr-xr-x 11 vcomdev spp 4096 Jan 5 11:04 vcom406 VCOM is installed in the directory vcom406 and the symbolic link vcom points to that directory. All VCOM environment variables refer to that symbolic link, not the real root directory. For the new version we simply create a new root directory, migrate the settings from the existing VCOM node and, when done, point the symbolic link to the new VCOM root directory. The existing installation will remain untouched making it easy to revert back to it just by pointing the symbolic link to the root of the old version. 1. Log on as VCOM administration and make sure that the VCOM environment is set up. If possible, stop VCOM. It is possible to migrate a running VCOM, however there is a risk that configuration changes made afterwards won't make their way to the new VCOM.. dat/vcomdef.sh - or- if you are using the C-shell % source dat/vcomdef.csh vcomstop 2. Move to the directory where you want to create the new VCOM root directory: cd /opt/vroot 3. Get the software distribution and unpack it. uncompress vcom552_sunos_x86.tar.z tar xvpf vcom552_sunos_x86.tar x vcom552, 0 bytes, 0 tape blocks x vcom552/bin64, 0 bytes, 0 tape blocks x vcom552/bin64/vcomopmon, bytes, 1228 tape blocks x vcom552/bin64/vcompspl, bytes, 653 tape blocks x vcom552/bin64/vcomshutdown, bytes, 291 tape blocks.. 4. Move to the vcom552 directory: cd vcom Execute the vcommigrate.sh script. It needs two arguments, the current VCOM_ROOT directory and the directory to become the new VCOM root. Placing the VCOM_ROOT inside double quotes helps get better error diagnostics if your shell is set up to treat undefined variables as errors../install.sh Retrieving system information. VCOM Installation Menu version Install 2. Upgrade existing VCOM node US2570.UB1204 at /home/vcomdev/vcom 3. Migrate existing VCOM node US2570.UB1204 at /home/vcomdev/vcom 0. Exit

8 Enter choice: 3 Migrate configuration to version for the following VCOM node: VCOM network : US2570 VCOM node : UB1204 VCOM root : /home/vcomdev/vcom New VCOM root: /home/vcomdev/vcom552 VCOM version : Is this information correct [ y/n ]: y Starting migration... Saving configuration file from the software distribution to./org directory... Copying VCOM configuration database (.tab) files... Copying other VCOM configuration (.dat) files... Copy tcpdef.dat [ y n ]: y Copy tcpdef_rl.dat [ y n ]: y Copy vcomservts.dat [ y n ]: y Copy vcomtcps.dat [ y n ]: y Migrate setting for the vcomdef.sh and vcomdef.csh files. The settings are migrated from the existing vcomdef.sh file. Check if VCOM_APPS and VCOM_APPLIB directories exist and copy their contents... Migration completed successfully. Next steps require that the VCOM node being migrated is shut down and all VCOM applications are stopped. Run./migrate_distr.sh passing the absolute path to the new VCOM distribution data base directory. The old VCOM environment must be in effect when running this script. After that you may proceed to update the symbolic link to point to the new VCOM. Then log off and log on again and execute the vcomdef.sh (or vcomdef.csh if you are using the C shell). Before starting VCOM, run the check_dirs.sh script. It will check that the directories pointed to by the various VCOM environment variables exist. 6. Next steps require that the VCOM node being migrated is shut down and all VCOM applications are stopped. Run./migrate_distr.sh passing the absolute path to the new VCOM distribution data base directory. The old VCOM environment must be in effect when running this script. After that you may proceed to update the symbolic link to point to the new VCOM. Then log off and log on again and execute the vcomdef.sh (or vcomdef.csh

9 if you are using the C shell). Before starting VCOM, run the check_dirs.sh script. It will check that the directories pointed to by the various VCOM environment variables exist. 7. At this point you should check that the following configuration files have been correctly migrated: vcomdef.csh vcomdef.sh vcombasdef vcomcsproc.dat vcomdsproc.dat vcomuserproc.dat All these files are located in the dat directory of the new VCOM. The original template files from the software distribution are saved in the directory./org. 8. Before proceeding stop VCOM if you have not done that yet. Also make sure that all VCOM applications are stopped before proceeding to migrate the distribution data base. 9. If you have distributions, they must be migrated and converted into version 3.6 format. Run the migrate_distr.sh script. It needs the new VCOM distribution database directory as an argument:./migrate_distr.sh /opt/vroot/vcom551/db 10. Next update the symbolic link to point to the new VCOM root: cd /opt/vroot rm vcom ln -s vcom551 vcom It should now look something like this: ls -l lrwxrwxrwx 1 vcomdev spp 23 Apr 23 16:04 vcom -> vcom552/ drwxr-xr-x 14 vcomdev spp 4096 Oct 10 08:54 vcom406/ drwxr-xr-x 14 vcomdev spp 4096 Apr 23 16:00 vcom552/ Next log off and log on again. Then execute the vcomdef.sh (or vcomdef.csh if you are using the C-shell) if these scripts are not invoked by your login scripts.. dat/vcomdef.sh - or- if you are using the C-shell % source dat/vcomdef.csh 11. Move back to the inst_upg directory of the software distribution and execute the check_dirs.sh script. It checks that the directories specified by the VCOM environment variables exist and otherwise attempts to create them. cd inst_upg./check_dirs.sh 12. If you need to grant permissions for users outside the VCOM group, execute the vcomperms.sh script. 13. You are now ready to start the upgraded VCOM: vcomstart Upgrade 1. Log on as VCOM administration and make sure that the VCOM environment is set up. 2. Unpack the VCOM software distribution to a temporary location. For example: cd /tmp tar xzvpf vcom552_linux_x86.tar.gz 3. Stop VCOM if it is running. cd../vcom vcomstop 4. Move to the vcom552 directory where you have extracted the software distribuition: cd /tmp/vcom /install.sh Retrieving system information.

10 VCOM Installation Menu version Install 2. Upgrade existing VCOM node US.HOUSTON at /home/vcom 3. Migrate existing VCOM node US.HOUSTON at /home/vcom 0. Exit Enter choice: 2 Upgrade the following VCOM node to version VCOM network : US VCOM node : HOUSTON VCOM root : /home/vcom VCOM version : Is this what you want to do [ y/n ]: y Starting upgrade... Saving the bin, examples, include and lib directories... Upgrading the bin, examples, include and lib directories... Generating vcomcsproc.dat... Generating vcomdsproc.dat file... Upgrade done. 6. At this point you should check that the following configuration files have been correctly updated: vcomdef.csh vcomdef.sh vcombasdef vcomcsproc.dat vcomdsproc.dat vcomuserproc.dat All these files are located in the directory pointed to by the environment variable VCOM_DAT. The original files are saved in the directory VCOM_ROOT/saved/dat. 7. Next log off and log on again. Then execute the vcomdef.sh (or vcomdef.csh if you are using the C-shell) if these scripts are not invoked by your login scripts.. dat/vcomdef.sh - or- if you are using the C-shell % source dat/vcomdef.csh 8. Move back to the inst_upg directory of the software distribution and execute the check_dirs.sh script. It checks that the directories specified by the VCOM environment variables exist and attempts to create those that may be missing when upgrading an ancient VCOM version.

11 cd /tmp/vcom552/inst_upg./check_dirs.sh 9. If you need to grant permissions for users outside the VCOM group, move back to the inst_upg directory and execute the vcomperms.sh script. 10. You are now ready to start the upgraded VCOM: vcomstart