openft_ux-readme.txt Fujitsu Siemens Computers openft V8.1A20 for Unix systems openft-ftam V8.0B for Unix systems March 2006 Release notice

Transcription

1 Fujitsu Siemens Computers openft V8.1A20 for Unix systems openft-ftam V8.0B for Unix systems March 2006 Release notice RELEASE NOTICE openft V8.1A20 for Unix systems openft-ftam V8.0B for Unix systems 1 General 1.1 Documentation 2 Product use Seite 1

2 2.1 Resource requirements 2.2 Software configuration 2.3 Product installation 2.4 Product operation 2.5 Obsolete functions (and those to be discontinued) 2.6 Incompatibilities 2.7 Restrictions 3 Software extensions 4 Hardware support 1. General This file contains important information, which is not noted in the Product Information Sheet or manuals, for using openft V8.1A for Unix systems and openft-ftam V8.0B for Unix systems under the ReliantUNIX, Sun-Solaris (Intel and SPARC), Linux, Linux390, AIX, HP-UX, OSF1(Tru64), SCO OpenServer and UnixWare operating systems. The release level is that of March openft V8.1A for Unix systems may only be used on the Unix system for which a license was purchased. The FTAM functionality (openft-ftam V8.0B for Unix systems) may only be enabled on the systems for which a corresponding license was purchased. If one or more previous versions are skipped when the product is installed, the installation information from the Release Notices of the previous versions must be noted. The release openft V8.1A20 is only available on Sun-Solaris (SPARC and Intel), Linux, Linux390 and HP-UX. On other plattforms openft V8.1A00 is valid anymore. Open Source modules that are subject to the GNU public license are used for the tool command library and graphical user interface. The files concerned are not subject to the openft license and can be copied and passed on without restrictions as long as the GNU public license is observed. The following files are concerned: - ft_tar, ft_gzip and ft_diff in directory /opt/openft/bin - all files in directory /opt/openft/tcltk and its subdirectories - all files in directory /opt/openft/scripts/lib 1.1 Documentation New manuals were published for the product openft V8.1A for Unix systems and can be ordered under the following delivery units: Seite 2

3 openft V8.1 for Unix systems U24846-J-Z User Guide openft V8.1 for Unix systems System Administrator Guide U24847-J-Z Printed manuals can be ordered under: 2. Product use 2.1 Resource requirements The products openft V8.1A for Unix systems and openft-ftam V8.0B for Unix systems require approximately 31 MB storage space on the hard disk plus an additional 1 MB for each instance. Approximately 2 MB main memory is required for each fta process plus 150 KB for each actual job. The /var partition should be dimensioned large enough to contain the administration files as well as logging and trace files that are stored in it. If necessary, /var/openft can be stored in its own, separate or large partition via a symbolic link. 2.2 Software configuration ReliantUNIX as of V5.44 Solaris (SPARC) as of V7 Solaris (Intel) as of V2.6 Linux as of SuSE 6.4 (kernel ) as of RedHat 6.2 (kernel ) or compatible Linux distributions Linux390 as of SuSE 8.0 (Kernel ) AIX as of V4.2 HP-UX as of V11.00 SCO OpenServer as of release OSF1 (Tru64) as of V5.0 UnixWare as of V7.1.1 openft V8.1A20 on Sun Solaris (SPARC) requires Sun Solaris 9. On Sun Solaris 7 and 8 (SPARC) openft V8.1A10 is available furthermore. CMX V5.1E40 is required for ReliantUNIX and SMAWcmx V6.0A is required for Sun-Solaris(SPARC). AIX V5.1 is required for using the instance concept with CMX V6.0. If CMX is not installed on the system, PCMX, that is supplied with openft, must be installed. In this case, connections can only be made over TCP/IP. At least JAVA V1.3 is required for using the JAVA interface. Further information on software configuration can be found in the Product Information Sheet. (see also Product installation The delivery unit openft for Unix systems comprises the following packages: PCMX Seite 3

4 openft: basic package with German and English user interface comprises FT (File Transfer Unix systems) FTAM (File Transfer OSI support) FTAC (File Transfer Access Control) The delivery unit openft-cr for Unix systems comprises the following package: openft-cr: encryption module for openft Installation must be carried out under the root ID. Before installing openft, CMX or PCMX must be installed and the tnsxd (and cmxredd with PCMX) process must be started. Proceed as follows for changing from CMX or SMAWcmx to PCMX (only relevant for ReliantUNIX and SUN-Solaris): 1. Deinstall CMX (pkgrm CMX or SMAWcmx) 2. Delete the "DIR1" directory as TNS entries can no longer be used (rm -r /opt/lib/cmx/dir1) If you want to continue using TNS backup files created with CMX V5/V6 in tnsxfrm format with PCMX, the version number in the first line must be changed to 4.0. The language is set with the LANG environment variable New installation The available "plug and play" installation can be used if you have no SNA connection. If you do have an SNA connection, the information in the system administrator manual must be noted. With a new installation, the following steps are made automatically in addition to reading in the product software: - Make standard TNS entries for openft or modify existing entries - Set operating parameters to default values - Set the processor name; the processor name of the operating system is entered - Enter the DNS name as the instance ID; if no DNS name exists, the processor name of the computer is entered - Install the instance-global and instance-specific rc files - Create a key pair set - Start the file transfer Update installation An update installation is carried out if openft V8.0 is already installed. If an openft version earlier than V8.0 is installed, it must be deinstalled before openft V8.1A is installed. FTAC environments exported in openft V7 can be imported in V8.1. With an update installation, you must ensure that the old trace and diagnostic files are deleted, currently running jobs are terminated and open graphical user interfaces are closed. The new instance-global rc file is installed; the old file is no longer saved. To ensure that all instances are automatically updated during the update, you should activate all deactivated instances with ftcrei before making the update installation. Otherwise, all deactivated instances must be updated with the ftupdi command after the installation. The following steps are executed during installation for all openft instances: - The file transfer is stopped - Existing jobs are unconditionally deleted from the job Seite 4

5 queue, whereby any follow-up processing is initiated - The product software is read in - Operating parameters are taken over and the DNS name is additionally entered as the instance ID; if no DNS name exists, the processor name of the computer is entered - The logging file and the FTAM catalog is taken over as are also the existing admission profiles and sets, and security level 1 is set to level 90 - The language setting from the previous version is taken over - The instance-specific rc file is installed after the rc file from the previous version is saved to the file /var/openft/<instance>/etcinit/openftinst.old - A key pair set is created - The file transfer is started Updating an installed openft V8.1 Exit all current openft V8.1 applications before starting the installation process. The installed version is automatically recognized and updated. During installation, openft and all active openft graphical interfaces are terminated. The key pair sets are taken over unchanged for all openft instances Deinstalling openft V8.1 Proceed as follows to deinstall: AIX: installp -u fileset where OPENFT.OPENFT, OPENFT-CR.OPENFT-CR or CMX.all can be specified for fileset HP-UX: swremove package where openft, openft-cr or CMX can be specified for package Linux: rpm -e package where openft, openft-cr or CMX can be specified for package The link from /emul/ia32-linux to /emul/ia32-linux must exist on Linux Itanium (ia64) (s ). OSF1: /opt/openft/uninstall.cr for openft-cr /opt/openft/uninstall.ft /opt/lib/cmx/cmx_pkg uninstall Use the pkgrm command in all other cases. for openft for CMX The instance directories that are located in /var/openft are deleted automatically during deinstallation Special considerations on the different platforms ReliantUNIX 1st Method: Mount the CD with mount -F hs -o dos device mountpoint (device e.g. /dev/ios0/sdisk005s0, mountpoint e.g. /cdrom0). Change into the mounted directory (here: cd /cdrom0) and call the procedure: 2nd method: Call cdinst. Seite 5

6 Sun-SOLARIS (SPARC/Intel) Insert the CD into the relevant drive. It will be mounted automatically. Change into the mounted directory. (here: cd /cdrom/openftv81) and start the procedure:. On Sun-Solaris 10 openft and PCMX will be installed automatically in the current zone (pkgadd switch -G). Live upgrade: openft for Unix systems does not provide active support for a live upgrade under Solaris, i.e. - Upgrading openft for Unix systems in the inactive boot environment is not supported, it must be done subsequently in what is then the live system (active boot environment) - You must make provision yourself for synchronizing with the current openft for Unix systems (/var/openft directory) before rebooting and thus restarting the system from the alternate boot environment. OSI stack on Solaris: To use the Solstice OSI for ISO connections via WAN (e.g. X.25) or LAN, you must first remove the relevant comment character (#) in the file cmxti.cfg (see /opt/lib/cmx/), in front of WANSBKA for WAN or OSITYPE for LAN and enter your own address (see also the instructions in the file) Linux To install, insert the CD in the relevant drive and mount it (e.g. mount /dev/cdrom). Change into the mounted directory (here: cd /cdrom) and start the procedure: The FTAM functionality is no longer installed automatically. To install it, use the command /opt/openft/bin/ftbin/install.ftam -i. Linux on Itanium (ia64): Due to a RPM incompatibility openft V8.1 can't be installed on Itanium Systems with Linux ia64. Before installation of openft and openft-cr a symbolic link from /emul/ia32-linux to /emul/ia32-linux must be created. For creation proceed as follows: cd /emul ; ln -s ia32-linux ia32-linux openft can be installed afterwards. Linux on /390 mainframes Linux-S runs as a VM2000 guest systen under BS2000/OSD on /S390 mainframes. VM2000 guest systems have no direct access to CD-ROM drives. Therefore all files of the directory linux390 from the openft product CD must be transferred to the Linux system (e.g. with ftp). Proceed as follows: Mount the CD on a Unix system with CD-ROM drive, change into the mounted directory and then into the directory linux390. Transfer the files cmx.ds install.all install.cmx Seite 6

7 install.ft openft.ds to the Linux /390 system and start the procedure Under Linux /390, any existing previous version must first be deinstalled AIX Insert the CD into the relevant drive and mount it with the following command: mount -v cdrfs -r device mountpoint (e.g. mount -v cdrfs -r /dev/cd0 /cdrom) Change into the mounted directory (here: cd /cdrom) and start the procedure: The FTAM functionality is no longer installed during a new installation. To install it, use the command /opt/openft/bin/ftbin/install.ftam -i. The FTAM functionality of an installed FTAM remains intact with an update installation (V8.0 to V8.1) or when updating V8.1. FTAM must be deinstalled if you have no FTAM license: /opt/openft/bin/ftbin/install.ftam -d HP-UX Insert the CD into the relevant drive and mount it with the following command: mount -o cdcase device mountpoint (e.g. mount -o cdcase /dev/dsk/c0d4t0 /cdrom) Change into the mounted directory (here: cd /cdrom) and start the procedure:. For technical reasons, the file transfer (fta -s) cannot be started automatically during installation. The FTAM functionality is no longer installed during a new installation. To install it, use the command: /opt/openft/bin/ftbin/install.ftam -i. The FTAM functionality of an installed FTAM remains intact with an update installation (V8.0 to V8.1) or when updating V8.1. FTAM must be deinstalled if you have no FTAM license /opt/openft/bin/ftbin/install.ftam -d SCO OpenServer Insert the CD into the relevant drive and mount it with the following command: mount -f HS,lower device mountpoint (e.g. mount -f HS,lower /dev/cd0 /cdrom) Change into the mounted directory (here: cd /cdrom) and start the procedure: Seite 7

8 OSF1 (Tru64) Insert the CD into the relevant drive and mount it with the following command: mount -r -t cdfs -o noversion device mountpoint (e.g. mount -r -t cdfs -o noversion /dev/disk/cdrom0a /cdrom) Change into the mounted directory (here: cd /cdrom) and start the procedure: Note: the symbolic links of the openft commands under /opt/bin are assigned the group name of the original login ID UnixWare Insert the CD into the relevant drive and mount it with the following command: mount -F cdfs -r device mountpoint (e.g. mount -F cdfs -r /dev/cdrom/cdrom1 /cdrom) Change into the mounted directory (here: cd /cdrom) and start the procedure: 2.4 Product operation The FTAC and FTAM functionality is also implicitly handed over with openft V8.1 for Unix systems. To use the FTAM functionality it is only necessary to purchase the relevant license (cf. 1.). For export regulation reasons, the free-of-charge delivery unit openft-cr V8.0 resp. V8.1A20 for Unix systems must be used in order to employ the encryption. Cluster configuration Cluster configuration is only supported for TCP/IP connections. No other adapters may be used by openft. To ensure this, any non-tcp/ip transport system entries must be removed from all openft-specific TNS entries. You will find configuration information on the product CD. Use of openft on Sun Solaris zones: Please note at setup of zones that /opt and /var must not be mounted loopback (no inherit-pkg-dir). They must be available separately in each zone in which openft shall be run. openft must be installed in global zone, if /usr is loopback mounted in local zone (inherit-pkg-dir: dir: /usr). openft and PCMX must be installed in each zone separately. For using the graphical interface on a zone the X11 runtime system must be available. If problems at connection setup to foreign implementations occur (RFC1006 of the foreign implementation does not accept userdata), set and export the environment variable NOCONRSUDATA before starting the fta process. The optimization of connection establishment will be switched off, if the variable is set. Sample: NOCONRSUDATA=1 ; export NOCONRSUDATA fta -s Seite 8

9 Language of the man pages under Linux If the default language setting is changed (with the ftlang command), this only becomes effective for the man pages under Linux after the cache is deleted (/var/cache/man/cat1/*.1.gz). With an SNA connection, it is no longer necessary to start TRANSIT before openft. It is therefore not necessary to restart openft if TRANSIT is restarted. If openft is to be connected to an SNA network, the products TRANSIT-CLIENT and TRANSIT-SERVER as of V3.5A10 must be installed on the openft host. On UnixWare systems, the command ifconfig net0 -rfc1323 must be issued before operating openft SNMP can only work together with one instance. The deciding factor is thereby the instance that was set when the agent was started. Files > 2 GB are supported on the ReliantUNIX, SUN-Solaris (SPARC/Intel), OSF1(Tru64), HP-UX, AIX and Linux platforms. No properties (e.g. sizes) are shown locally in the graphical user interface for files > 2 GB. These files cannot be viewed or processed. 2.5 Obsolete functions (and those to be discontinued) - not applicable Incompatibilities openft V8.1A20 on Sun Solaris (SPARC) requires Sun Solaris 9. On Sun Solaris 7 and 8 (SPARC) openft V8.1A10 is available furthermore. 2.7 Restrictions If you use md5 encryption or another encryption method different from DES on Linux distributions (i.e. RedHat or newer SuSE Linux), you can only process inbound jobs (transfer or file management) via FT profiles and not via "ID,,Password". The md5 encryption mechanisms or other encryption methods different from DES are not available to openft. Use of openft on Sun Solaris zones: openft and PCMX must be installed in each zone separately. SMAWcmx can only be installed in global zones. Please note at setup of zones that /opt and /var must not be mounted loopback (no inherit-pkg-dir). openft must be installed in global zone, if /usr is loopback mounted in local zone (inherit-pkg-dir: dir: /usr). Use on Itanium (ia64): openft V8.1 is a 32-Bit application and runs in emulated modus on Itanium. For this reason only C-programs are runnable, which are produced on a 32-Bit Linux. JAVA programs are not executable at this time. 3. Software extensions openft V8.1A has been extended over openft V8.0 by the following new functions: Seite 9

10 - Authentication As of openft versions 8.1 for Unix systems and Windows and V9.0 for BS2000 and z/os, openft supports an extended addressing and authentication concept for secure identity checks of the systems involved in a transfer. It is based on addressing the openft instances via network-wide unique IDs and exchanging partner-specific key information. This means that key pair sets can be created for each local openft instance and their public key made available to the partner systems. Conversely, public keys from partner systems are stored in the syskey directory in the instance file tree of the local openft instance. The local key is administered by the administrator with: - the -k switch of the fta command to create a key pair set - the new ftupdk command for updating public keys - the new -dk= switch of the fta command for deleting key pair sets The new -id= switch is provided in the fta command for defining the local instance ID. Instance IDs of partner systems are used for authentication as file names of the partner systems public key files. In addition, the instance IDs of the partner systems should match the address resolution by openft, if necessary with a TNS entry. - Integrity of transferred data The new -di switch of the ft and ncopy commands can be used to explicitly request an integrity check of the transferred data with openft partners as of V Extension of the openft instance commands openft instances created with openft V8.0 can be updated for V8.1 with the new ftupdi command. ftcrei now checks the version of the instance directory to be mounted. ftdeli now checks whether the instance to be deactivated is the currently set or the default instance. The path of the instance directory can be specified as selection criterion for ftshwi with the new -d switch. - New security level in the admission set A new, stricter security level 10 has been introduced for partner system authentication in the local system. The previous security level 1 for partners whose names are resolved via TNS, DNS or /etc/hosts has been shifted to security level 90. This change is made automatically by openft during an update installation. - Additional logging outputs FT logging records of jobs with openft partners now also contain information on the security functions used during the transfer. - Force/forbid encryption in the admission profile The new -c switch of the ftcrep and ftmodp commands can be used to force (-c=y) or forbid (-c=n) the use of encryption for a request via the admission profile. - New job status states In conjunction with the newly introduced authentication Seite 10

11 and data integrity, a number of new request status states can occur in the output of the fti -q or fti -l commands. - FTAM functionality FTAM is now also available for OSF1 - Further changes - The path of the instance directory can now be displayed with the new -d switch for ftshwi. - The previous restriction of pre- and post-processing timing out after 10 minutes no longer applies for openft partners as of V Encryption can now be disabled by setting the key length to 0. - The maximum record length for text and binary files has been increased to The maximum block length for text and binary files has been increased to Extensions to the graphical user interface - The contents of the syskey directory can be displayed with the new object "Public Keys" in the object tree. It can be used by normal users to determine whether a partner is authenticated. The system administrator can use the window to copy public keys in this directory via drag and drop. - With asynchronous requests, the transferred percentage is displayed in the request queue window as long as the job is still in the ACTIVE state. - The ID can be set in the operating parameters dialog field. The character set setting now offers the additional ISO8859 variants. The length of the transport unit has been extended to can now be specified for the key length if encryption is to be disabled. - The "Transfer file" dialog box provides the means for activating data integrity checks in the Options register card. The maximum record length has been increased to The "Create key" administration menu entry for key management has been renamed to a submenu "Key Pair Set Management". The submenu contains entries for: - creating a new key pair set - updating the public key files of the existing key pair sets - editing the file syspkf.comment - it also contains a menu item for each key pair set, in order to delete the key pair set concerned. - The contents of the "log/conslog" console message file can be displayed via a new menu entry in the menu "Administration". The menu entry is disabled if the user has no administrator rights or if the "log/conslog" file Seite 11

12 does not exist. openft_ux-readme.txt - Automation for FTAM partners (FTAC standard profile) An FTAC standard profile can be created in openft V8.1A for Unix systems for each ID with FTAM partners that specify a fixed access rights structure on the side of the partners. This profile can be used to define the access rights for all inbound jobs for which an ID and password was specified instead of an FTAC access authorization. This can set the defaults of the parameters that can be set in an FTAC profile for all accesses to an ID (e.g. follow-up processing, partners, etc.). The only restriction is that standard profiles cannot also be accessed via an FTAC access authorization. This means that specifying an access authorization other when creating and modifying a standard profile is not allowed, as are also specifying Valid (-v), Expiration date (-d) and Usage (-u). Standard profiles are accessed at the command interface with the name "@s". The profile name "*STD" can also be used in the graphical user interface. - Transferring files with fixed record length Until now, it was not possible to create or extend fixed record length files from openft for Unix systems to mainframe platforms (apart from binary data in later versions). As of this version, the -r=f<record_length> parameter can be used with the ncopy and ft commands to specify that the file is to be sent as a file with fixed record lengths. The actual record lengths must not exceed the record lengths specified with "-r=". The effect of -r=f<record_length> is as follows: together with the -t switch (with the openft protocol also without an additional format switch), the file is sent as a text file with fixed record length. If the records in the original file are shorter than this length, they are padded with spaces to the specified length. Together with the -b switch, the file is sent as a binary file with fixed record length (as with the combination -b -r=<record_length>). Together with the -u switch, -r=f<record_length> is currently handled as -r=<record_length>. For compatibility reasons, this combination should not be used. 4. Hardware support Please refer to the Product Information Sheet for the hardware supported by the products. (see also Seite 12

13 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009