transfer cft installation guide hp nonstop - · pdf filetransfer cft batch procedures 20 how...

Transfer CFT HP NonStopVersion 3.2.44 December 2017

Installation Guide

Copyright © 2017 Axway

All rights reserved.

This documentation describes the following Axway software:

Transfer CFT 3.2.4

No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, Axway.

This document, provided for informational purposes only, may be subject to significant modification. The descriptions and information in this document may not necessarily accurately represent or reflect the current or planned functions of this product. Axway may change this publication, the product described herein, or both. These changes will be incorporated in new versions of this document. Axway does not warrant that this document is error free.

Axway recognizes the rights of the holders of all trademarks used in its publications.

The documentation may provide hyperlinks to third-party web sites or access to third-party content. Links and access to these sites are provided for your convenience only. Axway does not control, endorse or guarantee content found in such sites. Axway is not responsible for any content, associated links, resources or services associated with a third-party site.

Axway shall not be liable for any loss or damage of any sort associated with your use of third-party content.

Contents

Preface 1

About Transfer CFT 1

Who should read this guide 1

Installation guide outline 1

Documentation 2

Support services 2

1 Introduction 3

Delivered components 3

Prerequisites 3

Disk space requirements 4

Additional requirements 4

End User License Agreement 4

Limitations 4

2 Install Transfer CFT 5

Upload the Transfer CFT archive 5

Add execution rights 6

Start the installation 6

Installation procedure results 7

Guardian files 8

Enter the Transfer CFT license key 8

Install the Guardian specific files 8

3 Post installation 10

Verify the installation 10

Check the Transfer CFT server 10

Check the Transfer CFT Copilot UI 11

Use the NonStop mode 13

Overview 13

Enable NonStop mode 14

Configure 15

Syntax 17

Help 19

4 Operating system specific features 20

System configuration and output 20

About the output file 20

About the system configuration file 20

Transfer CFTHP NonStop 3.2.4 Installation Guide i

Transfer CFT batch procedures 20

How it works 20

Event messages 26

Event messages format 26

Activate event log messages 27

Activate event accounting messages 28

Transfer CFT EMS 28

Transfer CFT APIs 30

Managing the API servers 30

Messages exchanges 30

Installation files 31

Operating system specific parameters 31

Platform specific characters 31

Platform specific parameters and values 33

5 Transfer CFT commands 35

About the commands 35

Prerequisites 35

Available commands 35

Launch PROFILE 35

Access CFTUTIL 35

Command structure 36

How to use the commands 36

Run a command 36

Redirect the command output 37

6 Update 39

7 Migrate 40

Partner and parameter files 40

System configuration file 41

Client exits and applications 43

8 Uninstall 44

Transfer CFTHP NonStop 3.2.4 Installation Guide ii

Preface

This document describes how to install Transfer CFT in a HP NonStop OSS environment.

About Transfer CFTTransfer CFT is the file transfer component in the Axway MFT platform, and provides a multi-platform, high-volume, file and message transfer service.

For more information on Axway products, visit www.axway.com.

Who should read this guideThis guide is intended for enterprise personnel involved in installing software and Axway Professional Services personnel. Familiarity with Axway products is recommended.

This guide presumes you have knowledge of:

l Your company’s business processes and practices

l Your company’s hardware, software, and IT policies

l The Internet, including use of a browser

l A basic knowledge of Transfer CFT and HP NonStop environments

Others who may find parts of this guide useful include network or systems administrators and other technical or business users.

Installation guide outlineThis guide explains how to perform a full installation of Transfer CFT. It also describes how to:

Introduction – Describes any prerequisite software or requirements.

Install – Describes how to perform a complete install as well as apply a service pack.

Post installation – Provides instructions on how to check if the installation was successful and set up Transfer CFT. Additionally it describes any tasks to perform before the administrator can log on to the product for initial configuration.

Migrate – Involves a change in product version and involves a configuration change (migrate partner and parameter files).

Uninstall – Describes how you can uninstall Transfer CFT.

Transfer CFTHP NonStop 3.2.4 Installation Guide 1

http://www.axway.com/

Preface

DocumentationTransfer CFT provides a complete set of documentation, covering all aspects of using the product. These documents include the following:

l Transfer CFT 3.2.4 Release Notes

l Transfer CFT 3.2.4 User Guide (HTML)

l Axway Supported Platforms Guide

Note This document makes references to HP Nonstop documents, such as the EMS Manuel. For any HP documentation referenced in this guide, you should check for the most recent version on the HP Support Center.

Support servicesThe Axway Global Support team provides worldwide 24 x 7 support, subject to validation of your license agreement. Email [email protected] or, for your local support telephone number, visit Axway Support at https://support.axway.com and click Contact Axway Support.


mailto:[email protected]

https://support.axway.com/

1 Introduction

This chapter describes how to install Transfer CFT 3.2.4 in a HP NonStop environment. HP NonStop exists on several hardware architectures, such as Itanium and Intel x86. On each of these runs a version of the HP NonStop OS, which is platform dependent. Therefore, there are two different versions of Transfer CFT for HP NonStop:

l Transfer CFT for HP NonStop Itanium, which runs specifically on HP NonStop for Itanium processors.

l Transfer CFT for HP NonStop x86, which runs specifically on HP NonStop for Intel x86 processors.

Note Transfer CFT for HP NonStop, globally stands for both versions of this product.

The NonStop OS basically consists of a Guardian layer, which is a lower level of the operating system, and an OSS layer that rests on top of Guardian and implements a Unix-like interface for the underlying Guardian layer. This document may contain references to Guardian, NonStop, or OSS, all of which refer to the same overall HP NonStop platform.

Note To accommodate changing product versions, the convention <version> is used in place of the actual product version in examples and lists. You should replace this with the actual value. Using the same logic, you can replace <os>, <arch>, and <xx> with your target platform details. For example, Transfer_CFT_<version>_<os>-<arch>-<xx> becomes Transfer_CFT_3.2.x_hp_nonstop_oss-ia64-32 when referring to Transfer CFT V3.2.x for HP NonStop OSS-IA64-32bits.

Note The Transfer CFT user interface may be referred to as Copilot in this documentation.

Delivered componentsAxway delivers the Transfer CFT product for NonStop OS as an electronic software download, which is available from the Axway support site at support.axway.com.

PrerequisitesPerform any prerequisites operations using the user account intended for the Transfer CFT installation in the OSS environment.


http://www.support.axway.com/

1 Introduction

Disk space requirementsThe following disk space calculations are the minimum requirements for a test environment. This calculation includes space required for service packs and a basic instance of the product. In a production environment, you must evaluate and modify the required disk and memory space per your requirements.

l Disk space: 430 MB for Transfer CFT for HP NonStop Itanium

l Disk space: 400 MB for Transfer CFT for HP NonStop x86

Additional requirements l Transfer CFT for HP NonStop Itanium is built on an H-series TNS/E Itanium machine. The operating system Release Version Update (RVU) used is H06.28.

l Transfer CFT for HP NonStop x86 is built on an L-series TNS/X x86 machine. The operating system Release Version Update (RVU) used is L15.08.

Note Even though it may be possible to run Transfer CFT for HP NonStop on an older RVU, we recommend that you run the product on a more recent RVU (or similar to the following) to ensure that the product stability and performance is not impaired by an old-system component. More information is available in the HP Release Version Update Compendium manuals.

l The Open System Services (OSS) subsystem should be installed.

End User License AgreementYou should read and accept the End User License Agreement (EULA) prior to installing Transfer CFT. The EULA file is in the directory where you decompressed the Transfer CFT package.

LimitationsCreateProcessAsUser is not supported on HP NonStop.


2 Install Transfer CFT

This chapter describes the steps to perform a Transfer CFT installation, as well as the automatic steps that occur when you run the installation procedure.

Note To accommodate changing product versions, the convention <version> is used in place of the actual product version in examples and lists. You should replace this with the actual value. Using the same logic, you can replace <os>, <arch>, and <xx> with your target platform details.

Upload the Transfer CFT archiveUpload the Transfer CFT package corresponding to the target platform to your machine. Perform this upload transfer in BINARY mode to ensure package integrity.

Example

Transfer_CFT_3.2.4_Install_hp_nonstop_oss-ia64-32_BN8580000.zip

Decompress the archive using the unzip command.

Example

Depending on your installation, the screen message may differ slightly from the following example.

/home/cftuser: unzip Transfer_CFT_3.2.4_Install_hp_nonstop_oss-ia64-32_

BN8

580000.zip

Archive: Transfer_CFT_3.2.4_Install_hp_nonstop_oss-ia64-32_

BN8580000.zip

creating: Transfer_CFT_OtherUnixes_V3.2.4/

inflating: Transfer_CFT_OtherUnixes_V3.2.4/TransferCFT_3.2.4_hp_

nonstop_oss-ia

64-32.run

inflating: EULA.txt

inflating: EULA.html

In the example, Transfer CFT package is unzipped in the Transfer_CFT_OtherUnixes_V3.2.4 directory.

Note Be certain to read the end-user license agreement.



Add execution rights Add execution rights to the Transfer_CFT_<version>_<os>-<arch>-<xx>.run package.

Enter:

chmod u+x Transfer_CFT_<version>_<os>-<arch>-<xx>.run

Start the installation Execute the install command to start the Transfer CFT installation procedure, replacing <installation_directory> with the directory where you want to install Transfer CFT.

You can use the following additional parameters:

l <guardian_installation_directory_prefix> installs the Guardian specific files

in its file system space. This parameter is optional. It is required only if you want to integrate Transfer CFT with Guardian procedures.

l --post_install_script <fullpathtopinstscript> runs a shell script during the installation procedure after the product has been initialized.

Enter:

./Transfer_CFT_<version>_<os>-<arch>-<xx>.run install <installation_

directory> [<guardian_installation_directory_prefix>] [--post_install_

script <fullpathtopinstscript>]

Examples

The following command installs Transfer CFT on the OSS directory /home/cftuser/CFT324. Additionally, the Guardian components are installed using /G/data14/cft32b (which is an equivalent of $DATA14.CFT32B) as a prefix.

/home/cftuser/Transfer_CFT_OtherUnixes_V3.2.4: ./ TransferCFT_3.2.4_hp_

nonstop_oss-ia 64-32.run install /home/cftuser/CFT324 /G/data14/cft32b

The following command installs Transfer CFT on the OSS directory /home/cftuser/CFT324. Additionally, a post installation script cft_postinst.sh is run at the end of the installation process.

/home/cftuser/Transfer_CFT_OtherUnixes_V3.2.4: ./ TransferCFT_3.2.4_hp_

nonstop_oss-ia 64-32.run install /home/cftuser/CFT324 --post_install_

script ./cft_postinst.sh



Installation procedure resultsThe Transfer CFT installation procedure automatically performs the following:

l Extracts the Transfer CFT package.

l Creates a Transfer CFT runtime.

l Initializes the sample configuration.

l Creates the Transfer CFT database.

l Creates a default user for Transfer CFT Copilot:

o Login: guest

o Password: guest



Guardian filesIf you opted to install the Guardian files, several files are created in the Guardian system space. The files' volume and subvolumes depend on the installation prefix that you provided.

For example, /G/data14/cft32b creates files where the volume name is $DATA14, the subvolume names begin with cft32b, and that ends with the values described in the following table.

Subvolume Description

<subvolume>IE Contains the Transfer CFT samples.

Some of these samples are copied in the user configuration volume <subvolume>UP, where they can be modified.

<subvolume>IF Contains the EMS dictionary and DDL template files.

CFTPLATE contains the Transfer CFT templates to be concatenated with the system template for an EMS collector. See the XCFTDDL section in Event messages, which describes the DDL template.

<subvolume>IX Transfer CFT executables and procedures.

<subvolume>IP Program samples.

<subvolume>IH Headers.

<subvolume>UD

Default Transfer CFT subvolume.

This is used when Transfer CFT needs to create a Guardian file.

<subvolume>UP Contains the procedures copied from the installation samples.

Enter the Transfer CFT license key After the installation completes, enter the Transfer CFT license key in the <installation_directory>/runtime/conf/cft.key file.

Install the Guardian specific filesIf you ran the installation procedure without providing the parameter <guardian_installation_directory_prefix>, the Guardian specific files were not installed. However, you can install these files later by calling the Guardian installation script.



1. Load the Transfer CFT profile:

<installation_directory>/runtime/profile

2. Install the Guardian files:

cftginst.sh /G/data14/cft32b

NOTE: You can use the following command to call the cftginst.sh online help:

cftginst.sh --help


3 Post installation

This chapter describes a series of checks that you should perform to verify your Transfer CFT installation. For more information on performing commands and using CFTUTIL, refer to the Transfer CFT 3.2.x User Guide.

Verify the installation

Check the Transfer CFT server 1. Load the Transfer CFT profile:

. <installation_directory>/runtime/profile

2. Verify the Transfer CFT version:

CFTUTIL about

3. Optionally, change the Transfer CFT Guardian process names if you are performing multiple installations. Because each Transfer CFT process is assigned a Guardian process name, these names should be globally unique.

l Use the cft.guardian.process_name_prefix UCONF parameter as described in the UCONF parameters section.

l Be certain to change this parameter's default value if you are running several Transfer CFT installations at the same time.

CFTUTIL uconfset id=cft.guardian.process_name_prefix,value=LB

4. Start the Transfer CFT server:

cft start

5. Verify that the default ports used in $CFTDIRRUNTIME/conf/cft-tcp.conf are available:

l 1761 (PeSIT Any protocol)

l 1762 (PeSIT Any protocol with SSL authentication)

If the ports are not available, modify the port(s) and re-apply the configuration:


https://docs.axway.com/u/documentation/transfer_cft/index.htm?version=3.2.4

3 Post installation

cftupdate $CFTDIRRUNTIME/conf/cft-tcp.conf

6. Check that Transfer CFT server is started:

cftping -v

cftlog

7. Perform a transfer:

CFTUTIL SEND PART=PARIS, IDF=TEST

8. Check the status of the transfer:

CFTUTIL LISTCAT

9. Stop the Transfer CFT server:

cft stop

10. Verify that the Transfer CFT server is stopped:

cftping –v

Check the Transfer CFT Copilot UI 1. Verify that the default port used for Transfer CFT user interface (1766) is available. If not,

change this port using the following command:

CFTUTIL UCONFSET id= copilot.general.serverport, value=<another_

port>

2. Start the Transfer CFT user interface (Copilot):

copstart

3. Connect to the Transfer CFT user interface as the default user.

l URL: http://hostname:1766/admin.html

l Login: guest

l Password: guest

4. Select the catalog, and check that you see your previous transfers listed.


3 Post installation

5. Disconnect from the Transfer CFT user interface.

6. Stop the Transfer CFT user interface:

copstop -f

Transfer CFT HP NonStop provides a start-process supervisor (CFTSUP) that can restart the Transfer CFT server or UI server in the case of an unexpected product stop. For more information, see Use the NonStop mode on page 13.


3 Post installation

Use the NonStop mode Transfer CFT HP NonStop provides a start-process supervisor (CFTSUP) that can restart the Transfer CFT server or UI server in case of an unexpected stop. This section presents the following NonStop information:

l Overview: describes the non-stop feature and compares it with the NonStop functionality delivered in previous versions

l Enable: how to activate the non-stop mode

l Configure: how to set additional non-stop mode parameters

l Syntax: the commands and their syntax

o Conventions: command conventions

o Messages: provides examples of using CFTSUP commands and returned messages

l Help: information on using command line help

OverviewThe CFTSUP interface consist of:

l A component watchdog called the supervisor

l A utility that allows you to:

o Start and stop the supervisor

o Start and stop the Transfer CFT server and Copilot server

o Display the status of these components

The differences between the CFTSUP interface and the NonStop mode delivered in Transfer CFT 2.3 are:

l The Transfer CFT server and Copilot server are both managed in NonStop mode.

l The CFTSUP interface replaces the former CFTNSMON and CFTNSHUT commands.

l Transfer CFT stops and is not restarted unless the reset command is set to RESTART=YES when you execute the Transfer CFT command CFTUTIL SHUT <...>.


3 Post installation

Enable NonStop modeThis section describes how to enable the NonStop mode and start Transfer CFT.

1. Activate the option:

CFTUTIL uconfset id=cft.guardian.nonstop,value=YES

2. Start the Transfer CFT server, for example, using the supervisor:

cftsup cft start

CFTL50I Started supervisor with process id $MDSUP

CFTL50I Started Transfer CFT with process id $MDAIN

3. Optionally, check the Transfer CFT server status. For example:

cftsup cft status

CFTL50I Transfer CFT ($MDAIN) is running

More information and additional commands are described in the following sections.

Recommendations l You can use the cftsup cft start command to start Transfer CFT, which also starts the supervisor. However, this does not mean the NonStop mode is running. To implement the NonStop mode, you must activate cft.guardian.nonstop in the UCONF configuration.

l If you need to kill the Transfer CFT server, for example, use the cftsup cft kill command to keep the component from restarting.


3 Post installation

ConfigureThe following table lists the UCONF parameters related to the NonStop option configuration. See the UCONF parameters on page 24 descriptions for more detailed information.

Parameter Default value Description

cft.guardian.nonstop No Enable the nonstop mode.

l Yes: Activate

l No: Deactivate

cft.guardian.collector <no value> Name of the EMS collector where the supervisor sends messages. See Customize the EMS collector for details.

cft.guardian.processor -1 Processor on which Transfer CFT is started.

cft.guardian.backup_processor

-1 Backup processor on which Transfer CFT is started.

cft.guardian.process_name_prefix

LA The first two letters of the Guardian process names.

Customize the EMS collectorTo use the same collector for the supervisor as for Transfer CFT log messages, perform the following steps:

1. Set the uconf cft.guardian.collector value to the name of the collector.

CFTUTIL uconfset id=cft.guardian.collector,value='$QACOL'

2. In the Transfer CFT configuration, modify the CFTLOG definition to:


3 Post installation

NOTIFY=’%uconf:cft.guardian.collector%’. For example:

CFTLOG ID = 'LOG0',

FNAME = '_CFTLOG',

AFNAME = '_CFTLOGA',

...

NOTIFY = ’%uconf:cft.guardian.collector%’,

CONTENT = 'FULL',

...

3. Interpret the modified CFTLOG object.


3 Post installation

Syntax Format

cftsup [component] Actions [Options]

Where:

component [ALL | SUPV | CFT | COPILOT]

l ALL (default): Action applies to all components

l SUPV: Watchdog utility

o Process is started with the name: prefix added to SUP

o For example: CFTL50I Started the supervisor with process id $LASUP

o Prefix = cft.guardian.process_name_prefix (the prefix in the example is LA)

o Stops when all components are terminated except if it was started explicitly as standalone process:

cftsup SUPV START

o In this case, it only stops with an explicit stop:

cftsup SUPV STOP

l CFT: Action applies to the Transfer CFT server

l COPILOT: Action applies to Copilot server

Actions [ START | STOP | STATUS | KILL | SHUT (for Transfer CFT server only)]

l KILL is only valid for the Transfer CFT and Copilot servers.

Note The SHUT option only apply to the Transfer CFT sever.

l CFTUTIL SHUT FAST=YES the equivalent is cftsup CFT SHUT FAST=YES

MessagesTable 1. Message when starting the supervisor and all components

cftsup start

CFTL50I Started supervisor with process id $MDSUP

CFTL50I Started Transfer CFT with process id $MDAIN

CFTL50I Started COPILOT with process id $MDCOP


3 Post installation

Table 2. Message when checking the status

cftsup status

CFTL50I SUPV ($MDSUP) status Running

CFTL50I CFT ($MDAIN) status Running

CFTL50I COPILOT ($MDCOP) status Running

Table 3. Message when performing a stop

cftsup stop

CFTL50I Processing command

CFTL50I Started COPSTOP with process id $MDCST

CFTL57E Error: Transfer CFT is still active (status=TERMINATING)

Table 4. Message when the supervisor is not started

cftsup supv status

CFTL59E Supervisor $MDSUP is not started


3 Post installation

HelpFrom the home directory, enter the help command. For example:

/home/axway/<user>: cftsup help

Syntax: cftsup [ALL|CFT|COPILOT|SUPV] Actions [Options]

: cftsup ? (or HELP) for a list of the component and actions

: cftsup Component ? (HELP) for actions to perform on components

Use command ? to display the parameter list:

/home/axway/<user>: cftsup "action" ?


4 Operating system specific features

This section describes features that are specific to Transfer CFT in a Tandem/Guardian environment.

System configuration and output

About the output fileTransfer CFT 3.2.4 HP NonStop reassembles all of the Transfer CFT process output in a main file, runtime/run/cft.out, whereas version 2.3.2 used either spooler output (one per process) or event messages (EMS).

About the system configuration fileThe system configurations file (CFGSYS) found in the previous version no longer exists in this version. The information that was in this file is now either obsolete (for example, processes output) or is managed by:

l Runtime/profile (sets environment variables)

l Transfer CFT uconf file (contains, for example, all parameters related to end of transfer procedure or server executions)

Transfer CFT batch proceduresTransfer CFT supports batch procedure from both native and OSS environments. This section describes the rules that determine the type of batch procedure and how it is executed.

How it works In the absence of TACL indicators in the first line of the batch procedure, the procedure is executed as a script in the OSS environment. If TACL indicators are present, certain characters and rules determines what happens next in the native environment (either Direct TACL processing or NetBatch processing).



The Decision rules section explains which characters indicate that it is a TACL procedure, and the exact type of processing that is used.

A batch procedure can contain a reference to Transfer CFT variables. The character used to indicate a variable is:

l &

o OSS script

o Example: &FNAME

l ^

o The same character as in the previous Tandem version

o TACL procedure

o Example: ̂ FNAME

Refer to Transfer CFT User Guide for a complete list of Transfer CFT variables.

Decision rulesIf the first line of the skeleton procedure begins with one of the following characters, it is a TACL procedure.

l ==

l ?

l #FRAME

l #PUSH



The characters following the initial " == " either set certain information for the TACL procedure or determine if the procedure is sent to the NetBatch interface for processing.

l == CFT^BT^FORCE^TACL ==

o A direct TACL procedure execution

o This execution type performed by default

o This parameter is kept to ensure compatibility with existing batch procedures

l == CFT^BT^FORCE^ZBAT ==

o Use NetBatch Interface

o To specify a given environment, you can declare it in the first line of the actual procedure. Add the following optional values in the first line of the skeleton procedure, in the order listed. If no values are declared, the UCONF default values are used.

o NetBatch process

o Job name

o Attachment-set

o For each field add a delimiter such as a colon (:), comma (,), or equal sign (=) followed by the parameter's value

Example

== CFT^BT^FORCE^ZBAT : $ZBA1 , JOBNAME , SETNAME ==

l NetBatch Process = $ZBA1

l Job name = JOBNAME

l Attachment Set = SETNAME

Processing 1. Regardless of if the procedure is OSS or native, Transfer CFT creates a temporary file with the

following locations and naming conventions:

l OSS: The same as on Transfer CFT Unix: /tmp/CFTxxxx

l Native: On the Transfer CFT default subvolume: CTMPnnnn

2> filenames $DATA14.CFT32BUD.*$DATA14.CFT32BUDCTMP0001 CTMP0002 CTMP0003 CTMP0004

2. Transfer CFT copies the skeleton in the temporary file, replacing variables with their real values (transfer information, file names, etc.).

3. Depending on the type of procedure, Transfer CFT:

l Starts the script (OSS)

l Starts the TACL direct processing

l Puts the temporary file in NetBatch for execution



Delete temporary filesThe started procedure MUST delete the temporary files, regardless of the environment.

l OSS

o rm $0

l NATIVE

o #PURGE [#IN]

o The same BTPURGE procedure as in the previous version is delivered and can be executed:

RUN <subvolume>UP.BTPURGE [#DEFAULTS]



UCONF parametersThe following unified configuration parameters are specific to HP Nonstop.

Parameter Default Description

cft.guardian.cftwrk The default working directory for the TACL and NETBATCH scripts.

The parameter is set with the default value of “<subvolume>UD” (see Guardian files on page 8) during the Guardian files installation.

cft.guardian.process_name_prefix LA The first two letters of the Guardian process names.

Each Transfer CFT process is assigned a name using this prefix and a suffix, which depends on the executable name.

For instance, using the default setting, CFTLOG is run with the name $LALOG with the Guardian convention (or /G/LALOG with the OSS convention).

If empty, no Guardian process name is given.

If you plan to run several instances of Transfer CFT at the same time on the same machine, you should assign each instance a unique value.

cft.guardian.processor -1 Processor on which Transfer CFT is started.

l -1 indicates that Transfer CFT is started on the processor from which the start-up command is executed

l Processor number

cft.guardian.backup_processor -1 Backup processor on which Transfer CFT is started.

l -1 indicates that no processor number is assigned

l Backup processor number




cft.guardian.priority -1 Guardian execution priority of the CFT processes.

l -1 means that CFT is started with the execution priority of the parent process.

l Process priority

cft.guardian.hometerm The Guardian home terminal for Transfer CFT processes.

l An empty value means that CFT is started with the OSS shell’s home terminal

l The value should be either set using the Guardian form ($ZTNT.#PTY4, $TTY), or the OSS form (/G/ZTNT/#PTY, /G/TTY)

cft.guardian.tcpip_resolver_name The TCPIP resolver name for Transfer CFT processes. Equivalent to the Guardian DEFINE TCPIP^RESOLVER^NAME.If set, the value should be a Unix pathname pointing to an existing resolver file.

cft.guardian.tacl.processor -1 Processor on which TACL is started.

l -1 means that TACL is started on same processor where Transfer CFT is running

l Processor number

cft.guardian.tacl.backup_processor

-1 Backup processor on which TACL is started. Valid only if different from -1 and from the cft.guardian.tacl.value.

cft.guardian.tacl.priority 90 Priority of a started TACL.

cft.guardian.tacl.output '$S.#ABTT' Output destination of the started TACL.

cft.guardian.tacl.home_terminal '$ZHOME' TACL home terminal.

cft.guardian.netbatch.process '$ZBAT' NetBatch process with which you send a request.

You can override this value in the first line of a TACL procedure.




cft.guardian.netbatch.jobname_prefix

'ZBBT' A jobname prefix used to build a jobname having 8 characters, and comprised of:

l This prefix

l A suffix that is composed of the last characters of the temporary file name


cft.guardian.netbatch.attachment_set

'NBASCFTLI' NetBatch attachment-set name.


cft.guardian.netbatch.priority 90 Priority of TACL run started.

cft.guardian.netbatch.selpri 4 JOB selection priority.

cft.guardian.netbatch.output '$S.#ABTZ' Output destination of the started TACL.

Event messagesTransfer CFT can issue Transfer CFT log messages and account records as Event Messages. A management application can then get these event messages by opening an Event Management System (EMS) distributor process and requesting the messages.

In this chapter, event-message tokens and their values are represented in DDL. For a quick explanation of DDL as it applies to SPI, refer to the SPI Programming Manual > Summary of DDL for SPI appendix.

For general information on how an application obtains event messages from a subsystem, refer to the EMS Manual.

Note For any HP documentation referenced in this guide, you should check for the most recent version on the HP Support Center.

Event messages formatTransfer CFT Guardian events were also available in the previous version, with the main difference being that each Transfer CFT process was defined as a sub system. In contrast, Transfer CFT version 3.2.4 only has one defined sub-system.

All messages have the following tokens:


http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=4201303&docId=emr_na-c02131958&docLocale=en_US

http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=4201303&docId=emr_na-c02131958&docLocale=en_US


Token Description

ZSPI-TKN-SSID The Transfer CFT subsystem ID, whose value is XCF2_VAL_EXTERNAL_SSID. This token is described in the SPI Programming Manual.

ZEMS-TKN-EVENTNUMBER

The event number, as described in the EMS Manual. Its value is one of the values described in the table below.

XCF2_TKN_SUBJ

The message subject for which the values are described in the Event messages table below.

XCF2_TKN_MSG

The message text.

For details about Transfer CFT LOG messages, see the Transfer CFT 3.2.4 Messages and error codes documentation.

The accounting messages are binary coded data, and are described in the exacct.h header.

Table 5. Event messages

The following table shows the relationship between the event, the subject, and the message type.

Event number EMS subject Event type

4 CFT INFO LOG Log information message

5 CFT WARN LOG Log warning message

6 CFT ERR LOG Log error message

7 CFT FAIL LOG Log failure message

8 CFT ACCOUNT Account message

Activate event log messagesThe CFTLOG object defines the Transfer CFT log file declarations. The name of the destination is provided in the fname parameter, which can be:

l A file: The files are created using a CFTUTIL command, as described in Transfer CFT Environment.

l Collector: Specifies the name of the collector to which log messages are written.

You can use the NOTIFY parameter of the CFTLOG object to combine the two destinations so that they refer to a Collector.


https://docs.axway.com/u/documentation/transfer_cft/3.2.4/Transfer_CFT_ErrorMessagesGuide_allOS_en.pdf


l NOTIFY: Name of the collector.

l OPERMSG: Allows you to filter the type of messages to be sent.

o This number is the sum of the values that correspond to the types of messages you want to filter

o For example, Operating error messages=16, System error messages=32, Operating fatal error messages=64, System fatal error messages=128 giving a total of 240

Note Refer to the Transfer CFT 3.2.4 Local Administration User Guide, available on the documentation portal, for a description of the CFTLOG object parameters.

Example

In the Transfer CFT configuration:

cftlog id = log0,

…

fname= ' log/cftlog',

afname= ' log/cftalog',

notify= '$COL',

opermsg= 240,

….

Activate event accounting messagesThe CFTACCNT object defines the destinations for the statistical data concerning terminated transfers (accounting messages). The possible destinations provided in the fname parameter are:

l A file: The files are created using a CFTUTIL command as described in Transfer CFT Environment.

l Collector: Specifies the name of the collector to which account messages are written.

Once defined, you can activate and link the object to the CFTPARM as shown in the following example.

Example

CFTACCNT ID=ACCNT1, TYPE=FILE, FNAME=$COL,...,MODE=REPLACE

CFTPARM ID=IDPARM0,...,ACCNT=ACCNT1,MODE=REPLACE

Transfer CFT EMSThe CFTPLATE file contains the Transfer CFT templates to be concatenated with the system template for an EMS collector.


https://docs.axway.com/u/documentation/transfer_cft/index.htm?version=3.2.4


The XCFTDDL and XCFTEMS files describe the Transfer CFT information and CFT EMS messages in DDL format.



Transfer CFT APIsYou can use Transfer CFT APIs either on HP NonStop, or via the native system. To use APIs with HP NonStop, refer to the services described in the Transfer CFT User Guide for Unix platforms.

On a Guardian platform, Transfer CFT APIs are available through a server. However, only one server can access the Transfer CFT catalog file at a time. This means that if an application is working with the catalog, the other applications are notified via a report and are set to pending. We therefore recommend using more than one server to avoid this limitation.

A Transfer CFT can be assigned up to nine servers that are named using the convention $xxAPn, where:

l $xx: is the Transfer CFT prefix selected at installation

l n: is a number between 1 and 9

These servers use a standard inter-process message exchange mechanism.

For more information on how to use Transfer CFT API services, refer to the Transfer CFT 3.2.4 Local Administration User Guide. An additional Transfer CFT API service called SRVEND is provided for Transfer CFT Guardian, which requests a server shutdown.

Managing the API serversTo start a server, you can use the CFTAPI TACL located in $volume.<subvolume>IX. This TACL starts the next server in the list beginning with 1.

To stop a server, use the Transfer CFT-specific SRVEND service, or use the STOP process command.

Both the API01 and API02 samples include the SRVEND service. For example:

API02 $xxAP1 SRVEND

Messages exchangesThe message structures are described in DDL and C language:

l The C files is derived from the DDL file

l Both the DDL and C header files are located in $volume.<subvolume>IH

l Except for the Guardian-specific message number at the beginning of the structure, the message information is the same as for other platforms



Installation filesThe following files are part of the installation:

l APIDDL: The DDL file describing the message structure

l APIC: The C header file resulting from the APIDDL compilation

l API01, API02: The sample C programs

Operating system specific parameters

Platform specific charactersFigure 1. Transfer CFT Guardian specific values

Notation Object Value

char_file Prefix for logical names =

char_mask Wildcard character ?

char_symb Prefix for symbolic variables ^

file_symb Prefix for a file name passed to CFTUTIL as a parameter @

Figure 2. File properties automatically retrieved for send operations

Notation Object

FSPACE YES

FLRECL YES

FBLKSIZE YES

FRECFM YES

FTYPE YES



Figure 3. FTYPE values and associated implicit FCODE default values for send operations

FTYPE FCODE

' ' BINARY

E ASCII

Figure 4. FTYPE, FRECFM, and FORG combinations for send operations

Guardiantype

Guardian code

File type

Implicit value for...

FTYPE FRECFM FORG

U # 101 Binary stream ' ' U SEQ

U = 101 Edit file E U SEQ

E # 1 Fixed sequential

' ' F SEQ

E = 1 Sequential, variable emulation

' ' V SEQ

R Direct fixed ' ' F [1] DIR

K Fixed indexed sequential

' ' F [1] IDX

Note Empty cells indicate that the information is not significant.

Note [1] You can also send variable length record files by setting FRECFM = V.

Figure 5. FTYPE, FRECFM, and FORG values for receive operations

FTYPE FRECFM FORG File TypeGuardian Type

Guardian Code

U Binary stream U 0

E Edit file U 101

F SEQ Fixed sequential E 0

V Sequential, variable emulation E 1

F DIR[2] Direct fixed R 0

V DIR [2]

Direct fixed, variable emulation R 1

F IDX [2]

Fixed indexed sequential K 0



FTYPE FRECFM FORG File TypeGuardian Type

Guardian Code

V IDX [2]

Indexed sequential, variable emulation

K 1

Note Empty cells indicate that the information is not significant.

Note [2] Read the file organization from the network, explicitly set FORG to FORG= ‘ ‘. Otherwise, FORG is always sequential (FORG = SEQ).

Platform specific parameters and valuesATTSUSER

Use the ATTSUSER parameter to set specific attributes for receiving native files. This parameter can take two values, FCODE and FORMAT.

FCODE

Forces the file CODE attribute. This value should be consistent with the file structure and the restrictions of the system. If FCODE is not specified, Transfer CFT sets the code per the table in Figure 5.

Example: ATTSUSER = 'FCODE=180'

The received file is created with 180 as the code.

FORMAT

Forces the file FORMAT attribute. This value is either 1 or 2. If FORMAT is not specified, Transfer CFT sets the format according to the estimated size of the received file. A file whose size is greater than 2GB has the format 2, while a file having a size less than 2GB has the format 1.

Example: ATTSUSER = 'FORMAT=2'

The received file is created with the format 2.

Use multiple values

Additionally, you can use multiple values:

Example: ATTSUSER = ' FCODE=180,FORMAT=1'

The received file is created with the format 1, and 180 as the code.

BUFFERED

If specified, this parameter forces the BUFFERED attribute for the Guardian file. The possible values are 0 (NO BUFFERED) and 1 (BUFFERED). If not specified, Transfer CFT does not force the attribute. A presentation of this attribute can be found in the File Utility Program (FUP) Reference Manual.



Example: ATTSUSER = 'BUFFERED=1'

The received file is created with a BUFFERED attribute set.


5 Transfer CFT commands

This chapter describes how to use Transfer CFT commands in a Tandem/Guardian environment.

About the commandsTransfer CFT offers a set of commands which can be used interactively or within procedures in your Guardian environment.

PrerequisitesPrior to executing Transfer CFT commands, you must install them. If you have not already done so, perform the task as described in Install the Guardian specific files on page 8.

You cannot use Transfer CFT Guardian 2.3.2 CFTUTIL commands with Transfer CFT 3.2.4.

Available commandsThree types of commands are available in the installed volume.<subvolume>IX:

l CFT: management commands to control the Transfer CFT product

l CFTUTIL: the command line interface for Transfer CFT

l CFTUTLX: the command line interface for Transfer CFT with INLINE parameters

l PKIUTIL: the command line interface to manage the local PKI

l PROFILE: customized file for accessing the other commands

A description of these commands is provided in Transfer CFT 3.2.4 Local Administration User Guide.

Launch PROFILEThe PROFILE file updates the PMSEARCHLIST so that it can call Transfer CFT commands from anywhere. It also contains PARAM and DEFINE entries, which are mandatory before using certain Transfer CFT commands such as CFTUTLX.

Before creating a NETBATCH attachment-set, you must call the PROFILE.

Access CFTUTILFrom the native command window enter the following to start, for example, CFTUTIL:



Example

$ YOURCO HOME > volume $DATA14.CFT32AIX

$DATA14 CFT32AIX 1> CFTUTIL

Command structure Transfer CFT Guardian commands are comprised of TACL macros (Tandem Advanced Command Language), which call their OSS counterparts. By doing so, these commands offer the same level of functionality in both OSS and Guardian environments.

How to use the commands

Run a commandExecuting a command is done by simply typing its name at the command prompt or calling it in a procedure.

Example

$DATA14 CFT32B 5> CFTUTIL about

CFTU20I

CFTU20I CFT/V3/UHPNONSTOP H06

CFTU20I Version 3.2.4 20150603

CFTU20I (C) Copyright AXWAY 1989-2015

CFTU20I ====> Starting Session on 18/06/2015 Time is 01:42:46

CFTU20I Parameters file : /home/cftuser/C..2.0/runtime/data/cftparm

CFTU20I Partners file : /home/cftuser/C..2.0/runtime/data/cftpart

CFTU20I Catalog file : /home/cftuser/C..2.0/runtime/data/cftcata

CFTU20I

CFT information :

* product = CFT/V3/UHPNONSTOP H06

* version = 3.2.4

* level =

* upgrade = 8694000

* target = hp_nonstop_oss-ia64-32

Host information :

* model =

* hostname = NSKIT06



* cpuid = XXXXXXXXXXX

* sysname = NONSTOP_KERNEL

* machine = NSE-A

* version = 29

* release = H06

* distrib = unknown

Axway information :

* ....

....

CFTU20I Ending Session on 18/06/2015 Time is 01:42:47

CFTU20I Session active for 0:00:01

Redirect the command outputThere are two ways to redirect Transfer CFT Guardian command output.

Redirect output to an OSS fileThis is done by using the standard Unix redirection symbol “>”.

$DATA14 CFT32B 16> CFTUTIL about > /home/axway/user1/cftout.txt

This generates a type 180 OSS unstructured file.

Redirect output to a Guardian EDIT fileYou must define a TACL variable before running the command. This variable contains the name of the file used to receive the output of the command. Additionally, the variable name depends on the command.

The following table gives the correspondences between the commands and the variables to use:

Command Variable

CFT CFTÔUT

CFTUTIL CFTÛTLOUT

PKIUTIL PKIÛTLOUT

This generates a type 101 Guardian unstructured file.

Example



l In the following example, the variable “CFTÛTLOUT” is set before using CFTUTIL.

l The command is launched.

l The content of the file is then listed, and the variable is unset.

$DATA14 CFT32B 30> push CFTÛTLOUT

$DATA14 CFT32B 31> set variable CFTÛTLOUT $DATA14.CFT32B.CFTUTL

$DATA14 CFT32B 32> CFTUTIL about

$DATA14 CFT32B 33> fileinfo

$DATA14.CFT32B

CODE EOF LAST MODIFIED OWNER RWEP PExt SExt

CFT 101 1300 18JUN2015 1:31 168,13 GGGO 14 28

CFTUTIL 101 1322 18JUN2015 1:31 168,13 GGGO 14 28

CFTUTL 101 1756 18JUN2015 3:08 168,13 GGGO 14 28

PKIUTIL 101 1322 18JUN2015 1:31 168,13 GGGO 14 28

$DATA14 CFT32B 34> fup copy CFTUTL

CFTU20I

CFTU20I CFT/V3/UHPNONSTOP H06

CFTU20I Version 3.2.4 20150603

CFTU20I (C) Copyright AXWAY 1989-2015

CFTU20I ====> Starting Session on 18/06/2015 Time is 03:08:55

[…]

* type = DATE

* expire = 2015/08/27

* cpuid =

* sysname = hp_nonstop_oss-ia64-32

* Nb Transfers = Max

* Nb CPU = Max

* Nb Partners = Max

* Nb EBICS partners = Unlimited

* In/Out Bandwidth = Unlimited

* In/Out Transfer activation = Unlimited

* Edition = Advanced

* Options = ODT WBS SSL XTF FIP ACC BWP CLU SNL CLP

* XSR

CFTU00I ABOUT _ Correct ()

CFTU20I Number of Command(s) 1

CFTU20I Number of error(s) 0

CFTU20I Ending Session on 18/06/2015 Time is 03:08:56

CFTU20I Session active for 0:00:01

56 RECORDS TRANSFERRED

$DATA14 CFT32B 35> pop CFTÛTLOUT

$DATA14 CFT32B 36>


6 Update

The update procedure is a limitation in this version.


7 Migrate

This section describes how to migrate the following elements:

l Partner file

l Parameter file

l Client exits and applications

Note You cannot migrate the Transfer CFT Guardian 2.3.2 catalog and communication files to Transfer CFT HP NonStop 3.2.4.

Partner and parameter filesThis section explains how to extract the definitions and import them in the new environment as part of a migration.

1. From the Transfer CFT 2.3.2 environment, export the configuration in a sequential file using the command:

CFTUTIL CFTEXT FOUT=generated_file

2. Transfer the file from the native environment to the OSS environment.

3. In the Transfer CFT 3.2.4 OSS environment import as follows:

a. Create the partner and parameter files

CFTUTIL cftfile type=parm,mode=create,fname='$CFTPARM', …

CFTUTIL cftfile type=part,mode=create,fname='$CFTPART', …

b. Import the configuration from the generated file:

CFTUTIL @generated_file


7 Migrate

System configuration fileTransfer CFT 2.3.2 is based on a CFGSYS configuration file. While you cannot use this configuration file in the current version of Transfer CFT, most of the previous parameters have an equivalent in the current version.

Table 6. System configuration file example

KW Type Volume.Subvolume

CFTWRK default $DATA00.CFT232UD

KW AP CPU PNL SMS MMS TERM IN COL SWAPF MEAS CPUBACKUP

CFTAPP 1 0 5 9600 600 $STTI $STTI $0 FSWAP01 Y 1

CFTAPP 2 1 X 0 0 default default $0 none X X

CFTAPP 3 0 5 0 0 default default $0 none X X

CFTAPP 4 0 X 0 0 default default $0 none X X

KW AP LMS ID PN PRI CPU OBJECT OUT

CFTTASK 1 3200 CFTMAIN $LAMGr 150 X $DATA00.CFT232X.CFTMGRx

$s.#amgr

CFTTASK 1 30 CFTLOG $LALoG 150 X $DATA00.CFT232X.CFTLOGx

$s.#alog

CFTTASK 1 30 CFTTCOM $LACoM 150 X $DATA00.CFT232X.CFTCOMX

$s.#acom

[…]

KW OP TERM

CFTTERM OPLOG $0

CFTTERM OP000001 $S.#OPOUT

CFTTERM OP000002 $S.#OPOUT

CFTTERM OP000003 $TRM3.#A

KW DEF VAL

CFTDEF CFGSYS $DATA00.moncfg.CFGSYS

CFTDEF TRKCNF $DATA00.moncfg.CONFSENT

CFTDEF CFTXFB $DATA00.moncfg.CONFIUI

CFTDEF CFTPARM $DATA00.monfiles.FPARM

CFTDEF CFTPART $DATA00.monfiles.FPART

CFTDEF CFTCATA $DATA00.monfiles.FCAT

CFTDEF CFTCOM $DATA00.monfiles.FCOM


7 Migrate

CFTDEF CFTLOG $DATA00.monfiles.FLOG

CFTDEF CFTLOGA $DATA00.monfiles.FLOGA

CFTDEF CFTACCNT $DATA00.monfiles.FACCNT

CFTDEF CFTACCNTA $DATA00.monfiles.FACCNTA

CFTDEF CFTPKU $DATA00.monfiles.PKIBASE

CFTDEF CFTHICNF $DATA00.monfiles.SECCNF

CFTDEF CFTHINI $DATA00.moncfg.SECINI

CFTDEF CFTHPARM $DATA00.monfiles.SECPARM

CFTDEF CFTHACT $DATA00.monfiles.SECFRACT

CFTDEF CFTHOBJ $DATA00.monfiles.SECFROBJ

KW MANAGER NB-ATTACH-SET

CFTBT TACL NBASCFTLI

KW PARM VAL

TCPPARM TCPIP^HOST^FILE $SYSTEM.ZTCPIP.HOSTS

TCPPARM TCPIP^PROCESS^NAME $ZTC0

TCPPARM TCPIP^HOST^FILE^2 $SYSTEM.ZTCPIP.HOSTS

TCPPARM TCPIP^PROCESS^NAME^2 $ZTC0

KW PARM VAL

X25PARM X25^CNX^TIME^OUT 40

KW PARM VAL

NONSTOP^RESTART^DELAY 20

NONSTOP^PLIST^TEMP^FILE $DATA00.montemp.PTMPLIST

Equivalents in Transfer CFT 3.2.4

l CFTWRK: cft.guardian.cftwrk

l CPU: cft.guardian.processor

l TERM: cft.guardian.hometerm

l CPUBACKUP: cft.guardian.backup_processor

l PN: cft.guardian.process_name_prefix

l PRI: cft.guardian.priority

l CFTTERM is no longer supported.

l CFTDEF:

o Most parameters have become environment variables that are accessible under OSS.

o CFGSYS is deprecated.

o TRKCNF is replaced by the Sentinel configuration in UCONF.


7 Migrate

o CFTXFB is deprecated.

l MANAGER: TACL is the default manager.

l NB-ATTACH-SET: cft.guardian.netbatch.attachment_set.

l X25PARAM is not supported.

Client exits and applicationsThe following rules apply to migrating client exits and client applications:

l The use of client exits and applications have not changed, but you must recompile the client programs to take into account the new data structure.

l The new data structures are described in a DDL format, and have the same name as in version 2.3.2, and are located in $volume.<subversion>IH.

l Additionally, the C language definition derived from the DDL definition is also part of the packaging.


8 Uninstall

Remove all Transfer CFT 3.2.x files to uninstall; there is no automatic uninstall procedure.


transfer cft installation guide hp nonstop - · pdf filetransfer cft batch procedures 20 how...

Documents