mft platform server for ibm i - tibco product … 6 tibco® managed file transfer platform server...

TIBCO MFT Platform Server™ for IBM i

User Guide Software Release 7.1.0 April 2013

Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, The Power of Now, TIBCO Managed File Transfer, TIBCO Managed File Transfer Command Center, TIBCO Managed File Transfer Internet Server, TIBCO Managed File Transfer Platform Server, TIBCO Managed File Transfer Platform Server Agent, Edge Server, RocketStream Accelerator, and Slingshot are either registered trademarks or trademarks of TIBCO Software Inc. or its subsidiaries in the United States and/or other countries.

All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

TIBCO® Managed File Transfer Internet Server with RocketStream® Accelerator is entitled TIBCO® Managed File Transfer Internet Server in certain other product documentation and in user interfaces of the product. Copyright ©2003-2013 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 Contents

TIBCO® Managed File Transfer Platform Server for IBM i

Contents

Preface ................................................................................................................ 7

RELATED DOCUMENTATION .......................................................................................... 8

TIBCO MFT Platform Server for IBM i ............................................................... 8

HOW TO CONTACT TIBCO CUSTOMER SUPPORT ........................................................ 9

Installation ........................................................................................................ 10

SYSTEM REQUIREMENTS ............................................................................................... 11

Supported Platforms ........................................................................................... 11

Minimum Hardware ........................................................................................... 11

Sizing Guidelines ............................................................................................... 11

Installation Notes ............................................................................................... 12

INSTALLATION ON IBM I................................................................................................ 13

Upload the Installation Package .......................................................................... 13

Steps to FTP the Save file from Windows to IBM i ................................ 13

Restore the MFT Library....................................................................... 14

Apply License Key ............................................................................................. 16

Upgrade ............................................................................................................. 16

Administration Main Menu ............................................................................... 21

CONFIGURATION MENU................................................................................................. 22

Global Parameter Menu ...................................................................................... 24

Global Parameter Display: .................................................................... 24

Global Parameter Update ..................................................................... 31

Network Configuration Menu ............................................................................. 31

Work With Network Configuration ......................................................... 32

Reorganize Network Configuration ....................................................... 38

User Profile Menu .............................................................................................. 38

Work With User Profile ......................................................................... 39

Reorganize User Profile ....................................................................... 43

MESSAGE LOG MENU ..................................................................................................... 44

Contents 4


Work With Message Log .................................................................................... 44

Purge Message Log ............................................................................................ 48

PURGE AUDIT MENU....................................................................................................... 49

Purge Audit ........................................................................................................ 49

DATA TRANSFER MENU ................................................................................................. 51

Send File Panel................................................................................................... 51

Receive File Panel .............................................................................................. 53

Send and Receive File Parameters ...................................................... 54

Send IFS File Panel ............................................................................................ 59

Receive IFS File Panel ....................................................................................... 60

Send and Receive IFS File Parameters ................................................ 61

Send Save File Panel .......................................................................................... 66

Receive Save File Panel...................................................................................... 67

Send and Receive Save File Parameters ............................................. 68

Send Library Panel ............................................................................................. 71

Receive Library Panel ........................................................................................ 72

Send and Receive Library Parameters ................................................. 73

Send Object Panel .............................................................................................. 76

Receive Object Panel .......................................................................................... 77

Send and Receive Object Parameters .................................................. 78

Execute Remote Command Panel ....................................................................... 82

ADMINISTRATION TRANS MENU.................................................................................. 88

Transaction Selection ......................................................................................... 88

Transaction Selection Criteria Parameters ........................................... 89

Purge Request Queue ......................................................................................... 92

INITIATOR SCHEDULER MENU ..................................................................................... 94

Starting the Initiator Scheduler ........................................................................... 94

Stopping the Initiator Scheduler .......................................................................... 95

RESPONDER MENU .......................................................................................................... 96

Starting the Responder........................................................................................ 96

Start SSL Responder ........................................................................... 97

5 Contents


Stopping the Responder ...................................................................................... 97

Stopping SSL Responder ..................................................................... 98

User Main Menu ............................................................................................... 99

DATA TRANSFER MENU ............................................................................................... 100

TRANSACTION SELECTION.......................................................................................... 101

Command Line Transfers ..................................................................................102

TRANSFER COMMANDS ............................................................................................... 103

Sending a File by Command Line ..................................................................... 103

Receive a File by Command Line ..................................................................... 106

Execute Remote Command Line Transfers ....................................................... 107

Sample Command Line Transfers ..................................................................... 109

Security Information ........................................................................................111

SECURITY ....................................................................................................................... 112

Security Validation ........................................................................................... 115

Security Validation of Incoming MFT Platform Server Transfer Requests ........ 115

IBM i Security Incoming Processing................................................................. 115

Security Validation of MFT Platform Server Outgoing Transfer Requests......... 116

IBM i Security Outgoing Processing ................................................................. 117

Already Verified Users ..................................................................................... 118

AUTO-START JOB ENTRIES .......................................................................................... 120

Job Entry for Start TCP/IP Command ............................................................... 120

Job Entry for Start Initiator Scheduler ............................................................... 121

Job Entry for Start Responder Command .......................................................... 123

SSL ...................................................................................................................125

AUTHENTICATION ........................................................................................................ 126

DATA ENCRYPTION ...................................................................................................... 127

Asymmetrical Encryption ................................................................................. 127

Symmetrical Encryption ................................................................................... 128

DIGITAL CERTIFICATES ............................................................................................... 129

Certificate Authority ......................................................................................... 129

Contents 6


Creating and Importing Certificates .................................................................. 130

SSL AUTHORIZATION ................................................................................................... 136

SSL Authorization Parameters .......................................................................... 137

Utilities ............................................................................................................142

FUSUTIL .......................................................................................................................... 143

Overview ......................................................................................................... 143

FUSUTIL Command Format ............................................................................ 143

Special Processing ............................................................................................ 144

Return Codes .................................................................................................... 144

Monitoring Messages ....................................................................................... 145

FUSPING .......................................................................................................................... 146

Overview ......................................................................................................... 146

FUSPING Command Parameters ...................................................................... 146

FUSPING Command Line Parameters .............................................................. 148

FUSPING Command Format ............................................................................ 148

Sample of the FUSPING Command .................................................................. 149

FUSPING Help ................................................................................................ 150

Monitoring Messages ....................................................................................... 150

RENAMING THE PRODUCT LIBRARY ......................................................................... 152

Appendix A – Code Page Conversion ................................................................153

CODE PAGE CONVERSION PANEL .............................................................................. 154

Code Page Conversion Parameters .................................................................... 154

Example Command Line Code Page Conversions ............................................. 156

Appendix B – Time File Name Token ................................................................158

Index ..............................................................................................................159

7 Preface


Preface This publication is intended for those individuals responsible for installing, configuring, managing, and operating the IBM i component of the File Transfer Management System.

Topics

• Related Documentation • How to Contact TIBCO Customer Support

Preface 8


Related Documentation

This section lists documentation you may find useful.

TIBCO MFT Platform Server for IBM i

The following documents below form the TIBCO MFT Platform Server for IBM i:

• TIBCO MFT Platform Server for IBM i Users Guide.docx: Read this manual for instructions on site preparation, installation, and on using the product to perform transfer requests and more between other Platform Server nodes.

• TIBCO MFT Platform Server for IBM i v7.1 Release Notes.docx: Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release.

9 Preface


How to Contact TIBCO Customer Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support, as follows:

• For an overview of the TIBCO Support and information on getting started with TIBCO Support, visit http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit https://support.tibco.com

Entry to this site requires a user name and password. If you do not have to login credentials, click Register with Support.

• Technical Support email address [email protected]

• Technical Support Call Centers:

o North and South America: +1.650.846.5724 or +1.877.724.8227 (1.877.724.TACS)

o EMEA (Europe, Middle East, Africa): +44 (0) 870.909.3893

o Australia: +61.2.4379.9318 or 1.800.184.226

o Asia: +61 2 4379 9318

http://www.tibco.com/services/support�

https://support.tibco.com/�

mailto:[email protected]�

Installation 10


Installation In this chapter you will learn how to install MFT Platform Server for IBM i. The main procedures will instruct you how to:

Topics

• System Requirements • Minimum Hardware • Sizing Guidelines • Installation on IBM i

11 Installation


System Requirements

Supported Platforms

The MFT Platform Server for IBM i is supported on IBM i Series 32-bit and 64-bit Versions 5.4, 6.1, and 7.1.

Note: Support for TIBCO Managed File Transfer is provided for IBM products that are currently in the mainstream support. When IBM reaches end of mainstream support they will fix security issues but there are limits on what they will do for non-security related issues. Because of this we may run into a problem where there is an IBM i issue that will not be addressed by IBM that may affect the level of support that TIBCO would be able to provide. Therefore, support for TIBCO MFT may be limited in some circumstances for the IBM I products that are in the Extended Support phase. Once an IBM product reached the end of the Extended Support phase TIBCO no longer provides any support for that product.

Minimum Hardware

• 1 GB of memory • 100 MB of disk space • An appropriate amount of additional local storage is

recommended for file transfer data

Sizing Guidelines

• In addition to the above minimum requirements: • For up to 100 concurrent transfers, two or more processor

cores at 2.5 GHz or faster • For up to 200 concurrent transfers, four or more processor

cores at 2.5 GHz or faster

Installation 12


• For more than 200 concurrent transfers, eight or more processor cores at 2.5 GHz or faster

• One additional processor core at 2.5 GHz or better for extensive use of encryption or compression

Installation Notes

To verify that MFT Platform Server will run properly on your system, please use the following as a guide.

Step 1: On the command line type the following:

DSPPTF

Step 2: The output from the display PTF command will display the PTF status. Check the FIRST TL number listed. The TL number must be equal or greater to TL06178.

If your TL number is less than what is listed here, you will have to contact IBM to acquire the cumulative PTF in order for MFT Platform Server to function properly on your system.

13 Installation


Installation on IBM i

Upload the Installation Package

MFT Platform Server for IBM i must be downloaded from the TIBCO download site at https://download.tibco.com/tibco/. The user must transfer the MFT Platform Server for IBM i save file to their system. The save file is MFT710V5.

Steps to FTP the Save file to IBM i

Step 1:

Sign on to IBM i with QSECOFR authority and create an empty save file called MFT710 using the following command:

CRTSAVF MFT710

Step 2:

Transfer the save file to the IBM i system using the following command:

FTP 192.100.100.1 (Substitute the IP Address of your IBM i system here)

Step 3:

Sign on with QSECOFR authority and enter the appropriate password.

Step 4:

Set the transfer mode to BINARY. To do this, enter the following on the command line:

BINARY

14 Installation


Step 5:

Execute the FTP PUT command to transfer the appropriate save file to IBM i. The target save file name should be QGPL/MFT710. Below is an example of the FTP commands needed to transfer the file to the IBM i system.

PUT c:\directory_name\MFT710V5 QGPL/MFT710 Step 6:

When the file has been uploaded to the IBM i machine, you can end the FTP session by typing the following on the command line:

QUIT

Restore the MFT Library

To restore the product on IBM i, you should follow the steps below while signed on as QSECOFR. Please note that the upper case values should be typed in exactly as stated. The lower case values may be changed to conform to your installation’s needs.

Step 7:

Create the MFT library on the IBM i. Enter the following command to create the MFT library:

CRTLIB LIB(MFTPLAT710) TEXT(‘MFT Platform Server v.v.v Product Library’)

This will create a library on your system that will be used with the restore command.

Where v.v.v is the new version of MFT Platform Server for IBM i.

Step 8:

Restore all objects into the MFT Platform Server library on the IBM i. Enter the following command to restore the MFT Platform Server objects:

Installation 15


RSTLIB SAVLIB(MFTPLATSHP) DEV(*SAVF) SAVF(QGPL/MFT710) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(MFTPLAT710)

MFTPLATSHP is embedded in the MFT710 save file when they are created. All objects from the MFT710 save file are restored to library MFTPLAT710.

When this restore is complete you will get a message similar to the following:

414 objects restored from MFTPLATSHP to MFTPLAT710

Step 9:

Add MFT Platform Server Library to the IBM i Library List.

ADDLIBLE MFTPLAT710

This adds the MFTPLAT100 library to your library list.

Step 10:

To create the MFT Platform Server user profile on IBM i, issue the following command from the IBM i command line:

CFCRTPRF

This runs the MFT Platform Server Create Product User Profile command. This will create a user profile called MFTPLAT710. This user profile is required to run the MFT Platform Server product. You must sign on as QSECOFR or have QSECOFR rights to run this command. If you have QSECOFR rights and have the Limit Capabilities parameter set to anything other than *NO in your profile, then you will not be able to execute this command.

16 Installation


You will be presented with the End User License Agreement. Page Down to read the agreement and then press F10 to accept the terms of the EULA by entering YES. When this MFT Platform Server Program is completed, you will get a message similar to the following:

Installation of MFT Platform Server 7.1.0 completed normally.

Apply License Key

MFT Platform Server needs a license key to function. The license is available on the TIBCO download site, download.tibco.com. Once the key is obtained, apply the key using the CFAPYKEY program. From the command line, type the following and press Enter:

CFAPYKEY

Copy and Paste the License Key provided in the field available and press the <Enter> key. The following message will appear when the license is applied correctly:

License Key applied successfully

If the license key is not applied the Initiator will shut down upon the first attempt at a transfer.

Upgrade

In this section you will learn how to upgrade MFT Platform Server for IBM i. The main procedures will instruct you how to upload the files to your IBM i system, shutdown all MFT Platform Server Service Programs on the IBM i system and restore the MFT Platform Server for IBM i libraries.

Upload MFT Platform Server to an IBM i System

MFT Platform Server for IBM i must be downloaded from the TIBCO download site at https://download.tibco.com/tibco/. The

Installation 17


user must transfer the appropriate MFT Platform Server for IBM i save file to their system. The save file is MFT710V5.

This section will describe how to FTP the MFT Platform Server save file to an IBM i system.

Steps to FTP the Save file from Windows to an IBM i System

Step 1:

Sign on to the IBM i with QSECOFR authority and create an empty save file called MFT710 using the following command:

CRTSAVF MFT710

Step 2:

Transfer the save file to the IBM i System using the following command:

FTP 192.100.100.1 (Substitute the IP Address of your IBM i here)

Step 3:

Sign on with QSECOFR authority and enter the appropriate password.

Step 4:

Set the transfer mode to BINARY. To do this, enter the following on the command line:

BINARY

Step 5:

Execute the FTP PUT command to transfer the appropriate save file to IBM i. The target save file name should be QGPL/MFT710. Below is an example of the FTP commands needed to transfer the file to the IBM i system.

PUT c:\directory_name\MFT710V5 QGPL/MFT710

18 Installation


Step 6:

When the file has been uploaded to the IBM i machine, you can end the FTP session by typing the following on the command line:

QUIT

Shutdown all MFT Platform Server Service Programs on IBM i

Make sure all previous MFT Platform Server transfer file requests have been processed.

Step 7:

After all transfer file requests have been process, stop all the MFT services. To stop the MFT Initiator Scheduler (CFSCHED in the QSYSWRK subsystem) issue the following command:

CFSTOPINT

To stop the MFT Responder (CFSERVER in the QSYSWRK subsystem) issue the following command:

CFSTOPRSP

Restore the MFT Platform Server Library on the system

To restore the product on the IBM i system, you should follow the steps below while signed on as QSECOFR. Please note that the upper case values should be typed in exactly as stated. The lower case values may be changed to conform to your installation’s needs.

Step 8:

Create the MFT Platform Server library on IBM i. Enter the following command to create the MFT Platform Server library:

CRTLIB LIB(MFTPLAT710) TEXT(‘MFT Platform Server v.v.v PTF nn Product Library’)

This will create a library on your system that will be used with the restore command.

Installation 19


Where v.v.v is the new version of MFT Platform Server for IBM I and nn is the new PTF number of MFT Platform Server for IBM i.

Step 9:

Restore all objects into the MFT library on the IBM i. Enter the following command to restore the MFT objects:

RSTLIB SAVLIB(MFTPLATSHP) DEV(*SAVF) SAVF(QGPL/MFT710) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(MFTPLAT710)

MFTPLATSHP is embedded in the MFT710 save file when they are created. All objects from the MFT710 save file are restored to library MFTPLAT710.

When this restore is complete you will get a message similar to the following:

414 objects restored from MFTPLATSHP to MFTPLAT710

Please note: the number of objects restored may vary slightly. There should never be any objects not restored.

Step 10:

Add MFT Library to the IBM i Library List.

ADDLIBLE MFTPLAT710

This adds the MFTPLAT710 library to your library list.

Step 11:

Upgrade MFT Platform Server on the IBM i. Issue the following command from the IBM i command line:

CFUPGRADE FRMLIB(MFTPLAT700)

This runs the MFT Platform Server Upgrade Program. This will upgrade the new MFT Platform Server by copying all configuration and message records from the previous MFT Platform Server to the new MFT Platform Server. The Upgrade

20 Installation


Program will also remove the previous MFT Platform Server user profile called MFTPLAT700.

Note: If the previous MFT Platform Server release does not have the Message Log Selection Screen then the administrator must clear the MFT Platform Server Message Log File on the previous MFT Platform Server release before upgrading the current MFT Platform Server product.

When this MFT Program is completed, you will get a message similar to the following:

Upgrade of MFT Platform Server 7.1.0 completed normally.

Step 12:

Create the MFT Platform Server User Profile on IBM i using the program provided. Issue the following command from the IBM i command line:

CFCRTPRF

This runs the MFT Platform Server Create Product User Profile command. This will create a user profile called MFTPLAT710. This user profile is required to run the MFT Platform Server product. To run the CFCRTPRF command, you must sign on as QSECOFR or have QSECOFR rights. If you have QSECOFR rights and have the Limit Capabilities parameter set to anything other than *NO in your profile, then you will not be able to execute this command.

You will be presented with the End User License Agreement. Page Down to read the agreement and then press F10 to accept the terms of the EULA by entering YES. When this MFT Platform Server Program is completed, you will get a message similar to the following:

Installation of MFT Platform Server 7.1.0 completed normally.

Administration Main Menu 21


Administration Main Menu This chapter discusses how to administer MFT Platform Server for IBM i from the Administration Main Menu. From this Menu a user can customize the MFT Platform Server for IBM i product for their environment.

To display the Administration Main Menu the MFT Platform Server library must be added to any users library list that will be using MFT Platform Server for IBM i. If this is not automatically done type the following command on the command line and pressing the <Enter> key:

ADDLIBLE MFTPLAT710

Topics

• Configuration Menu • Message Log Menu • Purge Audit Menu • Data Transfer Menu • Administration Trans Menu • Initiator Scheduler Menu • Responder Menu

22 Administration Main Menu


Configuration Menu

To access the Configuration Menu for MFT Platform Server for IBM i type the following command on the command line and pressing the <Enter> key:

GO CFADM

Note: The MFT Platform Server library, MFTPLAT710, must be added to the user’s library list for the above command to run successfully.

From the Administration Main Menu select Option 1.

The following panel will be displayed:

CFADM MFT Platform Server 7.1.0 Administration Main Menu System: SYSTEM NAME Select one of the following: Menus 1. Configuration Menu 2. Message Log Menu 3. Purge Audit Menu 4. Data Transfer Menu 5. Administration Trans Menu 6. Initiator Scheduler Menu 7. Responder Menu 90. Sign off Selection or command ===> __________________________________________________________ ________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu



CFCONFMNU MFT Platform Server 7.1.0 Configuration Menu System: SYSTEM NAME Select one of the following: Menus 1. Global Parameter Menu 2. Network Configuration Menu 3. User Profile Menu 90. Sign off Selection or command ===> ___________________________________________________________ ________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

This panel can also be accessed directly by typing the following command on the command line and pressing the <Enter> key:

GO CFCONFMNU


The configuration process is broken up into three components:

• Global Configuration: defines parameters used by the entire MFT Platform Server System.

• Network Configuration: defines the remote systems to MFT Platform Server.

• User Profile Configuration: defines users to MFT Platform Server.



Global Parameter Menu

Select Option 1 from the MFT Platform Server Configuration Menu to access the MFT Platform Server Global Parameter Menu. From this panel you can display or update the global parameters.


GO CFGLBMNU

The following panel will appear:

CFGLBMNU MFT Platform Server 7.1.0 Global Parameter Menu System: SYSTEM NAME Select one of the following: Commands 1. Global Parameter Display CFDSPGLB 2. Global Parameter Update CFUPDGLB 90. Sign off Selection or command ===> _________________________________________________________ ______________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Global Parameter Display:

Select Option 1 from the MFT Platform Server Global Parameter Menu to access the MFT Platform Server Work with Global Parameter Screen. This displays the global parameters that have



been defined. This is a “view only” panel. No changes can be made here.


CFDSPGLB

A panel similar to the following will appear:

CFWRKGLB TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With Global Parameter Screen DISPLAY 14:54:50 Press Enter to continue. Error Try..................: 1 Init Scheduler Interval..: 60

(SS)

Required Node Init: N Resp: N (Y/N) Trace Initiator/Responder..: N (Y/N) TCP/IP Listen Port No: 46464

(1024-65535) Version: 7.1.0

SMTP Server.: smtp.server.com___________________________________________ Email From..: [email protected]______________________________________ Email Subj..: MFT Platform Server Email Notification____________________ License Key.: SR# ********* Expiration 12/31/2035 Build Number: 7.1.0.1 F1=Help F3=Exit F12=Cancel ENTER=Next Screen

mailto:[email protected]______________________________________�



CFWRKGLB TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With Global Parameter Screen DISPLAY 14:54:50 Press Enter to continue. SSL TCP/IP Listen Port No..: 56565

(1024-65535)

SSL Encryption..: 3 (0=None 1=DES 2=TDES 3=Blowfish 4=Blowfish Long 5=Rijndael) SSL Client Application ID..: SSLCERTIFICATE_____________________________

SSL Server Application ID..:

SSLCERTIFICATE_____________________________

Use SSL Authorization File.: N (Y/N) SSL Authorization File Name:

/qsys.lib/mftplat710.lib/sslauth.file/sslauth.mbr_

F1=Help F3=Exit F12=Previous Screen ENTER=Update Record Copyright (C) TIBCO Software Inc. 1995-2013 ALL RIGHTS RESERVED.

Below is a list of all the fields in alphabetical order for easy reference as well as a brief description of each.

Parameter Description Build Number This parameter shows the Build

Number of the MFT Platform Server product. This field is display only.

Email From This parameter allows the user to specify the “From Address” that appears on the email sent by MFT. This value can be up to 55 bytes including @ and dots. This parameter cannot contain any spaces. If this parameter is not specified, the email address you specify during sending or receiving will be ignored.

Email Subj This parameter allows the user to specify what will appear in the Subject line of the email sent by MFT Platform Server. This value can be up to 64 bytes.

Error Try The user can configure MFT Platform Server to set a number of error try



Parameter Description value for all transfer request records that have an error status. The error try number value will determine how many tries to give to the transfer request records with an error status. The number of error try entered should be a value number between 1 to 99.

Expiration This field is display only and is updated by the MFT Platform Server apply key program, CFAPYKEY.

Init Scheduler Interval The user can configure MFT Platform Server to set an Initiator Scheduler Interval time which will delay the Initiator Scheduler program until the interval value is reached. The Initiator Scheduler Interval time entered should be in seconds with valid values of 1 to 9999.

License Key This parameter shows the serial number of the machine where MFT Platform Server is running. This field is display only and updated by the MFT Platform Server apply key program, CFAPYKEY.

Required Node Init The user can configure MFT Platform Server to validate all outgoing initiator transfer requests in order to ensure that the receiving MFT Platform Server system is defined in the MFT Platform Server for IBM i network configuration. It does this by matching the Remote Name of the outgoing initiator transfer request against the Node Name defined in the Network Configuration. Values N/Y

If “Y”, MFT Platform Server will validate all MFT Platform Server Network Configuration record settings for all of the remote systems. Before



Parameter Description an outgoing transfer request is sent, MFT Platform Server will ensure that the network definition has been configured for the remote system that will receive the transfer request. If there is no match for the Remote Node Name, the transfer request is terminated with an error status.

If “N”, MFT Platform Server will not validate outgoing initiator transfer requests against the MFT Platform Server Network Configuration.

Required Node Resp The user can configure MFT Platform Server to validate all incoming transfer requests in order to ensure that the initiating MFT Platform Server system is defined in the MFT Platform Server for IBM i network configuration. It does this by matching the IP address of the incoming request against the IP address defined in the Network Configuration. Values N/Y

If “Y”, MFT Platform Server will validate all MFT Platform Server Network Configuration record settings for all of the remote systems. Before an incoming transfer request is accepted, MFT Platform Server will ensure that the network definition has been configured for the system that initiated the transfer request. If there is no match for the IP address, the transfer request is terminated with a network error.

If “N”, MFT Platform Server will not validate incoming transfer requests against the MFT Platform Server Network Configuration.

SMTP Server This parameter allows the user to



Parameter Description specify the SMTP (Simple Mail Transfer Protocol) server name. If this parameter is specified, MFT Platform Server sends Email messages though this SMTP server. If this parameter is not specified, the email address you specify during sending, or receiving will be ignored.

SSL Authorization File Name This parameter allows the user to specify the SMTP (Simple Mail Transfer Protocol) server name. If this parameter is specified, MFT Platform Server sends Email messages though this SMTP server. If this parameter is not specified, the email address you specify during sending, or receiving will be ignored.

SSL Client Application ID This parameter allows the user to specify the Client Application ID Name for outgoing SSL transfer requests.

Default Value: SSLCERTIFICATE SSL Encryption The user can configure the encryption

type to use for all outgoing SSL transfer requests. Values: 0= None 1=DES 2=3DES (Triple DES) 3=Blowfish 4=Blowfish Long 5=Rijndael

Note: If an SSL transfer is setup and the Encryption type value is left blank, then the Global SSL Encryption Type value will be used.

SSL Server Application ID This parameter allows the user to specify the Server Application ID Name for incoming SSL transfer requests.



Parameter Description Default Value: SSLCERTIFICATE

SSL TCP/IP Listen Port No This parameter defines the SSL port that MFT Platform Server will listen on for incoming transfer requests using SSL. The number entered should be a valid IP port between 1024 and 65535. This parameter must match the IPPORT defined on the remote system.

TCP/IP Listen Port Number This parameter defines the TCP/IP port that MFT Platform Server for IBM i will listen on for incoming transfer requests. The number entered should be a valid IP port between 1024 and 65535. This parameter must match the IPPORT defined on the remote system.

Trace Initiator/Responder MFT Platform Server can be configured to trace both incoming and outgoing MFT transfer requests. MFT Platform Server will create secure files containing information about the data received from and sent to the remote systems, as well as status information about the programs processing the transfer request. This option should be turned on only when TIBCO technical support requests a trace.

If “Y”, MFT Platform Server will trace all incoming and outgoing transfer requests.

Use SSL Authorization File The user can select if the incoming SSL transfer requests the remote user to be validated by its SSL Authorization File. Values N/Y

If “Y”, the incoming SSL transfer requests the remote user to be validated by its SSL Authorization File.

Version This field displays the version of MFT Platform Server for IBM i that is



Parameter Description currently running. This field is display only.

Global Parameter Update

Select Option 2 from the MFT Platform Server Global Parameter Menu to access the MFT Platform Server Work with Global Parameter Screen. This screen enables the user to define the status, control settings, security, debugging and TCP/IP parameters that are required by MFT.


CFUPDGLB

Note: You must stop the Responder before updating the Global settings.

For a description of each field found on the screens see the Global Parameter Display section of the manual.

Network Configuration Menu

Select Option 2 from the MFT Configuration Menu in order to access the MFT Network Configuration Menu. All of the network configuration will be done through this set of panels.


GO CFNETMNU




CFNETMNU MFT Platform Server 7.1.0 Network Configuration Menu System: SYSTEM NAME Select one of the following: Commands 1. Work With Network Configuration CFWRKNET 2. Reorganize Network Configuration CFREORGNET 90. Sign off Selection or command ===> _________________________________________________________ ______________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Work With Network Configuration

The Work with Network Configuration Screen allows a user to Add, Change, Copy, Delete or Display the detailed network configuration for a remote MFT Platform Server configured in the system.


CFWRKNET




CFWRKNET TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With Network Configuration Screen JOB NAME 14:54:50 Type action, Press Enter: 1=Add 2=Change 3=Copy 4=Delete 5=Display Remote Link System Act Node Type Type System Description _ ________ _ IBMISYS *TCPIP IBM i IBM i System Configuration _ ZOSSYS *TCPIP z/OS z/OS System Configuration _ WINSYS *TCPIP Windows WINDOWS System Configuration _ UNIXSYS *TCPIP UNIX UNIX System Configuration F1=Help F3=Exit F5=Refresh F7=Page Up F8=Page Down F12=Cancel

Add a remote MFT Platform Server

When a user chooses to add the details of a remote MFT Platform Server, a screen similar to the one below will be displayed:



CFWRKNET TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With Network Configuration Screen MODE 14:55:10 Type choices, Press Enter. Remote Node Name.....: ________________________ Remote Link Type.....: 1 (1=TCPIP) Remote System Type...: _ (1=z/OS 2=Windows 3=UNIX 4=IBM i) System Description...: _______________________________ Accept Verified User.: N (Y=Yes N=No)

_________

Data Compression.....: 0 (0=None 1=RLE 2=LZ) Remote TCP/IP Port Number......: 46464 Remote TCP/IP Address/Host Name:

(1024-65535) _________________________

Encryption: 0 (0=None 1=DES 2=TDES 3=Blowfish 4=Blowfish Long 5=Rijndael) _____________

Command Center Support (Y=Yes) All: ___ Audit: ___ Node: ___ Ping: ___ Profile: ___ Transfer: ___ Maintain by..: QSECOFR Maintain Date: 2/21/13 F1=Help F3=Exit F5=Refresh F12=Cancel

A list of all the fields available and a brief description has been provided below in alphabetical order for ease of reference:

Parameter Description Accept Verified Used MFT Platform Server can be

configured to accept or reject verified users for incoming MFT transfer requests for this node. For more information on MFT Platform Server Accept Verified User please refer to Chapter 6. Valid Values: N/Y

Command Center Support The Command Center Support parameters are explained below. To turn on a parameter, enter a Y next to the parameter.

All - Allows the MFT Platform Server for IBM i to accept all MFT Command Center requests. All of the functions



Parameter Description within Node, Profile, Transfer and Audit are allowed.

Audit - Allows the MFT Platform Server for IBM i to accept MFT Command Center requests to view and retrieve information in the MFT Platform Server for IBM i Audit log. MFT Command Center Collector and Audit Polling functions require this option to be set on the MFT Platform Server for IBM i Node definition.

Node - Allows the MFT Platform Server for IBM i to accept MFT Command Center requests to Add, List, Update and Delete MFT Platform Server for IBM i Node entries.

Ping - Allows remote MFT Platform Servers to check if MFT Platform Server for IBM i is running.

Profile - Allows the MFT Platform Server for IBM i to accept MFT Command Center requests to Add, List, Update and Delete MFT Platform Server for IBM i User Profile entries.

Transfer - Allows the MFT Platform Server for IBM i to accept MFT Command Center requests to initiate a Transfer on this MFT Platform Server for IBM i to send a file to a different MFT Platform Server system

Encryption The user can configure the encryption type to use for all outgoing transfer requests for this particular node.



Parameter Description Values: 0= None 1=DES 2=TDES (Triple DES) 3=Blowfish 4=Blowfish Long 5=Rijndael

Maintain by The MFT Platform Server Work With Network Configuration Program will automatically update the Maintain by field with the current user when they change, copy or add a record to the MFT Platform Server Network Configuration File.

Maintain Date The MFT Platform Server Work With Network Configuration Program will automatically update the Maintain Date with the current date when a user changes, copies, or adds a record to the MFT Platform Server Network Configuration File.

After entering the appropriate values, press Enter to process the network configuration record.

Remote Link Type The MFT Platform Server Work With Network Configuration Program will automatically update the Remote Link Type field. The Remote Link Type value will be 1 for TCPIP.

Remote Node Name The Remote Node Name is a name the user gives to a remote system configuration for MFT Platform Server for IBM i. The remote system configuration record will be in the MFT Platform Server Network Configuration File. The user can enter the remote node name on the selection field either to enter a new record or to update a Network



Parameter Description Configuration record. This name gives the user the ability to associate a name with a remote location instead of just using an IP address. The remote node entered by the user must be the name of a MFT Platform Server Remote System Configuration record, which will be used by MFT Platform Server to connect from a local location to a remote location. MFT Platform Server only accepts A-Z, 0-9, @, $, #, and _ (underscore). The Node name cannot begin with an underscore.

Remote System Type The user must enter one of four valid remote MFT Platform Server system types - IBM i, z/OS, Windows and UNIX.

Remote TCP/IP Address/Host Name

The user can enter the Remote TCP/IP Address Number or a Remote Host Name for a particular Remote System. MFT Platform Server will use this address/host name to locate that Remote System for incoming and outgoing transfer request processing. This field also is used when the Global Required Node initiator or responder parameters are set to YES. The IP address/Host Name of the incoming and outgoing transfer requests will be checked against this field to ensure that the remote system is defined to this MFT Platform Server system.

Remote TCP/IP Port Number The user may enter a Remote TCP/IP Port Number between 1024 and 65535. This parameter must match the IP port that the remote MFT Platform Server is listening to connect. Default value is 46464.

System Description The user may enter the System Description of the MFT Network



Parameter Description Configuration record setting. This field allows a user to attach a comment to a Network Configuration.

Reorganize Network Configuration

Select Option 2 from the MFT Platform Server Network Configuration Menu in order to access the MFT Reorganize Network Configuration Command. The Reorganize Network Configuration Command purges deleted records from the Work With Network Configuration file and then sorts the file.


CFREORGNET

This screen does not contain any parameters. Press <Enter> to reorganize the system.

Note: Do not run this command when the Network Configuration File contains no records.

User Profile Menu

Select Option 3 from the MFT Platform Server Configuration Menu to access the MFT User Profile Menu.


GO CFPRFMNU



CFPRFMNU MFT Platform Server 7.1.0 User Profile Menu System: SYSTEM NAME Select one of the following: Commands 1. Work With User Profile CFWRKPRF 2. Reorganize User Profile CFREORGPRF 90. Sign off Selection or command ===> _________________________________________________________ ______________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Work With User Profile

The Work With User Profile screen allows a user to Add, Change, Copy, Delete or Display the details of a defined local user profile configured in the system that is directly linked to one of the defined remote MFT Platform Server configured in the Work With Network Configuration Screen. All standard IBM i security is utilized for the user profile's job running on the local location.


CFWRKPRF




CFWRKPRF TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With User Profile Screen JOB NAME 14:54:50 Type action, Press Enter: 1=Add 2=Change 3=Copy 4=Delete 5=Display Remote Local Local User Act Node User Description _ _______________ ___________________ _ UNIX TSS01 TSS01 User Profile Description _ HPUX TSS02 TSS02 User Profile Description _ WINDOWS TSS03 TSS03 User Profile Description _ ZOSSYS TSS04 TSS04 User Profile Description _ IBMISYS TSS05 TSS05 User Profile Description F1=Help F3=Exit F5=Refresh F7=Page Up F8=Page Down F12=Cancel

Add a local User Profile

When a user chooses to add a user profile to be user when sending to a specific remote MFT Platform Server, a screen similar to the one below will be displayed:



CFWRKPRF TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With User Profile Screen ADD 14:55:10 Type choices, Press Enter. Remote Node Name........: SYSISYS

_________

Local User Name.........: TSS01 ___________________________

(Name *All)

Remote User Name........: TSS02____________________________________

New Remote Password.....: (Case Sensitive) New Password (To Verify): (Case Sensitive) Maintain by.........: QSECOFR Maintain Date.......: 2/21/13 F1=Help F3=Exit F5=Refresh F12=Cancel

A list of all the available fields and a brief description has been provided below in alphabetical order for ease of reference:

Parameter Description Local User Name Used to define the local IBM i user id

that will have the authorization to conduct transfer requests to the particular Remote Node. Enter *ALL in the Local User Profile Name field. This will allow all User Profile to transfer requests to that particular remote node. Valid Values: 1-32 characters, *ALL

Maintain by The Work With User Profile screen will automatically update the Maintain by field with the current user adding a profile to the system.

Maintain Date The Work With User Profile screen will automatically update the Maintain Date with the current date when a



Parameter Description user adds a new profile to the system.

New Remote Password This password field holds the present password being used to login to the remote MFT Platform Server Node this local profile is being associated with. The Remote Password can be up to 32 characters in length and is upper and lower case sensitive. This is a non-display field.

New Password (To Verify) This field is used to verify the password defined in the New Remote Password field.

Remote Node Name The Remote Node is a name the user gives to a remote system configuration for the MFT Platform Server for IBM i. The remote system configuration record will be in the MFT Platform Server Network Configuration File. The user can enter the remote node name on the selection field to either enter a new record or to update a User Profile record. This name gives the user the ability to associate a name with a remote location rather than just an IP address.

Remote User Name The Remote User Name is the name of a user on a remote node system that will be used by MFT Platform Server on the IBM i. The Remote User Name can be up to 32 characters in length while the IBM i System user profile can only be 10 characters in length. The Remote User Name will be used to sign-on the remote node system for outgoing transfer requests using MFT Platform Server product.



After entering the appropriate values, press Enter to process the user profile record.

Reorganize User Profile

Select Option 2 from the User Profile Menu in order to access the Reorganize User Profile Command. The Reorganize User Profile Command purges deleted records from the Work With User Profiles Menu and then sorts the file.


CFREORGPRF

This screen does not contain any parameters. Press <Enter> to reorganize the system.

Note: Do not run this command when the Work With User Profiles file contains no records.



Message Log Menu

Select Option 2 from the Administration Main Menu to access the MFT Platform Server Message Log Menu. The Message Log Menu allows a user to work with all the MFT Platform Server Messages and Audit records generated for transaction requests.

This panel can also be accessed directly by typing the following command on the command line:

GO CFMSGMNU

CFMSGMNU MFT Platform Server 7.1.0 Message Log Menu System: SYSTEM NAME Select one of the following: Commands 1. Work With Message Log CFWRKMSG 2. Purge Message Log CFPRGMSG 90. Sign off Selection or command ===> ___________________________________________________________ ________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Work With Message Log

To view user(s) message records from the message record log file that have been generated for MFT Platform Server transaction requests, select the Work With Message Log option.




CFWRKMSG


CFWRKMSG TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With Message Log Selection Screen Job Name 15:44:19 Type choices, Press Enter. Selection Criteria Value ------------------ ----- Local User Profile: *ALL

*ALL

From Date and Time: (MM/DD/YYYY) (HHMMSS) To Date and Time..: TODAY

(MM/DD/YYYY) (HHMMSS)

Number of Days....: 1

F1=Help F3=Exit F5=Refresh F12=Cancel

A list of all the available fields and a brief description has been provided below in alphabetical order for ease of reference:

Parameter Description From Date and Time The user can select the From Date and

Time to display all MFT Platform Server message log records from the MFT Platform Server Message Log file that are greater than or equal to the date and/or time entered.

Local User Profile The user can select any user profile and display all its MFT Platform Server message log records from the MFT Platform Server Message Log file. Valid Values: User ID or *ALL

Number of Days The user can select the number of day’s worth of message log records to



Parameter Description display. This parameter can also be used with the From Date and Time parameter. This will give message log records starting with the From Date and continuing through the number of days specified. This parameter can also be used with the To Date and Time parameter. In this case the number of days would go back in time.

To Date and Time The user can select the To Date and Time to display all MFT Platform Server message log records from the MFT Platform Server Message Log file only that are less than or equal to the date and/or time entered. Valid Values: MM/DD/YYYY or TODAY

When message logs are displayed the records will be in descending order showing the most recent record first.



FWRKMSG TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/321/13 SYSTEM NAME Work With Message Log Screen JOB NAME 14:54:50 Type action, Press Enter: 5=Display Trans Message Message Local Message Act Number Date Time User Text _ I916800003 05/16/2008 9:55:23 TSS02 <INITIATOR> END OF _ I916800002 05/16/2008 9:55:22 TSS02 <INITIATOR> Status _ I916800002 05/16/2008 9:55:22 TSS02 <INITIATOR> Commun _ I916800001 05/16/2008 9:50:26 TSS01 <INITIATOR> END OF _ I916800001 05/16/2008 9:50:26 TSS01 <INITIATOR> Status _ R913800003 04/13/2008 13:57:33 TSS03 <RESPONDER> END OF _ R913800003 04/13/2008 13:57:32 TSS03 <RESPONDER> Transa _ R913800002 04/13/2008 13:57:23 TSS02 <RESPONDER> END OF _ R913800002 04/13/2008 13:57:22 TSS02 <RESPONDER> Transf _ R913800001 04/13/2008 13:57:21 TSS01 <RESPONDER> Transa _ R913800001 04/13/2008 13:57:17 TSS01 <RESPONDER> END OF F1=Help F3=Exit F5=Refresh F7=Page Up F8=Page Down F12=Cancel

To display the details of a transaction record, type a 5 on the line next to the transaction number and press enter. A screen similar to the one below will be shown:

CFWRKMSG TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 2/21/13 SYSTEM NAME Work With Message Log Screen DISPLAY 14.55.10 Init Trans No...: I216800001 Remote IP Address: 11.22.33.44 Message Date....: 02/16/2013 Message Time.....: 09:50:26 Transfer Process: FILE Local User......: TSS01 Remote User.....: TSS02 Message Text Message.........: <INITIATOR> END OF TRANSACTION F1=Help F3=Exit F12=Cancel



Purge Message Log

To purge old messages from the system select option 2 for the Purge Message Log screen. From this screen an IBM i user can delete records from the MFT Platform Server for IBM i Message Log file.

This panel can also be accessed directly by typing the following command on the command line and pressing the <F4> key:

CFPRGMSG

Purge Message Log (CFPRGMSG) Type choices, press Enter. Number of Days to Retain . . . . 3

Number, *NONE

F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Specify in the field available the records that should be saved by setting the number of days to retain the log file. For instance if the current date is the 15th of February and the number of days to retain is specified as 3, records with dates February 13th through February 15th inclusively will be retained. All other records prior to February 13th will be purged. If you would like to purge all the messages from the system set the value to *NONE.

Note: Purging the messages should be done regularly to keep the file size small as part of the general maintenance for this product.



Purge Audit Menu

To purge old audits from the system select option 2 for the Purge Message Log screen. From this screen an IBM i user can delete records from the MFT Platform Server for IBM i Message Log file.


GO CFAUDMNU

CFAUDMNU MFT Platform Server 7.1.0 Purge Audit Menu System: SYSTEM NAME Select one of the following: Commands 1. Purge Audit CFPRGAUD 90. Sign off Selection or command ===> ___________________________________________________________ ________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Purge Audit

Select Option 1 from the MFT Platform Server Audit Menu to access the MFT Platform Server Purge Audit Message panel. From this panel an IBM i user can delete records from the MFT Platform Server Audit Message File.

This panel can also be accessed directly by typing the following command on the command line and pressing the <F4> key:

CFPRGAUD



Purge Audit (CFPRGAUD) Type choices, press Enter. Number of Days to Retain . . . . 3

Number, *NONE


Specify in the field available the records that should be saved by setting the number of days to retain the audit file. For instance if the current date is the 15th of February and the number of days to retain is specified as 3, audit records with dates February 13th through February 15th inclusively will be retained. All other records prior to February 13th will be purged. If there is a need to purge all the audit records from the system set the value to, *NONE.

Note: Purging the audit should be done regularly to keep the file size small as part of the general maintenance for this product.



Data Transfer Menu

This section provides details of how to setup transfer requests through the various panels available through the Data Transfer Menu as well as using the MFT Platform Server command line parameters.

This panel can also be accessed directly by entering the following command on the command line and pressing the <Enter> key:

GO CFTFRMNU

CFTFRMNU MFT Platform Server 7.1.0 Data Transfer Menu System: SYSTEM NAME Select one of the following: Commands 1. Send File Panel CFSNDFPNL 2. Receive File Panel CFRCVFPNL 3. Send IFS File Panel CFRCVIFSFP 4. Receive IFS File Panel CFRCVIFSFP 5. Send Save File Panel CFSNDSAVFP 6. Receive Save File Panel CFRCVSAVFP 7. Send Library Panel CFSNDLIBP 8. Receive Library Panel CFRCVLIBP 9. Send Object Panel CFSNDOBJP 10. Receive Object Panel CFRCVOBJP 11. Execute Remote Command Panel CFEXECPNL 90. Sign off Selection or command ===>_____________________________________________________________ _________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Send File Panel

To send a file to a remote MFT Platform Server select option 1 to open the Send File Panel or type the following command from the command line and press the <Enter> key:

CFSNDFPNL



CFSRF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 S10B7C9C Send File 16:03:34 Local File Name. . . . ___________ Library. . . ___________ NAME, *LIBL Member. . . .*FIRST_____ NAME, *FIRST, *ALL Remote File Path. . . . _____________________________________________ _____________________________________________________________________ Connection type . . . . _ 1. Node/LU 2. IP address 3. IP name Node ,IP Adr or Name. . ______________________________ (F4-Lookup Node) Remote IP port. . . . . 46464 1024-65535 Secure Socket Layer. N (Y or N) Remote userid . . . . . __________________________ Remote password . . . . (case sensitive) Remote Domain . . . . . __________________________ (For Windows only) Remote File Options . . X C. Create Y. Create/Append R. Replace Z. Create/ReplaceNew A. Append X. Create/Replace F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down

Page down to display the rest of the transfer attributes.

CFSRF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send File 16:03:34 Platform Option. . . . 4 1.z/OS 2.Windows 3.Unix 4.IBM i Convert to/from ASCII N (Y or N) Convert CR/LF . . . . N (Y or N) Remove Trailing Spaces Y (Y or N) Compression . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael DB2 template. . . . . N (Y or N) Target Release. . . *CURRENT Process name. . . . . PROCESSNAME User description. . . __________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Checkpoint Interval . _0 (0-99 min, 0 for none) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N) F1=Help F3=Exit F10=Command Entry ENTER=Submit Page Up



Receive File Panel

To send a file to a remote MFT Platform Server select option 2 to open the Send File Panel or type the following command from the command line and press the <Enter> key:

CFRCVFPNL

CFSRF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 S10B7C9C Receive File 16:03:34 Local File Name. . . . ___________ Library. . . ___________ NAME, *LIBL Member. . . .*FIRST_____ NAME, *FIRST, *ALL Remote File Path. . . . _____________________________________________ _____________________________________________________________________ Connection type . . . . _ 1. Node/LU 2. IP address 3. IP name Node ,IP Adr or Name. . ______________________________ (F4-Lookup Node) Remote IP port. . . . . 46464 1024-65535 Secure Socket Layer. N (Y or N) Remote userid . . . . . __________________________ Remote password . . . . (case sensitive) Remote Domain . . . . . __________________________ (For Windows only) Local File Options . . X C. Create Y. Create/Append R. Replace Z. Create/ReplaceNew A. Append X. Create/Replace F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFSRF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send File 16:03:34 Platform Option. . . . 4 1.z/OS 2.Windows 3.Unix 4.IBM i Convert to/from ASCII N (Y or N) Convert CR/LF . . . . N (Y or N) Remove Trailing Spaces Y (Y or N) Compression . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael DB2 template. . . . . N (Y or N) Target Release. . . *CURRENT Process name. . . . . PROCESSNAME User description. . . __________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N)



Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Checkpoint Interval . _0 (0-99 min, 0 for none) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N) F1=Help F3=Exit F10=Command Entry ENTER=Submit Page Up

Send and Receive File Parameters

A list of all the available fields and a brief description has been provided below in the order in which they appear on the screen:

Parameter Description Local File – Name Library Member

Specify the file Name, Library, and optional Member name to be sent. Note: The Member name should remain set to *FIRST or a specific member name when sending files to any MFT Platform Server other than an IBM i system. When sending to another IBM I system *ALL can also be used.

Remote File Path Specifies the path where the remote file should be placed. Examples:

Sending to another IBM i: qgpl/myfile(mymember) Member name is optional.

Sending to Windows: c:\temp\mydir\myfile

Sending to UNIX: /home/mydir/myfile

Sending to z/OS: mydsn1.test.mydsn

If you specify *FROMFILE for this parameter, MFT Platform Server will try to place the file in to the same location as the FROMFILE parameter. This is valid only for IBM i to IBM i transfers only. Note: When entering a Remote Path Name



Parameter Description that is a Source Physical File, the user can enter *ALL or a particular member name in the Member name field that will receive the transfer on the IBM i system. But if the remote system is not an IBM i system, the user can only receive one member at a time. The user can only enter a particular member name in the Member name field.

Connection Type Specifies the type value you are using to connect to the remote system. Valid values are 1 - Node, 2 - IP Address or 3 - IP Name.

Node, IP Adr, Name Species whether the remote location will be contacted using a: 1 – Node, 2 – IP Address, or 3 – Host Name

Remote IP port Specifies the port number on the remote system where MFT Platform Server is listening.

Secure Socket Layer Secure Socket Layer will process the request transfer using the TCP/IP security protocol. Valid values: N/Y

Remote userid Specify remote user ID to log on to the remote system.

Remote password Specifies the password for the remote user ID. This field is case sensitive.

Remote Domain Specifies the remote domain name to logon to the remote Windows system.

Remote File Options Options used to create the file on the remote system. Valid values are:

C - Create a new file at the remote location, this will only work if the remote file does NOT exist.

R - Replace an existing file, this will only work if the remote file already exists

A - Append to an existing file, this will only work if the remote file already exists

X -Create a new file or Replace an existing file



Parameter Description Y-Create a new file or Append to an existing file.

Z -Create a new file and if necessary create the directory path to this file or replace an existing file.

Local File Options Options used to create the file on the remote system. Valid values are:





Y-Create a new file or Append to an existing file.


Platform Option Specifies the remote system type. Valid values are: 1 – z/OS, 2 – Windows, 3 – UNIX, 4 – IBM i.

Convert to/from ASCII This determines the type of data translation that is required for the remote system, valid values are:

Y - Convert to/from ASCII (for Windows and UNIX)

N - Do not convert to/from ASCII (for IBM i and z/OS)

Convert CR/LF Carriage Return Line Feed control for transferring to another operating system. The valid values are :

Y - Replace Line Feed characters in the input file with Carriage Return and Line Feed



Parameter Description characters.

N - Do nothing with the Line Feed characters. Remove Trailing Spaces

Specifies if the trailing space in file line will be removed. Valid values: N/Y

Compression Set the data compression to be used for this transfer. Valid Values: 0 – None 1 – LZ LZ provides better compression

ratios and compresses a wider variety of different data types than RLE. Choose LZ if you need better compression ratios and can spare CPU cycles.

2 – RLE RLE is more data-dependent than LZ. That is, the compression ratio may vary widely based upon the type of data being compressed. Choose RLE if you network bandwidth is not a critical bottleneck for your network and you need to save CPU cycles.

Encryption The user can configure the encryption type to use for this transfer request. Valid values:

0= None 1=DES 2=3DES (Triple DES) 3=Blowfish 4=Blowfish Long 5=Rijndael

DB2 template (For transfer between IBM i systems only)

This option should be used when transferring SAVF with another IBM i system. Valid Values are:

Y - DB2 data definition is sent with data. N - DB2 data definition is not sent with data

Target Release This option is valid only when Y or *YES is specified for the DB2 template parameter.

*CURRENT – Target is at the same OS level. *PRV - Target is at the previous OS level.



Parameter Description V5R4M0 - Target is V5R4M0 release. V5R3M0 - Target is V5R3M0 release. V5R2M0 - Target is V5R2M0 release.

Process name User defined process name. By default it is set to the current user id.

User description Alpha numeric field to add a transfer description.

Email when Successful Specifies the email address to send successful notification.

Email when Failure Specifies the email address to send failure notification.

Hold file transfer When this parameter is set to yes the transfer is held until the user releases it. Valid values: Y/N Note: When set to Y an additional screen will open containing the wait parameters.

Priority Priority on job queue. The default is 5. Maximum Error Try Specifies the maximum number of error

retries. Checkpoint Interval Specifies the interval in minutes that the

checkpoint is taken. Checkpoint is not a valid option when transferring a SAVF file.

Post Processing Post processing allows users to process commands, calls executable programs, submit jobs, etc. Up to four post processing actions are allowed. Valid Values: Y/N

ST - Status that the transfer must have in order for the post processing to take effect. Valid values S/F

SRC - The system where the post processing will take place. Valid values: L – Local System, R – Remote System

CMD - This is the type of Command that will be executed.

1 – CALLPGM Call Program 2 – COMMAND: Command 3 – CALLJCL : Call JCL 4 – SUBMIT: Submit JCL



Parameter Description Data – This field holds the command to be executed.

Run Immediately Specifies when you want to run the transfer. Valid values: Y/N

When N is selected a prompt to enter the Schedule date and time.

Schedule date and time

This is the date in the format MMDDYYYY and time in the format HHMM that the transfer should be executed. This parameter appears when Run Immediately is set to N.

Send IFS File Panel

To send an ISF file to a remote MFT Platform Server select option 3 to open the Send IFS File Panel or type the following command from the command line and press the <Enter> key:

CFSNDIFSFP

CFSRIFSF TIBCO Software Inc. MFT Platform Server 7.1.0 2/26/13 S10B7C9C Send IFS File 16:04:41 Local IFS File Path . ________________________________________________ ______________________________________________________________________ Remote File Path. . . . *LOCALIFS_____________________________________ ______________________________________________________________________

Connection type . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . _____________________________ (F4-Lookup Node) Remote IP port. . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . *CURRENT Remote password . . . . (case sensitive) Remote Domain . . . . . ___________________________(For Windows only) Remote File Options . . X C.Create Y.Create/Append R.Replace Z.Create/ReplaceNew A.Append X.Create/Replace F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down




CFSRIFSF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send IFS File 16:03:34 Platform Option. . . . 4 1.z/OS 2.Windows 3.Unix 4.IBM i Convert to/from ASCII N (Y or N) Convert CR/LF . . . . N (Y or N) Compression . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael Process name. . . . . PROCESSNAME User description. . . __________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Checkpoint Interval . _0 (0-99 min, 0 for none) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N)

F1=Help F3=Exit F10=Command Entry ENTER=Submit Page Up

Receive IFS File Panel

To receive a file from a remote MFT Platform Server select option 4 to open the Receive IFS File Panel or type the following command from the command line and press the <Enter> key:

CFRCVIFSFP

CFSRIFSF TIBCO Software Inc. MFT Platform Server 7.1.0 2/26/13 S10B7C9C Receive IFS File 16:04:41 Local IFS File Path . ________________________________________________ ______________________________________________________________________ Remote File Path. . . . *LOCALIFS_____________________________________ ______________________________________________________________________

Connection type . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . _____________________________ (F4-Lookup Node) Remote IP port. . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . *CURRENT Remote password . . . . (case sensitive) Remote Domain . . . . . ___________________________(For Windows only) Local File Options . . X C.Create Y.Create/Append R.Replace Z.Create/ReplaceNew A.Append



X.Create/Replace F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFSRIFSF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Receive IFS File 16:03:34 Platform Option. . . . 4 1.z/OS 2.Windows 3.Unix 4.IBM i Convert to/from ASCII N (Y or N) Convert CR/LF . . . . N (Y or N) Compression . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael Process name. . . . . PROCESSNAME User description. . . __________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Checkpoint Interval . _0 (0-99 min, 0 for none) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N)


Send and Receive IFS File Parameters


Parameter Description Local IFS FilePath Specify the full path for the local IFS File. Remote File Path Specifies the path where the remote file

should be placed. Examples:

Sending to another IBM i:

/myDirectory/myfile

Sending to Windows: c:\temp\mydir\myfile

Sending to UNIX:



Parameter Description /home/mydir/myfile

Sending to z/OS: mydsn1.test.mydsn

If you specify *FROMFILE for this parameter, MFT Platform Server will try to place the file in to the same location as the FROMFILE parameter. This is valid only for IBM i to IBM i transfers only. Note: When entering a Remote Path Name that is a Source Physical File, the user can enter *ALL or a particular member name in the Member name field that will receive the transfer on the IBM i system. But if the remote system is not an IBM i system, the user can only receive one member at a time. The user can only enter a particular member name in the Member name field.








Remote File Options Options used to create the file on the remote



Parameter Description system. Valid values are:

C - Create a new file at the remote location.

R - Replace an existing file. (Remote file must exist.)






C - Create a new file at the remote location.

R - Replace an existing file. (Remote file must exist)







Y - Convert to/from ASCII (for Windows and



Parameter Description UNIX)



Y - Replace Line Feed characters in the input file with Carriage Return and Line Feed characters.

N - Do nothing with the Line Feed characters. Compression Set the data compression to be used for this

transfer. Valid Values: 0 – None 1 – LZ LZ provides better compression







Email when Successful Specifies the email address to send successful



Parameter Description notification.


Hold file transfer When this parameter is set to yes the transfer is held until the user releases it. Valid values: Y/N




Post Processing Post processing allows users to process commands, calls executable programs, submit jobs, etc. Up to four post processing actions are allowed. Valid Values: Y/N





Data – This field holds the command to be executed.







Send Save File Panel

To send a Save file to a remote MFT Platform Server select option 5 to open the Send Save File Panel or type the following command from the command line and press the <Enter> key:

CFSNDSAVFP CFSRSF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 S10B7C9C Send Save File 16:59:18 Local Save File Name. . . __________ Library . . . . . . . . *LIBL NAME, *LIBL Remote Save File Name . . *LOCALFILE Library . . . . . . . . __________ NAME Connection type . . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . . ______________________________ (F4-Lookup Node) Remote IP port. . . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . . *CURRENT Remote password . . . . . (case sensitive) Remote Save File Options. X C.Create R.Replace X.Create/Replace Compression . . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down

Page down to display the rest of the attributes.

CFSRSF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send Save File 16:03:34

User description. . . ___________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N)




Receive Save File Panel

To receive a Save file from a remote MFT Platform Server for IBM i select option 6 to open the Receive Save File Panel or type the following command from the command line and press the <Enter> key:

CFRCVSAVFP

CFSRF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 S10B7C9C Receive Save File 16:59:18 Local Save File Name. . . __________ Library . . . . . . . . *LIBL NAME, *LIBL Remote Save File Name . . *LOCALFILE Library . . . . . . . . __________ NAME Connection type . . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . . ______________________________ (F4-Lookup Node) Remote IP port. . . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . . *CURRENT Remote password . . . . . (case sensitive) Local Save File Options. X C.Create R.Replace X.Create/Replace Compression . . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFSRF TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send Save File 16:03:34

User description. . . ___________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N)




Send and Receive Save File Parameters


Parameter Description Local Save File Name

- Library Specify the local save file name and library where the save file is located.

Remote Save File Name - Library

Specify the remote save file name and library where the save file is located.

Connection Type Specifies the type value you are using to

connect to the remote system. Valid values are 1 - Node, 2 - IP Address or 3 - IP Name.






Remote File Options Options used to create the file on the remote system. Valid values are:







Parameter Description C - Create a new file at the remote location, this will only work if the remote file does NOT exist.






Encryption The user can configure the encryption type to use for all outgoing transfer requests for this particular node. Values:





Email when Failure Specifies the email address to send failure






retries. Post Processing Post processing allows users to process

commands, calls executable programs, submit jobs, etc. Up to four post processing actions are allowed. Valid Values: Y/N












Send Library Panel

To send a Library to a remote MFT Platform Server for IBM i select option 7 to open the Send Library Panel or type the following command from the command line and press the <Enter> key:

CFSNDLIBP

CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 S10B7C9C Send Library 16:59:18 Local Library Name. . . . __________ NAME Remote Library Name . . . *LOCALLIB NAME, *LOCALLIB Connection type . . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . . _______________________________ (F4-Lookup Node) Remote IP port. . . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . . *CURRENT Remote password . . . . . (case sensitive) Remote Library Options. . X C.Create R.Replace X.Create/Replace Remote Restore Object Opt A A.*ALL N.*NEW O.*OLD Remote Database Mbr Opt . M M.*MATCH A.*ALL N.*NEW O.*OLD Remote Obj Differences. . N N.*NONE A.*ALL Target Release. . . . . . *CURRENT Compression . . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael

F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send Library 16:03:34

Process name. . . . . ___________ User description. . . ___________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N)




Receive Library Panel

To receive a Library file from a remote MFT Platform Server for IBM i select option 8 to open the Receive Library Panel or type the following command from the command line and press the <Enter> key:

CFRCVLIBP CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 S10B7C9C Receive Library 16:59:18 Local Library Name. . . . __________ NAME Remote Library Name . . . *LOCALLIB NAME, *LOCALLIB Connection type . . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . . _______________________________ (F4-Lookup Node) Remote IP port. . . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . . *CURRENT Remote password . . . . . (case sensitive) Local Library Options . . X C.Create R.Replace X.Create/Replace Local Restore Object Opt. A A.*ALL N.*NEW O.*OLD Local Database Mbr Opt. . M M.*MATCH A.*ALL N.*NEW O.*OLD Local Obj Differences . . N N.*NONE A.*ALL Target Release. . . . . . *CURRENT Compression . . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael

F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Receive Library 16:03:34

Process name. . . . . ___________ User description. . . ___________________________ Email when Successful ________________________________________________ Email when Failure. . ________________________________________________ Hold file transfer. . N (Y or N) Priority. . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . _1 (0-99, 0 defaults to Unlimited) Post Processing . . . N (Y or N) Run Immediately . . . Y (Y or N)




Send and Receive Library Parameters


Parameter Description Local Library Name Specify the local library name to be used for

the transfer request.

Remote Library Name

Specify the remote library name to be used for the transfer request.







Remote Library Options

Options used to create the file on the remote system. Valid values are:




Remote Restore Obj Opt

This option will check the name, creation date and size of the remote objects.

Remote Database Mbr This option will check Physical Files names,



Parameter Description Opt creation date, size, and version.

Remote Obj Differences

This option will check the level ids, Authority list and ownership.

Local Library Options Options used to create the file on the remote system. Valid values are:




Local Restore Obj Opt This option will check the name, creation date and size of the remote objects.

Local Database Mbr Opt

This option will check Physical Files names, creation date, size, and version.

Local Obj Differences This option will check the level ids, Authority list and ownership.







Parameter Description 0= None 1=DES 2=3DES (Triple DES) 3=Blowfish 4=Blowfish Long 5=Rijndael
















Parameter Description Run Immediately Specifies when you want to run the transfer.

Valid values: Y/N




Send Object Panel

To send an Object to a remote MFT Platform Server for IBM i select option 9 to open the Send Object Panel or type the following command from the command line and press the <Enter> key:

CFSNDOBJP

CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send Object 16:03:34

Object Names. . . . . . _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ NAME, GENERIC*, *ALL Local Library Name. . . __________ NAME Remote Library Name . . *LOCALLIB NAME, *LOCALLIB Connection type . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. _______________________________ (F4-Lookup Node) Remote IP port. . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . *CURRENT Remote password . . . . (case sensitive) F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Send Object 16:03:34



Object Types. . . . . ._________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ *ALL Remote Library Options. X C.Create R.Replace X.Create/Replace Remote Restore Obj Opt. A A.*ALL N.*NEW O.*OLD Remote Database Mbr Opt M M.*MATCH A.*ALL N.*NEW O.*OLD Remote Obj Differences. N N.*NONE A.*ALL Target Release. . . . . *CURRENT Compression . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael Process name. . . . . . JBARKER User description. . . . F1=Help F3=Exit F10=Command Entry ENTER=Submit Page Down Page Up

Receive Object Panel

To receive a Library file from a remote MFT Platform Server for IBM i select option 8 to open the Receive Library Panel or type the following command from the command line and press the <Enter> key:

CFRCVOBJP

CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Receive Object 16:03:34

Object Names. . . . . . _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ NAME, GENERIC*, *ALL Local Library Name. . . __________ NAME Remote Library Name . . *LOCALLIB NAME, *LOCALLIB Connection type . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. _______________________________ (F4-Lookup Node) Remote IP port. . . . . 46464 (1024-65535) Secure Socket Layer. N (Y or N) Remote userid . . . . . *CURRENT Remote password . . . . (case sensitive) F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down




CFSRL TIBCO Software Inc. MFT Platform Server 7.1.0 2/21/13 SYSTEM NAME Receive Object 16:03:34

Object Types. . . . . ._________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ *ALL Local Library Options. X C.Create R.Replace X.Create/Replace Local Restore Obj Opt. A A.*ALL N.*NEW O.*OLD Local Database Mbr Opt M M.*MATCH A.*ALL N.*NEW O.*OLD Local Obj Differences . N N.*NONE A.*ALL Target Release. . . . . *CURRENT Compression . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.BFlong 5.Rijndael Process name. . . . . . Current User User description. . . . F1=Help F3=Exit F10=Command Entry ENTER=Submit Page Down Page Up

Send and Receive Object Parameters


Parameter Description Object Names Specify the names of the objects to be used

for the transfer request. To send all the objects in a library set *ALL.

Remote Library Name

Specify the remote library name to be used for the transfer request.

Local Library Name Specify the local library name to be used for the transfer request.


Node, IP Adr, Name Species whether the remote location will be contacted using a: 1 – Node, 2 – IP Address,



Parameter Description or 3 – Host Name





Object Types Specifies the types of system objects that are restored. Valid values: *ALL or specific object type for example *CMD (command).

Remote Library Options

Options used to create the library on the remote system. Valid values are:

C - Create a new library at the remote location; this will only work if the remote file does NOT exist.

R - Replace an existing library, this will only work if the remote file already exists

X -Create a new library or Replace an existing library.

Local Library Options Options used to create the library on the local system. Valid values are:

C - Create a new library.

R - Replace an existing library

X -Create a new library or Replace an existing library if it already exists.

Remote Restore Obj Opt

Specifies how the object(s) should be restored in the library. Valid values:

A – All objects will be written or replaced in the library.

N – Only objects that are new and don’t exist



Parameter Description in the library will be written.

O – Only existing objects in the library will be replaced.

Local Restore Obj Opt Specifies how the object(s) should be restored in the library. Valid values:

A – All objects will be written or replaced in the library.

N – Only objects that are new and don’t exist in the library will be written.

O – Only existing objects in the library will be replaced.

Remote Database Mbr Opt

Specifies how members should be restored on the remote system. Valid values:

M – All members will be written that match the remote system member names and versions. This option requires the members to exist.

A – All members will be written or replaced in the file.

N – Only members that are new and don’t exist in the file will be written.

O – Only existing members in the file will be replaced.

Local Database Mbr Opt

Specifies how members should be restored on the local system. Valid values:

M – All members will be written that match the remote system member names and versions. This option requires the members to exist.

A – All members will be written or replaced in the file.

N – Only members that are new and don’t exist in the file will be written.

O – Only existing members in the file will be replaced.



Parameter Description Target Release This option specified the release level the

target system is running at.

*CURRENT – Target is at the same OS level. *PRV - Target is at the previous OS level. V6R1M0 - Target is V5R4M0 release V5R4M0 - Target is V5R4M0 release. V5R3M0 - Target is V5R3M0 release.









Email when Failure Specifies the email address to send failure

















Execute Remote Command Panel



To execute a remote command on a remote MFT Platform Server for IBM i select option 11 to open the Execute Remote Command Panel and press the <Enter> key or type the following command from the command line and press the <Enter> key:

CFEXECPNL

CFEXECMD TIBCO Software Inc. MFT Platform Server 7.1.0 10/30/12 SYSTEM NAME Execute Remote Command 14:45:27 Execute command . . . . __________________________________________ __________________________________________________________________ __________________________________________________________________ _____________________________________ Connection type . . . . 1 1.Node/LU 2.IP address 3.IP name Node, IP Adr or Name. . __________________________(F4-Lookup Node) Remote IP port. . . . . 46464 (1024-65535) Remote userid . . . . . *CURRENT____________________________ Remote password . . . . (case sensitive) Remote Domain . . . . . ________________________(For Windows only) Local File Name. . . . . ____________ Library. . . . ____________ Member. . . . *FIRST______ NAME, *FIRST Local File Options . . X C.Create Y.Create/Append R.Replace Z.Create/ReplaceNew A.Append X.Create/Replace F1=Help F3=Exit F10=Command Entry F12=Cancel ENTER=Submit Page Down


CFEXECMD TIBCO Software Inc. MFT Platform Server 7.1.0 10/30/12 SYSTEM NAME Execute Remote Command 14:45:27 Platform Option . . . . 4 1.z/OS 2.Windows 3.Unix 4.IBM i Convert to/from ASCII . N (Y or N) Rcd Length._____ Compression . . . . . . 0 0.None 1.LZ 2.RLE Encryption. . . . . . . 0 0.None 1.DES 2.3DES 3.Blowfish 4.Blowfish Long 5.Rijndael Process name. . . . . . Current_User_ User description. . . . ________________________ Email when Successful . ___________________________________________ Email when Failure ... ___________________________________________ Hold file transfer. . . N (Y or N)



Priority. . . . . . . . 5 (0-9, 0 is lowest) Maximum Error Try . . . _1 (0-99, 0 defaults to 1) Post Processing . . . . N (Y or N) Secure Socket Layer. Y (Y or N) Run Immediately . . . . Y (Y or N) F1=Help F3=Exit F10=Command Entry ENTER=Submit Page Up


Parameter Description Execute Command The command that will be run on a

remote MFT Platform Server.








Local File – Name Library Member

Specifies the name of the local physical file which will receive data from the remote system after the remote command is executed successfully and produces output. Note: Only UNIX and WINDOWS Operating Systems will return data to the local file.



Parameter Description Local File Options Options used to create the file on the remote

system. Valid values are:









Y - Convert to/from ASCII (for Windows and UNIX)



Y - Replace Line Feed characters in the input file with Carriage Return and Line Feed characters.

N - Do nothing with the Line Feed characters. Compression Set the data compression to be used for this

transfer. Valid Values: 0 – None 1 – LZ LZ provides better compression



Parameter Description ratios and compresses a wider variety of different data types than RLE. Choose LZ if you need better compression ratios and can spare CPU cycles.












Post Processing Post processing allows users to process



Parameter Description commands, calls executable programs, submit jobs, etc. Up to four post processing actions are allowed. Valid Values: Y/N












Administration Trans Menu

This section provides details of how to view and purge transfer request transaction records that are either sitting on the queue or have already completed.


GO CFATRNMNU

CFATRNMNU MFT Platform Server 7.1.0 Administration Trans Menu System: System Name Select one of the following: Commands 1. Transaction Selection CFTRNSEL 2. Purge Request Queue CFPRGREQ 90. Sign off Selection or command ===>____________________________________________________________________ ________________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Transaction Selection

To view transfer requests that are either sitting on the queue or have already completed select option 1 from the Administration Trans Menu and press the <Enter> key to display the Transaction Selection Criteria screen.

This screen can also be accessed directly by typing the following command on the command line and pressing the <Enter> key:

CFTRNSEL

CFTRNSEL TIBCO Software Inc. MFT Platform Server 7.1.0 USER 3/06/13 S10B7C9C Transaction Selection Criteria SYSTEM NAME 11:46:36

Type choices, Press Enter. Selection Criteria Value



------------------ ----- Audit/Queue/Both B A(udit) Q(ueue) B(oth) Transaction Number __________ (Local) __________ (Remote) Remote System Name __________________________________ Local UserID ___________________________ Process Name _________ File or Library Name _________________________________________________ Entry Status __ I(nactive) H(eld) A(ctive) User Description *_________________________ Audit Only Value ------------------ ----- From Date and Time __________ ______ (MM/DD/YYYY) (HHMMSS) To Date and Time TODAY (MM/DD/YYYY) (HHMMSS) Number of Days 1 Transfer Exceptions _ S(uccessful) or U(nsuccessful) F1=Help F3=Exit F5=Refresh F10=Command Entry F12=Cancel

An administrator will be able to view all the transfer records. A user with less authority will only be able to view his or her transfer records.

Transaction Selection Criteria Parameters


Parameter Description Audit/Queue/Both This parameter controls if the transactions

displayed will be from the Request Queue, the Audit Message file, or both. Valid values: A – Audit, Q – Queue, B - Both

Transaction Number If the user would like to display a specific transaction and knows the Local or Remote transaction number, they would enter it here.

Remote System Name The user can select the Remote Node Name, Remote IP Address or Remote Host Name of a particular Remote System and display all its transaction records.

Local User ID The user can select any user profile and display all its MFT Platform Server message log records from the MFT Platform Server



Parameter Description Message Log file. Valid Values: User ID or *ALL

Process Name The user can select the To Date and Time to display all MFT Platform Server message log records from the MFT Platform Server Message Log file only that are less than or equal to the date and/or time entered. Valid Values: MM/DD/YYYY or TODAY

File or Library Name Enter either the specific file name or library used in a transfer to display only those transaction records. When entering the File Name, user must enter the file in system platform format example: For an IBM i System = Library Name/File Name(Member Name)

Entry Status The user can select the Entry Status and display the transaction records for that particular status. Valid values: I – Inactive, H – Held, A - Active

User Description Enter the User Description used for the transaction or set the value to “*” to display all.

From Date and Time The user can select the From Date and Time to display all MFT Platform Server message log records from the MFT Platform Server Message Log file that are greater than or equal to the date and/or time entered.

To Date and Time The user can select the number of day’s worth of message log records to display. This parameter can also be used with the From Date and Time parameter. This will give message log records starting with the From Date and continuing through the number of days specified. This parameter can also be used with the To Date and Time parameter. In this case the number of days would go back in time.

Number of Days The user can select the number of day’s worth of message log records to display. This parameter can also be used with the From



Parameter Description Date and Time parameter. This will give message log records starting with the From Date and continuing through the number of days specified. This parameter can also be used with the To Date and Time parameter. In this case the number of days would go back in time.

Transfer Exceptions (Audit Only)

Select the Audits to be displayed based on if the transaction was successful or failed. Valid values: S/F

As a result of the transaction selection criteria set a listing of Queue/Audit message transactions will be displayed. Below is an example of what a user could see:

CFTRNSEL TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 3/06/13 SYSTEM NAME Request Queue/Audit Message Trans Listing JOB NAME 13:15:40 Type action, Press Enter: A=Alter H=Hold P=Purge R=Release 5,or S=Display Local Trans Process Transfer Remote Local Local Act Number Name Status Node UserID File _ I305300001 PROCNAM1 ACTIVE NODE NAME TSS01 FILE1 _ I305300002 PROCNAM2 ACTIVE 111.222.33.12 TSS01 FILE2 _ I305300003 PROCNAM3 ACTIVE HOST NAME TSS02 FILE3 _ I305300004 PROCNAM4 INACTIVE NODE NAME TSS02 FILE4 _ I305300005 PROCNAM5 INACTIVE HOST NAME TSS03 FILE5 _ I305300006 PROCNAM6 INACTIVE 111.222.33.55 TSS03 FILE6 _ I305300007 PROCNAM7 HELD HOST NAME TSS04 FILE7 _ I305300008 PROCNAM8 HELD NODE NAME TSS04 FILE8 _ I305300009 PROCNAM9 HELD NODE NAME TSS05 FILE9 _ I305300010 PROCNA10 COMPLETED 111.222.33.16 TSS05 FIL10 _ I305300011 PROCNA11 COMPLETED NODE NAME TSS06 FIL11 _ I305300012 PROCNA12 FAILED HOST NAME TSS06 FIL12 _ I305300013 PROCNA13 FAILED NODE NAME TSS07 FIL13 F1=Help F3=Exit F5=Refresh F7=Page Up F8=Page Down F10=Command Entry F12=Cancel



From the listing screen a user can perform actions on the transaction records that are displayed based on whether they are a request found on the queue and/or an audit record.

Parameter Description A=Alter Use this action to make changes to a transfer request

that is sitting on the queue as INACTIVE or HELD. H=Hold Use this action when a transfer request that is INACTIVE

needs to be held. P=Purge Use this action to purge any transfer request that is

ACTIVE, INACTIVE, or being HELD. R=Release Use this action to release a transfer request that is being

INACTIVE or being HELD. S=Display Use this action to display the details of a transfer

request.

Purge Request Queue

Select Option 2 from the MFT Platform Server Administration Transaction Menu to access the MFT Platform Server Purge Request Queue panel. From this panel an IBM i user can delete records from the MFT Platform Server Request Queue File.

This panel can also be accessed directly by typing the following on the command on the command line and pressing the <F4> key:

CFPRGREQ

Purge Request Queue (CFPRGREQ) Type choices, press Enter. Number of Days to Retain . . . . 3 Number, *NONE F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys



Once the specified records have been deleted, the command will attempt to exclusively allocate the Request Queue File. If the Request Queue File is allocated successfully, the command will reorganize the Request Queue File by purging deleted records. An additional completion message will be issued if the file was reorganized.

• Number of Days to Retain

Specifies the number of records to retain based upon the number of days specified compared against the entry date. Valid values are: number, *NONE Example:

If the current date is the 15th of February and the number of days to retain is specified as 3, records with dates February 13th through February 15th inclusively will be retained. All other records will be purged.

Note: Purging the request should be done regularly to keep the file size small as part of the general maintenance for this product.



Initiator Scheduler Menu

For MFT Platform Server to initiate transfer requests from the IBM i system the Initiator Scheduler must be running. This section will describe how to start and stop the MFT Platform Server Initiator Scheduler.

Starting the Initiator Scheduler

To start the MFT Platform Server Initiator select option 6 from the Administration Main Menu and press the <Enter> key.

Note: You must be an IBM i Security Officer or Security Administrator to start the MFT Platform Server Initiator Scheduler program.


GO CFINTMNU

CFINTMNU MFT Platform Server 7.1.0 Initiator Scheduler Menu System: system name Select one of the following: Menus 1. Start Initiator Scheduler CFSTRINT 2. Stop Initiator Scheduler CFSTOPINT 90. Sign off Selection or command ===>____________________________________________________________ ________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Select option 1 and press the <Enter> key to start the Initiator Scheduler. Another option to start the Initiator Scheduler is to run the following command on the command line and press the <Enter> key:

CFSTRINT



The Job Name will be CFSCHED and the user profile that will be assigned to the program process will be MFTPLAT710.

Stopping the Initiator Scheduler

To stop the Initiator Scheduler, Select option 2 and press the <Enter> key from the Initiator Scheduler Menu. Another option to stop the Initiator Scheduler is to run the following command on the command line and press the <Enter> key:

CFSTOPINT



Responder Menu

For MFT Platform Server to respond to outside MFT Platform Server transfer requests the MFT Platform Server Responder must be running. This section will describe how to start and stop the MFT Platform Server Responder.

Starting the Responder

To start the MFT Platform Server Responder select option 7 from the Administration Main Menu press the <Enter> key.

Note: You must be an IBM i Security Officer or Security Administrator to start the MFT Platform Server Initiator Scheduler program.


GO CFRSPMNU

CFRSPMNU MFT Platform Server 7.1.0 Responder Menu System: SYSTEM NAME Select one of the following: Menus 1. Start Responder CFSTRRSP 2. Stop Responder CFSTOPRSP 90. Sign off Selection or command ===> F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

Start Responder (CFSTRRSP) Type choices, press Enter. Start SSL Responder . . . . . . *NO *NO, *YES, *BOTH F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys



The default non-secure port is 46464.

Another option to start the Non SSL Responder is to run the following command from the command line and press the <Enter> Key:

CFSTRRSP SSL(*NO)

The Job Name will be CFRESP and the user profile that will be assigned to the program process will be MFTPLAT710.

Start SSL Responder

If the IBM i System has been configured to use SSL (Secure Socket Layer) certificates MFT Platform Server Responder can be configured to communicate over a secure port in addition to accepting transfer request on a non secure port. The default port for SSL is 56565. From the Start Responder screen set the option to *YES to start only the SSL Responder. Set *BOTH if both the Non Secure and Secure ports should be listening.

Another option to start the SSL Responder is to run the following command from the command line and press the <Enter> Key:

CFSTRRSP SSL(*YES) or CFSTRRSP SSL(*BOTH)

Stopping the Responder

To stop the Responder from listening on the non-secure port, Select option 2 and press the <Enter> key from the Stop Responder screen. Another option to stop the Responder is to run the following command on the command line and press the <Enter> key:

CFSTOPRSP SSL(*NO)

Stop Responder (CFSTOPRSP) Type choices, press Enter. Stop SSL Responder . . . . . . *NO *NO, *YES, *BOTH



F3=Exit F4=Prompt F5=Refresh F12=Cancel 13=How to use this display F24=More keys

Stopping SSL Responder

To stop the Responder from listening on the Secure port set the value to *YES on the Stop Responder screen. To stop the Responder from listening on both the secure and non-secure ports set the value to *BOTH and press the <Enter> key.

Another option to stop the Responder is to run the following command on the command line and press the <Enter> key:

CFSTOPRSP SSL(*YES) or CFSTOPRSP SSL(*BOTH)

User Main Menu 99


User Main Menu This chapter discusses the User Main Menu screens provided for non-administrator users.

To display the User Main Menu the MFT Platform Server library must be added to any users library list that will be using MFT Platform Server for IBM i. If this is not automatically done type the following command on the command line and pressing the <Enter> key:

ADDLIBLE MFTPLAT710

Topics

• Data Transfer Menu • Transaction Menu

100 User Main Menu


Data Transfer Menu The Data Transfer Menu presented to a non-administrator contains no differences than the screens presented to an Administrator.


GO CFTFRMNU

CFTFRMNU MFT Platform Server 7.1.0 Data Transfer Menu System: SYSTEM NAME Select one of the following: Commands 1. Send File Panel CFSNDFPNL 2. Receive File Panel CFRCVFPNL 3. Send IFS File Panel CFRCVIFSFP 4. Receive IFS File Panel CFRCVIFSFP 5. Send Save File Panel CFSNDSAVFP 6. Receive Save File Panel CFRCVSAVFP 7. Send Library Panel CFSNDLIBP 8. Receive Library Panel CFRCVLIBP 9. Send Object Panel CFSNDOBJP 10. Receive Object Panel CFRCVOBJP 11. Execute Remote Command Panel CFEXECPNL 90. Sign off Selection or command ===>_____________________________________________________________ _________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

For an explanation of the panels and the fields available please see the Administrator Data Transfer Menu section.

User Main Menu 101


Transaction Selection To view transfer requests that are either sitting on the queue or have already completed select option 2 from the User Main Menu and press the <Enter> key to display the Transaction Selection Criteria screen.

This screen can also be accessed directly by typing the following command on the command line and pressing the <Enter> key:

CFTRNSEL

CFTRNSEL TIBCO Software Inc. MFT Platform Server 7.1.0 USER 3/06/13 S10B7C9C Transaction Selection Criteria SYSTEM NAME 11:46:36

Type choices, Press Enter. Selection Criteria Value ------------------ ----- Audit/Queue/Both B A(udit) Q(ueue) B(oth) Transaction Number __________ (Local) __________ (Remote) Remote System Name __________________________________ Local UserID ___________________________ Process Name _________ File or Library Name _________________________________________________ Entry Status __ I(nactive) H(eld) A(ctive) User Description *_________________________ Audit Only Value ------------------ ----- From Date and Time __________ ______ (MM/DD/YYYY) (HHMMSS) To Date and Time TODAY (MM/DD/YYYY) (HHMMSS) Number of Days 1 Transfer Exceptions _ S(uccessful) or U(nsuccessful) F1=Help F3=Exit F5=Refresh F10=Command Entry F12=Cancel

A non-administrator user will be able to view his or her transfer records only.

For an explanation of the fields available please see the Administrator Transfer Selection Criteria Parameters section.

102 Command Line Transfers


Command Line Transfers MFT Platform Server for IBM i has the built in panels to run transfer requests but it also provides the user the option to run transfer requests using the command line. This chapter discusses how to use the command line function interactively.

Topics

• Transfer Commands

Command Line Transfers 103


Transfer Commands

Sending a File by Command Line

In order to accomplish sending file(s) using a command line command, enter the following command and press the <Enter> key:

CFSNDF

The following screen will display for sending a file:

Send File (CFSNDF) Type choices, press Enter. Remote Location or *IPADDR . . . ____________________ From File Name . . . . . . . . . _____________ Name Library Name . . . . . . . . . *LIBL_____ Name, *LIBL Member . . . . . . . . . . . . *FIRST____ Name, *FIRST, *ALL F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Fill in the Remote Location (or *IPADDR) the From File Name, Library and Member fields and press the <Enter> key.

Note: If a remote location has not been defined, the Command Line may still be utilized. When the value for the Remote Location is set to *IPADDR an additional field labeled Internet Address will be displayed to hold the IP address of machine name.

The remainder of the parameters will be displayed.

Secure Socket Layer . . . . . . *NO To File Name . . . . . . . . . . *

*NO, *YES FROMFILE

________________________________________________________________ ______________________

Remote User ID . . . . . . . . . *CURRENT_______________________



Password . . . . . . . . . . . . Remote Domain for NT only . . . _______________________________ File Options . . . . . . . . . . CR Convert from/to ASCII . . . . .

_ *CREATE, *REPLACE, *APPEND... *NO

Convert CR/LF . . . . . . . . . _ *YES, *NO

*NO_ Remove Trailing Spaces . . . . .

*YES, *NO *NO_

*YES, *NO


Send File (CFSNDF) Type choices, press Enter. Compression . . . . . . . . . . *DFT *DFT, *NONE, *LZ, *RLE Encryption . . . . . . . . . . . *DFT *DFT ,*NONE, *DES, *TDES... DB2 Template . . . . . . . . . . *YES *YES, *NO Target Release . . . . . . . . . *CURRENT *CURRENT, *PRV,V4R5M0... Notify Email Success . . . . . . ________________________________ Notify Email Failure . . . . . . ________________________________ Process Name . . . . . . . . . . *CURRENT Character value, *CURRENT Description . . . . . . . . . . _______________________ Hold Transfer . . . . . . . . . *NO *NO, *YES Priority . . . . . . . . . . . . 5 1-9 Maximum Retry . . . . . . . . . 01 0-99 Checkpoint Restart . . . . . . . 00 0-99 Run Mode . . . . . . . . . . . . *IMMED *IMMED, *SUBMIT Wait . . . . . . . . . . . . . . *NO *NO, *YES Post Process . . . . . . . . . . *NO *NO, *YES F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

If Hold Transfer is set to *YES, then the additional WAIT parameters will be displayed.

Send File (CFSNDF)

Type choices, press Enter.

Wait . . . . . . . . . . . . . . > *YES *NO, *YES Wait interval in seconds . . . . 30__ 0001-9999 Wait time out in seconds . . . . 300_ 0001-9999 Wait time out purge . . . . . . *NO_ *NO, *YES Post Process . . . . . . . . . . *NO_



If Post Process is set to *YES, then the additional Post Processing parameters will be displayed.

Send File (CFSNDF) Type choices, press Enter. Post Process . . . . . . . . . . > *YES *NO, *YES *Success or *Failure . . . . . . *S, *F *Local or *Remote . . . . . . . *L, *R Post Process Type . . . . . . . *PGM, *CMD, *JCL, *SBM Post Process Data . . . . . . . ______________________________ ________________________________________________________________ *Success or *Failure . . . . . . *S, *F *Local or *Remote . . . . . . . *L, *R Post Process Type . . . . . . . *PGM, *CMD, *JCL, *SBM Post Process Data . . . . . . . ______________________________ ________________________________________________________________ *Success or *Failure . . . . . . *S, *F *Local or *Remote . . . . . . . *L, *R Post Process Type . . . . . . . *PGM, *CMD, *JCL, *SBM Post Process Data . . . . . . . ______________________________ ________________________________________________________________ *Success or *Failure . . . . . . *S, *F *Local or *Remote . . . . . . . *L, *R Post Process Type . . . . . . . *PGM, *CMD, *JCL, *SBM Post Process Data . . . . . . . ______________________________ ________________________________________________________________ Platform Options . . . . . . . . *SYSTEMI *ZOS, *WINDOWS, *UNIX... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Based on the Platform Option set for the Post Processing Action will be run against the settings will vary.

For Z/OS:



Send File (CFSNDF) Type choices, press Enter. Platform Options . . . . . . . . > *ZOS__ *ZOS, *WINDOWS, *UNIX... zOS File Format . . . . . . . . *FB *F, *FA, *FB, *FM, *FBA... Length . . . . . . . . . . . . . 0-9999 Block Size . . . . . . . . . . . 0-9999 Data Class . . . . . . . . . . . Name Management Class . . . . . . . . Name Storage Class . . . . . . . . . Name Allocation Type . . . . . . . . *BL *BL, *TR, *CY, *MB, *KB Primary Size . . . . . . . . . . 0-9999 Secondary size . . . . . . . . . 0-9999 Directory Block . . . . . . . . 0-9999 Volume . . . . . . . . . . . . . Name Unit . . . . . . . . . . . . . . Name F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

For WINDOWS:

Send File (CFSNDF) Type choices, press Enter. Platform Options . . . . . . . . > *WINDOWS *S390, *WINDOWS, *UNIX... System . . . . . . . . . . . . . *NO *NO, *YES Hidden . . . . . . . . . . . . . *NO *NO, *YES Read Only . . . . . . . . . . . *NO *NO, *YES Archive . . . . . . . . . . . . *NO *NO, *YES NTFS Compress . . . . . . . . . *NO *NO, *YES More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Receive a File by Command Line

In order to accomplish receiving a file(s) using a command line command enter the following command and pres the <Enter>



key:

CFRCVF

The parameters available to receive a file are the same parameters available on the Send File screens. Please refer to section Sending a File by Command Line section to view these screens.

Execute Remote Command Line Transfers

To execute a remote command using Execute Remote Command, the user may enter the following command on the command line and press the <Enter> key:

CFEXECMD

The following screen will display:

Execute Remote Command (CFEXECMD) Type choices, press Enter. Remote Location or *IPADDR . . . _______________________________ Execute Command . . . . . . . . _______________________________ F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Fill in the Remote Location (or *IPADDR) the From File Name, Library and Member fields and press the <Enter> key.

Note: If a remote location has not been defined, the Command Line may still be utilized. When the value for the Remote Location is set to *IPADDR an additional field labeled Internet Address will be displayed to hold the IP address of machine name.



Execute Remote Command (CFEXECMD) Type choices, press Enter. Remote Location or *IPADDR . . . _______________________________ Execute Command . . . . . . . . _______________________________ Internet Address . . . . . . . . ________________________ IP Port Number 1024-65535. . . . 46464 Character value Secure Socket Layer . . . . . . *NO_ *NO, *YES Remote User ID . . . . . . . . . *CURRENT______________________ Password . . . . . . . . . . . . Remote Domain for NT only . . . ______________________________ Local File Name . . . . . . . . Name Library Name . . . . . . . . . Name Member . . . . . . . . . . . . *FIRST____ Name, *FIRST File Options . . . . . . . . . . *CR *CREATE,*REPLACE,*APPEND... Record Length . . . . . . . . . 0-99999

More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys



Execute Remote Command (CFEXECMD) Type choices, press Enter. Platform Options . . . . . . . . > *WINDOWS *S390, *WINDOWS, *UNIX... Convert from/to ASCII . . . . . *NO *YES, *NO Compression . . . . . . . . . . *DFT *DFT, *NONE, *LZ, *RLE Encryption . . . . . . . . . . . *DFT *DFT, *NONE, *DES, *TDES... Notify Email Success . . . . . . ______________________________ Notify Email Failure . . . . . . _______________________________ Process Name . . . . . . . . . . *CURRENT Character value, *CURRENT Description . . . . . . . . . . _______________________ Hold Transfer . . . . . . . . . *NO *NO, *YES Priority . . . . . . . . . . . . 5 1-9 Maximum Retry . . . . . . . . . 00 0-99 Run Mode . . . . . . . . . . . . *IMMED *IMMED, *SUBMIT Schedule Date (MMDDYYYY) . . . . *NONE 0-99999999, *NONE Schedule Time (HHMM) . . . . . . *NONE Character value, *NONE Wait . . . . . . . . . . . . . . *YES *NO, *YES Wait interval in seconds . . . . 30 0000-9999 Wait time out in seconds . . . . 300 0000-9999 Wait time out purge . . . . . . *NO *NO, *YES Post Process . . . . . . . . . . *YES *NO, *YES More... F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Sample Command Line Transfers

Transfers can be done using either the panels or the command line. When using the command line, the user can use the panels as an aid, but using the panels is not necessary. Below are some examples using the MFT Platform Server Command Line:

The first example shows a Send from the IBM i system to a z/OS system.



CFSNDF RMTLOCNAME(os390a) FROMFILE(qgpl/test) TOFILE(mainfrm.dataset.name) RMTUSRID(rmtuser1) RMTPWD(pswd) ENCRYPT(*BFL)

The next example shows the same Send from the IBM i system to a z/OS system with additional parameters used for scheduling.

CFSNDF RMTLOCNAME(os390a) FROMFILE(qgpl/test) TOFILE(mainfrm.dataset.name) RMTUSRID(rmtuser1) RMTPWD(pswd) ENCRYPT(*BFL) RUNMODE(*SUBMIT) SCDDATE(11272004) SCDTIME(2200)

The next example shows a Receive of a file from a UNIX system with Post Processing.

CFRCVF RMTLOCNAME(unix1) TOFILE(qgpl/test) FROMFILE(/home/UserA/file) RMTUSRID(UserA) RMTPWD(pswd) POSTPROC(*YES) POSTFLG1(*S) POSTACT1(*L) POSTTYP1(*CMD) POSTDAT1(‘dir > output.txt’)

The following shows an Execute Remote Command example to a Windows system.

CFEXECMD RMTLOCNAME(windows2) EXECMD('dir > output.txt') RMTUSRID(wuser) RMTPWD(pswd) RMTDOMAIN(wdomain)

Security Information 111


Security Information This chapter describes the details of the security validation as well as the Auto Start processes for the MFT Platform Server Initiator Scheduler and MFT Platform Server Responder. It also describes the concept of Already Verified Users for incoming requests.

Topics

• Security • Auto-Start Job Entries

112 Security Information


Security

To access the MFT Platform Server for IBM i Administration Main Menu, your user profile must have the same rights as the Security Officer (QSECOFR). You can also be signed on as Security Officer (QSECOFR).

To process any MFT Platform Server for IBM i Administration Menu Options or Commands, the user profile must be either the Security Officer (QSECOFR), or Security Administrator (*SECADM) along with Special Authority (*ALLOBJ).

To access MFT Platform Server for IBM i please add the following two libraries to you library list:

MFTPLAT710

QTEMP

Any user profile can access the MFT Platform Server for IBM i Main Menu and any user profile can process any MFT Platform Server for IBM i Main Menu Options or Commands.

The IBM i administrator can change the authority of accessing the MFT Platform Server for IBM i Menus or process MFT Platform Server for IBM i Main Menu Options or Commands. This is done by using IBM i command EDTOBJAUT on the menus, programs, and commands object, and changing the *PUBLIC object authority to *EXCLUDE.

Note: To create or update remote or local files using MFT Platform Server Data Transfer Commands, the local and remote user profiles must have authority over the file.



To create or update IBM i files using MFT Platform Server, the IBM i user profile must have *CHANGE authority over the file, *CHANGE authority over the library and *USE authority over the IBM i command CRTPF (create physical file). The administrator can grant this authority to a user profile using the EDTOBJAUT (edit object authority) IBM i command.

The user authority profile can also incorporate all the authority rights needed to use the MFT Platform Server transfer process by being part of a group profile. In other words, the user authority profile can be at the lowest authority level without limit capabilities being *YES or *PARTIAL and still use the MFT Platform Server data transfer commands.

Only a profile with administrator authority has the right to transfer SAVF files using DB2 templates to an IBM i System. If the administrator wants the user authority profile to work with DB2 templates, then the administrator must give *USE authority over the IBM i command RSTOBJ. The administrator can grant this authority to a user profile using the EDTOBJAUT (edit object authority) IBM i command.

To access the MFT Administrative Main Menu, type the following on the command line:

GO CFADM




CFADM MFT Platform Server 7.1.0 Administration Main Menu System: SYSTEM NAME Select one of the following: Menus 1. Configuration Menu 2. Message Log Menu 3. Audit Menu 4. Data Transfer Menu 5. Administration Trans Menu 6. Initiator Scheduler Menu 7. Responder Menu 90. Sign off Selection or command ===> _____________________________________________________________ ___________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu

To access the MFT Platform Server User Main Menu, type the following on the command line:

GO CFMAIN

CFMAIN MFT Platform Server 7.1.0 Main Menu System: SYSTEM NAME Select one of the following: Menus 1. Data Transfer Menu 2. Transaction Menu 90. Sign off Selection or command ===>______________________________________________________________ ___________________________________________________________________ F1=Help F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F16=System main menu



Security Validation

To create or update IBM i files using MFT Platform Server, the IBM i user profile must have *CHANGE authority over the file, *CHANGE authority over the library and *USE authority over IBM i command CRTPF (create physical file). Only profiles with administrator authority can use the DB2 Template, which is used to transfer Save Files.

Security Validation of Incoming MFT Platform Server Transfer Requests

MFT Platform Server provides a security mechanism to insure that transfer requests are not made by unauthorized parties. This mechanism is controlled by the MFT Platform Server for IBM i configuration files.

Node validation: IBM i Network configuration entries must be made before a transfer request will be accepted from a remote node. If a transfer request is received from a MFT Platform Server system that is not defined in the Network Configuration file, the transfer request will be rejected.

IBM i Security Incoming Processing

MFT Platform Server can be configured to allow the IBM i security system to determine whether transfer requests should be received by a certain remote node system. In the Network Configuration screen, the MFT Platform Server administrator can specify a certain remote node name, which gives remote node security rights to receive a transfer request. MFT Platform Server can check the IBM i rights to determine if a transfer request should be allowed for a particular user or remote node name.



Below is an example of the checking that might be performed for a transfer request.

• Transfer request is received by MFT Platform Server for IBM i.

• MFT Platform Server will also utilize the IBM i Security System to determine if the remote user profile name or password that was received is invalid, if so the transfer request will be rejected.

• The IP Address of the MFT Platform Server system that initiated the transfer request is compared against the Network configuration. If an entry was not defined for this IP Address, the transfer request will be rejected.

Security Validation of MFT Platform Server Outgoing Transfer Requests

MFT Platform Server provides a variety of security mechanisms to insure that transfer requests are not made by unauthorized parties. These mechanisms are controlled by the MFT Platform Server for IBM i configuration files. Changes can be placed in two categories:

Network Configuration File: IBM i Network configuration entries must be made before a transfer request will be sent to a remote node. If a transfer request is sent to a MFT Platform Server system that is not defined in the Network Configuration file, the transfer request will be rejected.

User Profile File: IBM i User Profile entries must be made before a transfer request will be sent to a remote node. If a transfer request is sent to a MFT Platform Server system that is not defined in the User Profile file, then the transfer request will be rejected.



IBM i Security Outgoing Processing

MFT Platform Server can be configured to allow the IBM i security system to determine whether transfer requests should be sent out by a particular user to a certain remote node system. In the User Profile screen, the MFT Platform Server administrator can specify a certain local user in which gives the user security rights to send a transfer request to a particular remote node system and sign-on with a certain remote user name and password. MFT Platform Server can check the IBM i rights to determine if a transfer request should be allowed for a particular user or remote node name. Below is an example of the checking that might be performed for a transfer request.

A transfer request to a file by a user profile is detected and then a transfer request record is then created by the MFT Platform Server for IBM i.

MFT Platform Server can determine the target user profile for the transfer request.

If there was no user profile record found for the user profile, the transfer request will be rejected.

The remote node name of the MFT Platform Server system that will receive the transfer request is compared against the Network configuration. If an entry was not defined for this remote node name, the transfer request will be rejected.

The transfer request remote node IP Address of the MFT Platform Server system that will be used to send out the request is invalid a remote network error will occur. Depending on the global parameter file configuration the transfer request will be suspended. Later the transfer request will be activated and



process again. If a remote network error occurs again the transfer request will be rejected.

MFT Platform Server will also utilize the IBM i Security System to determine if the remote user profile name or password that was sent is invalid, if so the transfer request will be rejected.

Already Verified Users

MFT Platform Server for IBM i, z/OS and UNIX support a feature called Already Verified Users. This is sometimes referred to as Trusted Users. The idea of an Already Verified User is to not require a password to accompany a transfer request. Requiring passwords in either a command line or graphical screen is not desirable in many cases. User Profiles can be used to allow a user to complete a file transfer request without entering a password; the disadvantage of User Profiles is that a password is still sent to the server. If the password changes, the user profile must be updated. Note that if Already Verified User is utilized by MFT Platform Server the userid must be the same on both the Client and Server Systems.

When a user logs onto a system (whether IBM i, z/OS, Windows or UNIX) the user is prompted to enter their userid and password and is authenticated by the operating system. When a transfer request is initiated by a user, that user has already been verified by the operating system. The MFT Platform Server can detect the userid that initiated the transfer request. So at this point, the MFT Platform Server knows the userid that initiated the transfer request, and the MFT Platform Server knows that this user has been authenticated by the operating system.

If the Remote Userid and Remote Password parameters have NOT been defined by the MFT Platform Server user, then the MFT



Platform Server will set the Remote Userid to the currently logged on userid, and will set the Remote Password to a special password to indicate that the user has already been verified.

The MFT Platform Server system has the option of accepting or rejecting Already Verified User requests. If the Already Verified User request is accepted, the user is logged onto the system without specifying the userid and password. If the Already Verified User request is rejected, an error is sent to the server that indicates that the Already Verified User request was denied by the node configuration.

Note that any checking for Already Verified User support is done only on the Server side. The Client side will perform the Already Verified User processing regardless of whether Already Verified User is supported when communicating to a specific node.



Auto-start Job Entries Job Entry for Start TCP/IP Command

Auto-start job entry for the Start TCP/IP command, STRTCP, must be created in order to work with the MFT Platform Server auto-start job entry commands. IBM i has the ability to automatically start a job when the related subsystem is started. The IBM i user can create an auto-start job entry to start TCP whenever the subsystem in question is started. This can be very useful when using the STRTCP command. This means that it does not have to be manually started when the IBM i system is IPL’d.

Note: The IBM i Start TCP/IP command, STRTCP, must be processed before the MFT Platform Server Services (Initiator Scheduler or Responder) are started in the QSYSWRK subsystem.

The steps below show how to create the auto-start job entry for the STRTCP command.

Step 1:

End the subsystem using the following command:

ENDSBS SBS(QSYSWRK)

Step 2:

To create the autostart job entry for STRTCP, enter the following command to create a STRTCP job description:

CRTJOBD JOBD(QGPL/STRTCP) JOBQ(QSYS/QSYSNOMAX) TEXT('Autostart Job Start TCP/IP Command JOBD') USER(QPGMR) RQSDTA('QSYS/STRTCP')

Step 3:



Once the job description has been created, it must be attached to the QSYSWRK subsystem. The user may name the job anything they wish. Enter the following command:

ADDAJE SBSD(QSYSWRK) JOB(STRTCP) JOBD(QGPL/STRTCP)

Step 4:

To verify the autostart job entry was successfully applied within the QSYSWRK subsystem, enter the following command, which will display the subsystem description:

DSPSBSD SBSD(QSYSWRK)

Step 5:

Select option 3 and press Enter to Display Auto-start Job Entries.

Step 6:

Verify that the entry exists and is correct then restart the subsystem using the following command:

STRSBS SBSD(QSYSWRK)

Job Entry for Start Initiator Scheduler

IBM i has the ability to automatically start a job when the related subsystem is started. The IBM i user can create an auto-start job entry to start the MFT Platform Server Initiator Scheduler service whenever the subsystem in question is started. This can be very useful when using the CFSTRINT command. This means that it does not have to be manually started when the IBM i system is IPL’d.

Note: The TCP/IP Protocol (STRTCP) must be started before executing the CFSTRINT command.



The steps below show how to create the auto-start job entry for the CFSTRINT command.

Step 1: End the subsystem using the following command:

ENDSBS SBS(QSYSWRK)

Step 2: To create the auto-start job entry for CFSTRINT, enter the following command to move the job description:

MOVOBJ OBJ(“Production Library Name”/CFSTRINT#) OBJTYPE(*JOBD) TOLIB(QGPL)

Step 3: Once the job description has been moved, it must be attached to the QSYSWRK subsystem. The user may name the job anything they wish. Enter the following command:

ADDAJE SBSD(QSYSWRK) JOB(CFSCHED) JOBD(QGPL/CFSTRINT#)

Step 4: To verify the auto-start job entry was successfully applied within the QSYSWRK subsystem, enter the following command, which will display the subsystem description:


Step 5: Select option 3 and press Enter to Display Auto-start Job Entries.

Step 6:

Verify that the entry exists and is correct then restart the subsystem using the following command:




Job Entry for Start Responder Command

IBM i has the ability to automatically start a job when the related subsystem is started. The IBM i user can create an auto-start job entry to start the MFT Platform Server Responder service whenever the subsystem in question is started. This can be very useful when using the CFSTRRSP command. This means that it does not have to be manually started when the IBM i system is IPL’d.

Note: The TCP/IP Protocol (STRTCP) must be started before executing the CFSTRRSP command. The MFT Platform Server product has a TCP/IP Protocol Connection Retry Routine. The MFT Platform Server Responder program will keep trying to connect to TCP/IP Protocol on the IBM i system for 5 minutes. If no connection is made in that time frame, then it will send an error message and end the program

The steps as listed below show how to create the auto-start job entry for the CFSTRRSP command.

Step 1: End the subsystem using the following command: ENDSBS SBS(QSYSWRK)

Step 2: To create the auto-start job entry for CFSTRRP, enter the following command to move the job description:

MOVOBJ OBJ(“Production Library Name”/CFSTRRSP#) OBJTYPE(*JOBD) TOLIB(QGPL)

Step 3:



Once the job description has been moved, it must be attached to the QSYSWRK subsystem. The user may name the job anything they wish. Enter the following command:

ADDAJE SBSD(QSYSWRK) JOB(CFRESP) JOBD(QGPL/CFSTRRSP#)

Step 4: To verify the auto-start job entry was successfully applied within the QSYSWRK subsystem, enter the following command, which will display the subsystem description:


Step 5: Select option 3 and press Enter to Display Auto-start Job Entries.

Step 6: Verify that the entry exists and is correct then restart the subsystem using the following command:


SSL 125


SSL The Secure Sockets Layer, also known as SSL, was originally developed by Netscape Communications to allow secure transport of data over the Internet. Secure transport of data involves more than just encrypting data. SSL performs authentication and data encryption. This chapter is an explanation of how SSL implements authentication and data encryption.

Topics

• Authentication • Data Encryption • Digital Certificates • SSL Authorization

126 SSL


Authentication

In simple terms, authentication allows a client to confirm the identity of the Server, and the server to confirm the identity of the client. When I want to purchase a book, I connect to Amazon.com. Prior to entering my credit card information, I want to insure that I am REALLY connected to Amazon.com. This is done via Server Authentication. The SSL Software on my PC communicates with the server, and insures that the server is the real Amazon.com server. However, the Amazon.com server does not care who I am. As long as I enter my credit card information, it is unimportant that they check who I am. However, when it comes to transporting sensitive information, it is critical that the server authenticates the remote clients. When an MFT Platform Server receives a file transfer request from a remote system, it is important that we verify the identity of the remote system before we accept the data. This is called Client Authentication. MFT Platform Server supports both Server and Client authentication. That way, we can insure the client validates the identity of the server, and the server validates the identity of the client. Only after this authentication is complete, will MFT Platform Server allow a transfer to continue.

SSL 127


Data Encryption

When data is sent across an unsecured line, it is vulnerable to two types of attacks:

1. The data can be read by unauthorized people.

2. The data can be altered by unauthorized people.

The first problem can be resolved by simply encrypting the data. The second problem is more difficult because it requires us to detect that data has been changed. SSL accomplishes this by adding a message digest to all transmitted data. A message digest is a condensed representation of any message. The SHA produces a 20-byte message digest for every packet of data. If any component of the data changes, the message digest will almost certainly change. Both the sending and receiving side of a connection perform the message digest on the unencrypted data. The receiving side then insures that the message digests are the same before accepting the data.

There are two types of encryption algorithms that are used within SSL. They are asymmetrical encryption and symmetrical encryption.

Asymmetrical Encryption

Asymmetrical encryption is when the sending and receiving systems use different keys to encrypt and decrypt the data. This is typically done with public and private keys. Data is encrypted with a private key and is decrypted with a public key. That means that any user that has the public key can decrypt the data. Optionally, data can be encrypted with a remote user’s public key and the remote user can decrypt the data with its private key.

128 SSL


That way, only a user that has the private key is capable of decrypting the data. The main disadvantage of Asymmetrical encryption algorithm is that they are typically slower than Symmetrical Encryption algorithms.

Symmetrical Encryption

Symmetrical Encryption algorithms use the same key for both encryption and decryption of data. Symmetrical encryption algorithms are usually more efficient than Asymmetrical encryption algorithms. The disadvantage to Symmetrical encryption algorithms is that both sides must use the same key to encrypt and decrypt data. Obviously it would be a bad thing to send an encryption key over the line. SSL solves this problem by using a combination of Asymmetrical and Symmetrical encryption. The SSL software performs its handshake using Asymmetrical encryption. Then the software sends the Symmetrical encryption key encrypted by the Asymmetrical encryption algorithm. That way, both partners have the same encryption key, but the key was transmitted in a very secure form. From this point on, data can be transmitted using the more efficient Symmetrical encryption algorithm. Symmetrical encryption algorithms supported include DES, Triple DES (also known as TDES), Blowfish and AES (also known as Rijndael).

SSL 129


Digital Certificates

SSL uses digital certificates to confirm identity in two ways. The digital certificate confirms the owner’s identity. A digital certificate received allows a user to identify their communications partner. This is the component that is presented to the remote user to perform authentication. This includes the public key that enables others to decrypt data that is encrypted with our private key.

Note that MFT Platform Server is not a Certificate Manager. MFT Platform Server does not create certificates, nor does it manage certificates. MFT Platform Server uses certificates that are produced by the Certificate Authority. The contents of a certificate are governed by the X.509 certificate specification. Typical contents of a certificate include:

• Certificate version number

• Certificate Serial Number

• Information about the Certificate Authority that issues the certificate

• The public key and the algorithm that created it

• The time in which the certificate is valid and information about the owner of the certificate

Certificate Authority

When a certificate is received, there must be a way to validate that the certificate is valid. When a certificate is created, the Certificate Authority adds a digital signature to the certificate. A

130 SSL


digital signature is simply a piece of data that is encrypted using the private key of the Certificate Authority. Using the public key of the file, the data can be decrypted and validated. When a is checked, you can see the CA that created the certificate. But can you trust this CA, and did this CA actually issue the certificate? There is an additional keystore that MFT Platform Server uses that defines the Certificate Authorities that SSL will trust. SSL checks the Trusted CA keystore to see if the CA that issued the certificate is defined. If it is in the keystore, SSL uses the public key to the decrypt and validate the CA digital signature on the user’s certificate. Only if the CA is included in the Trusted CA keystore, and the CA Signature is valid, will SSL accept a certificate request.

Creating and Importing Certificates

The certificate can be generated using certificate authority such as Verisign, RECF, or using IBM i as a local certificate authority. The following describes the steps to generate a certificate using a certificate authority to generate the certificate.

Here is the general flow of generating a certificate:

1. Generate a certificate request so that CA can issue a certificate.

2. Receive CA certificate and server certificate from CA. 3. Import certificates. 4. Assign application to use server certificate. Below each step is listed with more detail.

1. Generate a certificate request.

SSL 131


a. Make sure that HTTP *Admin server on IBM i is running. b. Start a web browser. c. Enter http://HostName:2001/ in the Address field. HostName is the IP Name or Address of IBM i. d. Enter your IBM i userid and password. e. In the left hand panel click “Internet Configurations”. f. In the right hand panel click the “Digital Certificate Manager” link. You will be prompted for your user id and password again. Enter them and click the OK button. f. On the left pane, click “Select a Certificate Store”. g. It may take few seconds for the right pane to refresh. Select “System” and hit “Continue”. h. The name of the *SYSTEM certificate store will display which is: /QIBM/USERDATA/ICSS/CERT/SERVER/DEFAULT.KDB. Type the password for the certificate store. Hit “continue”. (Do not hit the Enter key on V5R1 as this may result in NET.DATA Error.) i. The name of the *SYSTEM certificate store will display which is: /QIBM/USERDATA/ICSS/CERT/SERVER/DEFAULT.KDB. Type the password for the certificate store. Hit “continue”. (Do not hit the Enter key on V5R1 as this may result in NET.DATA Error.) j. On the left pane, click “Create Certificate”. k. On the right pane, click “Server or Client Certificate” hit “Continue”. l. Select “VeriSign or other Internet Certificate Authority (CA)”. m. Fill in the form. Click “Continue”. This will create a Certificate Request. n. Copy and paste the certificate request to be sent to your CA.

http://hostname:2001/�

132 SSL


SSL 133


2. Receive CA certificate and server certificate from CA. a. Send the certificate request to CA. Copy and paste the certificate request to a separate file, or use the form provided by your CA. b. CA will create the certificate and return it back to you. You will also need the CA certificate. If this is not returned with the certificate, then you will need to download it from the CA. c. When receiving certificates from CA, save them in the IFS file system and note the path.

3. Import CA and Server certificates. a. Click “Manage Certificates” on the left pane. b. Select “Import Certificate”. c. Select “Certificate Authority (CA)” to import the CA certificate (see step 1.m.) to the *SYSTEM certificate store first. The path of the certificate locations is used in step 2.a. The CA certificate must be imported before you can import the server certificate.

134 SSL


d. Go back to step 3.b. to “Import Certificate”.

e. This time, select “Server or Client”.

f. Import the server certificate from IFS to the *SYSTEM certificate store. The path of the certificate locations is used in step 2.a.

4. Add the Application to assign Server Certificates a. On the left pane, click “Manage Applications” and then from the sub menu click “Add Application”. b. Select “Server”. c. Type in Application ID and Application description. Application ID is the name of MFT Platform Server and Client Application ID. This Application ID must be defined in the MFT Global Configuration file. The default value for the server and client is “SSLCERTIFICATE” (see “Global Configuration”). Application Description is user defined.

SSL 135


You do not have to update any other fields. Click Add. d. Now click “Update certificate assignment”. e. Select “Server”. f. Select the MFT Platform Server application from the list. g. Click the “Update Certificate Assignment” button. h. Verify the certificate that you are assigning to the application and click the “Assign New Certificate” button when you are done. i. You are now ready to run your MFT Platform Server application with SSL.

136 SSL


SSL Authorization MFT Platform Server supports an extension to the standard SSL processing to allow the system administrator to determine which certificates should be accepted and which should be rejected. This is done by the creation of an SSLAUTH file. This is supported on all MFT Platform Servers. The format of the file is the same on all platforms, but the way that the file is defined is dependent on each platform.

For IBM i, SSLAUTH file is located in IFS. The path is defined in the MFT Platform Server Global Configuration file (see below).

CFWRKGLB TIBCO Software Inc. MFT Platform Server 7.1.0 QSECOFR 3/06/13 SYSTEM Work With Global Parameter Screen UPDATE 15:44:15

Type choices, Press Enter.

SSL TCP/IP Listen Port No..: 56565 (1024-65535) SSL Encryption..: 3 (0=None 1=DES 2=TDES 3=Blowfish 4=Blowfish Long 5=Rijndael) SSL Client Application ID..: SSLCERTIFICATE______________________ SSL Server Application ID..: SSLCERTIFICATE______________________ Use SSL Authorization File.: N (Y/N) SSL Authorization File Name: /qsys.lib/mftplat710.lib/sslauth.file/sslauth.mbr__ F1=Help F3=Exit F12=Previous Screen ENTER=Update Record

Note that the authorization file checking is above and beyond the authorization checking performed by SSL. Only if a certificate is accepted by SSL will the authorization file processing be performed.

The authorization file is compared against the Certificate that was received by the MFT Platform Server. The authorization file is not used on MFT clients. The components of the Certificate’s

SSL 137


Distinguished Name (DN) are compared to the parameter in the authorization file to determine if a certificate should be accepted or rejected. On many of the parameters, a generic character is supported. A generic character is defined in a parameter by an *. When a generic character is defined, all characters from that point on are assumed to be a match.

If no authorization file is defined, or a match is not found in the authorization file, the request will be accepted. If you want to reject all requests unless defined by the authorization file, then you should insert the following statement as the last entry in the authorization file:

REVOKE

There are two request types supported within the authorization file:

ACCEPT Accept an SSL request

REVOKE | REJECT Do not accept an SSL request

All of these requests accept a variety of parameters. If a parameter is not defined, then it is assumed that the parameter is a match. Parameters can be defined on a single line or they can be continued over multiple lines. If the input record ends with a comma (,) then the input record will be continued on the next record. All parameter data is case sensitive. Be very careful when entering the values when using mixed case fields.

SSL Authorization Parameters

Parameters allowed in the authorization file. These parameters must be defined in upper case.

138 SSL


/CN Define the Common Name defined in the Certificate. This is usually the name of the person who is requesting the certificate. Generic entries are supported.

/OU Defines the Organization Unit defined in the Certificate. This is also known as the Department. Generic entries are supported.

/O Defines the Organization defined in the Certificate. This is also known as the Company. Generic entries are supported.

/L Defines the Locality defined in the Certificate. This is also known as the City. Generic entries are supported.

/ST Defines the State/Province defined in the Certificate. Generic entries are supported.

/C Defines the Country defined in the Certificate. Generic entries are supported.

/SN Defines the Serial Number defined in the certificate. Generic entries are NOT supported.

/SDATE Defines the Start date for the certificate in the format: ccyymmdd. Generic entries are NOT supported. The start date is compared against the date that the transfer request is received by MFT Platform Server. If the start date is before the current date, then SSLAUTH processing will check the next parameter. If the start date is after the current date, then the transfer request will be terminated and an error will be sent to the remote system.

/STIME Defines the Start time for the certificate in the format: hhmm. Generic entries are NOT supported. The start time is only checked if the SDATE parameter exactly matches the

SSL 139


current date. The start time is compared against the time that the transfer request is received by MFT Platform Server. If the start time is before the current time, then SSLAUTH processing will check the next parameter. If the start time is after the current time, then the transfer request will be terminated and an error will be sent to the remote system.

/EDATE Defines the End date for the certificate in the format: ccyymmdd. Generic entries are NOT supported. The end date is compared against the date that the transfer request is received by MFT Platform Server. If the end date is after the current date, then SSLAUTH processing will check the next parameter. If the end date is before the current date, then the transfer request will be terminated and an error will be sent to the remote system.

/ETIME Defines the End time for the certificate in the format: hhmm. Generic entries are NOT supported. The end time is only checked if the EDATE parameter exactly matches the current date. The end time is compared against the time that the transfer request is received by MFT Platform Server. If the end time is after the current time, then SSLAUTH processing will check the next parameter. If the end time is before the current time, then the transfer request will be terminated and an error will be sent to the remote system.

/USER This parameter is supported only by the IBM i and z/OS system. It allows the administrator to define a userid that should be used when an SSL certificate is accepted. This userid overrides the userid associated with the file transfer. Using this option, the remote user does not have to have any knowledge of a userid/password on this system.

Examples of authorization file processing:

140 SSL


Accept /OU=Marketing/O=TIBCO

revoke

MFT Platform Server will accept all certificates defined with an Organization of TIBCO and an Organization Unit of Marketing. It will reject all other certificates.

REVOKE /SN=987654

REVOKE /SN=123456

ACCEPT

MFT Platform Server will reject any certificates with a serial number of 987654 or 123456. It will accept all other certificates.

Accept /OU=ACCT*/O=ACME

revoke

MFT Platform Server will accept all certificates defined with an Organization of ACME and an Organization Unit starting with ACCT. It will reject all other certificates.

Accept /CN=Joe*,

/L=New York,

/ST=NY,

/C=US,

/OU=Dept1,

/O=ACME,

/SDATE=20081201,

SSL 141


/EDATE=20101130

revoke

MFT Platform Server will accept all certificates that match the information defined by the /CN, /L, /ST, /C, /OU and /O parameters. The certificate is valid from December 1, 2008 until November 30, 2012. If the certificate is received before December 1, 2008 or after November 30, 2012, the request will be rejected. All other certificates not matching these criteria will be rejected.

142 Utilities


Utilities In this chapter you will learn how to install MFT Platform Server for IBM i. The main procedures will instruct you how to:

Topics

• FUSUTIL • FUSPING • Sizing Guidelines

Utilities 143


FUSUTIL When a file transfer completes, the user may wish to perform some action such as renaming or deleting a file. All of the platforms have different commands to rename or delete a file. This utility will allow the use of a common interface to rename or delete a file. Additionally, it enables the user to see if a file exists on a remote platform.

Overview

There are three functions of the FUSUTIL utility:

Delete File Rename File Determine if a file exists

When a request is received by the MFT Platform Server, the request should be converted to the proper request for that operating system. The following table shows the relationship between the FUSUTIL command and the operating system command.

In the table shown above, N/A means that there is no operating system request that performs the function. Note that there must be one or more spaces between the command parameters.

FUSUTIL Command Format

The first parameter is required and is the command name:

Parameter WINDOWS UNIX z/OS IBM i RENAME MOVE mv N/A RNMOBJ

DELETE ERASE rm N/A DLTF

EXIST N/A N/A N/A CHKOBJ

144 Utilities


FUSUTIL

The second parameter is required and is the request type:

RENAME: Rename a file R: Rename a file DELETE: Delete a file D: Delete a File EXIST: See if a file exists E: See if a file exist

The third parameter is required and defines the file name for each option. The fourth parameter is required only for Rename; it defines the new file name.

Examples:

FUSUTIL DELETE my.file FUSUTIL D my.file FUSUTIL RENAME my.file my.new.file FUSUTIL R my.file my.new.file FUSUTIL EXIST my.file FUSUTIL E my.file

Special Processing

When processing the EXIST function, you should also ensure that the file is available for use. This should be done on all platforms except UNIX, since there is no standard call to accomplish this on UNIX.

Return Codes When the function is successful, the return code is set to 0, and any output data is returned to caller, in the same way as any other command.

Utilities 145


When the function is unsuccessful, the return code is set to a non-zero value, and a send error is returned to the caller along with a message indicating the cause of the failure (if possible).

Monitoring Messages

FUSUTIL command returns CPF messages when error condition occurs. These messages can be monitored by MONMSG command in CL program. The most common messages are:

CPF9801 Object not found. CPF9810 Library not found. CPF3202 Object in use.

146 Utilities


FUSPING MFT Platform Server FUSPING utility can be used to determine the version and release of MFT Platform Server products and determine if MFT Platform Server on a remote system is active. Data returned from the FUSPING utility could include information such as system name, port version and license key expiration.

Overview

The program is called FUSPING. On IBM i, the parameters are case insensitive and will be delimited by a space or a colon. The Responder will return System and MFT Platform Server versions and key information to the Initiator.

Userid and password are NOT validated in this program. You do not need a userid or password to perform a FUSPING request. However, the remote system must be configured to accept a FUSPING request by adding the Command Center Support parameter with a value of PING or ALL.

If an error is detected by the Responder, a message will be generated containing the cause of the failure.

FUSPING Command Parameters

There are 2 ways in which the FUSPING command can be accessed. The first is by entering FUSPING on the command line and pressing F4. The panel below will be displayed.

Utilities 147


Ping Command (FUSPING) Type choices, press Enter. Ping Request Command . . . . . . Character value Ping Parameter 1 . . . . . . . . _______________ Ping Parameter 2 . . . . . . . . _______________ Ping Parameter 3 . . . . . . . . _______________ Ping Parameter 4 . . . . . . . . Character value F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

The first entry is required and is the command name:

FUSPING

The request command is the first parameter and is required. It specifies the ping request or host command. For FUSPING, this parameter would be r or request.

Ping Parameter 1 is the second parameter and is not required. It specifies the first parameter of the ping command. For FUSPING, this parameter would be version.

Ping Parameter 2 is the third parameter and is not required. It specifies the second parameter of the ping command. For FUSPING, this parameter would be h or host.

Ping Parameter 3 is the fourth parameter and is not required. It specifies the third parameter of the ping command. For FUSPING, this parameter would be IP Name (SYSTEM1) or IP Address (11.22.33.44).

Ping Parameter 4 is the fifth parameter and is not required. It specifies the fourth parameter of the ping command. For FUSPING, this parameter would be the IP Port (46464).

148 Utilities


FUSPING Command Line Parameters

The second way the FUSPING command can be accessed is by entering the entire command on the command line. The format of the FUSPING command is as follows:

FUSPING REQUEST VERSION HOST:IPNAME:IPPORT

FUSPING Command Format

The FUSPING command can be executed in several different ways. Below are the various formats that can be used.

FUSPING REQUEST VERSION HOST:IPNAME:46464 FUSPING REQUEST VERSION H:IPNAME:46464 FUSPING REQUEST VERSION HOST: '999.999.999.999' 46464 FUSPING REQUEST VERSION H: '999.999.999.999' 46464 FUSPING REQUEST VERSION HOST:IPNAME FUSPING REQUEST VERSION H:IPNAME FUSPING REQUEST VERSION HOST: '999.999.999.999' FUSPING REQUEST VERSION H: '999.999.999.999' FUSPING R:VERSION HOST:IPNAME:46464 FUSPING R:VERSION H:IPNAME:46464 FUSPING R:VERSION HOST:IPNAME FUSPING R:VERSION H:IPNAME FUSPING R:VERSION HOST: ’999.999.999.999’ 46464 FUSPING R:VERSION H: ’999.999.999.999 46464 FUSPING R:VERSION Host: ’999.999.999.999’ FUSPING HOST: ’999.999.999.999’ 46464 FUSPING H: ’999.999.999.999’ 46464 FUSPING HOST: ’999.999.999.999’ FUSPING H: ’999.999.999.999’

Parameter Shortcut Values Required Description REQUEST R VERSION YES Version indicates that

this is a PING Version request. If this parameter is not defined, the default is VERSION.

HOST H IPNAME:PORT IPADDR:PORT

YES Defines the IP Address or IP Name to PING. If the PORT parameter is not defined, then the PORT will default to

Utilities 149


In the samples above, 46464 is the port and 999.999.999.999 is the IP Address. Also note, in most cases, there is a space after the HOST parameter when the IP Address is used. The chart below shows the shortcuts that may be used in the FUSPING command.

Sample of the FUSPING Command

Below is a sample of the FUSPING command for a remote MFT Platform Server on a UNIX system as well as the output of the command.

fusping request version host: '11.22.33.44' 46464

Output:

Host: 11.22.33.44 Port: 46464 System Name: Unix1 Key Expiration: 20121008 Version: cfsend, MFT: MFT Initiator Version 7.1 Build 290 cfrecv, MFT: MFT Initiator Version 7.1 Build 290 cfdir, 7.1 Build 272 cfnode, TIBCO (R) cfnode - MFT Node Definition Maintenance Utility Copyright (C) TIBCO Software Inc 1995-2012. ALL RIGHTS RESERVED. 7.1 Build 290 cfprofile, TIBCO (R) cfprofile - MFT User Profile Maintenance Utility Copyright (C) TIBCO Software Inc 1995-2012. ALL RIGHTS RESERVED. 7.1 Build 290

46464.

HELP N/A N/A No Shows Help screen.

150 Utilities


cfrprofile, TIBCO (R) cfrprofile - MFT Responder Profile Maintenance Utility Copyright (C) TIBCO Software Inc 1995-2012. ALL RIGHTS RESERVED. 7.1 Build 290

FUSPING Help

Help for fusping can be obtained by using one of the following commands:

FUSPING HELP FUSPING H

Below is the output of the fusping help request:

fusping - PING Maintenance Utility usage: fusping [parameters:][values] [parameters]: r: or Request: - Type of Request. Only "Version" is supported h: or Host and Port: - IpAddress:PortNumber or IpName:PortNumber Help: - For Help Information

Monitoring Messages

FUSPING command returns messages when error condition occurs. The most common messages are:

Failed to Allocate Conversation. Invalid Parameter. Type Help for Help Information. Only "Version" Request is accepted.

Help information will be display if the command was entered incorrectly as shown below:

fusping - PING Maintenance Utility usage: fusping [parameters:][values] [parameters]:

Utilities 151


r: or Request: - Type of Request. Only "Version" is supported h: or Host and Port: - IpAddress:PortNumber or IpName:PortNumber Help: - For Help Information

152 Utilities


Renaming the Product Library The Rename Product Library (CFRNMLIB) command is used to rename the MFT Platform Server Product Library. It will define the Product Library Name and ensure that all the proper MFT Platform Server objects are either attached or installed into the new MFT Platform Server Product Library Name.

Note: Do not precede an entry with an asterisk unless the entry is a "special value" that is shown (on the display itself) with an asterisk.

This panel can only be accessed by typing the following on the command line:

CFRNMLIB


Rename Product Library (CFRNMLIB) Type choices, press Enter. To Library . . . . . . . . . . _________________ Name F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

• To Library (*req. field)

Specify the new library name that the user wants the MFT Platform Server library to be called.

Appendix A 153


Appendix A – Code Page Conversion Appendix A discusses the Code Page Conversion (CFCDEPGECV) command that uses the IBM Code Page CCSID tables and converts single/double coded character set identifier (CCSID) from a data file on the IBM i system to another single/double coded character set identifier (CCSID). Then copies or replaces the data to another local IBM i system file. MFT Code Page Conversion command converts ASCII from/to EBCDIC machine code translation.

Topics

• Code Page Conversion Panel

154 Appendix A


Code Page Conversion Panel Using the Code Page Conversion command can be done with a panel or it can be issued directly from the command line. In order to accomplish the MFT Platform Server Code Page Conversion of IBM i system files from the panel, the user may enter the following command from the command line and pressing the <F4> key to present the panel:.

CFCDEPGECV

Code Page Conversion (CFCDEPGECV) Type choices, press Enter. From File Name . . . . . . . . . TESTFILE Name Library Name . . . . . . . . . TESTLIB Name Member . . . . . . . . . . . . TESTMBR Name To File Name . . . . . . . . . . TESTFILE2 Name Library Name . . . . . . . . . TESTLIB2 Name Member . . . . . . . . . . . . TESTMBR2 Name From CCSID Code . . . . . . . . 00874 00001-65533 To CCSID Code . . . . . . . . . 00838 00001-65533 F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

Enter all MFT Code Page Conversion command parameters and press Enter.

Note: All MFT Code Page Conversion command parameters are validated and must be entered.

Code Page Conversion Parameters

Listed below are the parameters, with a brief description, for the panels when the CFCDEPGECV command is issued. Also listed in

Appendix A 155


parenthesis are the parameters that would be used on the command line.

• From File Name (FROMFILE)

Specifies the name of the local file that will be converted.

• Library Name

Specifies the library name containing the file that will be converted.

• Member (*req. field)

Specifies the member name within the file that will be converted.

• To File Name (TOFILE)

Specifies the name of the local file that will receive the converted data.

• Library Name

Specifies the library name containing the file that will receive the converted data.

• Member (*req. field)

Specifies the member name within the file that will receive the converted data.

• From CCSID Code (*req. field)

This parameter defines the Coded Character Set Identifier that the from-file contains. Valid values range from 00001 through 65533.

• To CCSID Code (*req. field)

This parameter defines the Coded Character Set Identifier that the to-file will contain. Valid values range from 00001 through 65533.

156 Appendix A


Example Command Line Code Page Conversions

Example 1:

The Code Page Conversion command can be run directly from the command line. Below is an example:

The example shows a MFT Platform Server Code Page Conversion on the IBM i system.

CFCDEPGECV FROMFILE(TESTMBR/TESTLIB/TESTFILE) TOFILE(TESTMBR2/TESTLIB2/TESTFILE2) FCCSID(00874) TCCSID(00838)

Example 2:

Below is an example of adding Post Processing entries utilizing the MFT Platform Server Code Page Conversion command on all MFT Platform Server transfer panel commands from the CFSRF panel.

The first entry is calling a custom made code page conversion post process driver program.

The second entry is executing the MFT Platform Server Code Page Conversion command.

CFSRF TIBCO Software Inc. – MFT Platform Server 7.1.0 03/06/13 Post Processing Options............................ : ACTION Fields (Up to 4 parameters allowed) : : (ST: S=Success F=Failure) : : (SRC: L=Local R=Remote) : : ST SRC CMD (CMD: 1=CALLPGM 2=COMMAND 3=CALLJCL 4=SUBMIT) : : S R 2 CALL PGM(A2E) PARM(‘TESTMBR/TESTLIB/TESTFILE’ ’TESTMBR2/TESTLIB2 : : /TESTFILE2’) : : S R 2 CFCDEPGECV FROMFILE(TESTMBR/TESTLIB/TESTFILE) TOFILE(TESTMBR2/TE : : STLIB2/TESTFILE2) FCCSID(00874) TCCSID(00838) : :

Appendix A 157


: : : : F1=Help F3=Exit F12=Cancel.................................................

If you want to add the same Post Processing examples shown above via the command line you would enter the following:

POSTPROC(*YES) POSTFLG1(*S) POSTACT1(*L) POSTTYP1(*CMD) POSTDAT1(' CALL PGM(A2E) PARM(''TESTMBR/TESTLIB/TESTFILE'' ''TESTMBR2/TESTLIB/TESTFILE'')')

POSTPROC(*YES) POSTFLG1(*S) POSTACT1(*L) POSTTYP1(*CMD) POSTDAT1('CFCDEPGECV FROMFILE(TESTMBR/TESTLIB/TESTFILE) TOFILE(TESTMBR2/TESTLIB2/TESTFILE2) FCCSID(00874) TCCSID(00838)')

Appendix B 158


Appendix B – Time File Name Token When setting up a file transfer the time token may be used in the file name. The token format is as follows:

$(TIME)

This token will substitute the system time in the file name. For example, if the system time is, 5:03:45 PM, the following value placed in the file name field:

MYLIBRARY/$(TIME)

Would resolve to:

MYLIBRARY/170345

Index 159


Index Administration Transaction

CFPRGREQ, 97 Audit Log

CFPRGAUD, 50 autostart, 128, 129, 131 autostart job entry, 128, 130, 131 certificate request, 138 CFAPYKEY, 16 CFSTRINT, 100, 102 Collector, 35 Command, 60, 67, 72, 78, 85, 90, 115 command line, 12, 14, 110, 115, 116,

117, 162, 163, 164 Configuration

Global CFDSPGLB, 26

CFUPDGLB, 32

TCP/IP Listen Port Number, 163

Network CFREORGNET, 39, 44

User Profile CFPRFMNU, 40

CyberFusion, 7 Distinguished Name, 145 FUSUTIL, 151

DELETE, 152 EXIST, 152 RENAME, 152

Global, 25, 32 installing, 7 JCL, 60, 67, 72, 78, 85, 90 License Key, 16 Management, 7

menu CFADM, 23, 121 CFAUDMNU, 50 CFCONFMNU, 24 CFGLBMNU, 25 CFMAIN, 122 CFMSGMNU, 45 CFPRFMNU, 39

Message Log CFPRGMSG, 49 CFWRKMSG, 46

parameters, 110, 112 password, 13, 57, 65, 71, 76, 82, 87 Port Number, 38 Post Processing Options

CMD, 60, 67, 72, 78, 85, 90 SRC, 60, 67, 72, 78, 85, 90 ST, 60, 67, 72, 78, 85, 90

remote node, 37, 43 request types

supported, 145 security, 99, 101, 123, 125 Security, 40 Send Command Line

FROMFILE, 163 SSL, 102, 103, 133, 134, 135, 144 System Configuration, 37 TCP, 38 transfer, 14, 60, 67, 72, 78, 85, 90, 124 Transfer, 7, 35 UNIX, 56, 64 Windows, 56, 64 z/OS, 56, 64

mft platform server for ibm i - tibco product … 6 tibco® managed file transfer platform server...

Documents