NetView File Transfer Program Version 3 for OS/400 IBMpublib.boulder.ibm.com/tividd/td/netviewFTP/SH12-6177-01/...NetView File Transfer Program Version 3 for OS/400 A C 12 H ff W g

NetViewFile Transfer ProgramVersion 3 for OS/400

A

C 12

Hff

W

g

ZH

IBM

Installation and User's Guide

SH12-6177-01

NetViewFile Transfer ProgramVersion 3 for OS/400 IBM

Installation and User's Guide

SH12-6177-01

Note!

Before using this information and the product it supports, be sure to read the general information under “Notices” on page v.

Second Edition, March 1996

This is a major revision of, and obsoletes, SH12-6177-00.

This edition applies to Version 3 Release 1 of NetView File Transfer Program for OS/400 (5733-196), Version 3 Release 6 ofNetView File Transfer Program for OS/400 (5798-TBG), and to all subsequent releases and modifications until otherwise indicated innew editions or technical newsletters. Technical changes or additions to the text and illustrations are indicated by a vertical line tothe left of the change. Make sure you are using the correct edition for the level of the product.

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at theaddress below.

IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you may addressyour comments to the following address:

NetView FTP Information DevelopmentRome Networking Software LaboratoryIBM SEMEA S.p.A.Piazzale G. Pastore, 6

00144 Rome Italy

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believesappropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1991, 1996. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiAbbreviations and Special Terms . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1. What NetView File Transfer Program Is and Does . . . . . . . . 1The Structure of NetView FTP/400 V3 . . . . . . . . . . . . . . . . . . . . . . . . 2Creating File-Transfer Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3How NetView FTP Processes Requests . . . . . . . . . . . . . . . . . . . . . . . 5Using NetView FTP/400 V3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Using the Interactive Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Using the Control Language Interface . . . . . . . . . . . . . . . . . . . . . . . 7Writing Application Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Protecting Requests from Unauthorized Access . . . . . . . . . . . . . . . . . 7Specifying when NetView FTP/400 V3 Can Process a Request . . . . . . . . 8Assigning Server Classes and Priorities to Requests . . . . . . . . . . . . . . 8Using Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Identifying Remote Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Checking Requests at the Remote System . . . . . . . . . . . . . . . . . . . . 9

What You Need to Know about Files . . . . . . . . . . . . . . . . . . . . . . . . . 9Types of File NetView FTP Can Transfer . . . . . . . . . . . . . . . . . . . . . 9Transferring Files to OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Sending Files to and Retrieving Files from MVS, VM, and VSE . . . . . . . 13Automatically Creating Names for New Receiving Files . . . . . . . . . . . . 14

ASP Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Log File and Report File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Automatic Logon Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Restarting an Interrupted File Transfer . . . . . . . . . . . . . . . . . . . . . . . 16NetView FTP/400 V3 Prestarted Jobs . . . . . . . . . . . . . . . . . . . . . . . . 17Messages and Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Local Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Remote Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Communication Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 18Auditability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2. Installing NetView FTP/400 V3 . . . . . . . . . . . . . . . . . . . . 21Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Performing a NetView FTP/400 V3 Installation . . . . . . . . . . . . . . . . . . . 21

Authorizing NetView FTP/400 Users . . . . . . . . . . . . . . . . . . . . . . . 23Installing Other Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setting Up the Communication Configuration . . . . . . . . . . . . . . . . . . . . 26Setting Up the LU Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Verifying the Installation of NetView FTP/400 V3 . . . . . . . . . . . . . . . . . 29

Copyright IBM Corp. 1991, 1996 iii

Chapter 3. Using the NetView FTP/400 V3 Panels . . . . . . . . . . . . . . . 31Entering Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31The Panel Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Invoking NetView FTP/400 V3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Getting Help from NetView FTP/400 V3 . . . . . . . . . . . . . . . . . . . . . . . 33Creating a Request to Send a File . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Additional Panels for OS/400 Files . . . . . . . . . . . . . . . . . . . . . . . . 37Additional Panels for MVS Files . . . . . . . . . . . . . . . . . . . . . . . . . . 38Additional Panels for VM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Additional Panels for VSE Files . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Limiting the Scope of the Request List . . . . . . . . . . . . . . . . . . . . . . . 41Changing a Request to Send a File . . . . . . . . . . . . . . . . . . . . . . . . . 41Displaying a Request to Send a File . . . . . . . . . . . . . . . . . . . . . . . . . 42Creating, Changing, and Displaying a Request to Retrieve a File . . . . . . . . 42Displaying a File-Transfer Report . . . . . . . . . . . . . . . . . . . . . . . . . . 43Displaying Log Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Copying Selected Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Deleting Selected Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Renaming Selected Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Releasing and Holding File-Transfer Requests . . . . . . . . . . . . . . . . . . . 47Restarting Failed File-Transfer Requests . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4. Using the NetView FTP/400 V3 Administrator Panels . . . . . . 49Entering Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49The Panel Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Administering NetView FTP/400 V3 . . . . . . . . . . . . . . . . . . . . . . . . . 51

Working with Local Components . . . . . . . . . . . . . . . . . . . . . . . . . 51Working with Remotely Started Components . . . . . . . . . . . . . . . . . . 55Working with LU Directory Entries . . . . . . . . . . . . . . . . . . . . . . . . 57Printing Information File Entries . . . . . . . . . . . . . . . . . . . . . . . . . . 62Removing Information File Entries . . . . . . . . . . . . . . . . . . . . . . . . 63Removing Restart File Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Working with the Startup File . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Working with NetView FTP/400 V3 Administrators . . . . . . . . . . . . . . . 66Starting the NetView FTP/400 V3 Subsystem . . . . . . . . . . . . . . . . . . 67Reclaim DTAQ Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Printing NetView FTP/400 V3 History-File Entries . . . . . . . . . . . . . . . 68Deleting NetView FTP/400 V3 History-File Entries . . . . . . . . . . . . . . . 69

Chapter 5. Using the Control Language Interface . . . . . . . . . . . . . . . 71Specifying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Using the File-Transfer Request CL Commands . . . . . . . . . . . . . . . . . . 74Using the Agent and Server CL Commands . . . . . . . . . . . . . . . . . . . . 75Using Change APPC Password and Change Security Password . . . . . . . . 76Writing Application Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 6. Parameter Reference . . . . . . . . . . . . . . . . . . . . . . . . . 77Conventions Used to Describe Parameters and Their Values . . . . . . . . . . 77Types of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Agent Initialization Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Request Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Transfer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79NetView FTP/400 V3 Sending File Parameters . . . . . . . . . . . . . . . . . . 79

iv NetView FTP for OS/400 V3R6 Installation and User's Guide

NetView FTP/400 V3 Receiving File Parameters . . . . . . . . . . . . . . . . . 79NetView FTP/400 V3 Sending Parameters when the Remote System Is

NetView FTP Version 2 MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80NetView FTP/400 V3 Receiving Parameters when the Remote System Is

NetView FTP Version 2 MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81NetView FTP/400 V3 Sending Parameters when the Remote System Is

NetView FTP VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82NetView FTP/400 V3 Receiving Parameters when the Remote System Is

NetView FTP VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82NetView FTP/400 V3 Sending Parameters when the Remote System Is

NetView FTP VSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83NetView FTP/400 V3 Receiving Parameters when the Remote System Is

NetView FTP VSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Agent Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Maximum Number of Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Number of Servers to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Server Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Server Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Number of Servers to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Server Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Server Suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Retry and Server Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Request Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Request Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Hold Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Request Originator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Request Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89New and Verify Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Not-before and Not-after Date and Time . . . . . . . . . . . . . . . . . . . . . 89

Transfer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Nickname of Remote LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Restart from Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Automatic Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92APPC Conversation Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Remote Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Exit-Routine Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

NetView FTP/400 V3 Sending and Receiving File Parameters . . . . . . . . . . 94Library Name and File Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Member Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95File Type for OS/400 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Member Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Maximum Number of Members per File . . . . . . . . . . . . . . . . . . . . . 97Maximum Number of Records . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97File Text Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Public Access Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Record Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Expiration Date for Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Parameters for Files at NetView FTP Version 2 MVS, NetView FTP VM, andNetView FTP VSE Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Contents v

Data Set Name (MVS), File ID (VSE, VM), and CMS File Name (VM) . . 100DD Name (MVS) or File Name (VSE) . . . . . . . . . . . . . . . . . . . . . 103Running Mode of Remote Server (MVS, VSE) . . . . . . . . . . . . . . . . 104Recipient of Report (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . 105Type (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Cluster Password (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . . 107Security Parameters (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . 107Disposition (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . 108DCB Parameters (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . . 109Space Parameters (MVS, VSE, VM) . . . . . . . . . . . . . . . . . . . . . . 115Device Type (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . . . . . 117Volume Serial Numbers (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . 117Volume Count (MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Data Set Sequence Number (MVS) or File Sequence Number (VM, VSE) 119Retention Period (MVS, VSE) . . . . . . . . . . . . . . . . . . . . . . . . . . 119Expiration Date (MVS, VSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . 119VSAM Parameters (MVS, VM, VSE) . . . . . . . . . . . . . . . . . . . . . . 120VM Access (VM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Link Parameters (VM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126SMS Parameters (MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Chapter 7. Examples of Using the NetView FTP/400 V3 Panels . . . . . 135Example 1: Sending a File to a Remote MVS System . . . . . . . . . . . . . 135Example 2: Retrieving a File from a Remote OS/400 System . . . . . . . . . 139

Chapter 8. What to Do if an Error Occurs in NetView FTP/400 V3 . . . . 143Initial Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Submitting an APAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Checking Which NetView FTP/400 V3 PTFs are Installed . . . . . . . . . . . 144

Appendix A. How NetView FTP Creates Names for Receiving Files . . . 145How NetView FTP V2 MVS Creates Names for Files Received from NetView

FTP/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145How NetView FTP VM Creates Names for Files Received from NetView

FTP/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146How NetView FTP VSE Creates Names for Files Received from NetView

FTP/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147How NetView FTP/400 V3 Creates Names for Data Sets Received from MVS,

VSE, and VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148How NetView FTP/400 V3 Creates Names for CMS Files Received from VM 148How NetView FTP/400 V3 Creates Names for Files Received from OS/400 . 149

Appendix B. Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . 151

Appendix C. NetView FTP/400 V3 Receiving File Defaults . . . . . . . . . 153

Appendix D. List of Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Appendix E. Machine Requirements . . . . . . . . . . . . . . . . . . . . . . 159Program Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Appendix F. Performance Considerations . . . . . . . . . . . . . . . . . . 161

vi NetView FTP for OS/400 V3R6 Installation and User's Guide

Appendix G. Communications Considerations . . . . . . . . . . . . . . . 163

Appendix H. Example of an AS/400-to-System/370 SDLC LineConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

AS/400 Line Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165AS/400 Controller Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 166AS/400 Device Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166AS/400 Mode Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167System/370 NCP/VTAM Definitions . . . . . . . . . . . . . . . . . . . . . . . . 167

NCP/VTAM Group Definition Statement . . . . . . . . . . . . . . . . . . . . 168NCP/VTAM Line Definition Statement . . . . . . . . . . . . . . . . . . . . . 168NCP/VTAM PU Definition Statement . . . . . . . . . . . . . . . . . . . . . . 168NCP/VTAM LU Definition Statements . . . . . . . . . . . . . . . . . . . . . 169

System/370 VTAM Macroinstructions . . . . . . . . . . . . . . . . . . . . . . . 169MODETAB and MODEENT Macroinstructions . . . . . . . . . . . . . . . . 169APPL Macroinstruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Appendix I. Working with the Post-Transfer Data Queue . . . . . . . . . 171Specifying Post-Transfer Data Storage . . . . . . . . . . . . . . . . . . . . . . 171Maintaining the Data Queue’s Storage . . . . . . . . . . . . . . . . . . . . . . 171Post-Transfer Data Queue Layout . . . . . . . . . . . . . . . . . . . . . . . . . 172Sample Application Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Appendix J. Relationships between Sending File and Receiving FileAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199The NetView FTP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Related AS/400 Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Related System/370 Publications . . . . . . . . . . . . . . . . . . . . . . . . . 200

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Contents vii

viii NetView FTP for OS/400 V3R6 Installation and User's Guide

Notices

References in this publication to IBM products, programs, or services do not implythat IBM intends to make these available in all countries in which IBM operates.Any reference to an IBM product, program, or service is not intended to state orimply that only IBM’s product, program, or service may be used. Any functionallyequivalent product, program, or service that does not infringe any of IBM’sintellectual property rights may be used instead of the IBM product, program, orservice. Evaluation and verification of operation in conjunction with other products,except those expressly designated by IBM, is the user’s responsibility.

IBM may have patents or pending patent applications covering subject matter inthis document. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, to the IBM Director ofLicensing, IBM Corporation, 500 Columbus Avenue, Thornwood NY 10594, U.S.A.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:

IBM CorporationP.O. Box 121953039 CornwallisResearch Triangle Park, NC 27709-2195USA

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

Trademarks| The following terms are trademarks or service marks of the IBM Corporation in the

United States or other countries or both:

ACF/VTAM APPN AS/400IBM MVS/ESA MVS/XAOperating System/400 OS/400 RACFSystem/370 VM/XA VTAM

Windows is a trademark of Microsoft Corporation.

PC Direct is a trademark of Ziff Communications Company and is used by IBMCorporation under license.

UNIX is a registered trademark in the United States and other countries licensedexclusively through X/Open Company Limited.

Other company, product, and service names, which may be denoted by a doubleasterisk (**), may be trademarks or service marks of others.

Copyright IBM Corp. 1991, 1996 ix

x NetView FTP for OS/400 V3R6 Installation and User's Guide

About This Book

This book applies to NetView File Transfer Program Version 3 for OS/400 Release| 1, Program Number 5733-196, and to NetView File Transfer Program Version 3 for| OS/400 Release 6, Program Number 5798-TBG, and is based on Version 3 of the

operating system OS/400. Version 2 was skipped. If you are using Version 1 ofNetView File Transfer Program for OS/400, you still can order NetView FileTransfer Program for OS/400 Installation and User's Guide Release 1.1,SH12-5776.

| In the following sections, whenever the term NetView File Transfer Program| Version 3 for OS/400 (NetView FTP V3 for OS/400), is used by itself it refers to| both Release 1 and Release 6.

This book describes how to install, use, and administer NetView File TransferProgram Version 3 for OS/400.

Abbreviations and Special TermsThroughout this book, the following abbreviations are used:

NetView FTPNetView File Transfer Program (regardless of version number andoperating system)

NetView FTP V2 MVSNetView File Transfer Program Version 2 for MVS

NetView FTP/400 V1NetView File Transfer Program Version 1 for OS/400

NetView FTP/400 V3| NetView File Transfer Program Version 3 for OS/400 Release 1 and| NetView File Transfer Program Version 3 for OS/400 Release 6

NetView FTP VSENetView File Transfer Program for VSE

NetView FTP VMNetView File Transfer Program for VM

In this book:

� The abbreviation MVS refers to MVS/370, MVS/XA, and MVS/ESA.� The abbreviation VM refers to VM/SP and VM/XA.� The terms data set, file, and cluster are used as synonyms.

If you come across an unfamiliar word, refer to the glossary on page 191.

The term NetView FTP administrator is used frequently throughout this book. Itrefers to a person who operates NetView FTP/400 V3, and is authorized to performNetView FTP/400 V3 administration tasks.

Copyright IBM Corp. 1991, 1996 xi

Who Should Read This BookThis book is written for people who want to use NetView FTP/400 V3 to transferfiles from one system in a network to another. It also contains the informationneeded to install and operate NetView FTP/400 V3.

How to Use This BookRead Chapter 1 first, it gives you an overview of what NetView FTP is, how itworks, and what it can do. Read other chapters according to the tasks you have toperform.

xii NetView FTP for OS/400 V3R6 Installation and User's Guide

Chapter 1. What NetView File Transfer Program Is and Does

NetView File Transfer Program Version 3 Release 1 (abbreviated to NetViewFTP/400 V3 in this book) is an application program that enables one node in anSNA network to transfer copies of files quickly and reliably to or from other nodes inthe network using the SNA LU 6.2 protocol.

NetView FTP/400 V3 can send files to or retrieve files from systems where NetViewFTP V2 MVS, NetView FTP VM, NetView FTP VSE, NetView FTP/400 V1, orNetView FTP/400 V3 is installed.

NetView FTP/400 V3 transfers files directly from a storage device in one system toa storage device in another system, without intermediate spooling.

Note: NetView FTP/400 V3 only supports tape devices at remote MVS, VM, andVSE systems.

NetViewFTP

NetViewFTP

Because the transfer programs at any two systems work together to transfer files,they can communicate using only the functions both transfer programs support.

Copyright IBM Corp. 1991, 1996 1

The Structure of NetView FTP/400 V3The following figure shows the structure of NetView FTP/400 V3 with two serversprocessing local file-transfer requests. One server sends data to a remote system,the other retrieves data from a remote system.

You communicate with NetView FTP/400 V3 using the following:

� A user and administrator interactive interface� An Application program� A Control Language (CL) interface.

2 NetView FTP for OS/400 V3R6 Installation and User's Guide

You use these interfaces to add requests to the request database, to display,release, rename, change, and delete requests that are in the request database, andto perform the NetView FTP/400 V3 administration tasks.

A component called the NetView FTP/400 Agent is used to:

� Control communication between the interfaces and servers� Distribute requests to the servers.

You can start up to 99 servers, depending on the AS/400 system unit and availablestorage. For more information about machine requirements see Appendix E,“Machine Requirements” on page 159.

NetView FTP/400 V3 servers perform the following tasks:

� Allocate and deallocate sessions� Send data to and receive data from remote NetView FTP systems

� Access files� Read records from and write records to files� Perform existence and authorization checking� Create new files and libraries� Add members to files� Replace existing members� Append records to an existing member.

For file transfers between two NetView FTP/400 V3 systems you can transfer oneor all members of a data or source file using a single file-transfer request.

Creating File-Transfer RequestsYou use NetView FTP by creating file-transfer requests. A request tells NetViewFTP such things as:

� Whether to transfer a file to or from another system� Which system to transfer the file to or from� Which file is transferred from the sending system� What name the file must have at the receiving system� When a request should run.

You can create requests by:

� Entering values in the input fields of the NetView FTP/400 V3 panels� Issuing NetView FTP Control Language (CL) commands� Writing and running application programs.

After you create a request, you can immediately create another; you do not have towait until NetView FTP has processed the first request.

After you create a request, NetView FTP/400 V3 adds it to the request database,where it waits to be processed.

The system where the request is created is called the requesting system.

Chapter 1. What NetView File Transfer Program Is and Does 3

A file-transfer request can have the following states:

Waiting The request is in the request database and is waiting to beprocessed.

You can hold or delete any waiting request to prevent it from beingprocessed. You can also modify some of the attributes of yourwaiting requests. If you do modify a waiting request, its statuschanges to held.

Held The request is held and will not be processed until you release it.

Note: All requests that you create with the interactive interface areput on hold.

Scheduled If a held request with a scheduled date is released, the request statechanges to scheduled .

Not started If a scheduled request cannot be started during the scheduled timeperiod (for example, if the server is inactive), the request’s statuschanges to not started .

Active While a request is being processed and while its corresponding filetransfer is taking place, the request has the status active .

After the file transfer is complete, information about the outcome ofthe file transfer is added to the request. The request’s status changesto:

finished If the file transfer was successful

failed If the file transfer was unsuccessful

waiting or scheduledAfter a temporary error prevents the file transferand automatic retry is set to yes or ifscheduling parameters are specified for therequest.

It remains in the request database until you delete it.

Finished The request finished successfully.

You can process a finished request again by releasing it. Afterreleasing the request its status is changed from finished to waiting .

Failed The request failed. You can process a failed request again byreleasing it. After releasing the request its status is changed fromfailed to waiting .

A scheduled request’s status changes to failed when:

� The number of restarts, defined by the NetView FTPadministrator, is exceeded.

� The next retry or restart attempt happens after the scheduled timeand date.

� There is a permanent error.


How NetView FTP Processes RequestsTo process requests, NetView FTP uses components called servers. In thefollowing illustrations, NetView FTP/400 V3 communicates with NetView FTPVersion 2 MVS. A server is represented by a small box with an S inside. ForNetView FTP MVS, VM, and VSE each server has its own logical unit (LU) nameand runs independently of any other servers. In NetView FTP/400 V3 a server isone of a defined maximum for a subsystem.

The NetView FTP/400 Agent checks if there are any requests in the requestdatabase that are eligible for processing (that is, a request with the status waitingor scheduled ). If there are, it then informs a server with a corresponding class,which retrieves a copy of a request from the request database and changes therequest’s status from waiting or scheduled to active . A message is sent to informthe request originator. The request is only processed if there is a server with acorresponding class.

RemoteSystemNetView

FTPNetView

FTP

LocalSystem

The server uses the nickname of the responding LU specified in the request toinitiate a conversation with a server at the responding system.

NetViewFTP

NetViewFTP

RemoteSystem

LocalSystem

After the conversation has been established, the requesting server sendsinformation contained in the request to the responding server. This informationincludes the direction of the file transfer. Both servers then know which server is tosend, and which server is to receive the file. The direction of the file transfer isindependent of the server that started the conversation.

The sending server allocates the file to be sent (the sending file) and the receivingserver allocates the file into which the sending file is received (the receiving file). Ifthe receiving file does not already exist, the receiving server can, depending on therequest’s specifications, create it before the file transfer begins.


Both servers then work together to transfer the file.

RemoteSystemNetView

FTPNetView

FTP

LocalSystem

After the servers have finished transferring the file, they terminate the conversation.Each server writes a file-transfer report to a report file. The local server also writesa completion message to the log file, and writes a message to the message queueof the user who released the file-transfer request indicating whether the transferwas successful or not. If the conversation was initiated by NetView FTP/400 V3,the server passes status information back to the agent, which changes therequest’s status from active to finished , failed , waiting or scheduled . The localserver is now ready to process the next request.

RemoteSystemNetView

FTPNetView

FTP

LocalSystem

The NetView FTP/400 Agent then checks if there are any more requests in therequest database that are eligible for processing. If there are, it then informs aserver with the corresponding class, which retrieves a copy of the request from therequest database, and the process begins again.

LocalSystem NetView

FTPNetView

FTP

RemoteSystem

All the servers in each system simultaneously follow the same procedure to transferfiles throughout the network. Each server only processes requests assigned to itsserver class.


Using NetView FTP/400 V3The following describes the ways you can use NetView FTP/400 V3.

Using the Interactive InterfaceNetView FTP/400 V3 has a set of display panels that make it easy for you tocreate, change, copy, delete, display, rename, hold, and release file-transferrequests. You can also perform the administration and operation tasks using theinteractive interface. The panels include a set of help panels that give you onlinehelp whenever you need it.

Which of the panels NetView FTP/400 V3 displays and the order in which itdisplays them depends on the task you select. The panel flow is shown inFigure 5 on page 32 and Figure 21 on page 50.

Using the Control Language InterfaceYou can use the CL commands to:

� Create requests to send files to remote systems� Create requests to retrieve files from remote systems� Change and delete existing requests� Start and stop the agent� Start and stop servers� Change the APPC password� Change the MVS, VM, or VSE security password.

How to use the CL commands is described in Chapter 5, “Using the ControlLanguage Interface” on page 71.

Writing Application ProgramsYou can write application programs that use the CL commands to:

� Create requests to send files to remote systems� Create requests to retrieve files from remote systems� Change and delete existing requests� Start and stop the agent� Start and stop servers� Change the APPC password� Change the MVS, VM, or VSE security password.

How to use the CL commands is described in “Writing Application Programs” onpage 76.

Protecting Requests from Unauthorized AccessNetView FTP/400 V3 knows the originator ID of every interactive user, CL interfaceuser, and application program that creates a request. If you do not haveadministrator authorization, you can only work with the requests that you own. ANetView FTP administrator can work with any request regardless of who created it,and also create requests for other users.


Specifying when NetView FTP/400 V3 Can Process a RequestIn each request, you can specify times before which and after which NetViewFTP/400 V3 is not to process that request.

You can specify that a request that is submitted every day is scheduled forprocessing in a specific time frame, provided that the not-after time is later than thenot-before time. NetView FTP/400 V3 assumes the not-before date or the not-afterdate to be the current date if you do not specify a date or dates.

If you do not specify dates or times, your request can be scheduled any time after ithas been submitted.

Assigning Server Classes and Priorities to RequestsTo each request you create, you assign one of 36 server classes and one of 10request priorities. The server class you specify determines which servers canprocess it. A server can process a request only if the server class specified in thatrequest is one of those assigned to that server.

A NetView FTP/400 V3 system can use the different classes to group differenttypes of file transfers. For example, at your system a certain class might bereserved for one of the following:

� Transfers of certain types of files� Transfers of files of a certain size� Transfers to or from a certain remote system.

The agent searches the request database for waiting requests with the highestpriority. The agent delivers each request found to a waiting server with thecorresponding class. If a server with the corresponding class is not waiting, therequest remains waiting.

Using Data CompressionTo reduce the time needed to transfer a file, you can select whether the transferprogram at the sending system compresses the file before sending it, and thetransfer program at the receiving system decompresses the file after receiving it.

NetView FTP/400 uses adaptive compression. Adaptive compression works byreplacing character strings that are repeated in a file with references to a directoryof such character strings.

Identifying Remote SystemsYou identify a remote system by specifying the nickname of a server at thatsystem. Each nickname has a corresponding entry in an LU directory, which is aspecial file maintained by your NetView FTP/400 administrator. The nicknames canbe meaningful names (such as NEWYORK), which makes them easier toremember than LU names (such as F0098731). Each entry in the LU directory alsospecifies the operating system of the corresponding remote server. NetView FTPuses this information to check requests for incorrect or missing parameters beforeadding the requests to the request database.


Checking Requests at the Remote SystemYou can have your requests checked by the NetView FTP at the remote systembefore transferring the file. In this way, you can be warned about inconsistencies inyour requests. This is most useful when you specify that a file should not betransferred before a certain date or time.

If you specify remote checking, the contents of your request are sent to, andvalidated at, the remote system immediately after the request is released andprovided that a server is available. However, no file transfer is performed at thistime. The results of the remote check are recorded in the log file.

If the remote check completes without errors, the request is scheduled for filetransfer processing according to your specifications, otherwise the request fails.

What You Need to Know about FilesThe following describes the things you need to know about files to send them to, orretrieve them from, a remote system.

Types of File NetView FTP Can TransferThe following list gives the access methods NetView FTP MVS, VM, and VSE usewhen processing the different types of file:

Access Method Types of Files

VSAM ESDS—Entry Sequenced Data Set (MVS, VM, VSE)KSDS—Key Sequenced Data Set (MVS, VM, VSE)SAM ESDS—VSAM managed sequential (VSE)

QSAM Physical sequential file stored on a DASD (MVS, VM)Physical sequential file stored on labeled tape (MVS, VM)Physical sequential file stored on unlabeled tape (MVS, VM)Single PDS member, without directory information (MVS)

SAM Physical sequential file stored on labeled tape (VSE)Physical sequential file stored on unlabeled tape (VSE).

AS/400* has only one database management system. Anyone wanting to store orretrieve data on the AS/400 uses this database management system.

NetView FTP/400 V3 can process the following types of file:

Physical data file A member in a physical data file can contain both numeric andcharacter data of any AS/400 data type. Physical data filescan be 1 to 32766 bytes long.

Physical source fileA physical source file generally stores text or sourcestatements instead of data as follows:

� The first field of a source file is always a sequencenumber (6 bytes)

� The second field always contains a date (6 bytes)

� The third part contains text. Text fields are of the typecharacter.

A physical source file can be 13 to 32766 bytes long.


Save file Is used to store data with a fixed record length of 528 bytes ona disk.

Note: All OS/400 files have a fixed record length.

NetView FTP does not allow records to be truncated. The sending logical recordlength must not exceed the maximum possible for the receiving operating system.If a sending file record is shorter than the records of a fixed size receiving data set(non-VSAM at an MVS, VM or VSE system), the transfer is aborted.

The sending and receiving locations need not have the same operating systems.Also, a file being received need not be the same type as the file being sent. Forexample, a VSAM file can be sent from an MVS system to an OS/400 system,where it can be received as a physical data file.

Table 1. Valid Combinations for Sending and Receiving Files with MVS, VSE, or VM

File Type Data File(DTAF)

SourceFile

(SRCF)

Save File(SAVF)

Physical sequential file on DASD � � �

Physical sequential file on alabeled or unlabeled tape

� � �

Single member of partitionedorganized data set (PDS) withoutdirectory information

� � �

VSAM KSDS � �

VSAM ESDS � � �

SAM ESDS � � �

Table 2. Valid Combinations for Sending and Receiving Files with OS/400

File Type Data File(DTAF)

SourceFile

(SRCF)

Save File(SAVF)

Data file (DTAF) � �

Source file (SRCF) � �

Save file (SAVF) �


Transferring Files to OS/400In a request you can specify many parameters that describe the attributes that thereceiving file should have. For example, maximum members per file and initialnumber of records. If you only specify the required sending file parameters and noreceiving file parameters, NetView FTP/400 V3 retrieves values from the sendingfile and uses them to create a new file at the receiving system. For data files andsource files, NetView FTP/400 V3 uses the following OS/400 values from thesending file to create a new receiving file.

OS/400 keywords DescriptionFILE File and LibraryMBR MemberTEXT Text descriptionMAXMBRS Maximum membersMAXRCDS Maximum recordsSIZE Member sizeRCDLEN Record lengthEXPDATE Expiration date for memberAUT Public access authority

Note: For data files and source files, no other values from the sending file areretrieved. If you want all parameters of a sending file, then you must transfer yourfile as the contents of a save file (SAVF).

Transferring a Source File to Data FileIf you transfer a source file (SRCF) to a data file (DTAF), NetView FTP/400 V3transfers the text fields of the source file as data into the data file, but not the dateand the sequence number fields.

Transferring a Data File to Source FileIf you transfer a data file (DTAF) to a source file (SRCF), NetView FTP/400 V3transfers the data into the text fields of the source file, and automatically createsthe sequence number and date fields. If you create a new AS/400 file andmember, specify a record length that is the length of the sending file plus 12 bytes(6 bytes for the date and 6 bytes for the sequence number).

Transferring a Save File to a Save FileIf you transfer a save file (SAVF) to a save file, specify enough storage for the fileusing the NetView FTP/400 V3 maximum number of records parameter. If you donot specify enough storage, the transfer is interrupted and no data is transferred.


NetView FTP/400 V3 File OptionsIn a request you can specify file and member options. These are used todetermine how a file is processed in the receiving system. The decision tablesshown in Table 3 and Table 4 show you how to specify these options.

The file options are described in “File Option” on page 96, and the member optionsare described in “Member Option” on page 96. The following are two examples ofspecifying data-set options:

1. In this example, if the file does not exist at the receiving side, it is created,otherwise an error message is sent.

File option *NEW

Member option *ADD

2. In this example, all transmitted records are added to the specified member.

File option *OLD

Member option *APPEND

Table 3. Specifying File Options

File Option CreateFile andMember

AddMember

ReplaceMember

AppendtoMember

*NEWThe file does not already exist,NetView FTP/400 V3 creates it.

X

*REGThe file is allocated regardless ofwhether or not it exists. If the filedoes not exist, NetView FTP/400V3 creates it.

X X X X

*OLDThe file must already exist.

X X X

Table 4. Specifying Member Options

Member Option CreateFile andMember

AddMember

ReplaceMember

AppendtoMember

*ADDThe file member must not alreadyexist, NetView FTP/400 V3 adds itto the file.

X X

*REPLACEThe file member might not exist. Ifit does exist NetView FTP/400 V3,replaces it, otherwise a newmember is created.

X X

*APPENDThe file member might not exist. Ifit does exist NetView FTP/400 V3,appends the new data, otherwisea new member is added to the file.

X X


Sending Files to and Retrieving Files from MVS, VM, and VSEFiles at MVS, VM, or VSE systems can have records of fixed, variable, orundefined length. While a fixed or undefined length record consists of user dataonly, the user data in variable length records is preceded by a 4-byte fieldcontaining the length of the record (the length of the user data plus 4).

If the record length of a file sent from OS/400 to a receiving file on MVS, VM, orVSE is of:

� Fixed length, the length of the user data of a record sent must be equal to thereceiving file’s specified or existing record length.

� Variable length, the length of the user data of a record sent must not be greaterthan the receiving file’s specified or existing record length minus 4.

� Undefined length, the length of the record sent must not be greater than thereceiving file’s physical block.

The logical record length and the block size must not exceed the maximumpossible for the receiving operating system.

If the records of a file sent from MVS, VM, or VSE to OS/400 have:

� Fixed length, they must not exceed the length specified for the receiving file. Ifthe receiving file is a source file, then the receiving file record lengthspecification must not be less than the sending record length plus 12. Themaximum record length of the sending file must not exceed 32766.

� Variable length, they must not exceed the length specified for the receiving fileplus 4. If the receiving file is a source file, then the receiving file record lengthspecification must not be less than the sending file record length plus 8. Themaximum record length of the sending file must not exceed 32766.

� Undefined length, the blocks must not exceed the length specified for thereceiving file. If the receiving file is a source file, then the receiving file recordlength specification must not be less than the sending file block length plus 12.The maximum record length of the sending file must not exceed 32766.

If the user data part of a sending file record is less than the user data part of areceiving file record, NetView FTP/400 V3 fills the remainder of the record withblanks.

You can specify a VSAM KSDS option together with a key length and a key offset.NetView FTP/400 V3 transfers the file to a VSAM KSDS data set. VSAM uses thekey you specify as the primary key.

Save files provide a convenient way to back up data on an MVS, VM, and VSEsystem. However, you can only transfer a file from an MVS, VM, or VSE system toa save file at OS/400 if the MVS, VM, or VSE file contains a save file. That is, ifyou previously sent the save file to MVS, VM, or VSE.

Automatically Creating Names for New Receiving FilesIf you do not specify a name for a new receiving file, NetView FTP creates oneusing information contained in the request and obtained from the system in which itruns. The way in which NetView FTP/400 V3 creates names for new receiving filesis described in Appendix A, “How NetView FTP Creates Names for ReceivingFiles” on page 145.


ASP ThresholdTo ensure that storage capacity is not exceeded NetView FTP/400 V3 checks thecapacity of the auxiliary storage pool (ASP) that the file to receive the data residesin. For transfers between two AS/400 systems the transfer starts only if there issufficient storage capacity for the number of bytes to be received. During thetransfer the storage capacity is checked, depending on the file size, as below:

File size < 1MB No further check during transfer

File size < 10MB Capacity check after every 10% of data transferred

File size < 100MB Capacity check after every 5% of data transferred

File size > 100MB Capacity check after every 1% of data transferred.

If, at any time, a capacity check indicates that there is insufficient auxiliary storage,the transfer ends with a temporary failure.

For transfers from MVS, VM, or VSE systems a minimum capacity of 1MB isnecessary before the transfer starts. The capacity is rechecked after every 1MBhas been received.

Log File and Report FileFor every file transfer, whether successful or not, the servers at the sending andreceiving systems record such things as the outcome of the file transfer, thetransfer start and stop date and times, and any error messages. This information iswritten to a log file.

For each file transfer NetView FTP/400 V3 writes a record, containing the numberof transferred records, and the names of the sending and receiving files, to a reportfile. NetView FTP/400 V3 also sends a message to the local request owner sayingwhether the transfer was successful or not.

Note: For file transfers with NetView FTP for MVS, VM, or VSE, you can specifyin the request the user ID and node ID of the recipient of the file transfer report.How to do this is described in “Recipient of Report (MVS, VM, VSE)” on page 105.


SecurityThe AS/400 security officer (QSECOFR) is as default a NetView FTP/400 V3administrator. A NetView FTP/400 V3 administrator can authorize other NetViewFTP/400 V3 users as administrators. Users who do not have administratorauthorization can only create and work with their own requests. NetView FTP/400V3 administrators can work with all requests, and create requests for other users.In a request, you can include the following security information:

� APPC Conversation Security

– User ID – Password

Notes:

1. The value *NONE for an LU 6.2 ALLOCATE is not supported.

2. APPC conversation security is mandatory for requests sent to NetViewFTP/400 V3.

� VM Link password (for a file at a VM location)

� RACF* security parameters (for a file at an MVS, VSE, or VM location)

– User ID – Password – Group ID

� VSAM cluster password

� Public access authority (for files at an OS/400 location).

For the file being sent, the local NetView FTP/400 V3 user who releases therequest must have operational authority for the object, and read authority for thedata.

For the file being received, the NetView FTP/400 V3 user who releases the requestmust have operational authority, management authority, and exist authority for theobject. If the file is new it is created using the public access authority informationspecified in the request, or, if nothing is specified, the file is created using thepublic access authority of the sending file.

Automatic Logon RetrySometimes a server cannot initiate a conversation with a server at a remote systembecause:

� All the servers at the remote system are busy with other transfers.� No servers at the remote system have been started.� A path is temporarily unavailable between the two servers.

When this happens, the server at your system automatically changes the status ofthe request from active back to waiting or scheduled , and goes on to process thenext request in the request queue. Later, NetView FTP tries again to process therequest. It keeps trying until it succeeds in initiating a conversation, or until itexceeds the allowed maximum number of retries or the next retry would happenoutside the schedule period. This is called using automatic logon retry.


Restarting an Interrupted File TransferSometimes file transfers are interrupted, for example, when:

� The sending or receiving server terminates

� The sending or receiving server cannot allocate the file being sent or received

� There is a prolonged conversation interruption.

You can specify in a file-transfer request that:

� NetView FTP/400 V3 automatically retries the failed file-transfer request. Formore information see “Automatic Retry” on page 91.

� If the file-transfer request fails, it restarts either from the last record successfullywritten to the receiving file or from the beginning of the file. For moreinformation see “Restart from Interruption” on page 91.

Note: If the sending file is modified after the file transfer is interrupted and beforethe file transfer is restarted, then, after the file transfer has finished, the sendingand receiving files may have different contents.

For every file transfer NetView FTP writes information about the file transfer to theRestart file. This file is used for restarting failed file-transfer requests. NormallyNetView FTP/400 V3 deletes the corresponding restart record at the end of asuccessful file transfer. However, if a request ends abnormally, the request’srestart record remains in the restart file. Over a period of time the restart file canfill up. How to remove restart entries is described in “Removing Restart FileEntries” on page 64.

Automatic Transfer Restart: If you specify *YES for the Automatic Retryparameter, and the file transfer is interrupted with a temporary error, NetViewFTP/400 V3 changes the status of the request back to waiting or scheduled .NetView FTP/400 V3 will then periodically reprocess the request until it succeeds inrestarting the transfer. If Restart from interruption is set to *YES, NetView FTP/400V3 tries to restart from the interruption point, otherwise the transfer restarts fromthe beginning of the file. If NetView FTP/400 V3 is unable to restart a transferautomatically, or if you specify in your request that you do not want it to try,NetView FTP/400 V3 changes the status of the request to failed and does notreprocess it.

Manual Transfer Restart: If a file transfer is interrupted, and you did not specify*YES for the Automatic Retry parameter, you can restart the transfer by releasingthe request again.

For more information about restarting failed requests see “Restarting FailedFile-Transfer Requests” on page 47 and “Restart from Interruption” on page 91.


NetView FTP/400 V3 Prestarted JobsNetView FTP/400 V3 uses prestarted jobs to improve performance when it acts asthe remote system. During installation, NetView FTP/400 V3 adds prestarted jobentries to the subsystem description (SBSD) DVGSBS. The prestarted job entry(PJE) determines the following:

� How many remote servers start when DVGSBS starts (INLJOBS)

� When to start additional remote servers (THRESHOLD)

� How many additional remote servers to start (ADLJOBS).

The values in parentheses refer to CL keywords for the OS/400 ADDPYEcommand.

The INLJOBS value can be changed using the FTP/400 Administrator FunctionsInterface. On the Work with Remotely Started Components panel (DVG380) avalue can be entered for the ‘Initial number of servers’ by pressing F15=Changeparameters. The values determined for THRESHOLD and ADLJOBS in theprestarted job entry depend on the value specified for the Maximum number ofservers parameter:

If Maximum number of servers is set to 0, OS/400 runs the ENDPJ command, theADLJOBS and THRESHOLD values do not change.

Note: Incoming transfer requests are rejected with a temporary error if they try touse a communications device allocated in DVGSBS and if there is a prestarted jobentry in the subsystem, but no prestarted jobs are active.

For a transfer request from a remote system to be processed by a prestartedserver ensure that:

� Subsystem DVGSBS is started and has a prestarted job entry for programDVGFTPA1. Use the OS/400 DSPSBSD command to verify this.

� The prestarted job is active. Use F16=Include prestarted jobs on the ‘Workwith remotely started components’ panel (DVG380) to verify this.

� The Maximum number of servers parameter is set to 1 or more.

� The communications device requested by the remote transfer request isallocated to the DVGSBS subsystem.

For more information about prestarted jobs refer to AS/400 Work ManagementGuide.

Maximum number ofservers

ADLJOBS THRESHOLD

> 2 2 22 1 11 0 1


Messages and CodesAll NetView FTP components issue messages at various times, for example if theydetect an error. The messages issued by NetView FTP/400 V3 indicate thesuccess or failure of a file-transfer request, and are sent either to the user’smessage queue or the log file. These messages can be displayed by theinteractive user or administrator. You can display only the messagescorresponding to your requests and view their associated second level help.

The messages are included in the file DVGMSGF in one of the following libraries:

� DVGO2924 (English) � DVGO2928 (French) � DVGO2929 (German) � DVGO2962 (Kanji).

Local Error MessagesAll messages written to the log file by the local system are in your selected primarylanguage.

Remote Error MessagesMessages issued by the remote system and sent to the local system are written tothe log file, and can be either in your selected primary language, or in English. TheEnglish messages from the remote system are in the form:

DVG4ð9ð DVGxxxx message-text

DVGxxxx One of the following:

DVG4xxx Messages issued by a remote NetView FTP/400 V3 system.

DVGxxxc Messages issued by a remote NetView FTP Version 2 MVS,NetView FTP VSE, or NetView FTP VM system, where c isthe message type code.

Further information about messages issued when the remotesystem is NetView FTP Version 2 MVS, NetView FTP VSE,or NetView FTP VM can be found in NetView FTP Version 2for MVS Version 1 for VSE and VM Messages and Codes.

If you cannot determine which error has occurred, contact thesystem administrator at the remote system.

message-text is the message text in English.

Communication Error MessagesIf a communication error occurs, a message in the range from DVG4601 toDVG4604 is displayed with a major/minor code. The major/minor codes aredescribed in AS/400 Communications: Advanced Program-to-ProgramCommunication Programmer’s Guide.


AuditabilityAn administrator with SECOFR authorization can specify, using the administratorinterface, whether or not to use the audit facility. The audit facility records NetViewFTP/400 V3 transfer activities in a NetView FTP/400 V3 history file. The NetViewFTP/400 V3 history file contains a member for each month.

An administrator who is authorized to maintain the NetView FTP/400 V3 history filecan print and remove NetView FTP/400 V3 history file members.

The audit facility is specified (*YES or *NO) with the auditability parameter in thestartup file.



Chapter 2. Installing NetView FTP/400 V3

Before you can use NetView FTP/400 V3 you must do the following:

� Install NetView FTP/400 V3. The QSECOFR does this using a series ofinstallation panels. This is described in “Performing a NetView FTP/400 V3Installation.”

� Set up the communication configuration. This is described in “Setting Up theCommunication Configuration” on page 26.

� Set up the LU directory. This is described in “Setting Up the LU Directory” onpage 28.

� Check whether the installation was successful by following the steps describedin “Verifying the Installation of NetView FTP/400 V3” on page 29.

Installation PrerequisitesBefore starting to install NetView FTP/400 V3:

� If you have password authorization on your system, you must be able to signon as the AS/400 security officer (QSECOFR).

� Ensure that no AS/400 library names starting with DVG are on the disk. Youcan check this using the OS/400 command: WRKLIB LIB(DVG*).

Note: Library names that are the same as those of the NetView FTP/400 V3libraries will be deleted.

� Obtain the following names of the remote LUs you are going to use:

– Local location name– Remote location name– Remote network identifier

– MODE.

Performing a NetView FTP/400 V3 InstallationTo install NetView FTP/400 V3 do the following steps:

1. Sign on to OS/400 as QSECOFR.

2. Create group user profile NFTP using the command:

CRTUSRPRF USRPRF(NFTP) PASSWORD(\NONE) USRCLS(\PGMR)

TEXT('Group profile for NetView FTP/4ðð V3')

Note: The group profile NFTP must be created as it is used during theinstallation and for internal purposes. NFTP is the owner of all NetViewFTP/400 V3 objects. For security reasons, do not use it for any other purpose,in particular do not use NFTP as a user profile.

3. Insert the tape with the volume ID DVGRST into the tape unit.

4. Type the following command and press the ENTER key:

RSTOBJ OBJ(\ALL) SAVLIB(QTEMP) DEV('device name')

The device name is the name of your tape device.


5. Do not remove this tape, type DVGRST and press function key F4 to prompt thecommand screen.

6. Type the tape device name and press the ENTER key.

| One of the following panels is displayed, depending on which release of the| product you have:

à ðDVG4ð1 NETVIEW FTP/4ðð INSTALLATION

NETVIEW FILE TRANSFER PROGRAM FOR OS/4ðð

VERSION 3.1.ð

PROGRAM NUMBER 5733-196

(C) COPYRIGHT IBM CORP. 1991, 1994. ALL RIGHTS RESERVED.

PRESS ENTER TO CONTINUE

F3=EXIT F12=CANCEL

á ñ

Figure 1. NetView FTP/400 V3 Installation

| à| ð| DVG4ð1 NETVIEW FTP/4ðð INSTALLATION

| NETVIEW FILE TRANSFER PROGRAM FOR OS/4ðð

| VERSION 3.6.ð

| PROGRAM NUMBER 5798-TBG

| (C) COPYRIGHT IBM CORP. 1994, 1996. ALL RIGHTS RESERVED.

| PRESS ENTER TO CONTINUE

| F3=EXIT F12=CANCEL

| á| ñ

| Figure 2. NetView FTP/400 V3 Installation

7. Press the ENTER key to continue with the installation. The libraries shown inthe following table are created:


Table 5 (Page 1 of 2). NetView FTP/400 V3 Libraries

Library Name Library Contents

DVGD01 Contains physical and logical data files, for example, request database,report file, log file, trace file.

DVGO01 Contains the executable objects.

DVGO2924 NetView FTP/400 V3 supports several languages. Alllanguage-dependent objects are included in separate libraries. Only theEnglish language library is created during installation. How to createother language libraries is described in “Installing Other Languages” onpage 25.

DVGUSR Contains a NetView FTP/400 V3 sample application program forpost-transfer processing.

8. When the installation is complete, message Installation of NetView FTP/400finished successfully is displayed. Press the ENTER key.

9. Add a communication entry, for each remote location, to the subsystemdescription DVGSBS in library DVGO01 using the following command:

ADDCMNE SBSD(DVGOð1/DVGSBS) RMTLOCNAME('remote location name')

JOBD(DVGOð1/DVGJOBD) DFTUSR(\SYS) MODE('mode name')

You must issue this command for each remote location. The communicationentry lets the remote NetView FTP system initiate communication with NetViewFTP/400 V3.

For more information about MODE refer to “Setting Up the CommunicationConfiguration” on page 26 or AS/400 Communications: User’s Guide.

10. Start NetView FTP/400 V3 using the command STRFTP.

11. Select Option 3 Administrator Functions from the main menu.

12. Add NetView FTP/400 V3 administrators using the procedure described in“Creating a New Administrator” on page 67.

13. Authorize NetView FTP/400 V3 users. How to authorize users is described in“Authorizing NetView FTP/400 Users.”

Authorizing NetView FTP/400 UsersWhen you install NetView FTP/400 V3, every user in your system can work withNetView FTP/400 V3.

NetView FTP/400 V3 uses two authorization lists (DVGAUTL and DVGADMAUTL)for all objects. Authorization list DVGAUTL is for authorizing users to work with allNetView FTP objects. Authorization list DVGADMAUTL is for authorizingadministrators.

The following entries are created in the respective authorization lists:

Table 6. Authorization List (DVGAUTL)

User Object Authority List Management

NFTP *ALL X

Chapter 2. Installing NetView FTP/400 V3 23

Table 6 on page 23 and Table 7 show the authorization lists included in theinstallation tape. In these authorization lists all members of the group NFTP areNetView FTP/400 V3 administrators, all other OS/400 users are authorized to workwith NetView FTP/400 V3.

Table 6. Authorization List (DVGAUTL)


*PUBLIC *CHANGE

Table 7. Authorization List (DVGADMAUTL)


NFTP *ALL X

*PUBLIC *EXCLUDE


You can, however, change these authorization lists so that only specified users areallowed to work with NetView FTP/400 V3. Table 8 and Table 9 show the valuesyou need to specify for object authority:

In this example:

� Only the users USER1 and USER2 are authorized to work with NetViewFTP/400 V3. USER3 is the NetView FTP/400 V3 administrator.

� You must change the object authority for *PUBLIC to *EXCLUDE.

Table 8. Sample Authorization List (DVGAUTL)


USER3 *ALL X

USER1 *CHANGE

USER2 *CHANGE

*PUBLIC *EXCLUDE

Table 9. Authorization List (DVGADMAUTL)


USER3 *ALL X

*PUBLIC *EXCLUDE

Installing Other LanguagesWhen you have installed NetView FTP/400 V3, you can use a language libraryother than the English language library. You can order the following languagelibraries:

DVGO2928 FrenchDVGO2929 GermanDVGO2962 Kanji (DBCS)

Note: Each language is delivered on a separate distribution tape.

To install a different language:

1. Sign on as QSECOFR.

2. Insert the tape with the volume ID DVGNLS into the tape unit.

3. Type the following command and press the ENTER key:

RSTOBJ OBJ(\ALL) SAVLIB(QTEMP) DEV('device name')

The device name is the name of your tape device.

4. Do not remove this tape, type DVGNLS and press function key F4 to promptthe command help screen.


5. Type the tape device name and press the ENTER key.

A panel similar to the following is displayed:

à ðDVG4ð2 NetView FTP/4ðð Installation

Press Enter to confirm the language installation

The language you are going to install is French

Press Enter to continue

F12=Cancel

á ñ

Figure 3. NetView FTP/400 V3 Installation

6. When the installation is complete, a message is displayed. Press the ENTERkey.

7. Select the primary language using the procedure described in “Working with theStartup File” on page 65.

Setting Up the Communication ConfigurationBefore you can use NetView FTP/400 V3 you must configure all the lines you aregoing to use. The following list shows the OS/400 commands you can use tocreate and check the communication configuration:

Command Function (Description)

CHGNETA Check the network attributes (system characteristics)

CRTLINSDLC Create AS/400 line description (physical link between systems)

CRTCTLAPPC Create AS/400 controller description (relationship between localand remote systems)

CRTCOSD Check class-of-service description (APPN network nodes andtransmission groups)

CRTMODD Check mode description (session characteristics and number ofsessions)

CRTDEVAPPC Create AS/400 device description (device characteristics)

CRTCTLHOST Create CTL description (SNA Host).


Figure 4 shows a sample line configuration for an AS/400-to-System/370, and foran AS/400-to-AS/400 connection. In this example, NetView FTP/400 V3 on SYSAcommunicates with NetView FTP Version 2 MVS on a System/370, and withNetView FTP/400 V3 on SYSB.

System/370

3725 Controller

System AS/400

APPC CTLD

APPC DEVDAPPC DEVD

HOST CTLD

APPC DEVDAPPC DEVD

X25 LINDAPPC CTLD

APPC DEVDAPPC DEVD

X25 Line

MVS

VTAM V3R2

NCP V4R3

System AS/400

X25 LIND

SDLCNonswitchedLink

NetView FTPfor MVS

Version 2

NetViewFTP/400

NetViewFTP/400

System name: SYSAOS/400

SDLC LIND

System name: SYSBOS/400

Figure 4. Example of a Line Configuration for NetView FTP/400

Both dependent and independent LUs can be used to communicate with remotesystems running NetView FTP using an LU type 6.2 session.


The basic AS/400 communication configuration includes the line, controller, anddevice description. The AS/400 terms device and controller are equivalent to theSystem/370 terms logical unit (LU) and physical unit (PU).

In Figure 4 on page 27 two AS/400 systems are connected via an X.25packet-switching data network (PSDN). This communication configuration isdescribed in detail in the AS/400 Communications: User’s Guide.

For an example of how to configure an SDLC line for an AS/400-to-System/370connection see Appendix H, “Example of an AS/400-to-System/370 SDLC LineConfiguration” on page 165.

NetView FTP/400 V3 supports all types of LU 6.2 connection, for example:

� SDLC (leased and switched)

� X.25

� Token ring

� Ethernet.

Setting Up the LU DirectoryThe LU directory contains information about the remote servers in the network.The administrator can create, change, copy, rename, display, and delete entries inthis table using the administrator interactive interface. How to do this is describedin “Working with LU Directory Entries” on page 57.

To establish a conversation with a remote NetView FTP system, NetView FTP/400V3 must know the logical unit (LU) name of a server in the remote system. Whenyou create a request you can specify the nickname for the remote LU whichcorresponds to an entry in the LU directory.

An LU directory entry consists of the following:

� The nickname of the remote LU.

� The remote location name.

� The operating system under which the remote server runs.

� The local location name.

� The remote network identifier.

� The communication mode.

The communication mode points to a mode description in which theadministrator specifies the session parameters for the server, for example, RUsize and class of service. How to specify the mode description is described inAS/400 Communications: Advanced Program-to-Program CommunicationProgrammer’s Guide. The communication mode can be different for each LUdirectory entry.

� A description of the remote LU.

� Date of the last update.

� User ID of the last update.


Verifying the Installation of NetView FTP/400 V3Once you have installed NetView FTP/400 V3 you can verify that it is functioningcorrectly by using the following procedure:

1. Sign on as a NetView FTP/400 V3 administrator.


3. Select Option 3 Administrator Functions on the Main Menu.

4. Start the NetView FTP/400 V3 subsystem using the interactive interface byselecting Option 9 on the Administrator Functions panel.

5. Select Option 1 to vary on the line for NetView FTP/400 on the OS/400 Workwith Configuration Status panel.

6. Start the agent and two servers by:

a. Selecting Option 1 Work with Local Components from the AdministratorFunctions panel.

b. Pressing F13=Start Agent.

The agent is the central component of NetView FTP/400 V3. If the agent is notrunning, waiting file-transfer requests remain in the request database.However, file-transfer requests initiated from a remote location can still beprocessed, even if the agent is not running.

You can start the agent from the administrator interactive interface or by usingthe CL command STRAGNFTP. How to use the administrator interactiveinterface is described in “Administering NetView FTP/400 V3” on page 51.Starting the agent using the CL interface is described in Chapter 5, “Using theControl Language Interface” on page 71.

7. Create a request by following the procedure described in “Example 2:Retrieving a File from a Remote OS/400 System” on page 139.

8. Release the request by typing 6 in the option field of the Requests to RetrieveFiles panel, next to the request you have just created.

9. Check whether the transfer has been processed successfully, by returning tothe Main Menu and selecting Option 2. NetView FTP/400 V3 displays theRequests to Retrieve Files panel.

If the file transfer finishes successfully, the Request Status field is set tofinished. If the file transfer does not finish successfully, the Request Statusfield is set to failed. If the request fails, check the log file for messages thatmay help you solve the problem. How to do this is described in “DisplayingLog Data” on page 44.

You can periodically recheck the status of the request by pressing function keyF5=Refresh.

Note: To transfer a file successfully NetView FTP/400 V3 must be installed atthe remote system. The NetView FTP/400 V3 subsystem at the remote systemdoes not need to be active.



Chapter 3. Using the NetView FTP/400 V3 Panels

NetView FTP/400 V3 has a set of display panels that make it easy for you tocreate, and work with requests, and to administer NetView FTP/400 V3.

Entering DataYou use the panels by:

� Entering the number of a displayed option in the option column of a panel, orentering values in the input fields of the panel. Use the -->|, |<--, and <-' keysto move from field to field.

� Using the function keys to select functions.

Sometimes NetView FTP/400 V3 fills an input field with a value that it will useunless you change it to something else. Such a value is called a default value. Tochange a default value, overtype it.

NetView FTP/400 V3 checks whether you have entered data in all fields thatrequire it and whether the data you entered is valid. If it detects missing orincorrect data, it displays a message and moves the cursor to the beginning of thecorresponding field. When you have entered all the data correctly, NetViewFTP/400 V3 displays the next panel in the series, or performs the function youselect using one of the function keys.

If you want to leave a panel without saving any of the values you typed on it, pressfunction key F12=Cancel.

Function key F3=Exit returns you to a selection menu, a main menu, or the systemmenu, depending on the panel you are currently on.


The Panel FlowThe way in which panels are chained together so that you can move from one toanother is called the panel flow. Which panels NetView FTP/400 V3 displays, andthe order in which it displays them, depends on the task you select, and on thedata you enter in the input fields of other panels. The panel flow for NetViewFTP/400 V3 is shown in Figure 5.

NetViewFTPMain Menu

Requests toSendFiles

Requests toRetrieveFiles

AdministratorFunctions

LimitRequestList

Create aRequest

SelectRemoteLU

Change aRequest

CopySelectedRequests

DeleteSelectedRequests

SelectRemoteLU

DisplayRequest

RenameSelectedRequests

DisplayTransferReport

DisplayLogData

AdditionalOperatingSystem Panels

AdditionalDisplayPanels

DisplayLogDetail

AdditionalChangePanels

Figure 5. Requests to Send Files and Retrieve Files Panel Flow


Invoking NetView FTP/400 V3To invoke the NetView FTP interactive interface, log on to OS/400 and then issuethe command:

STRFTP LANG(language-identifier)

where language-identifier can be one of the following:

Identifier Language2924 English (US)2928 French2929 German2962 Kanji (DBCS)

If you do not specify a language-identifier, NetView FTP/400 V3 uses the primarylanguage defined during installation and stored in the startup file.

NetView FTP/400 V3 displays the Main Menu, which is shown in the followingfigure:

à ðDVGððð Main Menu NetView FTP/4ðð

Select one of the following:

1. Requests to send files

2. Requests to retrieve files

3. Administrator functions

Selection or command

===> _________________________________________________________________

______________________________________________________________________

F3=Exit F4=Prompt F9=Retrieve F12=Cancel

F13=User Support F16=System Main Menu

á ñ

Figure 6. NetView FTP/400 V3 Main Menu

Getting Help from NetView FTP/400 V3To ask for help about a particular data field on a panel, position the cursor at thedata field you want help about and press the help function key. NetView FTP/400V3 displays a help panel. To get help about the panel itself, position the cursor atthe Selection or command field (or any part of the panel that is not a data field) andpress the help function key.

Press function key F12=Cancel, or the ENTER key, to return to the data entrypanel.

Chapter 3. Using the NetView FTP/400 V3 Panels 33

To get help for a log file message, type 5 next to the message on the Display Logspanel (DVG010) and then press ENTER.

Note: NetView FTP/400 V3 supports the help function key only on panels and noton CL commands.

Creating a Request to Send a FileEach file-transfer request is made up of parameters, to which you assign values.The values tell NetView FTP/400 V3 how to transfer a file.

You can find examples of the way the panels can be used in Chapter 7, “Examplesof Using the NetView FTP/400 V3 Panels” on page 135.

To create a request to send a file, select Option 1 from the NetView FTP/400 V3Main Menu. NetView FTP/400 V3 displays a panel that lists all the requests tosend files that have been created by the logged-on user.

à ðDVG1ðð Requests to Send Files

Type options, press ENTER.

1=Create 2=Change 3=Copy 4=Delete 5=Display 6=Release

7=Rename 8=Report 9=Log 11=Hold

Request Nickname of Request

Option Name User Remote LU Sending File Status

_ __________

_ REQUEST1 AUSER PARIS LIBRARY/TESTFILE WAITING

_ REQUEST2 AUSER NEWYORK1 LIBRARY/TESTFILE FINISHED

_ REQUEST3 AUSER NAIROBI LIBRARY/TESTFILE FINISHED

F3=Exit F5=Refresh F12=Cancel F15=Limit Scope F16=Sort by Date/Name

á ñ

Figure 7. Example of the Requests to Send Files Panel

This panel contains a list of requests. You can limit the scope of this list, or sortthe list by either name or creation change date.

How to limit the scope of the list is described in “Limiting the Scope of the RequestList” on page 41. Normally, when you start NetView FTP/400 V3, all the requestsyou are authorized to use are listed sorted by date. The last created or changedrequest appears first in the list. If the request list is sorted by name, pressingfunction key F16=Sort by Date/Name redisplays the list sorted by date. If therequest list shown on the panel is limited by scope, pressing function key F16=Sortby Date/Name removes your selection criteria and displays all your requests. Youcannot combine limit scope and sort by date/name.

You can also get updated status information or remove any outstanding selectionsusing the function key F5=Refresh.


To create a new request, type 1 in the option field of the first entry line of the panel.You can now do either of the following:

� Type the name you want to give the request in the request name column andpress the ENTER key.

You must specify a unique name for the request. If a request with the samename and the same user ID already exists, a message is displayed on thepanel. If you specify a unique name, NetView FTP/400 V3 displays the Createa Request to Send a File panel.

� Press the ENTER key without specifying a request name.

à ðDVG1ð1 Create a Request to Send a File

Type choices, press ENTER.

Main Transfer Parameters

Request name. . . . . . . . . __________ Name

Nickname of remote LU . . . . __________ Name

Remote check. . . . . . . . . ____ \NO, \YES

Request priority. . . . . . . _ ð-9

Server class. . . . . . . . . _ A-Z, ð-9

Sending File Parameters

Library . . . . . . . . . . . __________ Name

File. . . . . . . . . . . . . __________ Name

Member. . . . . . . . . . . . __________ \FIRST, Name, \ALL

File type . . . . . . . . . . _____ \DTAF, \SAVF, \SRCF

APPC Conversation Security

User ID . . . . . . . . . . . __________ Name

Password. . . . . . . . . . . __________ Name

F3=Exit F4=LU Directory F12=Cancel F17=Create Request

á ñ

Figure 8. Create a Request to Send a File Panel

The parameters are described on the following pages:

Page Parameter88 Request name91 Nickname of the remote LU93 Remote check89 Request priority86 Server class94 Library name94 File name95 Member name95 File type92 APPC conversation security.

If you do not know the nickname of the remote LU, press function key F4=LUDirectory. NetView FTP/400 V3 displays a list of all available LUs, from which youselect one.


à ðDVGðð2 Select Remote LU

Type option, press ENTER.

1=Select

Remote Operating

Option Nickname Loc Name System Text

_ NEWYORK1 NYFTPMVS MVS

_ NEWYORK2 NYFTPOS4 OS/4ðð

_ PARIS EHNFTPMVS MVS

_ NAIROBI NBRFTPOS4 OS/4ðð

F5=Refresh F12=Cancel

á ñ

Figure 9. Example of the Select Remote LU Panel

To select a remote LU, type 1 next to the LU you want, and press the ENTER key.You return to the Create a Request to Send a File panel.

When you have finished specifying the parameters for this panel, you can now doeither of the following:

Specify Additional ParametersPress ENTER to validate the panel, and specify additional parameters. Thenext panel in the sequence is displayed. It allows you to specify the followingadditional parameters:

Page Parameter92 Compression91 Restart from Interruption91 Automatic Retry104 Running mode of remote server (MVS, VSE)89 Scheduling parameters.

The panel that is displayed next depends on the operating system, see“Additional Panels for OS/400 Files” on page 37, “Additional Panels for MVSFiles” on page 38, “Additional Panels for VM Files” on page 39, or “AdditionalPanels for VSE Files” on page 40.

Create the RequestPress function key F17 to validate the panel and add the request to the requestdatabase. After the request is added to the request database, you return to theRequests to Send Files panel. The request is held and will not be processeduntil you release it. You release the request using option 6=Release on theRequests to Send Files panel.


Additional Panels for OS/400 FilesYou must specify additional parameters if the basic set for a file transfer does notcompletely fulfill your requirements. If the remote operating system is OS/400,NetView FTP/400 V3 first displays panel DVG105 to start specifying additionalparameters:


Request/User: REQUEST1__ AUSER___ Remote LU: PARIS_____

Sending File: LIBRARY/TESTFILE______________________________________

Specify receiving file parameters for a Source or Data File

Receiving File Parameters

Library . . . . . . . . . . . __________ Name

File. . . . . . . . . . . . . __________ Name

Member. . . . . . . . . . . . __________ Name, \FROMMBR

File Type . . . . . . . . . . _____ \DTAF, \SRCF

Receiving File Options

File option . . . . . . . . . ____ \NEW, \OLD, \REG

Member option . . . . . . . . _______ \ADD, \REPLACE, \APPEND

Expiration date for member. . _______ YYMMDD, YY/MM/DD

F3=Exit F12=Cancel F17=Create Request

á ñ

Figure 10. Additional Transfer Parameters (OS/400)


Page Parameter94 Library94 File95 Member95 File type96 File option96 Member option99 Expiration date for member.


Additional Panels for MVS FilesYou must specify additional parameters if the basic set for a file transfer does notcompletely fulfill your requirements. If the remote operating system is MVS,NetView FTP/400 V3 first displays panel DVG116 to start specifying additionalparameters:

à ðDVG116 Create a Request to Send a File



Specify receiving file parameters.


Data set name . . . . . . . . __________________________

__________________________

DD name . . . . . . . . . . . ________

Data set type . . . . . . . . ______ \PS,\PO,\LAB,\UNLAB,\VSAM

Security parameters

User ID . . . . . . . . . . . ________

Password. . . . . . . . . . . ________

Group ID. . . . . . . . . . . ________

F3=Exit F12=Cancel F17=Create Request F21=User Exit Routine

á ñ

Figure 11. Additional Transfer Parameters Panel (MVS)


Page Parameter100 Data set name103 DD name106 Data set type107 Security parameters.


Additional Panels for VM FilesYou must specify additional parameters if the basic set for a file transfer does notcompletely fulfill your requirements. If the remote operating system is VM, NetViewFTP/400 V3 first displays panel DVG501 to start specifying additional parameters:






File name . . . . . . . . . . ________

File type . . . . . . . . . . ________

File mode . . . . . . . . . . __

Data set name . . . . . . . . _____________________

_____________________

Type . . . . . . . . . . . . ______ \PS, \LAB, \UNLAB, \VSAM

Security Parameters

User ID . . . . . . . . . . . ________

Password . . . . . . . . . . ________

Group ID . . . . . . . . . . ________

VM access . . . . . . . . . . . _ 1=minidisk

2=default minidisk

3=shared file pool


á ñ

Figure 12. Additional Transfer Parameters Panel (VM)


Page Parameter100 File name100 File type100 File mode106 Type107 Security parameters126 VM access.


Additional Panels for VSE FilesYou must specify additional parameters if the basic set for a file transfer does notcompletely fulfill your requirements. If the remote operating system is VSE,NetView FTP/400 V3 first displays panel DVG601 to start specifying additionalparameters:






File ID . . . . . . . . . . . ______________________

______________________

File name . . . . . . . . . . ________

File type . . . . . . . . . . ________ \VSAM, \LAB, \UNLAB

Security Parameters

User ID . . . . . . . . . . . ________

Password . . . . . . . . . . ________


á ñ

Figure 13. Additional Transfer Parameters Panel (VSE)


Page Parameter100 File ID100 File name100 File type107 Security parameters126 VM access.


Limiting the Scope of the Request ListYou can limit the scope of requests displayed on the Requests to Send Files panelor the Requests to Retrieve Files panel by pressing function key F15=Limit Scope.NetView FTP/400 V3 displays panel DVG001:

à ðDVGðð1 Limit Scope of Request List


from to

Request name. . . . . . . . . . . REQUEST1 REQUEST5 Name

Request date. . . . . . . . . . . 9ð/ð4/ð2 9ð/ð4/1ð YYMMDD

YY/MM/DD

User ID . . . . . . . . . . . . . AUSER Name,\ALL

Nickname of remote LU . . . . . . \ALL Name,\ALL

Request status. . . . . . . . . . \ALL \ALL, \ACT, \HLD, \WAIT

\FIN, \FAIL, \SCHD, \NSTD

F3=Exit F4=LU Directory F12=Cancel

á ñ

Figure 14. Example of the Limit Scope of the Request List Panel

You must specify the following criteria:

� A range for the request name.

� A request date period. Specify the date in the form shown on the panel.

� A user ID, or *ALL to get requests from all users.

� A request status, or *ALL to get requests in all states.

� A nickname for the remote LU, or *ALL to get requests for all servers.

When you have specified the selection criteria, press ENTER. You return to theprevious panel which contains a list of requests you have selected, sorted byrequest name.

Changing a Request to Send a FileTo change a request, type 2 in the option field next to the requests that you want tochange, and press the ENTER key.

NetView FTP/400 V3 displays the Change a Request to Send a File panel with thefields filled in with the parameters for that request. With the exception of therequest name, you can change any of the parameters shown on the panel.

You can select the nickname of a different remote LU only if the remote locationname belongs to the same operating system. You are not, for example, allowed toselect an LU nickname belonging to an MVS system when the request wasoriginally created for an LU nickname belonging to an OS/400 system.


This is because the parameters specified in a request are different for the differentoperating systems and therefore different panels are used.

When you have finished changing the parameters on a panel, you can do either ofthe following:

Change additional parametersPress ENTER to validate your changes and display the next panel in thesequence. If an error occurs, a message is displayed. You must correct theerror before continuing.

Change the request in the request databasePress the function key F17 to validate the request and change the request inthe request database. If an error occurs, a message is displayed. You mustcorrect the error before the request is changed in the request database. Ifthere are no errors, the request is changed in the request database and youreturn to the list of requests.

Displaying a Request to Send a FileTo display a request, type 5 in the option field next to the requests you want to seeand press the ENTER key. You can select more than one request at a time.

NetView FTP/400 V3 displays all the panels in sequence with the specified fieldsfilled in. If you select more than one request, the display function displays thepanels for each request in sequence.

Press function key F12=Cancel to return to the Requests to Send Files panel. Allrequests which were displayed before you pressed the command key are no longermarked. The selected requests that have not yet been displayed are still marked.You can use function key F5=Refresh to remove any remaining selections from thepanel, or press ENTER to display the remaining requests.

Creating, Changing, and Displaying a Request to Retrieve a FileTo create, change, or display a request to retrieve a file, select Option 2 in theNetView FTP/400 V3 Main Menu. NetView FTP/400 V3 displays the Requests toRetrieve Files panel.

You create a request to retrieve a file just as you would create a request to send afile. The panels are very similar to those used for creating a request to send a file,and are not shown in this book. Refer to “Creating a Request to Send a File” onpage 34.

You change a request to retrieve a file just as you would change a request to senda file. Refer to “Changing a Request to Send a File” on page 41.

You display a request to retrieve a file just as you would display a request to senda file. Refer to “Displaying a Request to Send a File.”


Displaying a File-Transfer ReportTo display a file transfer report, type 8 in the option field next to the request in theRequests to Send Files panel, or Requests to Retrieve Files panel, and press theENTER key. You can select more than one request at a time.

Note: Panel DVG006 is displayed with a message if there is no report informationavailable.

For each request that has been started, NetView FTP/400 V3 displays a panelsimilar to the following:

à ðDVGðð6 Display Report

Request/User. . . . . . . . . . . : REQUEST1 AUSER

Transfer mode . . . . . . . . . . : RETRIEVE

Remote LU . . . . . . . . . . . . : NYFTPMVS

Sending file parameters

Sending file. . . . . . . . . . : FTPLIB.TESTFILE(MEMBER1)

File type . . . . . . . . . . . : \PO

Volume serial number. . . . . . :

Receiving file parameters

Receiving file. . . . . . . . . : FTPLIBRARY/TESTFILE(MEMBER1)

File type . . . . . . . . . . . : \DTAF

Volume serial number. . . . . . :

Press Enter to continue.

F3=Exit F5=Refresh F12=Cancel

á ñ

Figure 15. Example of the Display Report Panel

If you press ENTER again, the next panel in the sequence is displayed:

à ðDVGðð7 Display Report

Request/User. . . . . . . . . : REQUEST1 AUSER

Transfer mode . . . . . . . . : RETRIEVE

Remote LU . . . . . . . . . . : NYFTPMVS

Transfer parameters

Sending file records. . . . : 21ðð69

Transfer starting time. . . : 9ð/ð3/11 11:24:16

Transfer ending time. . . . : 9ð/ð3/11 11:33:17

Number of retrieved records : 21ðð69

Compression percentage. . . : 42

Restart parameters

Number of automatic retries : ððð

Number of automatic restarts: ððð

Transfer retry time . . . . :

Press Enter to continue.


á ñ

Figure 16. Example of the Display Report Panel


If you have selected more than one request, you can display the report for the nextrequest by pressing ENTER.

Note: The sending file records field will only be filled if the sending location iscapable of sending the information about the number of records.

Displaying Log DataTo display a request’s log data, type 9 in the option field next to the request in theRequests to Send Files panel, or Requests to Retrieve Files panel, and press theENTER key. You can select more than one request at a time. NetView FTP/400V3 displays panel DVG010, with the log data for the first request:

à ðDVGð1ð Display Logs

Transfer mode: SEND Request: REQUEST1 User: AUSER

Type options, press ENTER

5=Display

Option Log ID Log Data

_ DVG4211 Request created by user AUSER on 9ð/ð4/ð4 at 12:34:44

_ DVG4212 Request changed by user AUSER on 9ð/ð4/ð4 at 13:22:56

_ DVG4452 File transfer REQ1 from local system started on 9ð/ð4/ð4 at 13

_ DVG4453 File transfer REQ1 from local system finished on 9ð/ð4/ð4 at 1

F3=Exit F5=Refresh F11=Complete View F12=Cancel F18=End of List

á ñ

Figure 17. Example of the Display Logs of a Request Panel

The entries are sorted by date and time, with the latest entry appearing at thebottom of the panel. You can scroll through the entries using the Page Up andPage Down keys. If the messages are too long to fit on one line, you can displaythe complete message on two lines by pressing function key F11=Complete View.You can jump to the end of the list using function key F18=End of List. Pressingfunction key F5=Refresh gives you the latest information available.

If you have selected more than one request, you can display the log data for thenext request by pressing the ENTER key.

If *N appears in the message text for a parameter value, the value was notavailable to the program that sent the message.

To get second level help for a log file message, type 5 next to the message on theDisplay Logs panel (DVG010) and then press ENTER.


Copying Selected RequestsTo copy a request, type 3 in the option field next to the requests you want to copyin the Requests to Send Files panel, or Requests to Retrieve Files panel, and pressthe ENTER key. NetView FTP/400 V3 displays a panel that lists the requests youhave selected:

à ðDVGðð3 Copy Selected Requests

To copy requests type new request name.

Request New Request New

Name User ID Name User ID

REQUEST1 AUSER SAVE1 AUSER




F12=Cancel

á ñ

Figure 18. Example of the Copy Selected Requests Panel

The new request name that you specify must be unique in the request database.Requests in the request database are identified by the combination of requestname and user ID. Report and log entries are not copied with the request.

An administrator can also change user IDs.

Press the ENTER key to validate the panel. You must correct any errors before anyrequest is copied in the request database. A new request is given a creation dateand put on hold.

Deleting Selected RequestsTo delete a request from the request database, type 4 in the option field next to therequest in the Requests to Send Files Panel or Requests to Retrieve Files Paneland press the ENTER key. You can select more than one request at a time.NetView FTP/400 V3 displays a panel that lists the requests you have selected.Either, press the ENTER key to confirm the delete, or press function key F12 tochange your selections. NetView FTP/400 V3 checks the status of the request. Ifthe request status is active , NetView FTP/400 V3 displays a message saying soand the request is not deleted. Otherwise, the request is deleted from the requestdatabase. However, if the trace file, log file, or report file are locked, the request isdeleted but the entries remain in the file that is locked. Press F12=Cancel to returnto the previous panel without deleting any requests.


Renaming Selected RequestsTo rename a request, type 7 in the option field next to the requests that you wantto rename in the Requests to Send Files panel, or Requests to Retrieve Filespanel, and press the ENTER key. NetView FTP/400 V3 displays panel DVG005,with all the requests you have selected:

à ðDVGðð5 Rename Selected Requests

To rename requests type new request name.

Request New Request Request New Request

Name Name Name Name

REQUEST1 REQST1

REQUEST2 REQST2

TONEWYORK REQST3

FROMPARIS REQST4

F12=Cancel

á ñ

Figure 19. Example of the Rename Selected Requests Panel

You must change the New Request Name field so that the name is unique in therequest database. Requests in the request database are identified by thecombination of request name and user ID.

Press the ENTER key to validate the panel. You must correct any errors before therequest is renamed in the request database. If no error occurs, the request isrenamed in the request database. If the request status is active , you get amessage and the request is not renamed.

The entries in the log file, trace file, and report file that correspond to the oldrequest name are removed. The new request is given a creation date and put onhold. An entry is made in the log file. However, if the trace file, log file, or reportfile are locked, the request is renamed but the entries remain in the file that islocked. Press F12=Cancel to return to the previous panel without renaming anyrequests.


Releasing and Holding File-Transfer RequestsAll requests that you create or change are put on hold. You must release arequest before it can be processed. You can also hold waiting requests andscheduled requests. To hold a request, type 11 in the option field of the Requeststo Send Files panel or the Requests to Retrieve Files panel, next to the requestsyou want to hold, and press the ENTER key. The request’s status is changed toheld and is not processed for transfer until you release it.

To release a request, type 6 in the option field of the Requests to Send Files panelor the Requests to Retrieve Files panel, next to the requests you want to releaseand press ENTER. If the request is not still active or being used, its status ischanged to waiting or scheduled and is processed for transfer when a server isavailable during, if specified, the scheduled time period.

Restarting Failed File-Transfer RequestsYou can restart a failed file transfer from the point of interruption if you specify*YES for the restart from interruption parameter and release the request by typing 6in the option field of the Requests to Send Files panel or the Requests to RetrieveFiles panel, next to the request. Only the receiving NetView FTP can determine ifa restart is possible. If a restart from interruption is not possible, then the filetransfer is restarted from the beginning.

However, if you want to restart a failed request from an interruption and you did notspecify a receiving file name, you must retrieve the receiving file name that thereceiving system used for the failed request. You do this by pressing function keyF20=Get Restart Data on the Receiving File Parameters panel.

For more information about restarting file-transfer requests refer to “Restarting anInterrupted File Transfer” on page 16 and to “Restart from Interruption” onpage 91.

à ðDVG135 Change a Request to Send a File



Specify receiving file parameters for a Source or Data file.

Receiving File

Library . . . . . . . . . . . __________ Name

File. . . . . . . . . . . . . __________ Name

Member. . . . . . . . . . . . __________ Name, \FROMMBR

File type . . . . . . . . . . _____ \DTAF, \SRCF


File option . . . . . . . . . _____ \NEW, \OLD, \REG

Member option . . . . . . . . __________ \ADD, \REPLACE, \APPEND

Expiration date for member. . . _______ YYMMDD, YY/MM/DD

F3=Exit F12=Cancel F17=Change Request F2ð=Get Restart Data

á ñ

Figure 20. Receiving File Parameters Panel (OS/400)



Chapter 4. Using the NetView FTP/400 V3 AdministratorPanels

NetView FTP/400 V3 has a set of display panels that make it easy for you toadminister NetView FTP/400 V3.

Entering DataYou use the panels by:

� Entering the number of a displayed option in the option column of a panel, orentering values in the input fields of the panel. Use the -->|, |<--, and <-' keysto move from field to field.

� Using the function keys to select functions.

Sometimes NetView FTP/400 V3 fills an input field with a value that it will useunless you change it to something else. Such a value is called a default value. Tochange a default value, overtype it.

NetView FTP/400 V3 checks whether you have entered data in all fields thatrequire it and whether the data you entered is valid. If it detects missing orincorrect data, it displays a message and moves the cursor to the beginning of thecorresponding field. When you have entered all the data correctly, NetViewFTP/400 V3 displays the next panel in the series, or performs the function youselect using one of the function keys.

If you want to leave a panel without saving any of the values you typed on it, pressfunction key F12=Cancel.

Function key F3=Exit returns you to a selection menu, a main menu, or the systemmenu, depending on the panel you are currently on.


The Panel FlowThe way in which panels are chained together so that you can move from one toanother is called the panel flow. Which panels NetView FTP/400 V3 displays, andthe order in which it displays them, depends on the task you select, and on thedata you enter in the input fields of other panels. The panel flow for NetViewFTP/400 V3 is shown in Figure 21.

NetViewFTPMain Menu

Requests toSendFiles

Work withLocalComponents

Create a NewLU DirectoryEntry

Work withRemotely Started Components

Change an LU Directory Entry

Work withLU DirectoryEntries

CopyLU DirectoryEntries

Print InformationFile Entries

Delete LU DirectoryEntries

RemoveInformationFile Entries

DisplayLU DirectoryEntries

Confirm DeleteLU DirectoryEntries

Confirm RemoveInformationFile Entries

Change Parametersfor Remotely StartedComponents

RemoveRestart FileEntries

RenameLU DirectoryEntries

Confirm RemoveRestartEntries

Requests toRetrieveFiles

AdministratorFunctions

Work withStartupFile

Work withNetView FTP/400Administrators

StartNetView FTP/400Subsystem

Print NetViewFTP/400 HistoryFile Entries

ReorganizeData Queue

Remove NetViewFTP/400 HistoryFile Entries

Confirm Remove HistoryFile Entries

Figure 21. Administrator Interface Panel Flow


Administering NetView FTP/400 V3The administrator interface allows you to control execution of the NetView FTP/400V3 components and environment. You must have NetView FTP administratorauthorization to use this interface.

To perform the administrator functions, select Option 3 from the NetView FTP/400V3 Main Menu. NetView FTP/400 V3 displays the Administrator Functions panel:

à ðDVG3ðð Administrator Functions

Select one of the following:

1. Work with local components

2. Work with remotely started components

3. Work with LU directory entries

4. Print information file entries

5. Remove information file entries

6. Remove restart file entries

7. Work with startup file

8. Work with NetView FTP/4ðð administrators

9. Start NetView FTP/4ðð subsystem

1ð. Reclaim DTAQ storage

11. Print NetView FTP/4ðð history file entries

12. Remove NetView FTP/4ðð history file entries

Selection

__

F3=Exit F12=Cancel

á ñ

Figure 22. Administrator Functions Panel

Note: Selections 11 and 12, printing and removing history file entries, aredisplayed if you are the AS/400 Security Officer or if you are authorized to use theNetView FTP/400 V3 history file DVGHSTP in library DVGD01.

Working with Local ComponentsBy selecting Option 1 on the Administrator Functions panel, you can do any of thefollowing tasks:

� Start the agent� Start one or more servers� Start a trace with a specific level� Stop a trace� Stop the agent and all servers� Stop one or more servers.

Chapter 4. Using the NetView FTP/400 V3 Administrator Panels 51

NetView FTP/400 V3 displays panel DVG310:

à ðDVG31ð Work with Local Components

Number of servers that can be started: 12 Number of started servers: ð3

Type options, press Enter

1=Trace Level 1 2=Trace Level 2 3=Trace Level 3 4=Stop 5=Stop Trace

---Active Request---

Option Agent/Server Activity Status Name User Pty Trace

_ DVGNVAGENT ACTIVE

_ DVGSRVð1 ACTIVE REQUEST 3 AUSER 7 OFF

_ DVGSRVð2 WAITING

_ DVGSRVð3 WAITING

F3=Exit F4=Prompt F5=Refresh F11=View 2 F12=Cancel

F13=Start Agent F14=Start Server

á ñ

Figure 23. Example of the Work with NetView FTP/400 V3 Components Panel (View 1)

Press function key F11=View 2 to show the alternative display for panel DVG310:

à ðDVG31ð Work with Local Components

Number of servers that can be started: 12 Number of started servers: ð3


1=Trace Level 1 1=Trace Level 2 3=Trace Level 3 4=Stop 5=Stop Trace

---Server Specifications---

Option Agent/Server -------Server Classes-------- Retries Restarts Interval

_ DVGNVAGENT

_ DVGSRVð1 ABCDEF ð ð 5

_ DVGSRVð2 \ALL ð ð 5

_ DVGSRVð3 XYZ 2 1 5

F3=Exit F4=Prompt F5=Refresh F11=View 1 F12=Cancel

F13=Start Agent F14=Start Server

á ñ

Figure 24. Example of the Work with NetView FTP/400 V3 Components Panel (View 2)

Press function key F11=View 1 to redisplay the first view of panel DVG310.


A server can have the following states:

Start-Pending The server has been started but is not ready for a file transfer.

Waiting The server has been started and is ready for a file transfer, butno request is waiting to be processed.

Active The server is busy performing a file transfer.

Stop-Pending The server has been stopped.

Starting the AgentBefore you can start the agent the DVGSBS subsystem must be active. To startthe agent, press function key F13 on the Work with Local Components panel.NetView FTP/400 V3 then displays a command panel allowing you to change theagent initialization parameters:

� Maximum number of servers� Number of servers

� Server prefix � Server class � Retry parameter.

For more information about the agent initialization parameters see “AgentParameters” on page 85.

Starting One or More ServersTo start a server, press function key F14 on the Work with NetView FTP/400 V3Components panel. You cannot start a server before the agent has been started.NetView FTP/400 V3 then displays a command panel allowing you to change theserver parameters and the number of servers to start:

� Number of servers to start � Server class � Retry parameters.

For more information about the server parameters see “Server Parameters” onpage 87.

Starting a TraceNote: The trace facility is for diagnosing problems in NetView FTP/400 V3, itshould only be used if you are directed to do so by IBM*. For more informationabout diagnosing problems see Chapter 8, “What to Do if an Error Occurs inNetView FTP/400 V3” on page 143.

NetView FTP/400 provides three trace levels. Trace level 1 provides informationabout the program flow. Trace level 2 provides information about the interfacebetween the different programs. Trace level 3 provides information about theprocessing in each component’s internal subroutines. Trace level 3 also providestrace level 1 and 2 information.


To trace a NetView FTP/400 V3 local component, type 1, 2, or 3 in the option fieldnext to the component, on the Work with NetView FTP/400 V3 Components panel,and press the ENTER key. NetView FTP/400 V3 writes the processing steps of theselected component into a trace file. You can invoke the trace function for eachcomponent separately. If the server is active, the trace state changes to show thetrace level and the trace is started the next time the server status is changed fromwaiting to active .

For information about how to trace a NetView FTP/400 V3 remotely startedcomponent see “Working with Remotely Started Components” on page 55.

Stopping a TraceTo stop tracing a NetView FTP/400 V3 component, type 5 in the option field next tothe component, on the Work with NetView FTP/400 V3 Components panel, andpress the ENTER key. NetView FTP/400 V3 stops writing any processing steps tothe trace file. If the server is active, the trace state changes to OFF PENDING,and the trace is stopped when the server status is changed from active to waiting .

Stopping the Agent and All ServersTo stop the agent and all servers, type 4 in the option field next to the agent ID onthe Work with NetView FTP/400 V3 Components panel and press the ENTER key.The agent does not stop until all the running servers have finished any processingthey are currently performing.

Stopping One or More ServersTo stop a server, type 4 in the option field next to the server IDs of the servers youwant to stop, on the Work with NetView FTP/400 V3 Components panel. You canstop a server in two ways:

� If you press ENTER, the server does not stop until it has finished anyprocessing it is currently performing.

� You can force a server to stop immediately by pressing the function keyF4=Prompt. NetView FTP/400 V3 displays a command panel containing theserver parameters. Change the server stop mode to *IMMED and press theENTER key. The server stops immediately, any requests currently beingprocessed end abnormally.


Working with Remotely Started ComponentsRemotely started servers are servers that get started when a session is requestedby a remote server.

You can change the parameters for a remotely started server, or stop a server thatwas remotely started, immediately, by selecting Option 2 on the AdministratorFunctions panel. NetView FTP/400 V3 displays panel DVG380:

à ð DVG38ð Work with Remotely Started Components

Number of servers that can be started: 2ð Number of started servers: ð_

Initial number of prestarted jobs. . : 1_ Number of prestarted jobs: 1_

Trace all servers. . . . . . . . . . : YES Trace Level. . . . . . . : 1


1= Cancel transfer

---Active Request--- Remote Trace

Option Server Type APPC User Name/User ID NetView FTP Level

_ NEWYORK PJ PPDS 1

F3=Exit F5=Refresh F12=Cancel F15=Change Parameters

F16=Exclude prestarted jobs F17=Start prestarted jobs F18=End prestarted jobs

á ñ

Figure 25. Work with NetView FTP/400 Remotely Started Servers

Three fields on this panel deserve special mention:

Initial number of prestarted jobsDisplays the value of the INLJOBS parameter inthe prestarted job entry (PJE) for DVGSBS.

Number of prestarted jobs Displays the INLJOBS parameter in the PJE plusall of the prestarted servers started in addition bythe ADLJOBS in the PJE for DVGSBS.

Type Displays either PJ for a prestarted job or EJ foran evoked job.

Canceling a Remotely Initiated File TransferTo cancel a remotely initiated file transfer you must stop the remotely started serverthat is serving the file transfer. Type 1 in the option field next to the server youwant to stop, and press the ENTER key. NetView FTP/400 V3 displays a panel thatasks you to confirm your selections. Either, press the ENTER key to confirm yourselections, or press function key F12 to return to change your selections.


Working with Prestarted JobsPressing function key F16 either includes or excludes information about prestartedjobs from the list of servers on the panel. To start the prestarted jobs, pressfunction key F17=Start prestarted jobs. To stop the prestarted jobs, press functionkey F18=Stop prestarted jobs.

Changing Parameters for Remotely Started ServersTo change the parameters for a remotely started server, press function keyF15=Change Parameters on the Work with NetView FTP/400 V3 Remotely StartedComponents panel. NetView FTP/400 V3 displays panel DVG382:

à ð DVG382 Change Parameters for Remotely Started Components


Maximum number of servers. . . . . . . __ ð-99

Initial number of servers. . . . . . . __ 1-99

Trace all servers. . . . . . . . . . . ____ \YES. \NO

Trace level. . . . . . . . . . . . . . _ 1, 2, 3

F3=Exit F12=Cancel

á ñ

Figure 26. Change Parameters for Remotely Started Servers

On this panel you can:

� Start or stop tracing for all remotely started servers by typing *YES to start atrace, or *NO to stop a trace in the Trace all servers field.

� If you specify *YES, specify trace level 1, 2, or 3.

� Change the number of servers that can be remotely started by typing a valuefrom 0 to 99 in the Maximum number of servers field. If you specify 0, it is notpossible for a server to be started remotely.

� Specify the number of servers, from 1 to 99, to start when NetView FTP/400 V3starts.

Press the ENTER key to confirm your changes.

Note: These changes do not affect servers that are already active.


Working with LU Directory EntriesThe LU directory contains information about the remote LUs (remote servers) in anetwork. You can create, change, copy, delete, display, and rename entries in theLU directory by selecting Option 3 from the Administrator Functions panel. NetViewFTP/400 V3 displays panel DVG320:

à ðDVG32ð Work with LU Directory

Type options, press Enter.

1=Create 2=Change 3=Copy 4=Delete 5=Display 7=Rename

Remote Operating

Option Nickname Loc Name System Text

_ NEWYORK1 NYNFTPð1 MVS

_ NEWYORK2 NYNFTPð2 OS/4ðð

_ PARIS PRNFTPð1 VM

_ NAIROBI NINFTPð1 VSE


á ñ

Figure 27. Example of the Work with LU Directory Panel

Creating a New LU Directory EntryType 1 in the option field, and the nickname of the remote LU in the nickname fieldof the first entry line of the panel, and press the ENTER key. NetView FTP/400 V3displays panel DVG321:

à ðDVG321 Create a New LU Directory Entry

Type choices, press Enter.

Nickname. . . . . . . . . . __________ Name

Remote location name. . . . __________ Name

Operating system. . . . . . _ 1=OS/4ðð 3=VSE

2=MVS 4=VM

Local location name . . . . __________ Name, \LOC, \NETATR

Remote network identifier . __________ Name, \LOC, \NETATR, \NONE

Communication mode. . . . . __________ Name, \NETATR

Text. . . . . . . . . . . . ___________________________

F3=Exit F12=Cancel

á ñ

Figure 28. Create a New LU Directory Entry Panel


The following describes how to specify the fields of this panel:

NicknameSpecify the nickname you want to give the remote server (remote LU). It canbe up to 10 characters.

Remote location nameSpecify the LU name of the remote server.

Operating systemSpecify 1 for OS/400, 2 for MVS, 3 for VSE, or 4 for VM, depending on theoperating system where the server runs.

Local location nameIs the name of your local location. Possible values are:

*LOC The local location name associated with the remote location is used.

*NETATR The local location name specified in the network attributes is used.

Name Is the local location name associated with the program device. Onlyspecify the local location name if you want to indicate a differentspecific local location name for the remote location. If the locallocation name is not valid, a log entry is made for the correspondingrequest when the program device is acquired.

Remote network identifierIs the remote network identifier of the remote location. Possible values are:

*LOC Any remote network identifier for the remote location may be used.

*NETATR The remote network identifier specified in the network attributes isused.

*NONE No remote network identifier is used.

Name Specify a remote network identifier to be associated with theprogram device entry.

Communication ModeSpecify the mode name you want to use for this LU entry. The mode namecan be different for each LU directory entry. You must specify acommunication mode.

The mode name points to a mode description in which the administratorspecifies the session parameters for the server. The administrator can create amode description using the OS/400 command CRTMODD. How to do this isdescribed in AS/400 Communications: Advanced Program-to-ProgramCommunication Programmer’s Guide.

TextA string of up to 30 characters describing the remote LU. Do not enclose thestring in apostrophes.


The following shows how entries in the LU directory must match the parameters ofthe CRTDEVAPPC AS/400 command:

LU Directory Entry CRTDEVAPPC

Nickname

Remote location name

Operating system

Local location name

Remote network identifier

Communication mode

:

:

:

:

:

:

a

b

c

d

a

b

c

d

SYSBD01

AS400BU3

1

AS400BU1

*NONE

BLANK

RMTLOCNAME(AS400BU3)

LLOCNAME(AS400BU1)

RMTNETID(*NONE)

MODE(BLANK)

Changing an LU Directory EntryType 2 next to the LU nickname you want to change, and press the ENTER key.NetView FTP/400 V3 displays panel DVG322:

à ðDVG322 Change LU Directory Entry

Nickname. . . . . . . . . . PARIS


Remote location name. . . . __________ Name

Operating system. . . . . . _ 1=OS/4ðð 3=VSE

2=MVS 4=VM

Local location name . . . . __________ Name, \LOC, \NETATR

Remote network identifier . __________ Name, \LOC, \NETATR, \NONE

Communication mode. . . . . __________ Name, \NETATR

Text. . . . . . . . . . . . ___________________________

F3=Exit F12=Cancel

á ñ

Figure 29. Change an LU Directory Entry Panel

With the exception of the LU nickname you can change any of the parameters onthe panel.


Copying LU Directory EntriesType 3 next to the LUs you want to copy, and press the ENTER key. NetViewFTP/400 V3 displays panel DVG323:

à ðDVG323 Copy LU Directory Entries

To copy LU directories type a new LU nickname.

LU New LU LU New LU

Nickname Nickname Nickname Nickname

NEWYORKð1 NEWYORKð1A




F12=Cancel

á ñ

Figure 30. Example of the Copy LU Directory Entries Panel

You must ensure that the new LU nickname is unique in the LU directory. Pressthe ENTER key to validate the panel. If an error occurs while copying, the copyfunction is interrupted. To continue copying you must correct the error, and pressENTER.

Deleting LU Directory EntriesType 4 next to the LUs you want to delete, and press the ENTER key. NetViewFTP/400 V3 displays a panel that asks you to confirm your selections. Either,press the ENTER key to confirm the delete, or press function key F12=Cancel tochange your selections.


Renaming LU Directory EntriesType 7 next to the LUs you want to rename, and press the ENTER key. NetViewFTP/400 V3 displays panel DVG325 with all the LUs you have selected:

à ðDVG325 Rename LU Directory Entries

To rename LU directories type a new LU nickname.

LU New LU LU New LU

Nickname Nickname Nickname Nickname

NYRKð1 NEWYORKð1

NYRKð2 NEWYORKð2

NYRKð3 NEWYORKð3

NYRKð4 NEWYORKð4

F12=Cancel

á ñ

Figure 31. Example of the Rename LU Directory Entries Panel

You must ensure that the new LU nickname is unique in the LU directory. Pressthe ENTER key to validate the panel. If an error occurs while renaming, the renamefunction is interrupted. To continue renaming you must correct the error, and pressENTER.


Printing Information File EntriesTo print information about NetView FTP processing, select option 4 from theAdministrator Functions panel. NetView FTP/400 V3 displays panel DVG330,which allows you to select the type of information you want to print:

à ðDVG33ð Print Information File Entries

Type your selections and press ENTER.

Information type. . . . . . . . _ 1=Log information

2=File transfer report

3=Trace output

Trace level . . . . . . . . . . _ 1, 2, 3

Component (Agent/Server). . \ALL______ Name, \ALL

from to

Request name. . . . . . . . __________ __________

Time Interval

Entry time. . . . . . . . ðð:ðð:ðð 23:59:59 HHMMSS, HH:MM:SS

Entry date. . . . . . . . 86/ð1/ð1 9ð/ð2/11 YYMMDD, YY/MM/DD

User. . . . . . . . . . . . \ALL______ Name, \ALL

Request origin. . . . . . . \ALL \LCL, \RMT, \ALL

F3=Exit F12=Cancel

á ñ

Figure 32. Print Information File Entries Panel

To print information do the following steps:

1. Select the type of information you want in the Information type field.

2. If you select 1=Log information, type the component name in the Componentfield and the request names in the Request name field.

3. If you select 2=File transfer report, type the request names in the Requestname field. You are not allowed to select a component name for 2=Filetransfer report.

4. If you select 3=Trace output, type the level in the Trace level field, thecomponent name in the Component field, and the request names in theRequest name field.

5. Type, using the format shown on your panel, the period for which you want toprint information in the Time Interval fields.

6. Type the user ID in the User field.

7. Type the request origin in the Request origin field.

8. Press the ENTER key.

A job with the name DVG11CB is submitted to the job queue DVGJOBQ1. This jobuses the printer device and output queue defined in your user profile. The print fileDVG01P is spooled to the output queue, and, after printing, it is saved.

Note: The job DVG11CB uses the job description DVGJOBD1.


Removing Information File EntriesTo remove information file entries, select option 5 from the Administrator Functionspanel. NetView FTP/400 V3 displays panel DVG340:

à ðDVG34ð Remove Information File Entries


Information type. . . . . . . . _ 1=Log information

2=File transfer report

3=Trace output

Trace level . . . . . . . . . . _ 1, 2, 3

Component (Agent/Server). . \ALL______ Name, \ALL

from to

Request name. . . . . . . . __________ __________

Time Interval

Entry time. . . . . . . . ðð:ðð:ðð 23:59:59 HHMMSS, HH:MM:SS

Entry date. . . . . . . . 86/ð1/ð1 9ð/ð1/16 YYMMDD, YY/MM/DD

User. . . . . . . . . . . . \ALL______ Name, \ALL

Request origin. . . . . . . \ALL \LCL, \RMT, \ALL

F3=Exit F12=Cancel

á ñ

Figure 33. Remove Information File Entries Panel

You can only remove information file entries when the agent and servers have notbeen started. If the information file is in use by another job, no information fileentries can be removed. You must ensure that no user is currently using theinteractive interface.

Note: No remotely started server can run when information file entries are beingremoved.

To remove information file entries do the following steps:

1. Select the type of information you want in the Information type field.

2. If you select 1=Log information, type the component name in the Componentfield and the request names in the Request name field.

3. If you select 2=File transfer report, type the request names in the Requestname field. You are not allowed to select a component name for 2=Filetransfer report.

4. If you select 3=Trace output, type the level in the Trace level field, thecomponent name in the Component field and the request names in theRequest Name field.

5. Type the period, using the format shown on your panel, for which you want toremove information in the Time Interval fields.




8. Press the ENTER key. NetView FTP/400 V3 displays the Confirm Remove ofInformation Entries Panel.

9. Either, press the ENTER key to confirm your selection or press function key F12to return to the previous panel.

A job with the name DVG12CB is submitted to the job queue DVGJOBQ1.


Removing Restart File EntriesNetView FTP/400 V3 automatically deletes the corresponding restart record at theend of a successful file transfer. Over a period of time, however, the restart file canfill up. If a request ends abnormally, the request’s restart record remains in therestart file.

To remove restart file entries, select option 6 from the Administrator Functionspanel. NetView FTP/400 V3 displays panel DVG350.

You can only remove restart file entries when the agent and servers have not beenstarted. If the restart file is being used by another job, no restart file entries can beremoved. You must ensure that no user is currently using the interactive interface.

Note: No remotely started server can run when restart file entries are beingremoved.

à ðDVG35ð Remove Restart File Entries

Type time period to remove restart file entries and press ENTER.

from to

Restart entries time . . ðð:ðð:ðð 23:59:59 HHMMSS, HH:MM:SS

Restart entries date . . 86/ð1/ð1 9ð/ð1/16 YYMMDD, YY/MM/DD

F3=Exit F12=Cancel

á ñ

Figure 34. Example of the Remove Restart File Entries Panel

Specify the time period, using the format shown on your panel, for which you wantentries to be deleted, and press the ENTER key. NetView FTP/400 V3 displays apanel that asks you to confirm your selections. Press the ENTER key to confirmyour selections. All entries entered within that period are deleted from the restartfile, regardless of the request type, or request originator.


Working with the Startup FileBy selecting option 7 from the Administrator Functions panel, you can change thefollowing:

� The primary language� The NetView FTP/400 V3 system name defined during system installation� The auditability parameter� The post-transfer queue entry parameter.

Note: The Auditability field, which specifies whether or not NetView FTP/400creates and updates a NetView FTP/400 V3 history file, is only displayed if you arethe AS/400 Security Officer or are authorized to use the NetView FTP/400 V3history file DVGHSTP in library DVGD01. NetView FTP/400 V3 displays panelDVG361:

à ð DVG361 Work with Startup File


Primary Language. . . . . . . . ____ Number

NetView FTP/4ðð Name. . . . . . __________ Name

Auditability. . . . . . . . . . ____ \YES, \NO

Post transfer queue entry . . . ____ \YES, \NO

F3=Exit F12=Cancel

á ñ

Figure 35. Work with Startup File

Note: You cannot change any of the parameters on panel DVG361 while theagent is active.

The primary language can be one of the following:

Identifier Language2924 English (US)2928 French2929 German2962 Kanji (DBCS)

Note: If you change the primary language, the library list of the job descriptionDVGJOBD is changed to:

QTEMP QGPL DVGOxxxx DVGOð1 DVGDð1

where xxxx is the primary language.

The NetView FTP/400 V3 name can be up to 10 characters; it is the name of theagent. This name is used by NetView FTP/400 V3 for restarting failed filetransfers. It should be unique within a network.


The Auditability field, if displayed, allows you to specify whether or not NetViewFTP/400 V3 logs transfer activities in the NetView FTP/400 V3 history file.

The Post transfer queue entry field allows you to specify whether or not NetViewFTP/400 V3 writes an entry to the post-transfer data queue after a file transfer. Formore information about post-transfer processing see Appendix I, “Working with thePost-Transfer Data Queue” on page 171.

Note: If you normally work with prestarted jobs and change the startup file whenno prestarted jobs are active, the next request (request 1) runs using the oldstartup file contents. Requests after this request (request 1) will use the newstartup file contents. If you change the startup file when a prestarted job is active,the next request using that prestarted job will use the new startup file contents.

Working with NetView FTP/400 V3 AdministratorsA NetView FTP/400 V3 administrator can give other users NetView FTP/400 V3administrator authorization by selecting option 8 on the Administrator Functionspanel.

Note: The AS/400 security officer (QSECOFR) is by default a NetView FTP/400V3 administrator.

à ð DVG37ð Work with NetView FTP/4ðð Administrators


1=Create 4=Delete

Option User ID Description

_ __________

_ BROWN ALASTAIR BROWN

_ SMITH JOHN SMITH

_ JONES LINDA JONES


á ñ

Figure 36. Work with NetView FTP/400 V3 Administrators


Creating a New AdministratorTo create an administrator, type 1 in the option field of the top entry line of theWork with NetView FTP/400 V3 Administrators panel and press the ENTER key.NetView FTP/400 V3 displays panel DVG371:

à ð DVG371 Create a new NetView FTP/4ðð Administrator


User ID . . . . . . . . . . . . __________ Name

Description . . . . . . . . . . ______________________________

F3=Exit F12=Cancel

á ñ

Figure 37. Create a New NetView FTP/400 V3 Administrator

Type the user ID of the user you want to make an administrator in the user ID field,and any description you want in the description field, and then press the ENTERkey. The user is added to the authorization lists DVGAUTL and DVGADMAUTLwith the object authority *ALL and list management.

Deleting an AdministratorTo delete an administrator, type 4 next to the administrator you want to delete.Work with NetView FTP/400 V3 Administrators panel and press the ENTER key.NetView FTP/400 V3 displays panel DVG372 that asks you to confirm yourselections. Either, press the ENTER key to confirm your selections, or pressfunction key F12=CANCEL to return to change your selections.

Note: The user is removed from the authorization lists DVGAUTL andDVGADMAUTL.

Starting the NetView FTP/400 V3 SubsystemBefore you can use NetView FTP/400 V3, the NetView FTP/400 V3 subsystemDVGSBS must be active. You start this subsystem by selecting option 9 on theAdministrator Functions panel.


Reclaim DTAQ StorageSelect option 10 on the Administrator Functions panel to reorganize the storageallocated to but not currently used by the post-transfer data queue DVGPTDTAQ.For more information about post-transfer processing see Appendix I, “Working withthe Post-Transfer Data Queue” on page 171.

Printing NetView FTP/400 V3 History-File EntriesNetView FTP/400 can maintain a file of information about every request that isreleased. This file contains one member for each month. The name of eachmember identifies the year and month that it was created.

Note: You can only print history-file entries if you are the AS/400 Security Officeror are authorized to use the NetView FTP/400 V3 history file DVGHSTP in libraryDVGD01.

To print history-file entries, select option 11 from the Administrator Functions panel.NetView FTP/400 V3 displays panel DVG390 which allows you to specify a rangeof NetView FTP/400 V3 history-file entries for NetView FTP/400 to print:

à ð DVG39ð Print NetView FTP/4ðð History-File Entries


from to

Time Interval

Entry time. . . . . . . . . ðð:ðð:ðð 23:59:59 HHMMSS, HH:MM:SS

Entry date. . . . . . . . . 91/ð7/ð1 91/ð9/3ð YYMMDD, YY/MM/DD

User. . . . . . . . . . . . . \ALL______ Name, \ALL

Request origin. . . . . . . . \ALL \LCL, \RMT, \ALL

F3=Exit F12=Cancel

á ñ

Figure 38. Print NetView FTP/400 V3 History-File Entries

To print NetView FTP/400 V3 history-file entries, do the following:

1. Type the period, using the format shown on your panel, for which you want toprint NetView FTP/400 V3 history-file entries in the Time Interval fields.



A job with the name DVG13CB is submitted to the job queue DVGJOBQ1. This jobuses the printer device and output queue defined in your user profile. The print fileDVG02P is spooled to the output queue, and, after printing, it is saved.



Figure 39 shows an example of a history file report.

History 92/ð3/25

Date Page ððð1

SELECTION CRITERIA

from to

Time Interval

Time. . . . . . . . . . . . : ðð:ðð:ðð 14:37:46

Date. . . . . . . . . . . . : 92/ð3/1ð 92/ð3/25

User. . . . . . . . . . . . . : \ALL

Request origin. . . . . . . . : \ALL

History 92/ð3/25

Date Page ððð2

Request origin User Date Time MSG-ID Message Text

\LCL DEM 92/ð3/1ð ð8:23:54 DVG4452 File transfer ASPTHð2V1 from local system started on 92/ð3/1ð at ð8:23:54

\RMT DEM 92/ð3/1ð ð8:24:ð5 DVG4461 Transfer from remote system started on 92/ð3/1ð at ð8:24:ð5

\LCL DEM 92/ð3/1ð ð8:24:4ð DVG4717 FTP name of the remote system is AGENT

\LCL DEM 92/ð3/1ð ð8:24:4ð DVG4715 Sending file name is SENDLIB/BIGFILE(BIGFILE2)

\LCL DEM 92/ð3/1ð ð8:24:41 DVG4718 Receiving file name is RECEIVELIB/BIGFILE(BIGFILE2)

\LCL DEM 92/ð3/1ð ð8:24:51 DVG4591 Member BIGFILE2 cleared in file BIGFILE in library RECEIVELIB by DVGSRVð1

\RMT DEM 92/ð3/1ð ð8:25:ð1 DVG4717 FTP name of the remote system is AGENT

\LCL THU 92/ð3/1ð ð9:49:ð4 DVG4452 File transfer N32765_ðð2 from local system started on 92/ð3/1ð at ð9:49:ð4

\LCL THU 92/ð3/1ð ð9:5ð:56 DVG4717 FTP name of the remote system is AGENT

\LCL THU 92/ð3/1ð ð9:51:2ð DVG4716 Total number of records sent is ðððððððð2

\LCL THU 92/ð3/1ð ð9:51:2ð DVG4453 File transfer N32765_ðð2 from local system finished on 92/ð3/1ð at ð9:51:2ð

\RMT DEM 92/ð3/1ð 1ð:32:ð1 DVG4472 File transfer ASPTHð2V1 from remote system finished 92/ð3/1ð at 1ð:32:ð1

\LCL DEM 92/ð3/1ð 1ð:32:ð2 DVG4719 Total number of records retrieved is ðððð55136

\LCL DEM 92/ð3/1ð 1ð:32:ð2 DVG4453 File transfer ASPTHð2V1 from local system finished on 92/ð3/1ð at 1ð:32:ð2

\LCL XSM 92/ð3/1ð 1ð:34:22 DVG4452 File transfer C3275ð_ðð1 from local system started on 92/ð3/1ð at 1ð:34:22

\LCL XSM 92/ð3/1ð 1ð:36:17 DVG4717 FTP name of the remote system is AGENT

\LCL XSM 92/ð3/1ð 1ð:36:46 DVG4716 Total number of records sent is ðððððððð1

\LCL XSM 92/ð3/1ð 1ð:36:46 DVG4453 File transfer C3275ð_ðð1 from local system finished on 92/ð3/1ð at 1ð:36:46

\LCL XSM 92/ð3/1ð 1ð:36:47 DVG4452 File transfer C3275ð_ðð2 from local system started on 92/ð3/1ð at 1ð:36:47

\LCL XSM 92/ð3/1ð 1ð:38:23 DVG4717 FTP name of the remote system is AGENT

\LCL XSM 92/ð3/1ð 1ð:39:ð6 DVG4716 Total number of records sent is ðððððððð2

\LCL XSM 92/ð3/1ð 1ð:39:ð6 DVG4453 File transfer C3275ð_ðð2 from local system finished on 92/ð3/1ð at 1ð:39:ð6

-----------------------------------------------------------END OF REPORT--------------------------------------------------------

Figure 39. Example of a History File Report

Deleting NetView FTP/400 V3 History-File EntriesNote: You can only delete NetView FTP/400 V3 history-file entries if you are theAS/400 Security Officer or are authorized to use the NetView FTP/400 V3 historyfile DVGHSTP in library DVGD01.

To delete NetView FTP/400 V3 history-file entries, select option 12 from theAdministrator Functions panel and press the ENTER key.

NetView FTP/400 V3 displays panel DVG392 that lets you specify a period of yearsand months for which you want to delete all the NetView FTP/400 V3 history-fileentries.

Specify the period and press the ENTER key. NetView FTP/400 V3 displays apanel that asks you to confirm the period of years and months to delete. Either,press the ENTER key to confirm the range, or press function key F12=CANCEL toreturn to the previous panel.



Chapter 5. Using the Control Language Interface

You can use the Control Language (CL) interface to:

� Create requests to send and retrieve files� Change existing requests in the request database� Delete requests from the request database� Change the APPC password� Change the security password� Start and stop the agent� Start and stop a server.

You use the CL interface by entering commands at your terminal and then eitherpressing the ENTER key to execute the command or pressing function keyF4=Prompt to display a panel containing the parameters you need to specify.

The following is an example of a command to send an object to a remote NetViewFTP/400 V3 system. Press ENTER to process the command.

CRTSRQMVS RMSERVER(NEWYORK1)

REQNAME(MYREQUEST) SFILE(MYLIB/MYFILE)

If you type this command and then press function key F4=Prompt, the followingpanel is displayed:

à ðCreate Send Request MVS (CRTSRQMVS)


Request name . . . . . . . . . > MYREQUEST Name

Nickname of remote LU. . . . . > NEWYORK1 Name

APPC user ID . . . . . . . . . Name

Password . . . . . . . . . . . Character value

Sending file . . . . . . . . . > MYFILE Name

Sending library. . . . . . . > MYLIB Name

Sending file type. . . . . . . \DTAF \DTAF,\SAVF,\SRCF

F3=Exit F4=Prompt F5=Refresh F1ð=Additional Parameters F12=Cancel

F13=How to use this display F24=More keys

á ñ

Figure 40. NetView FTP/400 CL Prompt Panel

You can change any of the values shown on this panel.


If you type only the command and then press function key F4=Prompt, the followingpanel is displayed:

à ðCreate Send Request MVS (CRTSRQMVS)


Request name . . . . . . . . . __________ Name

Nickname of remote LU. . . . . __________ Name

APPC user ID . . . . . . . . . __________ Name

Password . . . . . . . . . . . __________ Character value

Sending file . . . . . . . . . __________ Name

Sending library. . . . . . . ________ Name

Sending file type. . . . . . . \DTAF \DTAF,\SAVF,\SRCF

F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel

F13=How to use this display F24=More keys

á ñ

Figure 41. NetView FTP/400 CL Prompt Panel

If you are using the prompt panel of the CL interface, take the following intoconsideration:

� If, for example, you want to change more than the first volume serial number ina sequence of volume serial numbers, you must specify *SAME for the valuesyou do not want to change.

� The prompt panel allows you to specify a maximum of 512 characters for aparameter. This means that if you want to specify more than 512 charactersfor the second Exit-Routine Input parameter, you must use the command line tospecify the parameter.

Note: For a description of the OS/400 command keys refer to AS/400Programming: Control Language Programmer’s Guide. The following table lists theCL commands:

Table 10 (Page 1 of 2). Control Language (CL) Commands

Function Command Notes

Create a request to send anobject to NetView FTP/400V3

CRTSRQOS4 A send request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Create a request to send anobject to NetView FTPVersion 2 MVS

CRTSRQMVS A send request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Create a request to send anobject to NetView FTP VM

CRTSRQVM A send request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Create a request to send anobject to NetView FTP VSE

CRTSRQVSE A send request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.


Table 10 (Page 2 of 2). Control Language (CL) Commands

Function Command Notes

Create a request to retrievean object from NetViewFTP/400 V3

CRTRRQOS4 A retrieve request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Create a request to retrievean object from NetView FTPVersion 2 MVS

CRTRRQMVS A retrieve request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Create a request to retrievean object from NetView FTPVM

CRTRRQVM A retrieve request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Create a request to retrievean object from NetView FTPVSE

CRTRRQVSE A retrieve request is created and stored in the requestdatabase. The request name for each user must be uniquein the request database.

Change a request to sendto or retrieve from NetViewFTP/400 V3

CHGSRQOS4CHGRRQOS4

You can change only those requests that you own. If youare an administrator, you can change the requests of anyuser.

Change a request to sendto or retrieve from NetViewFTP Version 2 MVS

CHGSRQMVSCHGRRQMVS


Change a request to sendto or retrieve from NetViewFTP VM

CHGSRQVMCHGRRQVM


Change a request to sendto or retrieve from NetViewFTP VSE

CHGSRQVSECHGRRQVSE


Delete a request DLTREQFTP You can delete only those requests that you own. If you arean administrator, you can delete the requests of any user.

Start the NetView FTP/400Agent

STRAGNFTP The agent must be started before any file transfer ispossible. At least one server must be started when theagent is started. This command can only be used by aNetView FTP/400 V3 administrator.

Stop the NetView FTP/400Agent

ENDAGNFTP No file transfer is possible after the agent has been stopped.This command can only be used by a NetView FTP/400 V3administrator.

Start a server STRSRVFTP No file transfer is possible until at least one server isrunning. This command can only be used by a NetViewFTP/400 V3 administrator.

Stop a server ENDSRVFTP No file transfer is possible if no servers are running. Thiscommand can only be used by a NetView FTP/400 V3administrator.

Start NetView FTP/400 V3 STRFTP Start NetView FTP/400 V3.

Change requests APPCpassword

CHGAPPCPWD You can change the APPC password for a series of yourrequests. If you are an administrator, you can changeanother user’s request.

Change requests securitypassword

CHGSECPWD You can change the MVS, VSE, or VM security password fora series of your requests. If you are an administrator, youcan change another user’s request.

Chapter 5. Using the Control Language Interface 73

Specifying ParametersYou specify NetView FTP/400 V3 parameters in the form keyword(value) . Thekeyword tells NetView FTP/400 V3 which parameter is being set and the value tellsNetView FTP/400 V3 which value the parameter is being set to. Refer toChapter 6, “Parameter Reference” on page 77 for detailed information about theNetView FTP/400 V3 parameters. The following rules apply when you specifyparameters:

� Keywords are separated by blanks.

� If you code a parameter incorrectly, NetView FTP/400 V3 rejects the requestand issues an error message.

Using the File-Transfer Request CL CommandsThe following table shows which parameters to specify for the CL commandsCRTSRQOS4, CRTSRQMVS, CRTRRQOS4, CRTRRQMVS, CHGSRQOS4,CHGSRQMVS CHGRRQOS4, and CHGRRQMVS. It also gives the pages whereyou can find a list of parameters.

Table 11. Parameters You Need to Specify for Sending and Retrieving Files

Sending Retrieving ParameterList onPage

ToOS/400

ToMVS

FromOS/400

FromMVS

Commands: Request parametersTransfer parametersOS/400 sending parametersOS/400 receiving parametersMVS sending parametersMVS receiving parameters

CRTSRQOS4CHGSRQOS4

�

�

�

�

— —

CRTSRQMVSCHGSRQMVS

�

�

�

— — �

CRTRRQOS4CHGRRQOS4

�

�

�

�

— —

CRTRRQMVSCHGRRQMVS

�

�

— �

�

—

78 79 79 79 80 81

The following table shows which parameters to specify for the CL commandsCRTSRQVM, CRTSRQVSE, CRTRRQVM, CRTRRQVSE, CHGSRQVM,CHGSRQVSE CHGRRQVM, and CHGRRQVSE. It also gives the pages whereyou can find a list of parameters.


Table 12. Parameters You Need to Specify for Sending and Retrieving Files

Sending Retrieving ParameterList onPage

ToVM

ToVSE

FromVM

FromVSE

Commands: Request parametersTransfer parametersOS/400 sending parametersOS/400 receiving parametersVM sending parametersVM receiving parametersVSE sending parametersVSE receiving parameters

CRTSRQVMCHGSRQVM

�

�

�

— — �

— —

CRTSRQVSECHGSRQVSE

�

�

�

— — — — �

CRTRRQVMCHGRRQVM

�

�

— �

�

— — —

CRTRRQVSECHGRRQVSE

�

�

— �

— — �

—

78 79 79 79 82 83 84 84

Using the Agent and Server CL CommandsThe following table shows the parameters you can specify for the CL commandsSTRAGNFTP, ENDAGNFTP, STRSRVFTP and ENDSRVFTP:

Table 13. CL Parameters

Parameter Keyword STRAGNFTP ENDAGNFTP STRSRVFTP ENDSRVFTP Descriptionon Page

Maximum number ofservers

MAXSRV � — — — 85

Number of servers ACTSRV � — — — 85

Server prefix SRVPFX � — — — 86

Number of servers tostart

NBRSRV — — � — 87

Server stop mode ENDMODE — — — � 87

Server suffix SRVSFX — — — � 87

Server class SRVCLS � — � — 86

Maximum number orretries

RTRY � — � — 86

For a detailed description of the parameters see Chapter 6, “Parameter Reference”on page 77.

Chapter 5. Using the Control Language Interface 75

Using Change APPC Password and Change Security PasswordYou can change the APPC password for a series of your requests with theCHGAPPCPWD command. You can change the MVS, VSE, or VM securitypassword for a series of your requests with the CHGSECPWD command.

With both commands, if you are an administrator, you can change another user’srequest.

If you run either command, a panel is displayed that prompts you to enter thefollowing information:

Request originator Specify either the name of the request originatoror, if you are an administrator and want to changeall requests to a specific remote LU, *ALL.

APPC user ID or Security user IDSpecify the user ID for which you want to changethe password.

Nickname of remote LU Specify the nickname of the remote LU.

New password Specify a valid password; the characters you typewill not be displayed.

Verify new password Enter the password again to verify it, again thecharacters that you type will not be displayed.

Press ENTER to change the password or F12=CANCEL to remove the panel if youchange your mind.

Writing Application ProgramsYou can use NetView FTP/400 V3 in an application program by calling the programQCMDEXC. See Chapter 5, “Using the Control Language Interface” on page 71for information about how to use the CL interface. The following is an example ofhow you call this program in your application program:

CALL PGM(QCMDEXC) PARM(CRTSRQOS4 RMSERVER(NEWYORK) REQNAME(MYREQUEST)

SFILE(MYLIB/MYFILE) 62)

Figure 42. Example of How an Application Program Calls QCMDEXC

Note: For a detailed description of how to use QCMDEXC refer to AS/400Programming: Control Language Programmer’s Guide.


Chapter 6. Parameter Reference

This chapter gives detailed information about the NetView FTP/400 V3 parameters.

Conventions Used to Describe Parameters and Their ValuesThis book uses the following conventions when describing NetView FTP/400 V3parameters:

� Terms printed in bold, uppercase type (LIKE THIS ) represent keywords, andvalues that you code exactly as shown.

� Terms printed in italic, lowercase type (like this) represent values that you codeas described in the accompanying text.

� Default values are underlined (LIKE THIS ).

� Bold, lowercase letters that appear in some keywords (such as the x inxFILTYPE ) are place holders. When coding such keywords, replace the lettersshown in lowercase with the letters described in the accompanying text.

� Vertical bars (|) between values mean that you are to specify one, but no morethan one, of the values separated by the bars.

Types of ParametersThe NetView FTP/400 V3 parameters fall into one of the following categories:

� Agent initialization parameters. You use these parameters when setting up theagent.

� Server parameters. You use these parameters when starting and stopping aserver.

� Request parameters. These parameters tell NetView FTP/400 V3 about whena transfer is to be performed and by which class of server and request priority.

� Transfer parameters. These parameters tell NetView FTP/400 V3 how toconduct the file transfer.

� NetView FTP/400 V3 Sending file parameters. These parameters tell NetViewFTP/400 V3 about the file to send to an OS/400 system.

� NetView FTP/400 V3 Sending file parameters when the remote system isNetView FTP Version 2 MVS, NetView FTP VSE, or NetView FTP VM. Theseparameters tell NetView FTP/400 V3 about the file to send from an MVS, VSE,or VM system.

� NetView FTP/400 V3 Receiving file parameters. These parameters tellNetView FTP/400 V3 about the file to receive at an OS/400 system.

� NetView FTP/400 V3 Receiving file parameters when the remote system isNetView FTP Version 2 MVS, NetView FTP VSE, or NetView FTP VM. Theseparameters tell NetView FTP/400 V3 about the file to receive at an MVS, VSE,or VM system.


Agent Initialization ParametersUse these parameters for starting the agent. You can start the agent using eitherthe administrator interactive interface or the CL interface.

Table 14. Agent Initialization Parameters

Parameter Name Keyword Description on Page

Number of servers to start ACTSRV 85

Maximum number of servers MAXSRV 85

Retry parameter RTRY 86

Server class SRVCLS 86

Server prefix SRVPFX 86

Server ParametersUse the server parameters for starting and stopping a server. You can start andstop a server using either the administrator interactive interface or the CL interface.

Table 15. Server Parameters


Server stop mode ENDMODE 87

Number of servers to start NBRSRV 87

Retry parameter RTRY 86


Server suffix SRVSFX 87

Request ParametersRequest parameters tell NetView FTP/400 V3 about the requests you want tocreate, change, or delete.

Table 16. NetView FTP/400 V3 Request Parameters


Hold request REQHLD 88

Request name REQNAME 88

Request originator RQORG 88

Request priority RQPTY 89

New password NEWPWD 89

Not-before and not-after date and time SCHDL 89


Verify password VRYPWD 89


Transfer ParametersUse these parameters to tell NetView FTP/400 V3 how to conduct a file transfer.

Table 17. NetView FTP/400 V3 Transfer Parameters


Automatic retry ATMRTRY 91

Compression COMPRESS 92

APPC conversation security password PASSWORD 92

Exit-routine input one PPXIN1 94

Exit-routine input two PPXIN2 94

Restart from interruption RESTART 91

Nickname of remote LU RMSERVER 91

Remote check RMTCHK 93

Location of report recipient RRNID 105

Recipient of report RRUID 105

Running mode of remote server SRVMODE 104

APPC conversation security user ID USRID 92

NetView FTP/400 V3 Sending File ParametersUse these parameters to tell NetView FTP/400 V3 about the sending file when thesending file is at a NetView FTP/400 V3 system.

Table 18. NetView FTP/400 V3 Sending File Parameters


Library SFILE 94

File SFILE 94

Type SFILTYPE 95

Member SMBR 95

NetView FTP/400 V3 Receiving File ParametersUse these parameters to tell NetView FTP/400 V3 about the receiving file when thereceiving file is at a NetView FTP/400 V3 system.

Table 19 (Page 1 of 2). NetView FTP/400 V3 Receiving Parameters


Public access authority AUT 99

Expiration date for member EXPDATE 99

File option FILOPT 96

Maximum members per file MAXMBRS 97

Chapter 6. Parameter Reference 79

Table 19 (Page 2 of 2). NetView FTP/400 V3 Receiving Parameters


Maximum number of records MAXREC 97

Member option MBROPT 96

Record length RCDLEN 99

Library RFILE 94

File RFILE 94

Type RFILTYPE 95

Member RMBR 95

Initial number of records SIZE 97

Increment number of records SIZE 97

Maximum increments SIZE 97

File text description TEXT 98

NetView FTP/400 V3 Sending Parameters when the Remote System IsNetView FTP Version 2 MVS

Use these parameters to tell NetView FTP/400 V3 about the sending file when thesending file is at a NetView FTP Version 2 MVS system.

Table 20. NetView FTP/400 V3 Sending Parameters when the Remote System is NetView FTP Version 2 MVS

Parameter Keyword Description on Page

Physical block size SBLKSIZE 110

Data set name or VSAM cluster name SFILEID 100

DD name SFNAME 103

Type SFTYPE 106

Cluster password SFTYPE 107

Logical record length SLRECL 110

Record format SRECFM 110

Security parameters SSECURP 107

Data set sequence number SSEQNO 119

Catalog name SUCATID 123

Device type SUNIT 117

Volume serial number SVOLSER 117


NetView FTP/400 V3 Receiving Parameters when the Remote System IsNetView FTP Version 2 MVS

Use these parameters to tell NetView FTP/400 V3 about the receiving file when thereceiving file is at a NetView FTP Version 2 MVS system.

Table 21 (Page 1 of 2). NetView FTP/400 V3 Receiving Parameters when the Remote System is NetView FTPVersion 2 MVS


Expiration date EXPDATE 119

Generic GENERIC 133

Average record multiplier RAVGREC 129

Average length RBLKLEN 116

Physical block size RBLKSIZE 110

Data class RDATACL 130

Data name (VSAM) RDATAID 123

Tape density RDEN 114

Directory blocks RDIRBLK 116

Data set name or VSAM cluster name RFILEID 100

DD name RFNAME 103

Type RFTYPE 106

Cluster password RFTYPE 107

Model DSCB RGDGMDI 114

Index name (VSAM) RINDEXID 123

Key length RKEYS 125

Key offset RKEYS 125

KSDS option RKSDS 121

Logical record length RLRECL 110

Like RLIKE 131

Management class RMGMTCL 131

Model name RMODELID 122

Model password RMODELID 122

Retention period RPERIOD 119

Record format RRECFM 110

Data organization RRECORG 124

Average record size RRECSIZE 125

Maximum record size RRECSIZE 125

Reference DD statement RREFDD 132

Security model RSECMOD 133

Security parameters RSECURP 107

Data set sequence number RSEQNO 119

Primary space quantity RSPCPRIM 116


Table 21 (Page 2 of 2). NetView FTP/400 V3 Receiving Parameters when the Remote System is NetView FTPVersion 2 MVS


Secondary space quantity RSPCSEC 116

Space units RSPCUNIT 115

Storage class RSTORCL 134

Disposition RTDISP 108

Catalog name RUCATID 123

Catalog password RUCATID 123

Device type RUNIT 117

Volume count RVOLCNT 118

Volume serial number RVOLSER 117

NetView FTP/400 V3 Sending Parameters when the Remote System IsNetView FTP VM

Use these parameters to tell NetView FTP/400 V3 about the sending file when thesending file is at a NetView FTP VM system.

Table 22. NetView FTP/400 V3 Sending Parameters when the Remote System is NetView FTP VM


VM access SACC 128


CMS file ID SCMSID 100

Type SFTYPE 106


Minidisk parameter SLINKP 128




File sequence number SSEQNO 119

File ID or VSAM cluster name SFILEID 100

SFS directory access SSFSP 128

Catalog name SUCATID 123



NetView FTP/400 V3 Receiving Parameters when the Remote System IsNetView FTP VM

Use these parameters to tell NetView FTP/400 V3 about the receiving file when thereceiving file is at a NetView FTP VM system.

Table 23. NetView FTP/400 V3 Receiving Parameters when the Remote System is NetView FTP VM


VM access RACC 128


CMS file ID RCMSID 100

Data name RDATAID 123


File ID or VSAM cluster name RFILEID 100

Type RFTYPE 106


Index name RINDEXID 123




Link parameters for a minidisk RLINKP 128









File sequence number RSEQNO 119

SFS directory access parameter RSFSP 128









NetView FTP/400 V3 Sending Parameters when the Remote System IsNetView FTP VSE

Use these parameters to tell NetView FTP/400 V3 about the sending file when thesending file is at a NetView FTP VSE system.

Table 24. NetView FTP/400 V3 Sending Parameters when the Remote System is NetView FTP VSE



File ID or VSAM cluster name SFILEID 100

File name SFNAME 100

Type SFTYPE 106





File sequence number SSEQNO 119

Catalog password SUCATID 123

Device type SUNIT 117


NetView FTP/400 V3 Receiving Parameters when the Remote System IsNetView FTP VSE

Use these parameters to tell NetView FTP/400 V3 about the receiving file when thereceiving file is at a NetView FTP VSE system.

Table 25 (Page 1 of 2). NetView FTP/400 V3 Receiving Parameters when the Remote System is NetView FTPVSE


Expiration date EXPDATE 119


Data name (VSAM) RDATAID 123


File ID or VSAM cluster name RFILEID 100

File name RFNAME 103

Type RFTYPE 106


Index name (VSAM) RINDEXID 123





Table 25 (Page 2 of 2). NetView FTP/400 V3 Receiving Parameters when the Remote System is NetView FTPVSE





Retention period RPERIOD 119






File sequence number RSEQNO 119







Device type RUNIT 117

Logical record size RVLRECL 124


Agent ParametersUse these parameters for starting the agent. You can start the agent using eitherthe administrator interactive interface or the CL interface.

Maximum Number of ServersThis parameter specifies the maximum number of servers that can be started inone NetView FTP/400 V3 system. The agent rejects any attempt to start a server ifthis limit has been reached.

CL Interface Only

MAXSRV(20 | 1 to 99)


Number of Servers to StartThis parameter specifies how many servers are started when the agent starts.Servers are identified by their suffixes (01 to 99). This parameter must not have avalue greater than the maximum number of servers.

CL Interface Only

ACTSRV(2 | 1 to 99)

Server PrefixThe server prefix specifies a prefix for a server ID. For example, a server prefix ofDVGSRV and a server suffix of 01 gives a server ID of DVGSRV01.

CL Interface Only

SRVPFX(DVGSRV | server-prefix)

server-prefixA string of up to eight characters. The default is DVGSRV.

Server ClassUse this parameter to specify a server class for your request.

Each class is represented by an integer from 0 to 9 or a letter from A to Z.

To find out which class is most appropriate for a request, contact your NetViewFTP/400 administrator.

CL Interface Only

SRVCLS(A to Z | 0 to 9)

RetryYou can specify the following parameters during START AGENT and STARTSERVER commands using the RTRY keyword:

� Number of transfer retries� Number of transfer restarts� Transfer retry interval.

A retry is a resumption of the transfer when the receiving server has not writtentransfer restart information. A restart is a resumption of the transfer when thereceiving system has written transfer restart information.


CL Interface Only

RTRY(max-retries max-restarts retry-interval)

max-retriesThe number of times a server attempts to retry a transfer. A number in therange 0 to 999, the default is 100.

max-restartsThe number of times a server attempts to restart a transfer. A number inthe range 0 to 999, the default is 100.

retry-intervalThe time in minutes between a transfer end and an automatic restart orretry. A number in the range 1 to 999, the default is 5.

Server ParametersUse the server parameters for starting and stopping a server. You can start andstop a server using either the administrator interactive interface or the CL interface.

Number of Servers to StartYou can specify how many additional servers you want to start. Servers areidentified by their suffix (01 to 99).

CL Interface Only

NBRSRV(1 to 99)

Server Stop ModeThis parameter is only valid for stopping a server. You can specify whether theserver stops immediately or whether it finishes processing the request beforestopping.

*C | *CNTRLDThe server stops when it has finished processing a request.

*I | *IMMEDThe server stops immediately, regardless of whether the request beingprocessed has finished.

CL Interface Only

ENDMODE(*C | *CNTRLD | *I | *IMMED)


Server SuffixThis parameter is only valid for stopping a server. You must specify the suffix ofthe server to stop. The server prefix and suffix combine to form the server ID.

CL Interface Only

SRVSFX(01 to 99)

Retry and Server ClassThe retry and server class parameters are described in the “Agent Parameters”section earlier in this chapter.

Request ParametersRequest parameters tell NetView FTP/400 V3 about when a file transfer is to takeplace and with which priority and server class.

Request NameThis parameter tells NetView FTP/400 V3 the name of a request to delete from therequest database, change in the request database, add to the request database, orto display. When creating, copying, or renaming a request, you must specify aunique request name.

CL Interface Only

REQNAME(name)

nameA string of up to 10 characters.

Note: For rules about coding OS/400 names see Appendix B, “NamingConventions” on page 151.

Hold RequestUse this parameter to put a request on hold, or release it for processing.

CL Interface Only

REQHLD(*YES | *NO)

*YESThe request’s status is changed to hold. The request is not processed untilyou release it.

*NOThe request’s status is changed to waiting or scheduled , and is processedwhen a server is available and, if specified, the scheduled time interval ismet.


Request OriginatorThis parameter, together with the request name, identifies a request. If you are anadministrator and you want to work with the requests of other users, you mustspecify the user ID of the request originator.

Note: This parameter is only valid for CHANGE commands.

CL Interface Only

RQORG(user-id | *CURRENT)

user-idA string of up to 10 characters. The default is the user ID of the user that islogged on.


Request PriorityUse this parameter to tell NetView FTP/400 V3 which priority to assign to yourrequest. Each priority is represented by an integer from 0 to 9. The lowest priorityis 9 and the highest is 0.

CL Interface Only

RQPTY(0 | 1 | 2 | ... |5| ... | 8 | 9)

New and Verify PasswordUse these parameters to specify and then verify a new password for savedrequests. You can specify these parameters only when you run theCHGAPPCPWD or CGHGSECPWD commands, for more information see “UsingChange APPC Password and Change Security Password” on page 76. If you arean administrator, you can change the password of all requests, otherwise, you canonly change the password of your own requests.

CL Interface Only

NEWPWD(password)

VRYPWD(password)

passwordA valid password up to 10 characters long.


Not-before and Not-after Date and TimeBy specifying a not-before-date, a not-before-time, a not-after-date, and anot-after-time, you can tell NetView FTP/400 V3 when it can process a request.NetView FTP/400 V3 does not process a request before its not-before time anddate, or after its not-after time and date. You must give the times in 24-hourformat. For example, you would represent 1:57 pm as 13:57.

If you specify a time but not a date, NetView FTP/400 V3 assumes you mean thedate to be the current date. If you do not specify a not-before date or time, therequest is eligible for processing any time before the not-after date and time.Similarly, if you do not specify a not-after date or time, the request is eligible forprocessing any time after the not-before date and time. A not-after date and timemust be later than the current time and the corresponding not-before date and time.Any date or time you specify must be complete.

Requests can run daily to a scheduled time without having to change the request’snot-before date as NetView FTP/400 V3 assumes the not-before date to be thecurrent date, if not otherwise specified.


CL Interface Only

SCHDL(‘not-before-time|0 not-before-date|0 not-after-time|0 not-after-date|0’)

not-before-timeA 4-digit number. The first two digits represent the hour (00 through23). The last two digits represent the minute (00 through 59).

not-before-dateThe date in the date format specified by the job. The date hascomponents for year, month, and day or for the julian date format:

yearAny two-digit number from 00 to 99.

monthAny two-digit number from 01 to 12.

dayAny two-digit number from 01 to the number of days in the monthyou specify.

julian dateA julian date is the year (2 digits) and the number of the day in theyear (a 3-digit number in the range 001 to 366).

not-after-timeA 4-digit number. The first two digits represent the hour (00 through23). The last two digits represent the minute (00 through 59).

not-after-dateThe date in the date format specified for your NetView FTP/400 V3.The date has components for year, month, and day or for the juliandate format:

yearAny 2-digit number from 00 to 99.

monthAny 2-digit number from 01 to 12.

dayAny 2-digit number from 01 to the number of days in the month youspecify.

julian dateA julian date is the year (2 digits) and the number of the day in theyear (a 3-digit number in the range 001 to 366).


Transfer ParametersUse these parameters to tell NetView FTP/400 V3 how to conduct a file transfer.

Nickname of Remote LUThis parameter specifies the nickname of the remote LU as defined in the LUdirectory.

CL Interface Only

RMSERVER(name)

nameA string of 1 to 10 characters.

Restart from InterruptionIf a file transfer is interrupted and the corresponding request is later released,NetView FTP can restart the file transfer from either the last record successfullywritten to the receiving file before the interruption or the beginning of the file.

Specify one of the following values for the Restart from Interruption parameter:

*YES NetView FTP restarts the file transfer from the last record successfullywritten to the receiving file.

*NO NetView FTP restarts the file transfer from the beginning of the file.

If you want to restart a file transfer manually from an interruption and did notspecify a receiving file, you must retrieve the file name created by the receivingsystem for the failed request. How to do this is described in “Restarting FailedFile-Transfer Requests” on page 47.

If you want transfers to restart automatically, set Restart from interruption to *YESand also set Automatic Retry to *YES.

CL Interface Only

RESTART(*YES | *NO)

Automatic RetryYou can specify in a request that if a file transfer fails, and it can be retried, it willautomatically retry.

If the value of the automatic retry parameter is:

*YES The request is automatically retried after the time interval specified with theRTRY parameter has expired. NetView FTP/400 V3 retries the request upto the maximum number of retries specified with the RTRY parameter. Therequest can be held to prevent further processing.


*NO The request is not automatically retried. However, you can still restart afailed file-transfer request manually. How to do this is described in“Restarting Failed File-Transfer Requests” on page 47.

CL Interface Only

ATMRTRY(*YES | *NO)

CompressionTo reduce the time needed to transfer a file, you can have the transfer program atthe sending system compress the file before sending it, and the transfer program atthe receiving system decompress the file after receiving it.

NetView FTP/400 uses adaptive compression. Adaptive compression works byreplacing character strings that are repeated in a file with references to a directoryof these character strings.

Note: Adaptive compression does not work well with random data or file transfersinvolving a small amount of data.

Possible values are:

*ADAPT The file is compressed using adaptive compression by the sender, anddecompressed by the receiver.

*NONE No compression is performed.

CL Interface Only

COMPRESS(*ADAPT | *NONE)

APPC Conversation SecurityAPPC conversation security is used for accessing the remote system, and forstarting a conversation with the remote system.

When you send a file to, or retrieve a file from, a remote OS/400 system, the userID you specify for the APPC conversation security is the owner of the file at theremote system. If the user ID is a member of an OS/400 group profile, the objectownership is changed to group. If the user ID and the password you specify arenot valid for the remote system, no conversation is established. If you specify auser ID, you must also specify a password.

The APPC conversation security parameter is required when the remote system isOS/400, and optional when the remote system is MVS, VM, or VSE.


CL Interface Only

USRID(userid)A string of up to 10 characters.

PASSWORD(password)A string of up to 10 characters.


Remote CheckUse this parameter to specify whether the contents of the request are sent to, andvalidated at the remote system.

Possible values are:

*YES The contents of the request are sent to, and validated at the remotesystem. No file transfer is performed. Not all error conditions are checked.For example, if for member name *ALL is specified, only the first memberis checked. You can read the result of the validation in the log file, whichyou can either display or print. All messages from the remote check are inEnglish. If the check is successful, that is, with no errors, the transferrequest is released immediately. If you have specified schedulingparameters and specified Remote check=YES, the request will be validatedat release time and will run at the scheduled time.

The following conditions are not checked if the remote system is NetViewFTP Version 2 MVS:

� If sufficient access authority is given (for example, if the securityinformation provided in the request satisfies the RACF at the remotesystem).

� If the disposition of the remote data set matches the dispositionspecified in the request.

� Whether the running mode of the remote server matches the runningmode specified in the request.

*NO The contents of the request are checked at the remote system and the filetransfer is performed.

CL Interface Only

RMTCHK(*YES | *NO)


Exit-Routine InputIf told by your system programmer, use these parameters to specify informationrequired by the user-exit routines at a NetView FTP V2 MVS, VM, and VSEsystem. You can also specify this information in the Command Language Interfacewhen the remote NetView FTP is NetView FTP/400 V3.

CL Interface Only

PPXIN1(information)information is a character string of up to 62 characters.

PPXIN2(information)information is a character string of up to 1200 characters.

Note: NetView FTP/400 V3 can receive up to 1262 bytes of user-exit routine inputfrom remote MVS, VM, VSE, or OS/400 systems. The information received isstored in an OS/400 data queue. Your organization can write an application tomonitor this queue and perform post-transfer processing. The data queue layoutand a sample program are described in Appendix I, “Working with thePost-Transfer Data Queue” on page 171.

NetView FTP/400 V3 Sending and Receiving File ParametersUse these parameters to tell NetView FTP/400 V3 about the sending or receivingfiles when the sending or receiving files are at a NetView FTP/400 V3 system.

If no receiving parameters are specified, default values are taken.

If the sending system is NetView FTP/400 V3, the default values for the receivingfile parameters are the values of the sending file.

The default values for the receiving file parameters, if the sending system isNetView FTP Version 2 MVS, NetView FTP VM, or NetView FTP VSE, aredescribed in Appendix C, “NetView FTP/400 V3 Receiving File Defaults” onpage 153.

Library Name and File NameUse this parameter to specify the name of the file to send or retrieve. The libraryname is used to locate the file to send or retrieve. You must specify a library nameand file name for the sending file. If you do not specify a library name, a file name,and a file type for the receiving file, a default value is assigned by the receivingsystem. How the receiving system creates a name is described in Appendix A,“How NetView FTP Creates Names for Receiving Files” on page 145.


CL Interface Only

xFILE( library-name/file-name)Replace the x in this keyword with either S for sending, or R for receiving.

library-nameA string of up to 10 characters.

file-nameA string of up to 10 characters.


Member NameSpecifies the names of the file members being sent or received. The membername can be up to 10 characters. For rules about coding OS/400 names seeAppendix B, “Naming Conventions” on page 151.

Note: Member name is not valid for save files (*SAVF).

CL Interface Only

SMBR(*FIRST | *ALL | member-name)

RMBR(*FROMMBR | member-name)

*FIRSTOnly the first member of the specified file is transmitted.

*ALLAll members of the specified file are transmitted.

member-nameOnly the specified member is transmitted.

*FROMMBRThe receiving member takes the same name as the sending member.

Note: *FROMMBR is only valid if the sending file is an OS/400 source file,OS/400 data file, or an MVS PO data set.

File Type for OS/400 FilesThe file type specifies the type of file to send or retrieve. Possible values are:

*DTAF Physical data file

*SAVF Save file

*SRCF Physical source file.

CL Interface Only

xFILTYPE(*DTAF | *SAVF | *SRCF)Replace the x in this keyword with either S for sending, or R for receiving.


File OptionThis parameter specifies how the receiving system processes the receiving file.File options are:

*NEW A file is created in the OS/400 system. If the file already exists, this isregarded as an error and the file-transfer request is rejected. If thelibrary does not exist, it is created. This is the default.

*REG If the file exists, it is overwritten, otherwise, it is created. If the librarydoes not exist, it is created.

*OLD The specified file must exist. If the file does not exist, this is regardedas an error and the file-transfer request is rejected.

To be able to specify additional parameters for new receiving files interactiveinterface users must specify *NEW or *REG.

If an interrupted file transfer restarts after the receiving file has been allocated,NetView FTP/400 V3 changes this parameter to *REG before processing it.

CL Interface Only

FILOPT(*NEW | *REG | *OLD)

Member OptionSpecifies whether the members replace existing members or whether they areadded to the file. Member options are:

*ADD A new member is added.

*REPLACE An existing member is replaced. If the member does not exist, it isadded to the file.

*APPEND Records are appended to an existing member. If the member doesnot exist, it is added to the file.

Note: Member option is not valid for *SAVF files. Records in receiving save filesare replaced.

If you restart an interrupted file transfer after the receiving file was allocated,NetView FTP/400 V3 changes this parameter to *REPLACE before processing therequest.

CL Interface Only

MBROPT(*ADD | *REPLACE | *APPEND)


Maximum Number of Members per FileSpecifies the maximum number of members that the physical file being created canhave at any one time.

Note: You are not allowed to specify this parameter if the file type is *SAVF.

CL Interface Only

MAXMBRS(*NOMAX | maximum-members)

*NOMAXThe system maximum is used.

maximum-membersA number from 1 to 32767.

Maximum Number of RecordsUse this parameter to specify the maximum number of records that a save file(*SAVF) can have.

You can use the maximum number of records parameter to limit the size of thesave file. For example, if you want to ensure that the save file does not exceedapproximately 20 megabytes, specify 40000 for the maximum number of records(40000 multiplied by the save file record length (528) is approximately 20megabytes).

Note: This parameter is only valid for *SAVF files.

CL Interface Only

MAXREC(maximum-records | *NOMAX)

maximum-recordsA number from 1 to 3 997 574.

*NOMAXThe system maximum is used.

SizeUse this parameter to specify:

� The initial number of records. That is, the number of records that can beinserted into each member of a file before any increment occurs. *NOMAXspecifies that the system maximum is used.

� The increment number of records. That is, the number of records that can beinserted into a member for each increment.

� The maximum number of increments. That is, the maximum number of timesan increment can be added to a member.


The following conditions apply when specifying this parameter:

� If *NOMAX is specified for the initial number of records, then the systemmaximum is also used for increment number of records and maximum numberof increments.

� If you specify 0 for either the increment number of records or the maximumnumber of increments, no increments are added to the member.

Note: Do not specify this parameter for *SAVF files.

CL Interface Only

SIZE(initial-number-of-records increment-number-of-recordsmaximum-number-of-increments)

initial-number-of-recordsA number from 1 to 16 777 215.

increment-number-of-recordsA number from 0 to 32767.

maximum-number-of-incrementsA number from 0 to 32767.

SIZE(*NOMAX)The system maximum is used.

File Text DescriptionThe file text description briefly describes the file being received. If the filedescription is not specified, the file description of the sending file is taken.

CL Interface Only

TEXT('description')A string of up to 50 characters.


Public Access AuthorityAllows you to specify, for users other than the owner, the access authority for thenew received file.

CL Interface Only

AUT(*CHANGE | *ALL | *USE | *EXCLUDE)

*CHANGEThis lets users perform all operations on the file except those limited to theowner or controlled by the object-existence authority andobject-management authority. Change authority provides object-operationalauthority and all-data authority.

*ALLThis lets users perform all operations on the file except those limited to theowner or controlled by authorization-list-management authority. Users cancontrol the file’s existence, specify the security for the file, change the fileand perform basic functions on the file. Users cannot transfer ownership ofthe file.

*USEThis allows users to perform basic operations on the file, such as readingthe file. Users are prevented from changing the file. Use authority providesobject-operational authority and read authority.

*EXCLUDEThis prevents a user from accessing the file.

Record LengthSpecifies the record length, in bytes, of the records in a file.

Note: Record length is not valid for save files (*SAVF).

CL Interface Only

RCDLEN(record-length)A number from 1 to 32766 for DTAF files, or from 13 to 32766 for SRCFfiles.

Expiration Date for MemberThe expiration date is the date after which the source or data file member cannotbe used. Any attempt to open a member whose expiration date has passed resultsin an error. The date must be specified in the format defined by the current job andshown on the panel. You can specify any year from the current year to the year2039.

If you specify *NONE, no expiration date is given to the member. If you do notspecify an expiration date for a member, the expiration date of the sending memberis used. If you specify an expiration date for a multiple member transfer, the sameexpiration date is used for all members.


CL Interface Only

EXPDATE(*NONE | expiration-date)

*NONENo expiration date.

expiration-dateA date specified in the format defined by the current job and shown on thepanel. The date has components for year, month, and day or for the juliandate format:

year Any 2-digit number from 00 to 99.

month Any 2-digit number from 01 to 12.

day Any 2-digit number from 01 to the number of days in themonth you specify.

julian date A julian date is the year (2 digits) and the number of the dayin the year (a 3-digit number in the range 001 to 366).

Parameters for Files at NetView FTP Version 2 MVS, NetView FTP VM,and NetView FTP VSE Systems

Use these parameters to tell NetView FTP/400 V3 about the sending or receivingfiles when the sending or receiving files are at a NetView FTP Version 2 MVS,NetView FTP VM, or NetView FTP VSE system.

Data Set Name (MVS), File ID (VSE, VM), and CMS File Name (VM)The data set name1 identifies the sending or receiving file. An example of a file IDis ACCOUNT.LOG.DATA .

When you create a request the following conditions apply:

� You can allocate a file either by specifying the data set name or, if the MVSserver or VSE partition can use it, the DD name.2

� If you specify a data set name, the server uses dynamic allocation. If youspecify a DD name, the server uses job allocation. However, if you specifyboth data set name and DD name, the server uses job allocation but carriesout the file transfer only if the name specified with the data set name parameteris the same as the name specified in the DD statement (MVS), or the DLBL orTLBL statement (VSE).

1 VSE uses the term file ID in place of data set name.

2 VSE uses the term file name in place of DD name.


When specifying a value for data set name the following general conditions apply:

Sending fileYou must specify either a data set name or a DD name for the sending file.

Receiving FileSpecifying a data set name for the receiving file is optional. If you do notspecify a data set name, the transfer program at the receiving system creates adata set name for you. How this name is derived is explained in Appendix A,“How NetView FTP Creates Names for Receiving Files” on page 145.

If you manually restart an interrupted file transfer, you must specify a data setname for the receiving file. If the data set name was created by NetView FTP,use the interactive interface to change the Receiving file parameters panel andthen press F20 to display the data set name that NetView FTP created.

Also consider the following:

Partitioned Data Sets (MVS only)NetView FTP/400 V3 can only transfer single members of a partitioned data setwithout its accompanying directory information. To transfer a single memberspecify the name of the PDS as the value for the data set name parameter withthe name of the member in parentheses after the data set name, for example:'partit.ds.name(memname)'.

The first character of the member name must be alphabetic. The rest of thename (up to seven characters) can be A to Z, 0 to 9, @, $, or #.

Generation data groups (MVS only)If a data set is a generation data group, you can specify the name with either(1) an absolute generation and version number or (2) a relative generationnumber. Also, you must take care that the GDG of which the file is a memberis not updated in the time after the request is submitted and before the filetransfer is finished.

To transfer an entire GDG (GDG ALL request) you must specify a value eitherfor the data set name parameter or the DD name parameter for the sendingfile.

Data Sets on a TapeIf you transfer a file from a tape, note that the data set name that you specifydoes not necessarily match the one stored on the tapes header-1 label. A tapeheader contains only the rightmost 17 characters of the data set name if thename is more than 17 characters long. Therefore, the operating systemverifies a maximum of 17 characters.


CL Interface Only

xFILEID( file-id)Replace the x in this keyword with either S for sending, or R for receiving.

file-idA character string of up to eight characters. The following characters areallowed:

MVS The first character of each qualifier must be alphabetic capital (Ato Z) or national (@, $, #), the next seven characters must bealphabetic capitals, national characters, numeric (0 to 9), hyphen(-), or a character X'C0'. Each qualifier is separated by aperiod (.). The subqualifier which immediately follows the lastqualifier is enclosed in a left parenthesis (() and a rightparenthesis ()) and contains either a member name of apartitioned data set or the relative generation of a generationdata group. If the subqualifier indicates a member of apartitioned data set, the first character of the member name mustbe alphabetic capital, the remaining characters (up to seven)must be alphabetic capitals, national characters, numeric (0 to9). If the subqualifier indicates a relative generation of ageneration data group, the first character must be numeric oreither a plus sign (+) or a hyphen (-), the remaining characters(up to four) must be numeric.

VM With the exception of CMS files, the same characters areallowed as for MVS. Each qualifier must be separated by aperiod.

VSE The first byte of each qualifier must be an alphabetic capital or anational character, the remaining characters (up to 7) must bealphabetic capitals, national characters, numeric (0 to 9), or ahyphen (-). Each qualifier is separated by a period (.).

Transferring a CMS file is a special case:

CMS file (VM only)The file ID of a CMS file consists of filename, filetype, and filemode. Specifyingthe filemode is optional. The filemode consists of a filemode letter and afilemode number, for example, A1.


CL Interface Only

xCMSID(fn ft fm)

fn A CMS file name from 1 to 8 characters long.

ft A CMS file type from 1 to 8 characters long.

fm A CMS file mode 2 characters long consisting of a file mode letter and a filemode number.

For CMS files the following rules apply:

� The file name and file type can each be from one to eight characters.

� The valid characters are alphabetic (A-Z, a-z), national characters, numeric(0 to 9), plus sign (+), hyphen(-), colon (:), or underscore (_).

DD Name (MVS) or File Name (VSE)Specify the DD name parameter only for a data set that has already been allocatedin a server startup job (MVS) or a NetView FTP partition startup job (VSE).

The DD name3 is one of the following:

MVS The name of the DD statement, in a NetView FTP MVS server startupjob, that contains the name of the file to be transferred.

VSE The file name specified in the DLBL or TLBL statement in the NetViewFTP partition startup job that contains the file ID of the file to betransferred. Only the first seven characters are valid.

When you create a request the following conditions apply:

� You can allocate a file either by specifying the data set name or, if the MVSserver or VSE partition can use it, the DD name.4

� If you specify a DD name, the server uses job allocation. If you specify a dataset name, the server uses dynamic allocation. However, if you specify bothdata set name and DD name, the server uses job allocation but carries out thefile transfer only if the name specified with the data set name parameter is thesame as the name specified in the DD statement (MVS), or the DLBL or TLBLstatement (VSE).

� When you use job allocation, you must ensure that the server allocating the fileis also the server that is chosen for the file transfer. To do this specify theLU-directory entry that refers to the remote location name of the server.

3 VSE uses the term file name in place of DD name.

4 VSE uses the term file ID in place of data set name.


When specifying a value for the DD name parameter, the following generalconditions apply:

Sending fileYou must specify a value either for the data set name parameter or the DDname parameter for the sending file. If you use the DD name parameter, youmust specify a data set name in the startup job for the MVS server or the VSEpartition, even for an unlabeled tape.

Receiving fileSpecifying a DD name or a data set name for the receiving file is optional. Ifyou do not specify a DD name or a data set name, NetView FTP at thereceiving system uses dynamic allocation.

Partitioned Data Sets (MVS only)NetView FTP/400 V3 can only transfer single members of a partitioned data setwithout its accompanying directory information. To transfer a single memberspecify the name of the PDS as the value for the DD name parameter with thename of the member in parentheses after the data set name, for example:'partit.ds.name(memname)'

CL Interface Only

xFNAME( file-name)Replace the x in this keyword with either S for sending, or R for receiving.

file-nameFor MVS, a character string of up to eight characters.

For VSE, a character string of up to seven characters.

Running Mode of Remote Server (MVS, VSE)This parameter tells NetView FTP the running mode of the remote server. If therunning mode of the remote server does not match the value specified for thisparameter, the transfer is canceled. If the running mode of a remote server is:

*CONT The remote server continues running after transferring a file.

*SINGLE The remote server stops running after transferring a file.

CL Interface Only

SRVMODE(*CONT | *C | *SINGLE | *S)


Recipient of Report (MVS, VM, VSE)After every file transfer, whether successful or not, the server at the respondingsystem writes a report that explains the outcome of the transfer. The report alsocontains information about the transfer start stop times, and the parametersassigned or defaulted. Use this parameter to specify the recipient of thefile-transfer report and the file-transfer completion message issued by theresponding server.

The report recipient need not be at the same location as the server that writes andsends the report. You specify the report recipient with two parameter values:

user ID Is a character string of up to eight characters containing the user ID ofthe user to whom a server sends its file-transfer report and completionmessage.

Note: If the server at the responding system runs under MVS, a filetransfer completion message is only sent to user IDs that are on thesame JES node that the server is on.

location IDIs a character string of up to eight characters containing:

� For MVS, the JES node ID� For VM, the RSCS node ID� For VSE, the VSE/POWER node ID.

This is where the file-transfer report and completion message are sent.For a list of such node IDs, contact your system programmer.

If you specify a location ID, you must also specify a user ID.

If the location ID is not specified:

� For a responding MVS system, no file-transfer report is sent.

� For a responding VM or VSE system, the file-transfer report and the completionmessage are sent to the user ID at the location the server runs on.

If a report recipient resides:

� At an MVS location, the report is spooled to the recipient’s JES queue, fromwhich the recipient receives it with the TSO RECEIVE command. If therecipient is at the same JES node as the server that was involved in the filetransfer, the recipient is also sent a file-transfer completion message.

� At a VM location, the report is spooled to the recipient’s reader, from which theuser receives it with the CMS RECEIVE command. The recipient is also sent afile-transfer completion message.

� At a VSE location, the report is spooled to the VSE/POWER LST queue at thatsystem. If VSE is not running under VM, the file-transfer completion messageis routed to the recipient’s ICCF user ID. If VSE is running under VM, thesystem programmer specifies whether the file-transfer completion message isrouted to the recipient’s ICCF or CMS user ID via POWER/PNET. If theserver’s LST class is served by the VSE/POWER VM writer task, a copy of thereport is also sent to the recipient's VM reader.


CL Interface Only

RRUID(user-id)RRNID(location-id)user-id

A character string of up to eight characters. It is the user ID of the user towhom NetView FTP Version 2 MVS, NetView FTP VM, or NetView FTPVSE sends its report.

location-idA character string of up to eight characters. It is the JES node name of theuser to whom NetView FTP Version 2 MVS sends its report.

Type (MVS, VM, VSE)Use this parameter to specify the type of the sending and receiving files. You mustspecify the type of the sending file.

The following are valid types:

*VSAM The file is one of the following:

� A VSAM ESDS or KSDS at an MVS, VSE, or VM system� A SAM ESDS (VSAM-managed sequential) file at a VSE system.

*PS The file is a physical sequential file stored on a DASD. This value isvalid only for files located at MVS and VM systems.

*PO The data set is partitioned organized, that is, it is a PDS. This value isvalid only for files at an MVS system.

Note: Only one member can be transferred from or to a PDS. Thename of the member must be specified with the data set name.

*LAB The file is a physical sequential file stored on a labeled tape at a VSE,VM, or MVS system.

*UNLAB The file is a physical sequential file stored on an unlabeled tape at aVSE, VM, or MVS system.

If you do not specify a type for a receiving file at a remote system, the followingdefaults are used:

MVS *PS

VM *PS

VSE *VSAM


CL Interface Only

xFTYPE(*VSAM | *VSAM ( cluster-password) | *PS | *LAB | *UNLAB | *PO)Replace the x in this keyword with either S for sending, or R for receiving.

cluster-passwordUse the cluster password to specify one of the following:

� The password to use for gaining access to an existing VSAM cluster. Itmust be the same as the password specified when the VSAM clusterwas defined. You can only specify cluster protection if the catalog thatholds the cluster definition is also protected.

� The password to assign to a new VSAM cluster.

A cluster password is a character string of up to eight characters.

Cluster Password (MVS, VM, VSE)Use this parameter to specify one of the following:

� The password to use for gaining access to an existing VSAM cluster. It mustbe the same as the password specified when the VSAM cluster was defined.You can only specify cluster protection if the catalog that holds the clusterdefinition is also protected.

� The password to assign to a new VSAM cluster.

A cluster password can be up to eight characters.

Note: This parameter corresponds to the MPASSWORD parameter of the AMSDEFINE command.

CL Interface Only

In a CL command you specify the cluster password as a value of the Typeparameter. See “Type (MVS, VM, VSE)” on page 106 for more information.

Security Parameters (MVS, VM, VSE)The following are the security parameters:

� User ID � Password� Group ID (MVS and VM only).

Use these parameters to give a transfer program one of the following:

� Information it is to pass to a security program such as Access Control (VSE) orRACF (MVS or VM) to gain access to a file.

� Information it is to pass to pre-queuing, pre-transfer or post-transfer user-exitroutines.

If a security program is not active, the transfer program does not need any valuesto gain access to the file.


If you specify a value for the Password parameter, you must also specify a valuefor the User ID parameter. If you specify a value for the Group ID parameter, youmust also specify values for both the User ID and Password parameters.

User ID Use this parameter to specify a user ID that is authorized to accessthe sending or receiving file.

Password Use this parameter to specify the password that corresponds to theUser ID parameter.

Group ID Use this parameter to specify the group ID that corresponds to theUser ID parameter. This parameter is ignored by Access Control.

Whether you need to specify security parameters depends on how the servers, toand from which you transfer files, have been initialized. Ask the NetView FTPadministrator at the remote system whether you need to specify securityparameters.

CL Interface Only

xSECURP(user-id) | (user-id (password)) | (user-id (password) group-id)Replace the x in this keyword with either S for sending, or R for receiving.

user-idA character string of up to eight characters.

passwordA character string of up to eight characters, none of which can be blank(hex 40) or zero (hex 00).

group-idA character string of up to eight characters.

Disposition (MVS, VM, VSE)Use this parameter to tell a transfer program under what circumstances it is toallocate the receiving file.

*NEW The receiving transfer program allocates the receiving file only if it doesnot already exist. For a file at an MVS system, specifying this value isequivalent to specifying the disposition NEW,KEEP,KEEP for thereceiving file. If the receiving file is of the type VSAM, then thedisposition is ignored and the VSAM cluster is newly defined.

*CTG Only use this value for files to be stored at MVS locations. Thereceiving transfer program allocates the receiving file and makes acatalog entry only if the receiving file does not already exist. For a fileat an MVS system, specifying this value is equivalent to specifying thedisposition NEW,CATLG,CATLG for the receiving file.

*OLD The receiving transfer program allocates the receiving file only if italready exists. For a file at an MVS location, specifying this value isequivalent to specifying the disposition OLD,KEEP,KEEP for thereceiving file. If the receiving file is of the type VSAM, then thedisposition is ignored and the VSAM cluster is allocated as shared.


*MOD Only use this value for PDSs stored at MVS locations. The receivingtransfer program allocates the receiving file only if it already exists.Specifying this value is equivalent to specifying the dispositionMOD,KEEP,KEEP for the receiving file.

If a member with the same name already exists at the receiving location,the operating system at the receiving location rejects the directoryupdate after the transfer has finished, therefore, no data is transferred.

*SHR This value has the same effect as the value *OLD, except it lets thereceiving file be allocated by other users at the same time that it isallocated by the receiving server.

*REG Only use this value for CMS files. It tells NetView FTP VM to allocatethe file regardless of whether a file with the same name already exists.

The default value for this parameter depends on the type of the receiving file, thereceiving operating system, and the receiving transfer program.

Table 26. Dependencies of the Default Value for the Disposition Parameter for the Receiving File

Transfer Program Type Default Allowed Values

NetView FTP VSE VSAMLABUNLAB

*NEW*NEW*NEW

*NEW,*OLD*NEW*NEW

NetView FTP VM VSAMPSLABUNLAB

*NEW*NEW*NEW*NEW

*NEW,*OLD*NEW,*OLD,*REG*NEW,*OLD*NEW,*OLD

NetView FTP V2 MVS VSAMPSLABUNLABPO

*NEW*CTG*CTG*NEW*CTG

*NEW,*OLD,*SHR*NEW,*CTG,*OLD,*SHR*NEW,*CTG,*OLD,*SHR*NEW,*CTG,*OLD,*SHR*NEW,*CTG,*OLD,*MOD,*SHR

If your request manually restarts a file transfer that was interrupted after thereceiving file was allocated, you must change the value of this parameter to OLDbefore submitting the request.

CL Interface Only

RTDISP(*NEW | *CTG | *OLD | *MOD | *SHR | *REG)

DCB Parameters (MVS, VM, VSE)The following parameters make up a group called data control block parameters, orDCB parameters for short:

� Record Format� Logical Record Length� Physical Block Size� Model Data Set Control Block (DSCB)

� Tape Density.


Record Format, Logical Record Length, and Physical Block SizeThese parameters are valid for the sending file only when one of the following istrue:

� The file is stored on labeled or unlabeled tape at a VM or VSE system.

� The file is stored as a SAM ESDS and disposition is NEW at a VSE system.

� The file is to be dynamically allocated and is stored on unlabeled tape at anMVS system.

They are valid for the receiving file only when one of the following is true:

� The file is stored on labeled or unlabeled tape at a VSE system.

� The file is to be dynamically allocated and is a non-VSAM file stored on anMVS or VM system.

These conditions are illustrated in Figure 43.

Figure 43. Types of Data Sets for Which Record Format, Logical Record Length, and Physical Block Size ParametersApply

If you do not specify values for any of these parameters for the sending orreceiving files, the transfer program uses default values that correspond to thecharacteristics of the sending file. If for any reason these are not available, forexample, if the sending file is stored on unlabeled tape (or on an unlabeled tape ata VSE system), the transfer program uses the following defaults for both files:

� Record Format is undefined� Physical Block Size is 32760 (MVS) or 32767 (VSE).

Record Format: Use this parameter to specify how the records of a file areformatted. If you specify a value for this parameter, you must also specify thecorresponding file’s logical record length or physical block size, or both. Thesedependencies are shown in Table 27 on page 112. You can specify the followingvalues:

Value Description

*F The records have a fixed length and are not blocked.

*FB The records have a fixed length and are blocked.

*V The records have a variable length and are not blocked.

*VB The records have a variable length and are blocked.

*VS The records have a variable length, are not blocked, and can spanseveral tracks (MVS only).

*VBS The records have a variable length, are blocked, and can span severaltracks (MVS only).

*U The records have an undefined length.


CL Interface Only

xRECFM(*F | *FB | *V | *VB | *VS | *VBS | *U)Replace the x in this keyword with either S for sending, or R for receiving.

Logical Record Length and Physical Block Size: The logical record length isthe length in bytes of the fixed-length records, or the maximum length in bytes ofthe variable-length records of the sending or receiving file.

The physical block size is the length, in bytes, of the physical data blocks of a filethat contains fixed-length logical records, or the maximum length a physical datablock of a file that contains variable-length logical records.

You can specify a logical record length or a physical block size only if you specify acorresponding record format. The specification of a physical block size for a VMCMS file is ignored.

Only record formats F and V are valid for CMS files. Simulated OS files are notsupported.

If you specify a record format of undefined length, a physical data block is a logicalrecord of the same size.

The values you can specify for these parameters depend on the Record Formatparameter and the operating system at the file’s location. These dependencies areshown in Table 27.

Note: If a non-VSAM file has a variable-length record format, the logical recordsconsist of a 4-byte length record descriptor word (RDW) that precedes theuser data. The length field in this RDW is the sum of the user data lengthplus 4. This also applies to VM CMS files.

If a physical block size is also specified, the physical data block consists ofa 4-byte length block descriptor word (BDW) that precedes the logicalrecords. The length field in this BDW is the sum of the lengths of all logicalrecords plus 4. For more detailed information refer to the appropriatemanual for the operating system.

Logical records of VSAM files are of variable length, however, without alength field.


Table 27. Dependencies between Record Format and Other DCB Parameters for MVS and VM

RecordFormat

Logical Record Length and Physical Block Size OperatingSystem

Values Allowed forLogical RecordLength (LRECL) andPhysical Block Size(BLKSIZE)

F You must specify a logical record length. NetViewFTP ignores any physical block size you specify.

MVS or VM LRECL: 1 to 32 760Tape Input: 12 to32 760Tape Output: 18 to32 760

FB You must specify both a logical record length and aphysical block size. The physical block size must be amultiple of the logical record length.

MVS or VM LRECL: 1 to 32 760BLKSIZE: 1 to 32 760Tape Input: 12 to32 760Tape Output: 18 to32 760

V You must specify a logical record length, a physicalblock size, or both. If you specify both, the physicalblock size must be at least 4 bytes larger than thelogical record length. If you specify only the blocksize, the logical record length is set so that thephysical block size is 4 bytes larger than the logicalrecord length.

MVS or VM LRECL:5 to 32 760 (if noblock size specified)5 to 32 756 (if blocksize specified)BLKSIZE: 9 to 32 760Tape Input: 12 to32 760Tape Output: 18 to32 760

VB You must specify a logical record length, a physicalblock size, or both. If you specify both, the physicalblock size must be at least 4 bytes larger than thelogical record length. If you specify only the blocksize, the logical record length is set so that thephysical block size is 4 bytes larger than the logicalrecord length.

MVS or VM LRECL: 5 to 32 756BLKSIZE: 9 to 32 760Tape Input: 12 to32 760Tape Output: 18 to32 760

VS orVBS

You must specify both a logical record length and aphysical block size. The logical record length can belarger than the physical block size and can exceed themaximum track size of a specific storage device.

MVS LRECL: 5 to 32 756BLKSIZE: 9 to 32 760Tape Input: 12 to32 760Tape Output: 18 to32 760

VM Record format VS orVBS not supported

U You must specify a physical block size. NetView FTPignores any logical record length you specify.

MVS or VM BLKSIZE: 1 to 32 760Tape Input: 12 to32 760Tape Output: 18 to32 760


Table 28. Dependencies between Record Format and Other DCB Parameters for VSE

RecordFormat

Logical Record Length and Physical Block Size Values Allowed for LogicalRecord Length (LRECL) andPhysical Block Size (BLKSIZE)

F You must specify a logical record length. NetView FTP ignoresany physical block size you specify.

LRECL: 1 to 32 767Tape Input: 12 to 32 767Tape Output: 18 to 32 767

FB You must specify both a logical record length and a physicalblock size. The physical block size must be an integer multiple ofthe logical record length.For SAM ESDS you must specify a logical record size (RLRECS)and a record size (RRECSIZE) that is an integer multiple of it.

LRECL: 1 to 32 767BLKSIZE:Tape Input: 12 to 32 767Tape Output: 18 to 32 767

V You must specify a logical record length, a physical block size, orboth. If you specify both, the physical block size must be at least4 bytes larger than the logical record length. If you specify onlythe block size, the logical record length is set so that the physicalblock size is 4 bytes larger than the logical record length.

LRECL:5 to 32 767 (if no block sizespecified)5 to 32 763 (if block sizespecified)BLKSIZE:Tape Input: 12 to 32 767Tape Output: 18 to 32 767

VB You must specify a logical record length, a physical block size, orboth. If you specify both, the physical block size must be at least4 bytes larger than the logical record length. If you specify onlythe block size, the logical record length is set so that the physicalblock size is 4 bytes larger than the logical record length.

LRECL: 5 to 32 763BLKSIZE: 9 to 32 767Tape Input: 12 to 32 767Tape Output: 18 to 32 767

U You must specify a physical block size. NetView FTP ignoresany logical record length you specify.

BLKSIZE:Tape Input: 12 to 32 767Tape Output: 18 to 32 767

For a successful file transfer:

� The length of each record of the sending file must equal that of each record ofthe receiving file when the record format of the receiving file is F or FB.

� The logical record length of the sending file must be equal to or less than thatof the receiving file when the record format of the receiving file is anythingother than F or FB.

For more information about the Record Format parameter, see “Record Format” onpage 110.

CL Interface Only

xLRECL( lrecl)xBLKSIZE( blksize)

Replace the x in these keywords with either S for sending, or R forreceiving.

lreclThe length of the fixed-length records, or the maximum length of thevariable-length records of the sending or receiving file.

blksizeThe size of the blocks of the sending or receiving file.


Model DSCB (MVS)If the receiving file is a generation data set at an MVS system, use this parameterto specify the name of a DSCB at the receiving system that is used as a model forthe receiving file. If the receiving file is not a generation data set, do not specify avalue for this parameter.

The default value for this parameter is the DSCB, with the same name as thereceiving file already existing at the receiving location. If you do not specify a valuefor this parameter and if there is no such DSCB, an allocation error results and thereceiving transfer program does not carry out the file transfer. When allocating thereceiving file, the receiving transfer program uses the DCB parameters specified forthe model DSCB, except for the following, which the receiving transfer programsupplies itself:

� Data Set Organization (DSORG)� Record Format (RECFM)� Logical Record Length (LRECL)� Physical Block Size (BLKSIZE)� Tape Density (RDEN).

CL Interface Only

RGDGMDI(DSCB-model-name)

model-nameA character string of up to 44 characters.

Tape DensityUse this parameter to specify the density to write data to a tape at the receivingsystem. The tape densities and their corresponding parameter values are asfollows:

Value Tape Density0 200 bpi1 556 bpi2 800 bpi3 1600 bpi4 6250 bpiC5 38912 bpi (VM and VSE only)

If you do not specify a device type, the receiving program will use a default devicetype and a default tape density; it will ignore any tape density you specify.

The default tape density is:

� A hardware default at an MVS system� A VSE system default at a VSE system� 6250 bpi at a VM system.

5 If a 3480 tape subsystem is specified as a device type, you can activate its improved data recording technique (IDRC) with C (forcompaction). Specifying any other value, or nothing, results in no compaction.


If you specify a tape density and a device type, both must be compatible or the filetransfer will not be carried out.

CL Interface Only

RDEN(0 | 1 | 2 | 3 | 4 | C)

Space Parameters (MVS, VSE, VM)The following parameters make up a group called space parameters:

� Space Units� Primary Space Quantity� Secondary Space Quantity

� Average Length � Directory Blocks.

You can specify values for space parameters only if all of the following are true:

� The receiving file is a VSAM, PS, or PO file located at an MVS system, or aVSAM file at a VSE or VM system.

� The transfer program at the receiving system is NetView FTP.� The receiving file is to be allocated on DASD.� The receiving file is dynamically allocated.� The receiving file does not already exist.

If you do not specify a value for any of these parameters, the transfer programsuse defaults.

Space UnitsUse this parameter to tell the receiving transfer program the units of the primaryand secondary space quantities. The space units are:

*CYL For cylinders. Requests space allocation in cylinders of the DASDvolume. Do not specify an average length parameter. For VM andVSE, space in cylinders cannot be requested if the DASD type is anFBA device.

*TRK For tracks. Requests space allocation in tracks of the DASD volume.Do not specify an average length parameter. For VM and VSE, spacein tracks cannot be requested if the DASD type is an FBA device.

*BLK For blocks. Request space allocation in physical blocks. For MVS, thisspecification is only valid for non-VSAM data sets and also requires thatyou specify an average length parameter. For VM and VSE, thisspecification is only valid for VSAM files. Blocks can be specified forFBA-type devices only. Every block has a fixed size of 512 bytes.

*REC For records. Requests that the space allocation is calculated by thesystem using the logical record length as a base. You can specify thisvalue for VSAM files. You can specify this value also for any DASDdata set on MVS if SMS is active if you also specify a value for theaverage length parameter. It also requires that you specify the averagerecord multiplier parameter.


When you specify a value for this parameter, you must also specify a value for thePrimary Space Quantity parameter, which is described in “Primary and SecondarySpace Quantity.”

CL Interface Only

RSPCUNIT(*CYL | *TRK | *BLK | *REC)

Primary and Secondary Space QuantityUse these parameters to tell the receiving transfer program the amount of primaryand secondary space, in the units you specified for the Space Units parameter, toallocate for the receiving file. When you specify a primary space quantity, you mustalso specify a value for the Space Units parameter. When you specify a secondaryspace quantity, you must also specify a primary space quantity.

CL Interface Only

RSPCPRIM(primary-space)RSPCSEC(secondary-space)space

A number from 1 to 99 999.

Average LengthUse this parameter in conjunction with the space units parameter. Average lengthrepresents the average record length if the space units parameter is set to REC orthe average block length if the space units parameter is set to BLK.

Note: This parameter is only valid for MVS data sets.

CL Interface Only

RBLKLEN( length)length


Directory BlocksUse this parameter in conjunction with the space units parameter to tell thereceiving transfer program the number of directory blocks to allocate for thereceiving file at an MVS system. Specify a value for this parameter only if thereceiving file is a partitioned data set.

CL Interface Only

RDIRBLK( blocks)blocks



Device Type (MVS, VM, VSE)Use this parameter to specify the device type of a unit on which a file is stored if italready exists or is to be stored if it does not. It contains either a generic or aname supplied by IBM that identifies a particular device by its device name.Specify a value only for:

� A non-VSAM file that is to be dynamically allocated and is not cataloged at anMVS system.

� A labeled or unlabeled tape that is dynamically allocated at a VSE system.

If the receiving system is NetView FTP VSE:

� If you do not specify a device type, and the receiving file is to be stored ontape, an installation default is taken.

� When you specify a device type, and the receiving file is to be stored on tape,a tape unit of the specified device type must be assigned to the NetView FTPVSE partition that processes the request.

To find out which device types you can use, ask the system programmer at thereceiving system.

CL Interface Only

xUNIT(device-type)Replace the x in this keyword with either S for sending, or R for receiving.

device-typeThe device type is a character string of up to eight characters.

Volume Serial Numbers (MVS, VM, VSE)Use this parameter to tell a transfer program the serial numbers of the volumes onwhich a file resides (if it already exists) or is to reside (if it does not). You canspecify up to nine volume serial numbers for a single file. You can only specify onevolume serial number for a tape file at a VM system.

You must specify at least one volume serial number when the file is to bedynamically allocated and one of the following is true:

� The file is stored on a labeled tape at a VSE or VM system.

It is recommended that you also specify a volume serial number for unlabeledtapes at a VSE or VM system to identify your tape volumes more easily.

� The file is not cataloged and is stored at an MVS system.

� The file is a new VSAM cluster for which you did not specify a model name orany SMS parameters.

� You specified disposition OLD for a file, on a tape, at a VM system.


CL Interface Only

xVOLSER(volser) | (volser, volser,...)Replace the x in this keyword with either S for sending, or R for receiving.

volserIs a character string of up to six characters, and contains a volume serialnumber.

If the serial number of a volume is less than six characters and you encloseit in single quotes, it will be left-adjusted and padded with trailing blanks.

Volume Count (MVS)The value of this parameter specifies the maximum number of volumes on which areceiving data set can reside. This parameter is only valid for files of the typesLAB and UNLAB at MVS systems. You must specify a volume count when a newdata set is to reside on 6 or more volumes.

If a data set needs more volumes than the number of volume serial numbers youspecify for it, specify a volume count equal to the number of volumes that it needs.

If the volume count is greater than the number of volume serial numbers youspecify, the receiving system reserves other volumes for the file. If the volumecount is smaller than the number of volumes specified, the system ignores thevolume count.

If you specify a volume count, specify at least one volume serial number.Otherwise, the receiving server ignores the volume count you specify and uses amaximum of 5 volumes. The default volume count is 5.

The following figure shows how many volumes the receiving system reserves,depending on the volume count you specify, and shows the volume-count rangesyou can specify.

Table 29. Volume Count and Number of Volumes Reserved

Volume Count Specified Number of Volumes the Operating System Reserves

1 to 5 5

6 to 20 20

21 to 35 35

36 to 50 50

51 to 65 65

65 to 79 80...

...

241 to 255 255


CL Interface Only

RVOLCNT(volume-count)

volume-countA number between 1 and 255.

Data Set Sequence Number (MVS) or File Sequence Number (VM, VSE)The value of this parameter identifies the relative position of a data set on a tapevolume. This parameter is valid for the data set types LAB and UNLAB.Specifying 0 or 1 indicates the first data set on the tape volume. The default valueis 0.

CL Interface Only

xSEQNO(sequence-number)Replace the x in this keyword with either S for sending, or R for receiving.

sequence-numberA number from 0 to 9999.

Retention Period (MVS, VSE)Specify this parameter only for a new dynamically allocated non-VSAM data set atan MVS system or a dynamically allocated labeled tape at a VSE system.

Use this parameter to tell the receiving transfer program the retention period of thereceiving file. The retention period is a number from 0001 to 9999, in days, thattells the receiving transfer program how long to keep the receiving file. Forexample, if the retention period is 24 days, specify it in the form 0024.

If you specify a retention period, do not specify an expiration date.

CL Interface Only

RPERIOD(period)

periodA number from 0001 to 9999.

Expiration Date (MVS, VSE)Specify this parameter only for a new dynamically allocated non-VSAM data set atan MVS system or a dynamically allocated labeled tape at a VSE system.

The expiration date is the date when the receiving transfer program file can deletethe receiving file. The date must be specified in the format defined by the currentjob and shown on the panel. You can specify any year from the current year to theyear 2039.

If you specify an expiration date, do not specify a retention period.


CL Interface Only

EXPDATE(expiration-date)

expiration-dateA date specified in the format defined by the current job and shown on thepanel. The date has components for year, month, and day or for the juliandate format:

year Any 2-digit number from 00 to 99.

month Any 2-digit number from 01 to 12.

day Any 2-digit number from 01 to the number of days in themonth you specify.

julian date A julian date is the year (2 digits) and the number of the dayin the year (a 3-digit number in the range 001 to 366).

VSAM Parameters (MVS, VM, VSE)The following parameters make up a group called VSAM parameters:

� KSDS option � Model name � Model password � Data name � Index name � Catalog name � Catalog password � Data organization� Logical record size (VSE only)

� Key length � Key offset� Average record size� Maximum record size

� Volume � Cluster name.

Except for the KSDS option and catalog name, they are only valid for new VSAMfiles.

If the receiving file is a new VSAM file, you can use either of two methods to tellthe receiving transfer program what attributes it must have:

Method 1 Specify, for the Model Name parameter, the name of a VSAM cluster atthe receiving location. The receiving transfer program makes all theattributes it can set for the new VSAM file the same as those of thismodel file.

Method 2 Do not specify a value for the Model Name parameter. If the type of thesending file is:

VSAM The receiving transfer program creates the receiving filewith the same attributes as the sending file.

Not VSAM The receiving transfer program uses the defaults set byAMS.


If you use this method, you must specify at least one volume serialnumber. For more information about the Volume Serial Numberparameter, see “Volume Serial Numbers (MVS, VM, VSE)” onpage 117.

You must specify the key length for a VSAM KSDS receiving file if the sending fileis not a VSAM KSDS.

Regardless of which method you use, you can also specify values for any of theVSAM parameters. The transfer program uses the values you specify instead ofthe ones it would otherwise use.

KSDS OptionUse this parameter to tell the receiving transfer program how to treat a receiving filethat is a VSAM key-sequenced data set (KSDS). Do not specify this parameterunless the receiving file is a KSDS.

The KSDS option can be one of the following:

*MERGE This value tells the receiving transfer program to:

� Replace a receiving file record with a sending file record if the tworecords have the same key.

� Add a sending file record to the receiving file if it has a key that norecord in the receiving file has.

� Leave a receiving file record in the receiving file if it has a key thatno record in the sending file has.

The receiving file can be initially empty.

Because the receiving transfer program does not distinguish betweenrecords already in the receiving data set before the file transfer andrecords added during the file transfer, the transfer program can replacea record more than once during a file transfer.

*ADDBEGTells the transfer program to transfer the file only if the receiving file isempty.

*ADDKEYTells the receiving transfer program to:

� Add the sending file records to the receiving file.

� Terminate the file transfer, if the receiving file contains a record withthe same key as one of the records in the sending file, unless thetwo records are identical.

Because the receiving transfer program does not distinguishbetween records already in the receiving data set before the filetransfer and records added during the file transfer, if the sending filehas two records that have the same key but different contents, thefile transfer is terminated.


*REPKEYTells the receiving transfer program to:

� Replace a receiving file record with a sending file record if the tworecords have the same key.

� Terminate the file transfer if one of the sending file records has akey that no receiving file record has.

Because the receiving transfer program does not distinguish betweenrecords already in the receiving data set before the file transfer andrecords added during the file transfer, the transfer program can replacea record more than once during a file transfer.

*DELKEY Tells the receiving transfer program to delete the records of thereceiving file that have keys equal to the keys of records in the sendingfile. Records of the sending file whose keys do not match any recordsof the receiving file are ignored by the receiving transfer program.

CL Interface Only

RKSDS(*MERGE | *ADDBEG | *ADDKEY | *REPKEY | *DELKEY)

Model Name and Model PasswordUse these parameters to tell the receiving transfer program the name andpassword (if any) of the VSAM cluster to use as a model for a new VSAM-receivingfile. If you do not specify a model name and the type of the sending file is:

VSAM The transfer program creates the receiving file with the sameattributes as the sending file.

Not VSAM The transfer program uses the defaults set by AMS.

The model password must be the same as the password that was specified whenthe model VSAM cluster was defined.

CL Interface Only

RMODELID(VSAM-model-name) | (VSAM-model-name(VSAM-model-password))

model-nameA character string of up to 44 characters.

model-passwordA character string of up to eight characters.


Data Name and Index NameUse these parameters to specify the names to give the data and index componentsof a new VSAM-receiving file. Do not specify an index name unless the dataorganization is indexed.

CL Interface Only

RDATAID(VSAM-data-name)RINDEXID(VSAM-index-name)

data-nameA character string of up to 44 characters.

index-nameA character string of up to 44 characters. The first character of eachqualifier must be alphabetic capital (A to Z) or national (@, $, #), theremaining characters can be alphabetic capitals, national characters,numeric (0 to 9), hyphen (-), or the character X'C0'. Each qualifier isseparated by a period (.).

Catalog Name and Catalog PasswordUse these parameters to specify:

� The name and password of the VSAM catalog in which a new VSAM file is tobe cataloged.

If you do not specify values for these parameters, when a transfer programdefines a new VSAM cluster, it makes an entry in the catalog specified in:

– The server startup job (MVS)– The NetView FTP partition startup job (VSE)– The catalog specified in the profile of the file-service machine (VM).

If no catalog was specified, the transfer program makes an entry in the defaultcatalog determined by AMS or, for VSE, the NetView FTP VSE work filecatalog.

For files at an MVS system, if you specify a value for one of these parameters,you must specify a value for the other. For files at a VM or VSE system, youcan specify the catalog name only.

� The name of the VSAM catalog in which an existing VSAM file at a VSEsystem is cataloged.

If a VSAM cluster at a VSE system is to be dynamically allocated and is listedin a VSAM catalog other than the NetView FTP work file catalog, use theCatalog Name parameter to tell the corresponding transfer program the nameof the catalog in which it is listed.

The catalog password must be the same as the password that was specified whenthe VSAM catalog was defined. If you specify one of these parameters, specifyboth.


CL Interface Only

SUCATID(catalog-name)

RUCATID(catalog-name) | (catalog-name (catalog-password))

catalog-nameA character string of up to 44 characters.

catalog passwordA character string of up to eight characters

Data OrganizationUse this parameter to specify the organization of the new receiving VSAM cluster.In conjunction with SMS the RRECORG parameter overrides the recordorganization defined in the data class of the data set.

Note: Only use the Data Organization parameter for VSAM-receiving files that donot already exist.

CL Interface Only

RRECORG(*INDEX | *NONINDEX)

*INDEXRefers to an indexed cluster, a key sequenced data set (KSDS).

*NONINDEXRefers to a nonindexed cluster, an entry sequenced data set (ESDS).

Logical Record SizeThe logical record size is only used for new receiving SAM files in VSAM-managedspace (SAM ESDS) in a VSE system. Only specify a logical record size for a SAMfile in VSAM-managed space with a fixed-blocked record format.

Note: The Record Format parameter is described in “Record Format” onpage 110.

CL Interface Only

RVLRECL( record-size)

record-sizeA number from 1 to 32 761.


Key Length and Key OffsetUse these parameters to tell the receiving transfer program the length and offset ofthe key within each record of a new VSAM-receiving file. Specify a key offset onlyif you also specify a key length, or if you use SMS and you want to override thekey offset defined in the data class for the data set. The sum of the key length andkey offset cannot exceed the maximum record size.

Only use these parameters if the data organization is indexed.

CL Interface Only

RKEYS(length) | (length offset)

lengthA number from 1 to 255.

offsetA number from 0 to 32760.

Average and Maximum Record SizeUse these parameters to tell the receiving transfer program the average andmaximum record size of a new VSAM-receiving file.

The average record size allows VSAM performance and space optimization. If youspecify only the average record size, the maximum record size is defaulted. Thedefault is the greater of the record length of the sending file or the specifiedaverage record size. A maximum record size can only be specified if the averagerecord size is also specified.

To indicate to VSAM that all records will be the same length, specify the samevalue for both the average and the maximum record size. To indicate to VSAMthat records may vary in length, specify a lower value for the average record sizethan the maximum record size. However, regardless of what you specify, VSAMconsiders that all clusters have variable-length records. A VSAM record consists ofuser data only (unlike variable-length non-VSAM files that have control and lengthfields).

If the receiving VSAM file is indexed organized (KSDS), then the maximum recordsize must be equal to, or greater than the sum of the key length and key offset.

For VSAM-managed sequential files (SAM ESDS) on VSE, the value of theaverage and maximum record size is defaulted by the operating system if you donot specify values. If you specify a logical SAM record size (RLRECS) and arecord format of fixed blocked (RRECFM=FB), the VSAM record size must be aninteger multiple of the logical SAM record size (RLRECS). For all other recordformats the VSAM record size must be large enough to include user data plusspace for possible length fields. For more information refer to the IBM VSE/VirtualStorage Access Method Commands and Macros Version 2.


CL Interface Only

RRECSIZE(avrecsize) | (avrecsize maxrecsize)

avrecsizeThe average record size can be a number from 1 to 32 761.

maxrecsizeThe maximum record size can be a number from 1 to 32 761.

VM Access (VM)VSAM files only reside on OS-formatted minidisks, however, CMS files can residein a shared file pool or on minidisks. Use this parameter to specify how to link aVSAM or PS file.

If you do not specify either minidisk link and access parameters or SFS directoryaccess parameters and there is a default disk at the remote system, the transferprogram receives the file from, or sends the file to, the default minidisk. If aminidisk is not defined on the remote system, all file transfers are rejected.

VSAM clusters can only reside on OS-formatted minidisks. If you do not specifyminidisk link and access parameters and the remote system has a default minidisk,the transfer program receives the file from, or sends the file to, the default minidisk.If there is no default minidisk, the file transfer is rejected.

CL Interface Only

xACC(access-type)Replace x in the keyword with S for sending or R for receiving.

access-typeOne of the following:

1 Minidisk2 Default minidisk3 Shared file pool

Link Parameters (VM)Link parameters are valid for both VSAM and CMS files.

There are two ways to manage CMS files. CMS files can reside in Shared FileSystem (SFS) directories or on minidisks:

� If the sending or receiving file is stored on a minidisk, you must specify theparameters that are explained in “Minidisk Link and Access Parameters (VM).”

� If the sending or receiving file is stored in an SFS directory, you must specifythe parameters that are explained in “SFS Directory Access Parameters (VM)”on page 128.


If you do not specify either minidisk link and access parameters or SFS directoryaccess parameters and there is a default disk at the remote system, the transferprogram at that location stores the file on the default disk. Otherwise, the filetransfer is rejected.

Minidisk Link and Access Parameters (VM)The following parameters make up a group called Minidisk Link and AccessParameters and are valid for VSAM and PS file types only:

� Disk User ID � Disk Address � Link Password.

These parameters tell the transfer program at a remote VM system about the diskon which the sending or receiving file is stored.

Which of these parameters you need to specify values for depends on whether thetransfer program at the remote system has already linked the disk containing thefile it is to send or receive.

If the transfer program at the remote system has not already linked and accessedthe disk, the user has to specify values for the following parameters:

� Disk User ID � Disk Address� Link Password (if required).

NetView FTP encrypts the value the user gives for the link password before storingit internally.

If sending, the transfer program at the remote system will link the disk in RR mode,give it an unused address, and then access it. If receiving, it will link the disk in Mmode, give it an unused address, and then access it. When the transfer is finished,the transfer program at the remote system will release and detach the disk.

Disk User IDThe user ID of the disk that contains the file being sent or received.

Disk AddressTells the transfer program at the remote system the address—in the directory ofthe user specified in the Disk User ID parameter—of the disk that contains thefile being sent or received.

Link PasswordThe password needed to link to the disk that contains the file being sent orreceived. The user needs to specify this value only if the minidisk the transferprogram is to link to is password-protected. NetView FTP will encrypt the valuethe user gives for the link password before reading it in. For sending files usethe RR link password, for receiving files use the master password.


CL Interface Only

xLINKP( user-id disk-addr) | (user-id disk-addr (lpassword))Replace the x in this keyword with either S for sending, or R for receiving.

user-idA character string of up to eight characters.

disk-addrA character string of four characters.

lpasswordA character string of up to eight characters.

SFS Directory Access Parameters (VM)Use these parameters to tell the transfer program at a VM system about the SFSdirectory in which a file is stored. The SFS directory access parameters are:

Pool IDThe pool ID of the SFS pool that contains the file.

The value that you specify for the pool ID must be the name of the file poolwhere the file resides (if it already exists), or is to reside (if it does not alreadyexist). If you do not specify a value, NetView FTP uses its default file pool.

Top DirectoryThe user ID of the user that owns the directory containing the file.

The value that you specify for the top directory must be the name of the userwho owns the file. The top directory must be one of the following:

� The same as the RACF user ID, if you specified this security parameter.� The user ID of the NetView FTP server that handles the file transfer.

If you do not specify a value for the top directory parameter, NetView FTPtakes as a default:

� The value you specified for the user ID security parameter, if any.� The user ID of the NetView FTP server that processes the request.

SubdirectoriesThe names of the lower-level directories (subdirectories) containing the file.You can specify up to eight subdirectories. If you specify one subdirectory, youmust specify all preceding subdirectories.


CL Interface Only

xSFSP(topdir) | (pool-id)) | ((subdir)) | (subdir1...subdirn) | (topdir poolid) |(topdir (subdir)) | (topdir (subdir1...subdirn)) | (poolid (subdir)) | (poolid(subdir1...subdirn)) | (topdir poolid (subdir)) | (topdir poolid(subdir1...subdirn))Replace the x in these keywords with either S for sending, or R forreceiving. Replace the n in the xSUBDIRn keyword with an integer from 1to 8 to indicate for which of the 8 parameters you are specifying a value.

top-directoryA character string of up to eight characters.

pool-idA character string of up to eight characters.

subdirA character string of up to 16 characters.

SMS Parameters (MVS)The following parameters make up a group called SMS (Storage ManagementSystem) parameters:

� Average record multiplier � Data class � Like � Management class� Reference DD statement

� Security model � Storage class.

When you specify any of the SMS parameters, NetView FTP assumes that anAutomatic Class Selection (ACS) routine exists at the receiving MVS system.Therefore, NetView FTP does not take any attributes from the sending file. Toensure that values determined by the ACS routine are not overwritten by thesending file attributes, ensure that the attributes provided by these parameters aresufficient.

Note: You can only use these parameters when the remote MVS system hasSMS installed.

Average Record MultiplierUse this parameter when you define a new data set to specify that the space unitsare records and that the primary and secondary space quantities are in units ofones, thousands, or millions of records. This parameter corresponds to the SMSparameter AVGREC.

This parameter can have values:

*U The primary and secondary space quantities are in records.

*K The primary and secondary space quantities are in thousands ofrecords.


*M The primary and secondary space quantities are in millions of records.

If you specify the Average Record Multiplier parameter, you must:

� Specify REC for the receiving space units parameter.� Not specify the receiving DD name parameter.

CL Interface Only

RAVGREC(*U | *K | *M)

Data ClassUse this parameter to specify a data class for a new data set. The storageadministrator at the receiving MVS system has defined the names of the dataclasses you can specify. This parameter corresponds to the SMS parameterDATACLAS. If SMS is not installed at the receiving system, the receiving transferprogram ignores this parameter. If you do not specify a data class for a new dataset and the storage administrator has provided an ACS routine, ACS may select adata class.

The data class specifies the following:

� Data set organization � Record length � Key length � Key offset � Space allocation� Retention period or expiration date

� Volume count� For VSAM data sets: IMBED or REPLICATE, CISIZE, FREESPACE,

SHAREOPTIONS.

The following request parameters override the corresponding attributes in a dataclass:

� Receiving record organization or record format� Receiving record length� Receiving key length and offset� Average record multiplier

� Space units� Primary and secondary space� Expiration date and retention period� Receiving volume serial number.

If you specify the Data Class parameter, do not specify the receiving DD nameparameter.

CL Interface Only

RDATACL( data-class-name)

data-class-nameA character string of up to 8 characters.


LikeUse this parameter to specify the allocation attributes of a new data set by copyingthe attributes of a model data set. The model data set must already exist and mustbe cataloged. This parameter corresponds to the SMS parameter LIKE.

The following attributes are copied from the model data set:

� Data set organization � Record length� Key length and offset

� Space allocation.

If SMS is not installed at the receiving MVS system, the receiving transfer programignores this parameter.

The following request parameters override the corresponding attributes obtainedfrom the model data set:

� Receiving record organization or record format� Receiving record length� Receiving key length and offset� Average record multiplier

� Space units� Primary and secondary space.

If you specify the RLIKE parameter, you must not specify the receiving DD nameparameter.

CL Interface Only

RLIKE(data-set-name)

data-set-nameA character string of up to 8 characters.

Management ClassUse this parameter to specify a management class for a new data set. The storageadministrator at the receiving MVS system has defined the names of themanagement classes you can specify. This parameter corresponds to the SMSparameter MGMTCLAS.

After the file is allocated, attributes in the management class control:

� The migration of the file, which includes migration from primary storage toDFHSM-owned storage and from DFHSM-owned storage to archival storage.

� The backup of the file, including the frequency with which backups are made,the number of versions made, and the retention criteria for backup versions.


If SMS is not installed at the receiving system, the receiving transfer programignores this parameter. If you do not specify a management class and the storageadministrator has provided an ACS routine, ACS may select a management class.The use of a management class might be protected by RACF. The managementclass for a data set defines a maximum value for the expiration date or retentionperiod of a data set. This value limits the values that might be specified elsewherein the request, or that might be defined in the data class specified for the receivingdata set.

If you specify the management class name, do not specify the receiving DD nameparameter.

CL Interface Only

RMGMTCL(management-class-name)

management-class-nameA character string of up to 8 characters.

Reference DD StatementUse this parameter to specify the name of a DD statement in the startup job of theserver at the receiving MVS system from which SMS is to copy the followingattributes of the receiving data set:

� Data set organization � Record length � Key length � Key offset � Space allocation.

This parameter corresponds to the SMS parameter REFDD. Attributes notspecified in the DD statement are copied from the data class of the DD statement.

Attributes specified in the reference DD statement override the correspondingattributes of the data class specified for the receiving data set, if any. The followingrequest parameters override the corresponding attributes specified in both thereference DD statement and in the data class:

� Receiving record organization or record format� Receiving record length� Receiving key length and offset

� Average record � Space units� Primary and secondary space.

If SMS is not installed at the receiving MVS system, the receiving transfer programignores this parameter. If you specify a reference DD statement, do not specify avalue for the Like parameter.

The reference DD statement is a character string of up to 26 characters.


CL Interface Only

RREFDD(ddname | stepname.ddname | stepname.procstepname.ddname)

ddnameIs the backward reference to an earlier DD statement in the same step.

stepname.ddnameIs the backward reference to an earlier DD statement in an earlier step(defined by stepname).

stepname.procstepname.ddnameIs the backward reference to an earlier DD statement in a cataloged orin-stream procedure called by an earlier job step. stepname is the name ofthe job step that calls the procedure, and procstepname is the name of theprocedure step that contains the DD statement.

Security Model and GenericUse the Security Model parameter to specify a security model for a new data set.The storage administrator at the receiving MVS system has defined the names ofthe security models you can specify. This parameter corresponds to the SMSparameter SECMODEL.

Use the Generic parameter to indicate whether the profile of the security model is ageneric data set profile.

Use the Security Model parameter when you want a different RACF data-set profilefrom the default profile selected by RACF, or when there is no default profile.

Specify one of the following for the Generic parameter:

*YES The profile name refers to a generic data set

*NO The profile name does not refer to a generic data set.

The following information from the RACF data-set profile, which RACF uses tocontrol access to the data set, is copied to the discrete data-set profile of the newdata set:

OWNER The user or group designated as the owner.

ID The access list of users and groups authorized to accessthe data set.

UACC The universal access authority associated with the dataset.

AUDIT/GLOBALAUDITWhich access attempts are logged.

ERASE Indicates that the data set is to be erased when it isdeleted (scratched).

LEVEL The installation-defined level indicator.

DATA Installation-defined information.


WARNING Indicates that an unauthorized access causes RACF toissue a warning message but allows access to the dataset.

SECLEVEL The name of an installation-defined security level.

If SMS is not installed at the receiving system, the receiving transfer programignores this parameter. The use of a security model might be protected by RACF.

If you specify a security model parameter, do not specify the receiving DD nameparameter.

CL Interface Only

RSECMOD(profile-name)

profile-nameA character string of up to 44 characters.

GENERIC(*YES | *NO)Identifies that the profile name refers to a generic data-set profile.

Storage ClassUse this parameter to specify a storage class for a new data set. The storageclass determines the device type and volumes on which the data set is to bestored, and contains the attributes that identify a storage service level used by SMSto store the file. The storage administrator at the receiving MVS system hasdefined the names of the storage classes you can specify. This parametercorresponds to the SMS parameter STORCLAS.

If SMS is not installed at the receiving MVS system, the receiving transfer programignores this parameter.

If you do not specify a storage class and the storage administrator has provided anACS routine, ACS may select a management class. The use of a storage classmight be protected by RACF.

The storage-class name must have been defined by the administrator at yourinstallation.

If you specify the storage class parameter, do not specify the receiving DD nameparameter.

CL Interface Only

RSTORCL(storage-class-name)

storage-class-nameA character string of up to eight characters.



Chapter 7. Examples of Using the NetView FTP/400 V3Panels

This chapter gives examples of how you can use the NetView FTP/400 V3 panelsto do the following:

� Send a file to an MVS system

� Retrieve a file from an OS/400 system.

Example 1: Sending a File to a Remote MVS SystemImagine the following:

� You want to send a data file (DTAF) to a remote NetView FTP Version 2 MVSsystem. The remote LU nickname is NEWYORK1.

� The file has the name TESTFILE and is located in library TESTLIB .

� You want to give the receiving file the name NEWFILE.

This is how you create a request for this file transfer:


2. Select Option 1 from the NetView FTP/400 V3 Main Menu. NetView FTP/400V3 displays panel DVG100:







1 TONEWYORK AUSER

_ TOPARIS AUSER PARIS TESTLIB/TESTFILE WAITING

_ TONEWYORK2 AUSER NEWYORK2 TESTLIB/TESTFILE FAILED

_ TONAIROBI AUSER NAIROBI TESTLIB/TESTFILE ACTIVE


á ñ

Figure 44. Requests to Send Files


3. Type 1 in the option field of the first entry line, type the name you want to givethe request in the request name field, and press the ENTER key. NetViewFTP/400 V3 displays panel DVG101:



Main Transfer Parameters

Request name. . . . . . . . . TONEWYORK Name

Nickname of remote LU . . . . NEWYORK1__ Name

Remote check. . . . . . . . . \NO_ \NO, \YES

Request Priority. . . . . . . 5 ð-9

Server class. . . . . . . . . _ A-Z, ð-9


Library . . . . . . . . . . . TESTLIB___ Name

File. . . . . . . . . . . . . TESTFILE__ Name

Member. . . . . . . . . . . . \FIRST____ \FIRST, Name, \ALL

File type . . . . . . . . . . \DTAF \DTAF, \SAVF, \SRCF


User ID . . . . . . . . . . . __________ Name

Password. . . . . . . . . . . __________ Name

F3=Exit F4=LU Directory F12=Cancel F17=Create Request

á ñ

Figure 45. Create a Request to Send a File

4. Type NEWYORK1 in the Nickname of remote LU field. The LU directorycontains an entry that corresponds to an LU at an MVS system.

5. Type TESTLIB in the Library field.

6. Type TESTFILE in the File field.

7. Press the ENTER key. NetView FTP/400 V3 displays panel DVG115:


Request/User: TONEWYORK AUSER Remote LU: NEWYORK1

Sending File: TESTLIB/TESTFILE(\FIRST)

Specify additional transfer parameters.

Compression . . . . . . . . . . \ADAPT \ADAPT, \NONE

Restart from Interruption . . . \NO_ \NO, \YES

Automatic retry . . . . . . . . \NO_ \NO, \YES

Running mode of remote server . ______ \CONT, \SINGLE

Recipient of Report (remote)

User ID . . . . . . . . . . . ________

Location name . . . . . . . . ________

Scheduling Parameters

not-before not-after

Transfer starting time . . . ________ ________ HHMM, HH:MM

Transfer starting date . . . ________ ________ MMDDYY, MM/DD/YY


á ñ

Figure 46. Additional Transfer Parameters (MVS)


8. You do not need to specify anything on this panel, therefore, press the ENTERkey. NetView FTP/400 V3 displays the next panel in the sequence:



Sending File: TESTLIB/TESTFILE


Receiving file

Data set name . . . . . . . . NEWFILE____________

___________________

DD name . . . . . . . . . . . __________ Name

Data set type . . . . . . . . \PS \PS, \PO, \LAB, \UNLAB, \VSAM

Security parameters

User ID . . . . . . . . . . . _____ Name

Password. . . . . . . . . . . _____ Name

Group ID. . . . . . . . . . . _____ Name

F3=Exit F12=Cancel F17=Create Request F21=User-Exit Routine

á ñ

Figure 47. Receiving File Parameters (MVS)

9. Type NEWFILE in the Data set name field.

10. Type *PS in the Data set type field.

11. If necessary, type your user ID, password and group ID for the remote system.

12. Press the ENTER key. NetView FTP/400 V3 displays the next panel in thesequence:



Sending File: TESTLIB/TESTFILE

Specify receiving file parameters for a PS data set.

Disposition . . . . . . . . . \CTG \NEW, \OLD, \SHR, \CTG

Device type . . . . . . . . . _______ Name

Volume serial numbers . . . . _____ _____ _____

_____ _____ _____

_____ _____ _____

F3=Exit F12=Cancel F17=Create Request F19=SMS Parameters

á ñ

Figure 48. Receiving File Parameters for a PS Data Set Panel (MVS)

Chapter 7. Examples of Using the NetView FTP/400 V3 Panels 139

13. Type *CTG in the Disposition field.

You have now told NetView FTP/400 V3 everything it needs to know to conduct thefile transfer. Press function key F17 to create the request. NetView FTP/400 V3displays panel DVG100 with the request you have just created.







_ TONEWYORK AUSER

_ TONEWYORK AUSER NEWYORK1 TESTLIB/TESTFILE HELD

_ TOPARIS AUSER PARIS TESTLIB/TESTFILE WAITING

_ TONEWYORK2 AUSER NEWYORK2 TESTLIB/TESTFILE FAILED

_ TONAIROBI AUSER NAIROBI TESTLIB/TESTFILE ACTIVE


á ñ

Figure 49. Requests to Send Files


Example 2: Retrieving a File from a Remote OS/400 SystemImagine the following:

� You want to retrieve an SRCF file from a remote NetView FTP/400 V3 system.The remote LU nickname is DVGLU1.

� The file has the name DVGSRCFILE and is located in the library DVGLIB .

� You want to give the receiving file the name RCVFILE in the library RCVLIB .

� You do not want any expiration date for the file member.

This is how you would create a request for this file transfer:


2. Select Option 2 from the NetView FTP/400 V3 Main Menu. NetView FTP/400V3 displays the Requests to Retrieve Files panel:

à ðDVG2ðð Requests to Retrieve Files






1 REQUEST4

_ REQUEST1 AUSER DVGLU1 DVGLIB/DATAFILE ACTIVE

_ REQUEST2 AUSER NEWYORK2 NFTPLIB/SRCEFILE FINISHED

_ REQUEST3 AUSER NAIROBI NFTPLIB/TESTFILE WAITING


á ñ

Figure 50. Requests to Retrieve Files


3. Type 1 in the option field of the first entry line, type the name you want to givethe request in the Request name field, and then press the ENTER key.NetView FTP displays panel DVG201:

à ðDVG2ð1 Create a Request to Retrieve a File

Specify main transfer parameters.

Request name. . . . . . . . . REQUEST4 Name

Nickname of remote LU . . . . DVGLU1 Name

Remote check. . . . . . . . . \NO \NO, \YES

Request priority. . . . . . . 5 ð-9

Server class. . . . . . . . . ð A-Z, ð-9


User ID . . . . . . . . . . . USERB_____ Name

Password. . . . . . . . . . . Name

F3=Exit F4=LU Directory F12=Cancel

á ñ

Figure 51. Create a Request to Retrieve a File

4. Type DVGLU1 in the Nickname of remote LU field.

5. Type the APPC conversation user ID and the appropriate password. Thecontents of the password field are not shown.

6. Press the ENTER key. NetView FTP/400 V3 displays panel DVG215:

à ðDVG215 Create a Request to Retrieve a File

Request/User: REQUEST4 AUSER Remote LU: DVGLU1

Sending File:

Specify sending file parameters.


Library . . . . . . . . . . . DVGLIB____ Name

File. . . . . . . . . . . . . DVGSRCFILE Name

Member. . . . . . . . . . . . \ALL______ \FIRST, Name, \ALL

File type . . . . . . . . . . \SRCF \DTAF, \SAVF, \SRCF


á ñ



7. Type DVGLIB in the Library field.

8. Type DVGSRCFILE in the File field.

9. Type *ALL in the Member field.

10. Type *SRCF in the File type field and press the ENTER key. NetView FTP/400V3 displays the next panel in the sequence:



Sending File: DVGLIB/DVGSRCFILE(\ALL)

Specify additional transfer parameters.

Compression . . . . . . . . . . \ADAPT \ADAPT, \NONE

Restart from Interruption . . . \NO \NO, \YES

Automatic retry . . . . . . . . \NO \NO, \YES

Scheduling Parameters

not-before not-after

Transfer starting time . . . ________ ________ HHMM, HH:MM

Transfer starting date . . . ________ ________ MMDDYY, MM/DD/YY


á ñ


11. You do not need to specify anything on this panel, therefore, press the ENTERkey. NetView FTP/400 V3 displays the next panel in the sequence:



Sending File: DVGLIB/DVGDATFILE


Receiving file

Library . . . . . . . . . . . RCVLIB Name

File. . . . . . . . . . . . . RCVFILE Name

Member. . . . . . . . . . . . \FROMMBR__ Name, \FROMMBR

File type . . . . . . . . . . \SRCF \DTAF, \SRCF


File option . . . . . . . . . \NEW_ \NEW, \OLD, \REG

Member option . . . . . . . . \ADD_ \ADD, \REPLACE, \APPEND

Expiration date for member. . \NONE YYMMDD, YY/MM/DD, \NONE


á ñ



12. Type RCVLIB in the Library field.

13. Type RCVFILE in the File field.

14. Type *FROMMBR in the Member field.

15. Type *SRCF in the File type field.

16. Type *NEW in the File option field.

17. Type *ADD in the Member option field.

18. Type *NONE in the Expiration date for member field.

You have now told NetView FTP everything it needs to know to conduct the filetransfer. Press function key F17 to create the request. NetView FTP/400 V3displays the Requests to Retrieve Files panel with the request you have justcreated.

à ðDVG2ðð Requests to Retrieve Files






_ REQUEST4 AUSER

_ REQUEST1 AUSER DVGLU1 NFTPLIB/DATAFILE ACTIVE

_ REQUEST2 AUSER NEWYORK2 NFTPLIB/SRCEFILE FINISHED

_ REQUEST3 AUSER NAIROBI NFTPLIB/TESTFILE WAITING

_ REQUEST4 AUSER DVGLU1 DVGLIB/DVGSRCFILE HELD


á ñ

Figure 55. Requests to Retrieve Files


Chapter 8. What to Do if an Error Occurs in NetView FTP/400V3

If a problem occurs when you are using NetView FTP, do the following to find outwhat is causing the problem, and how to report the problem to IBM.

1. Initial Evaluation

Determine which system component is causing the problem. If NetView FTP iscausing the problem, identify the reason. How to do this is described in “InitialEvaluation” on page 143.

2. Submitting an APAR

If you cannot solve the problem, report the problem to an IBM Support Centerusing an Authorized Program Analysis Report (APAR). How to do this isdescribed in “Submitting an APAR” on page 143.

Initial EvaluationThe following describes the error recording facilities in NetView FTP. Thesefacilities can help you in an initial evaluation of a problem.

All NetView FTP components issue messages if they detect an error. Themessages are written into the log file. You can display only the messagescorresponding to your requests. You can view second-level help text by taking theappropriate action on the log-file message panel. The administrator can print allthe messages in the log file.

Submitting an APARTo describe the problem as precisely as possible, include all the availablediagnostic information in the Authorized Program Analysis Report (APAR), and thensend this to your IBM Support Center.

You should include the following information in the APAR:

� From the NetView FTP log file, details of the request that is in error.

� From the NetView FTP trace file, details of the request that is in error.

The trace facility in NetView FTP allows you to prepare error documentation forthe IBM Support Center. NetView FTP/400 V3 documents the following usingthe trace facility:

– The control flow of the modules within the specified NetView FTPcomponent.

– Whether the interface data from one NetView FTP/400 V3 component toanother change during the execution of the modules.

– The state of a specific storage area at a given time while NetView FTP isprocessing a file-transfer request.


For details about printing trace information see “Printing Information FileEntries” on page 62. You can use the OS/400 CPYSPLF command to copythe spooled print file to a file on disk or tape to send to your IBM SupportCenter.

How to invoke the trace facility is described in “Starting a Trace” on page 53.

� A list of the parameters that were specified for a file-transfer request.

� If the error is related to the request database, a softcopy of the requestdatabase.

� If the error is related to the restart file, a softcopy of the restart file.

Checking Which NetView FTP/400 V3 PTFs are InstalledThe PTFs are located in the file DVGPTFP in library DVGD01. You can display thecontents of this file using the OS/400 command DSPPFM, or using the data fileutility DFU. The PTF number is the first seven digits of each record.


Appendix A. How NetView FTP Creates Names for ReceivingFiles

If you do not specify a name for the receiving file and if the receiving transferprogram is NetView FTP, the receiving transfer program creates one.

How NetView FTP V2 MVS Creates Names for Files Received fromNetView FTP/400

Table 30. Rules for Creating Data Set Names

Name in OS/400 Name in MVS

libname/filname(membname) For PS and VSAM data sets:

hlq.libgen.filgen.membgen.Ddate.Ttime

libname/filname(membname) For PO data set:

hlq.libgen.filgen.Ddate.Ttime(membgen)

libname/filname(membname) For tape data set:

hlq.Ttime

Explanation:

libname Library name in OS/400, can be up to 10 characters.

filname File name in OS/400, can be up to 10 characters.

membname Member name in OS/400, can be up to 10 characters.

hlq High level qualifier. If a value for the GID initialization parameterwas specified by your system programmer, this value is used,otherwise, the User ID Security parameter is used if it wasspecified. If neither the GID initialization nor the User IDSecurity parameters were specified, NetView FTP V2 MVS setshlq to ‘FTP’.

libgen Leftmost 8 characters of libname.

filgen Leftmost 8 characters of filname.

membgen Leftmost 8 characters of membname.

Ddate The character D followed by the current date, in the formatYYMMDD.

Ttime The character T followed by the current time, in the formatHHMMSS.

Note: When creating a name, NetView FTP V2 MVS removes special characters(‘,’, ‘.’, and ‘_’), and translates other not valid characters to the character $. If thelength of the created data set name exceeds 44 characters, only the first 44characters are used.


How NetView FTP VM Creates Names for Files Received from NetViewFTP/400


Name in OS/400 Name in VM

libname/filname(membname) For VSAM data sets:



hlq.Ttime

libname/filname(membname) For PS data set (CMS files):

Ttime hlqTtime DVGFILE

Explanation:




hlq High level qualifier. If a value for the GID initialization parameterwas specified by your system programmer, this value is used,otherwise, the User ID Security parameter is used if it wasspecified. If neither the GID initialization nor the User IDSecurity parameters were specified, NetView FTP VM sets hlq to‘FTP’ for VSAM and tape data sets or to ‘DVGFILE’ for CMSfiles.






DVGFILE If neither the GID initialization nor the User ID Securityparameters were specified, NetView FTP VM uses the‘DVGFILE’ file type for CMS files.

Note: When creating a name, NetView FTP VM removes special characters(‘,’, ‘.’, and ‘_’), and translates other not valid characters to the character $. If thelength of the created data set name exceeds 44 characters, only the first 44characters are used.


How NetView FTP VSE Creates Names for Files Received fromNetView FTP/400


Name in OS/400 Name in VSE

libname/filname(membname) For VSAM data sets:



hlq.Ttime

Explanation:




hlq High level qualifier. If a value for the GID initialization parameterwas specified by your system programmer, this value is used,otherwise, the User ID Security parameter is used if it wasspecified. If neither the GID initialization nor the User IDSecurity parameters were specified, NetView FTP VSE sets hlqto ‘FTP’.






Note: When creating a name, NetView FTP VSE removes special characters(‘,’, ‘.’, and ‘_’), and translates other not valid characters to the character $. If thelength of the created data set name exceeds 44 characters, only the first 44characters are used.

Appendix A. How NetView FTP Creates Names for Receiving Files 149

How NetView FTP/400 V3 Creates Names for Data Sets Received fromMVS, VSE, and VM

Explanation:

qualifier 1 First qualifier of the data set name, up to 8 characters.

qualifier n N-th qualifier of the data set name, up to 8 characters.

membname Member name, up to 8 characters.

dsn1dtime The first character of the first qualifier of the data set name(=qualifier1) and 3 characters representing the number of theday in the current year (001 to 366) and 6 charactersrepresenting the current time in the form hhmmss.

Name in MVS, VSE, or VM Name in OS/400

For PO data set (MVS only):qualifier 1 -- -- qualifier n(membname)

DVGFTPDFT/dsn1dtime(membname)

For all other VSAM, LAB, and UNLABdata sets and MVS PS data sets:qualifier 1 -- -- qualilfier n

DVGFTPDFT/dsn1dtime(dsn1dtime)

How NetView FTP/400 V3 Creates Names for CMS Files Received fromVM

Explanation:

fn File name, up to 8 characters.

ft File type, up to 8 characters.

fm File mode, up to 2 characters. The first character is alphabeticand the second character is numeric.

namedtime The first character of the first qualifier of the file name (=fn) and3 characters representing the number of the day in the currentyear (001 to 366) and 6 characters representing the current timein the form hhmmss.

typetime Up to 4 leading characters of the file type (=ft) and 6 characterscurrent time in the format hhmmss.

Name in VM Name in OS/400

fn ft fm DVGFTPDFT/namedtime(typetime)


How NetView FTP/400 V3 Creates Names for Files Received fromOS/400

Explanation:

libname Library name where the file resides, can be up to 10 characters.

filname File name can be up to 10 characters.

member name Member name can be up to 10 characters.

Name in OS/400 Name in OS/400

libname/filname(membname) libname/filname(membname)

Appendix A. How NetView FTP Creates Names for Receiving Files 151


Appendix B. Naming Conventions

Use the following naming conventions when specifying names:

System Naming Rules

OS/400 Names consist of alphanumeric or national ($, #, @) characters, a period(.), or underscore (_). The first character must be alphabetic or national.

The structure of a data set name is as follows:libraryname/filename(membername). Library name, file name, andmember name can each be up to 10 characters.

MVS, VSE, and VMVSAM, LAB, and UNLAB data set names can be either an unqualified or aqualified name:

� An unqualified name consists of 1 to 8 alphanumeric or national ($, #,@) characters, hyphens (-), or left braces ({). The first character mustbe alphabetic or national. Hyphens must not be used forRACF-protected data sets.

� A qualified name consists of multiple unqualified names joined byperiods. The maximum length of a qualified name, including periods,is:

– 44 characters for a data set– 35 characters for a GDG– 17 characters for a tape file.

CMS file names in VM consist of a file name, a file type, and a file mode.The file name and file type can be 1 to 8 alphanumeric or national ($, #,@) characters, underscore (_), hyphen (-), plus (+), or colon (:).

The file mode is two characters long. The first character must bealphabetic and the second character must be numeric.



Appendix C. NetView FTP/400 V3 Receiving File Defaults

If no receiving parameters are specified in a file-transfer request, default values aretaken.

If the sending system is NetView FTP/400 V3, the default values for the receivingfile parameters are the values of the sending file.

The following table shows the default values that are used for the receiving file ifthe sending system is NetView FTP at an MVS, VM, or VSE location.

Table 33. NetView FTP/400 V3 Receiving File Default Values

Parameter Name Keyword Default Value

Library RFILE See Appendix A, “HowNetView FTP CreatesNames for Receiving Files”on page 145.

File RFILE See Appendix A, “HowNetView FTP CreatesNames for Receiving Files”on page 145.

Member RMBR *FROMMBR for MVSpartitioned organized datasets, otherwise, seeAppendix A, “How NetViewFTP Creates Names forReceiving Files” onpage 145.

File type RFILTYPE *DTAF

File option FILOPT *NEW

Member option MBROPT *ADD

Maximum members per file MAXMBRS 1

Maximum number of records MAXREC *NOMAX

Initial number of records SIZE 10000

Increment number of records SIZE 1000

Maximum increments SIZE 3

Public access authority AUT *CHANGE

Expiration date for member EXPDATE *NONE



Appendix D. List of Keywords

The following table lists all of the NetView FTP/400 V3 keywords in alphabeticorder and the possible values for each keyword. It also shows the pages wherethe keywords are described. The values listed are all enclosed in parentheses.

Keyword Values Page

ACTSRV 2 | 1 to 99 85

ATMRTRY *YES | *NO 91

AUT *CHANGE | *ALL | *USE | *EXCLUDE 99

COMPRESS *ADAPT | *NONE 92

ENDMODE *C | *CNTRLD | *I | *IMMED 87

EXPDATE *NONE | expiration-date 99,119

FILOPT *NEW | *REG | *OLD 96

GENERIC *YES | *NO 133

MAXMBRS *NOMAX | maximum-members 97

MAXREC 1 to 3997574 | *NOMAX 97

MAXSRV 20 | 1 to 99 85

MBROPT *ADD | *REPLACE | *APPEND 96

NBRSRV 1 | 1 to 99 87

NEWPWD password 89

PASSWORD password 92

PPXIN1 information 94

PPXIN2 information 94

RACC access-type 126

RAVGREC *U | *K | *M 129

RBLKLEN length 116

RBLKSIZE blksize 111

RCDLEN record-length 99

RCMSID filename filetype filemode 102

RDATACL data-class-name 130

RDATAID VSAM-data-name 123

RDEN 0 | 1 | 2 | 3 | 4 | C 114

RDIRBLK blocks 116

REQHLD *YES | *NO 88

REQNAME name 88

RESTART *YES | *NO 91

RFILE file-name 94

RFILEID file-id 100

RFILTYPE *DTAF | *SAVF | *SRCF 95


Keyword Values Page

RFNAME DD-name 103

RFTYPE *VSAM | *VSAM (cluster-password) | *PS | *LAB | *UNLAB | *PO 106

RGDGMDI DSCB-model-name 114

RINDEXID VSAM-index-name 123

RKEYS length | length offset 125

RKSDS *MERGE | *ADDBEG | *ADDKEY | *REPKEY | *DELKEY 121

RLIKE data-set-name 131

RLINKP user-id disk-addr | user-id disk-addr (lpassword) 126

RLRECL lrecl 111

RMBR *FROMMBR | member-name 95

RMGMTCL management-class-name 131

RMODELID VSAM-model-name | VSAM-model-name VSAM-model-password 122

RMSERVER name 91

RMTCHK *YES | *NO 93

RPERIOD retention-period 119

RQPTY 0 | 1 | 2 | ... |5| ... | 8 | 9 89

RQORG user-id | *CURRENT 88

RRECFM *U | *V | *F | *FB | *VB | *VS | *VBS 110

RRECORG *INDEX | *NONINDEX 124

RRECSIZE avrecsize | avrecsize maxrecsize 125

RREFDD ddname | stepname.ddname | stepname.procstepname.ddname 132

RRNID location-id 105

RRUID user-id 105

RSECMOD profile-name 133

RSECURP user-id (password) | user-id (password) group-id 107

RSEQNO sequence-number 119

RSFSP topdir | (pool-id) | (subdir) | subdir1...subdirn | topdir poolid | topdir (subdir) |..subdirn)) | topdir (subdir1...subdirn) | poolid (subdir) | poolid (subdir1...subdirn) |topdir poolid (subdir) | topdir poolid (subdir1...subdirn)

128

RSPCPRIM primary-space 116

RSPCSEC secondary-space 116

RSPCUNIT *CYL | *TRK | *BLK | *REC 115

RSTORCL storage-class-name 134

RTDISP *NEW | *CTG | *OLD | *MOD | *SHR | *REG 108

RTRY max-retries | max-restarts | retry-interval 86

RUCATID catalog-name (catalog-password) 123

RUNIT device-type 117

RVOLCNT volume-count 118

RVOLSER volume-serial-number-1 | volume-serial-number-1...volume-serial-number-n 117

RVLRECL record-size 124


Keyword Values Page

SACC access-type 126

SBLKSIZE blksize 111

SCHDL notbefore-time|0 notbefore-date|0 notafter-time|0 notafter-date|0 89

SCMSID filename filetype filemode 102

SFILE file-name 94

SFILEID VM-VSE-file-idMVS-data-set-name

100100

SFILTYPE *DTAF | *SAVF | *SRCF 95

SFNAME MVS-dd-nameVSE-file-name

103103

SFTYPE *VSAM | *VSAM (cluster-password) | *PS | *LAB | *UNLAB | *PO 106

SIZE initial-number-of-records increment-number-of-recordsmaximum-number-of-increments

97

SLINKP user-id disk-addr | user-id disk-addr (lpassword) 126

SLRECL lrecl 111

SMBR *FIRST | *ALL | member-name 95

SRECFM *U | *V | *F | *FB | *VB | *VS | *VBS 110

SRVCLS A ... Z | 0 ... 9 86

SRVMODE *C | *CONT | *S | *SINGLE 104

SRVPFX DVGSRV | server-prefix 86

SSECURP user-id (password) | user-id (password) group-id 107

SSEQNO sequence-number 119

SSFSP topdir | (pool-id) | (subdir) | subdir1...subdirn | topdir poolid | topdir (subdir) |..subdirn)) | topdir (subdir1...subdirn) | poolid (subdir) | poolid (subdir1...subdirn) |topdir poolid (subdir) | topdir poolid (subdir1...subdirn)

128

SUNIT device-type 117

SVOLSER volume-serial-number-1 | volume-serial-number-1...volume-serial-number-n 117

TEXT description 98

USRID user-id 92

VRYPWD password 89

Appendix D. List of Keywords 159


Appendix E. Machine Requirements

NetView FTP/400 V3 runs on all models of the AS/400. This appendix describesthe minimum system, program, and storage requirements for running NetViewFTP/400 V3.

Program RequirementsThe Operating System/400* Version 3 (program number 5763-SS1) Release 1 orhigher is a prerequisite for NetView FTP/400 V3 R1.

| The Operating System/400* Version 3 (program number 5716-SS1) Release 6 or| higher is a prerequisite for NetView FTP/400 V3 R6.

Storage Requirements| The following list shows the storage requirements for each of the components of| NetView FTP/400 V3 R1:

� For the first server session: 500KB

� For each additional server session: 250KB.

| The following list shows the storage requirements for each of the components of| NetView FTP/400 V3 R6:

| � For the first server session: 1MB

| � For each additional server session: 500KB.

| � Disk space: 40MB



Appendix F. Performance Considerations

The following factors affect the transmission performance of NetView FTP/400 V3:

� The compression method used� The number of records transferred� The number of conversations concurrently being handled by NetView FTP/400

V3� Speed and number of communication links� Overall network load� The general load on the system

� CPU speed � RU size � Pool size � PURGE parameter� Operating system version.

Some of these factors are outside the control of the NetView FTP/400 V3administrator and operator. However, some of these factors can be controlled, forexample, the compression method used, the pool size, and the number of recordstransferred:

� The originator of a file-transfer request can specify either adaptive or nocompression. The type of data to be transferred determines which of thesemethods is the most effective. The request originator must take the followinginto consideration when determining the compression method to use:

Adaptive compression:Adaptive compression works by replacing character strings that arerepeated in a file with a reference in a directory of these characterstrings. This is the most effective method for most types of data. Ifyou use compression, consider the following:

– For slower line speeds (for example, 9600 baud), compressionincreases the throughput.

– Compression increases the load on the CPU.

– Compression requires more CPU time for files that do not havemuch data that can be compressed.

No compression:Neither transfer program will compress or decompress the file. Nocompression uses the least CPU time but usually involves thetransfer of the greatest amount of data.

Use no compression in the following circumstances:

– The sending file contains random data.

– When the cost of the computing time that NetView FTP/400 V3would need to compress and decompress the data is higherthan the extra cost of transferring non-compressed data.

– Transferring small files.


� NetView FTP/400 V3 must run in a pool that is large enough to hold the mainpart of the program. Allocate a minimum of 500KB for the first server, and250KB for each additional server. The larger the pool available to NetViewFTP/400 V3 the faster it will run.

� Files containing the same amount of data require less time to be transferred ifthe record length is larger.

� Prestarted jobs reduce server initialization time at remote NetView FTP/400 V3installations.


Appendix G. Communications Considerations

The WAITFILE parameter of the ICF file DVG41I determines how long the APPCSupport waits for session resources to become available when performing anacquire operation. If the WAITFILE timer runs out, a code of either 82B3 or 81C2is returned. In certain networks (for example, APPN*), sessions may cross multiplesystems and lines to reach the remote system. In such cases the WAITFILE timershould be adjusted to allow more time. The WAITFILE value of the ICF fileDVG41I delivered with NetView FTP/400 V3 is set to 10 seconds. If a request failswith a major/minor code of 82B3 or 81C2, increase the value for the WAITFILEparameter using the command CHGICFF. The format of the CHGICFF commandis:

CHGICFF FILE(DVGOð1/DVG41I) WAITFILE(number-of-seconds)

Note: The WAITFILE parameter is ignored for sessions using switchedconnections.



Appendix H. Example of an AS/400-to-System/370 SDLC LineConfiguration

This appendix shows an example of how you would configure an SDLC leased linefor an AS/400-to-System/370 connection:

� Define the AS/400 SDLC line.

� Define the AS/400 controller.

� Define the AS/400 device.

� Create a mode description to define session characteristics.

� Create System/370 NCP/VTAM definitions.

For more information refer to AS/400 Communications: User’s Guide.

AS/400 Line DescriptionUse the following CL command to define an SDLC line:

CRTLINSDLC LIND(FTPLINC) RSRCNAME(LINð11)

ROLE(\SEC) EXCHGID(ð56ððððð)

TEXT('SDLC leased line to System/37ð')

Figure 56. Example of an AS/400 Line Description

Considerations

� The RSRCNAME(LIN011) is the name assigned to the physical port to beused.

� The data link ROLE must be the secondary for SDLC communication with thehost.

� When using a leased line the exchange ID value is not compared with theIDBLK and IDNUM fields in the Network Control Program (NCP). The valueshown is a sample only.


AS/400 Controller DescriptionBecause the controller describes the relationship between AS/400 and a host, itmust be defined as a *HOST controller. This controller supports both dependentand independent LUs. Use the following command to define the controller:

CRTCTLHOST CTLD(FTPCTLC) LINKTYPE(\SDLC)

APPN(\NO) LINE(FTPLINC) RMTNETID(\NONE)

STNADR(C1) TEXT('Host CTL on FTPLINC')

Figure 57. Example of a Controller Description

Considerations

� The LINE field will cross-reference this controller description to the appropriateline description.

� The station address is the SDLC link station address used by the host tocommunicate with the AS/400.

AS/400 Device DescriptionUse the CL command CRTDEVAPPC to define the APPC device descriptions.Both dependent and independent LUs can be used to communicate with remoteNetView FTP systems.

Dependent APPC Device Description

CRTDEVAPPC DEVDC(FTPDEVC1) RMTLOCNAME(NFTPðð1)

LCLLOCNAME(A2UU6ð1) RMTNETID(\NONE)

CTL(FTPCTLC) MODE(FTPBIND) LOCADR(ð1)

SNGSSN(\YES) APPN(\NO)

TEXT('LU 6.2 dependent')

Figure 58. Example of a Dependent APPC Device Description

Considerations

� The remote location name is arbitrary for dependent LUs. The combination ofremote location name and local location name must be unique.

� The attached controller (CTL) is the name of the controller description to whichthis device is to be attached.

� The MODE used in the device description can be a system-supplied modedescription or a user-defined mode description.

� For dependent LUs single session SNGSSN(*YES) must be specified.

� The local location address LOCADR(01) is a hexadecimal number on theAS/400. The corresponding address in the VTAM/NCP LU definition statementis specified in decimal and must match the AS/400 value.


Independent APPC Device Description

CRTDEVAPPC DEVDC(FTPDEVC2) RMTLOCNAME(NFTPðð1)

LCLLOCNAME(A2UU6ð1A) RMTNETID(\NONE)

CTL(FTPCTLC) MODE(FTPBIND) LOCADR(ðð)

SNGSSN(\NO) APPN(\NO)

TEXT('LU 6.2 independent')

Figure 59. Example of an Independent APPC Device Description

Considerations

� The local location address LOCADR must always be 00 for an independent LU.

� Single session SNGSSN(*NO) is specified because this independent device iscapable of parallel sessions. The number of sessions available is determinedby all modes associated with a unique local and remote location pair.

AS/400 Mode DescriptionThe mode description describes the session characteristics and number of sessionsthat are to be permitted between local and remote locations using this modedescription.

CRTMODD MODD(FTPBIND) MAXSSN(8) MAXCNV(8)

LCLCTLSSN(4) PREESTSSN(ð) MAXLENRU(256)

TEXT('Mode for NetView FTP')

Figure 60. Example of a Mode Description

Considerations

� The mode description must match the DLOG specified in the VTAM/NCP LUdefinition statement.

� The MAXLENRU should be the same as the RUSIZES specified in theMODEENT of the VTAM/NCP MODETAB macroinstruction. If not, it will benegotiated with the remote location. *CALC is the recommended value forMAXLENRU.

System/370 NCP/VTAM DefinitionsThe following example for the host side of an SDLC nonswitched point-to-pointnetwork includes GROUP, LINE, PU, and LU definitions statements for configuringNCP/VTAM.

Appendix H. Example of an AS/400-to-System/370 SDLC Line Configuration 169

NCP/VTAM Group Definition StatementThe group statement defines characteristics of the type of communication thatoccurs between NCP and any of the attached physical and logical units.

A2CGSDLC GROUP LNCTL = SDLC

NRZI = NO

ANS = CONT

CLOCKING = EXT

DIAL = NO

DISCNT = NO

ISTATUS = ACTIVE

MAXDATA = 256

MAXOUT = 7

AVGPB = 896

DATRATE = HIGH

DUPLEX = FULL

NEWSYNC = NO

PACING = ð

PASSLIM = 8

PAUSE = ð.2

PUTYPE = 2

RETRIES = (7,4,1ð)

SPDSEL = NO

SPEED = ð96ðð

TYP = NCP

SSCPFM = USSSCS

VPACING = ð

Figure 61. Example of a Group Definition Statement

NCP/VTAM Line Definition StatementThe line statement is used to define the characteristics of a line within a groupwhen starting NCP/VTAM.

A2UCðL36 LINE ADDRESS =(ð36, HALF)

Figure 62. Example of a Line Definition Statement

NCP/VTAM PU Definition StatementThe following is an example of the PU definition statement:

A2UU6K PU ADR = C1

XID = YES

Figure 63. Example of a PU Definition Statement


NCP/VTAM LU Definition StatementsThe following are the statements to define system devices:

dependent LU

A2UU6ð1 LU LOCADDR = ð1

ISTATUS = ACTIVE

Figure 64. Example of a Dependent LU Definition Statement

independent LU

A2UU6ð1A LU LOCADDR = ðð

ISTATUS = ACTIVE

RESSCB = 25

MODETAB = FTPFTF

DLOGMOD = FTPBIND

Figure 65. Example of an Independent LU Definition Statement

System/370 VTAM Macroinstructions

MODETAB and MODEENT MacroinstructionsThe following example shows the definitions to generate a new MODETABcontaining one entry with the name FTPBIND.

FTPFTF MODETAB

FTPBIND MODEENT LOGMODE=FTPBIND, X

TYPE=X'ðð', X

FMPROF=X'13', X

TSPROF=X'ð7', X

PRIPROT=X'Bð', X

SECPROT=X'Bð', X

COMPROT=X'DðB1', X

RUSIZES=X'8585', X

SSNDPAC=X'ð4'

Figure 66. Example of an Entry in a Logon Mode Table

Appendix H. Example of an AS/400-to-System/370 SDLC Line Configuration 171

APPL MacroinstructionThe following example defines two NetView FTP V2 MVS servers as an ApplicationProgram Major Node (definitions for NetView FTP VM and NetView FTP VSE aresimilar):

VBUILD TYPE=APPL

NFTPðð1 APPL AUTH=(ACQ,PASS),VPACING=4,ACBNAME=NFTPðð1,APPC=YES X

DLOGMOD=FTPBIND,MODETAB=FTPFTF,PARSESS=YES, X

AUTOSESS=ð,DDRAINL=ALLOW,DRESPL=ALLOW,DSESLIM=32, X

SECACPT=CONV,DMINWNL=1,DMINWNR=1

\

NFTPðð2 APPL AUTH=(ACQ,PASS),VPACING=4,ACBNAME=NFTPðð2,APPC=YES X

DLOGMOD=FTPBIND,MODETAB=FTPFTF,PARSESS=YES, X

AUTOSESS=ð,DDRAINL=ALLOW,DRESPL=ALLOW,DSESLIM=32, X

SECACPT=CONV,DMINWNL=1,DMINWNR=1

Figure 67. Defining Servers as an Application Program Major Node


Appendix I. Working with the Post-Transfer Data Queue

To provide easy access to information about the outcome of a transfer, NetViewFTP/400 V3 writes data about the transfer to the post-transfer data queueDVGPTDTAQ (in library DVGD01). An entry is written to the data queueregardless of whether NetView FTP/400 V3 is the local or remote system.

NetView FTP/400 V3 also uses this data queue to store up to 1262 bytes ofuser-exit information received from NetView FTP MVS, VM, or VSE systems. Youcan write application programs to monitor the data queue and to performpost-transfer processing, when an entry is written.

Each DTAQ entry contains:

� All information necessary to identify a transfer

� Information about the sending and receiving file names

� Information about whether or not the transfer finished normally

� User-exit input received from the requesting system (at the responding systemonly).

Entries are written to the DTAQ regardless of whether NetView FTP/400 V3 isacting as the local or remote system. Table 34 shows the layout of the DTAQ.

NetView FTP/400 V3 provides two administrator functions that involve thepost-transfer data queue:

� Specifying whether or not post-transfer data is stored

� Maintaining the data queue’s storage.

Specifying Post-Transfer Data StorageOn the Work with startup file panel an administrator can specify *YES or *NO in theProcess post-transfer data field to set a value for the PPXSP parameter. If theadministrator specifies *YES, NetView FTP/400 creates the DVGTDTAQ dataqueue in the DVGD01 library if it does not already exist.

If the administrator specifies *NO, NetView FTP/400 deletes and then recreates theDVGTDTAQ data queue in the DVGD01 library. This ensures that the storageallocated to the data queue is released and a new data queue is created with thecorrect attributes.

Maintaining the Data Queue’s StorageIf an administrator selects the Reclaim DTAQ storage from the AdministratorFunctions panel (DVG300) NetView FTP/400 V3 reclaims the storage allocated to,but not currently used by the DVGPTDTAQ data queue. This procedure isnecessary because NetView FTP/400 V3 dynamically allocates additional storagewhen an entry to be written to the data queue does not fit in the currently allocatedspace but does not release storage after the entry has been used.

This function cannot be used if either the agent or server is active.


Post-Transfer Data Queue Layout

Table 34 (Page 1 of 2). DTAQ Layout

Field Length Content

Start code 1 Either L for local, or R for remote

Request name 10 The name of the request specified when the request wascreated

Request mode 4 Either FROM for send, or TO for retrieve

Remote check 4 Either *YES or *NO

User ID 10 Either the request owner when local, or the APPC user IDwhen remote

Request result 2 00 Transfer finished successfully01 Transfer failed, permanent error03 Transfer failed, temporary error before restart window04 Transfer failed, all data processed08 Transfer failed, data not completely processed, job

terminated09 Transfer failed, invalid APPC security information13 Transfer failed, temporary error within restart window23 Transfer failed, temporary error after restart window

User-exit information part 1 62 62 bytes of data that can be evaluated by an applicationprogram

User-exit information part 2 1200 1200 bytes of data that can be evaluated by an applicationprogram

Remote FTP name 10 The name of the remote NetView FTP system

Remote LU name 10 The name of the remote LU

Sending library name OS/400 10 Identifies the OS/400 sending file

Sending file name OS/400 10 Identifies the OS/400 sending file

Sending member name OS/400 10 Identifies the OS/400 sending file

Sending file type 8 Identifies the sending file type

Receiving library name OS/400 10 Identifies the OS/400 receiving file

Receiving file name OS/400 10 Identifies the OS/400 receiving file

Receiving member name OS/400 10 Identifies the OS/400 receiving file

Receiving file type 8 Identifies the receiving file type

Sending data set name 44 MVS, VSE, or VM VSAM sending data set name

Sending MVS member name 8 MVS member name identity

Sending volume serial number 6 Sending volume identity

Receiving data set name 44 MVS, VSE, or VM VSAM sending data set name

Receiving MVS member name 8 Identifies the receiving MVS member name

Receiving volume serial number 6 Identifies the receiving volume

Sending VM file ID 8 Identifies the sending VM file ID

Sending VM file type 8 Identifies the sending VM file type

Sending VM file mode 2 Identifies the sending VM file mode

Receiving VM file ID 8 Identifies the receiving VM file ID


Table 34 (Page 1 of 2). DTAQ Layout

Field Length Content

Receiving VM file type 8 Identifies the receiving VM file type

Receiving VM file mode 2 Identifies the receiving VM file mode

Sample Application ProgramLibrary DVGUSR contains the external description of the data queue and sampleapplication programs that show you how to work with the post-transfer data queue:

DVG29CL in QCLSRCReads a data queue entry.

DVG29CB in QLBLSRCWrites a data queue entry to the DVGDTAQ file.

DVGPTDTP in QDDSSRCExternal definition of the layout of the DVGPTDAQP data queue.

DVGDTAQPFile into which the DVG29CB program writes data queue entries.

Appendix I. Working with the Post-Transfer Data Queue 175


Appendix J. Relationships between Sending File andReceiving File Attributes

This appendix shows the relationship between the type and record format attributesof the sending file and the resulting record length, record size, and block size of areceiving file of each type and record format.

┌─────────────┬────────────────────────────────────────────────────────────────┐

│Attributes of│ Rules for the │

│Sending File │ Receiving File Attribute Specification │

├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤

│ Type │Record│ Type │Record│ Record │ Record │ Block │ Comments │

│ │Format│ │Format│ Length │ Size │ Size │ │

├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│PS, │F │PS, │ │ │ │ │ RBLKSIZE must not │

│LAB, │ │LAB, │ │ RLRECL │ │ │ be specified. │

│or │ │or │ F │ = │ N/A │ N/A │ If present, the │

│UNLAB │ │UNLAB │ │ SLRECL │ │ │ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECL │ │RBLKSIZE│ RBLKSIZE required.│

│ │ │ │ FB │ = │ N/A │ = │ │

│ │ │ │ │ SLRECL │ │RLRECL\x│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECL │ │RBLKSIZE│ RBLKSIZE can be │

│ │ │ │ V │ >= │ N/A │ = │ specified. │

│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ = │ │

│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ │

│ │ │ │ │ SLRECL+4 │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ │

│ │ │ │ │ SLRECL+4 │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ │ │RBLKSIZE│ RBLKSIZE required.│

│ │ │ │ U │ N/A │ N/A │ >= │ │

│ │ │ │ │ │ │ SLRECL │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ │RRECSIZE │ │ RRECSIZE refers │

│ │ │ │ N/A │ N/A │ >= │ N/A │ to the maximum │

│ │ │ │ │ │ SLRECL │ │ record size. │

│ │ │VSAM ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECS │RRECSIZE │ │ Receiver is a VSE │

│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. │

│ │ │ │ │ SLRECL │RLRECS\x │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECL │ │ │ Receiver is an │

│ │ │SRCF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Source │

│ │ │ │ │ SLRECL+12 │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │DTAF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Data file. │

│ │ │ │ │ SLRECL │ │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │SAVF │ N/A │ = │ N/A │ N/A │ OS/4ðð Save file. │

│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘

Figure 68 (Part 1 of 16). Relationships between Sending File and Receiving File Attributes


┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│PS, │FB │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │

│LAB, │ │LAB, │ F │ = │ N/A │ N/A │ be specified. │

│or │ │or │ │ SLRECL │ │ │ │

│UNLAB │ │UNLAB ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ N/A │ = │ If present, the │

│ │ │ │ │ SLRECL │ │RLRECL\x│ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. │

│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ >= │ │

│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ │

│ │ │ │ │ SLRECL+4 │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ │

│ │ │ │ │ SLRECL+4 │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ U │ N/A │ N/A │ >= │ │

│ │ │ │ │ │ │ SLRECL │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ N/A │ N/A │ >= │ N/A │ to maximum record │

│ │ │ │ │ │ SLRECL │ │ size. │

│ │ │VSAM ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. │

│ │ │ │ │ SLRECL │RLRECS\x │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+12 │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │DTAF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Source │

│ │ │ │ │ SLRECL │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│PS, │V │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │

│LAB, │ │LAB, │ F │ = │ N/A │ N/A │ be specified. All │

│or │ │or │ │ SLRECL─4 │ │ │ records must be │

│UNLAB │ │UNLAB │ │ │ │ │ the maximum size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ N/A │ = │ All records must │

│ │ │ │ │ SLRECL─4 │ │RLRECL\x│ be the maximum │

│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. If │

│ │ │ │ │ SLRECL │ │RLRECL+4│ present, the │

│ │ │ │ │ │ │ │ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECL │ │RBLKSIZE│ │

│ │ │ │ VB │ >= │ N/A │ = │ RBLKSIZE required.│

│ │ │ │ │ SLRECL │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ RBLKSIZE required.│

│ │ │ │ │ SLRECL │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ RBLKSIZE required.│

│ │ │ │ │ SLRECL │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ │ │RBLKSIZE│ │

│ │ │ │ U │ N/A │ N/A │ >= │ RBLKSIZE required.│

│ │ │ │ │ │ │SLRECL─4│ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ │RRECSIZE │ │ RRECSIZE refers to│

│ │ │ │ N/A │ N/A │ >= │ N/A │ the maximum record│

│ │ │ │ │ │SLRECL─4 │ │ size. │

│ │ │VSAM ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. All │

│ │ │ │ │ SLRECL─4 │RLRECS\x │ │ records must be │

│ │ │ │ │ │ │ │ the maximum size. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+8 │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL─4 │ │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘


Appendix J. Relationships between Sending File and Receiving File Attributes 179

┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│PS, │VB │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │


│or │ │or │ │ SLRECL─4 │ │ │ records must be │


│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ N/A │ = │ All records must │


│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. │

│ │ │ │ │ SLRECL │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ >= │ If present, the │

│ │ │ │ │ SLRECL │ │RLRECL+4│ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ RBLKSIZE required.│

│ │ │ │ │ SLRECL │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ RBLKSIZE required.│

│ │ │ │ │ SLRECL │ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ │ │RBLKSIZE│ │

│ │ │ │ U │ N/A │ N/A │ >= │ RBLKSIZE required.│

│ │ │ │ │ │ │SLRECL─4│ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ │SLRECL─4 │ │ size. │

│ │ │VSAM ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ │ │ │ Receiver is a VSE │

│ │ │ │ │ RLRECS │RRECSIZE │ │ SAM ESDS. │

│ │ │ │ FB │ = │ = │ N/A │ All records must │

│ │ │ │ │ SLRECL─4 │RLRECS\x │ │ be the maximum │

│ │ │ │ │ │ │ │ size. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+8 │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL─4 │ │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│PS, │VS, │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │

│LAB, │or │LAB, │ F │ = │ N/A │ N/A │ be specified. All │

│or │VBS │or │ │ SLRECL─4 │ │ │ records must be │


│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ FB │ RLRECL │ │RBLKSIZE│ RBLKSIZE required.│

│ │ │ │ │ = │ N/A │ = │ All records must │


│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. │

│ │ │ │ │ SLRECL │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ >= │ │

│ │ │ │ │ SLRECL │ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ If present, the │

│ │ │ │ │ SLRECL │ │ │ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ If present, the │

│ │ │ │ │ SLRECL │ │ │ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ U │ N/A │ N/A │ >= │ │

│ │ │ │ │ │ │SLRECL─4│ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ │SLRECL─4 │ │ record size. │

│ │ │VSAM ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. All │

│ │ │ │ │ SLRECL─4 │RLRECS\X │ │ records must be │


│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+8 │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │DTAF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Data │

│ │ │ │ │ SLRECL─4 │ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│PS, │U │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │


│or │ │or │ │ SBLKSIZE │ │ │ records must be │


│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ FB │ RLRECL │ │RBLKSIZE│ RBLKSIZE required.│

│ │ │ │ │ = │ N/A │ = │ All records must │

│ │ │ │ │ SBLKSIZE │ │RLRECL\x│ be the maximum │

│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. │

│ │ │ │ │ SBLKSIZE+4│ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ >= │ │

│ │ │ │ │ SBLKSIZE+4│ │RLRECL+4│ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ │

│ │ │ │ │ SBLKSIZE+4│ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ │

│ │ │ │ │ SBLKSIZE+4│ │ │ │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ U │ N/A │ N/A │ >= │ If present, the │

│ │ │ │ │ │ │SBLKSIZE│ sending DCB can be│

│ │ │ │ │ │ │ │ accepted. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ │SBLKSIZE │ │ size. │

│ │ │VSAM ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. All │

│ │ │ │ │ SBLKSIZE │RLRECS\X │ │ records must be │


│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │SBLKSIZE+12│ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │SBLKSIZE │ │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│VSAM │ N/A │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │

│ │ │LAB, │ F │ = │ N/A │ N/A │ be specified. │

│ │ │or │ │ SRECSIZE │ │ │ SRECSIZE refers │

│ │ │UNLAB │ │ │ │ │ to the maximum │

│ │ │ │ │ │ │ │ sending record │

│ │ │ │ │ │ │ │ size. All records │

│ │ │ │ │ │ │ │ must be the │

│ │ │ │ │ │ │ │ maximum size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ N/A │ = │ SRECSIZE refers │

│ │ │ │ │ SRECSIZE │ │RLRECL\x│ to the maximum │


│ │ │ │ │ │ │ │ size. All records │

│ │ │ │ │ │ │ │ must be the │

│ │ │ │ │ │ │ │ maximum size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. │

│ │ │ │ │SRECSIZE+4 │ │RLRECL+4│ SRECSIZE refers │

│ │ │ │ │ │ │ │ to the maximum │


│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ >= │ SRECSIZE refers │

│ │ │ │ │ SRECSIZE+4│ │RLRECL+4│ to the maximum │


│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ SRECSIZE refers │

│ │ │ │ │ SRECSIZE+4│ │ │ to the maximum │


│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ SRECSIZE refers │

│ │ │ │ │ SRECSIZE+4│ │ │ to the maximum │


│ │ │ │ │ │ │ │ size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ U │ N/A │ N/A │ >= │ │

│ │ │ │ │ │ │SRECSIZE│ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│VSAM │N/A │VSAM │ │ │RRECSIZE │ │ RRECSIZE refers │


│ │ │ │ │ │SRECSIZE │ │ record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. All │

│ │ │ │ │ SRECSIZE │RLRECS\X │ │ records must be │


│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │SRECSIZE+12│ │ │ file. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SRECSIZE │ │ │ │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘


┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│VSAM │FB │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │

│ │(see │LAB, │ F │ = │ N/A │ N/A │ be specified. │

│ │note │or │ │ SLRECS │ │ │ SLRECS refers │

│ │after │UNLAB │ │ │ │ │ to the sending │

│ │table)│ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ N/A │ = │ SLRECS refers │

│ │ │ │ │ SLRECS │ │RLRECL\X│ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECL │ │RBLKSIZE│ RBLKSIZE can │

│ │ │ │ V │ = │ N/A │ >= │ be specified. │

│ │ │ │ │ SLRECS+4 │ │RLRECL+4│ SLRECS refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ = │ N/A │ >= │ SLRECS refers │

│ │ │ │ │ SLRECS+4 │ │RLRECL+4│ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ = │ N/A │ >= 9 │ SLRECS refers │

│ │ │ │ │ SLRECS+4 │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ = │ N/A │ >= 9 │ SLRECS refers │

│ │ │ │ │ SLRECS+4 │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ U │ N/A │ N/A │ >= │ SLRECS refers │

│ │ │ │ │ │ │ SLRECL │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│VSAM │FB │VSAM │ │ │RRECSIZE │ │ RRECSIZE refers │

│ │(see │ │ N/A │ N/A │ >= │ N/A │ to the maximum │

│ │note │ │ │ │ SLRECS │ │ record size. │

│ │after │ │ │ │ │ │ SLRECS refers │

│ │table)│ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. RRECSIZE│

│ │ │ │ │ SLRECS │RLRECS\X │ │ refers to the │

│ │ │ │ │ │ │ │ maximum record │

│ │ │ │ │ │ │ │ size. │

│ │ │ │ │ │ │ │ SLRECS refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECS+12 │ │ │ file. │

│ │ │ │ │ │ │ │ SLRECS refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECS │ │ │ SLRECS refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ log.record size. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘

Figure 68 (Part 10 of 16). Relationships between Sending File and Receiving FileAttributes


┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│SRCF │ N/A │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │


│ │ │or │ │ SLRECL─12 │ │ │ SLRECL refers │

│ │ │UNLAB │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ N/A │ = │ SLRECL refers │

│ │ │ │ │ SLRECL─12 │ │RLRECL\x│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ SLRECL refers │

│ │ │ │ │ SLRECL─8 │ │RLRECL+4│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VB │ >= │ N/A │ >= │ SLRECL refers │

│ │ │ │ │ SLRECL─8 │ │RLRECL+4│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VS │ >= │ N/A │ >= 9 │ SLRECL refers │

│ │ │ │ │ SLRECL─8 │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ = │ N/A │ >= 9 │ SLRECL refers │

│ │ │ │ │SLRECS─4 │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ U │ N/A │ N/A │ >= │ SLRECL refers │


│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│SRCF │N/A │VSAM │ │ │RRECSIZE │ │ RBLKSIZE required.│

│ │ │ │ N/A │ N/A │ >= │ N/A │ SLRECL refers │

│ │ │ │ │ │SLRECL─12│ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. │

│ │ │ │ │ SLRECL─12 │RLRECS\X │ │ RRECSIZE refers │

│ │ │ │ │ │ │ │ to the maximum │

│ │ │ │ │ │ │ │ record size. │

│ │ │ │ │ │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │SRCF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Source file│

│ │ │ │ │ SLRECL │ │ │ SLRECL refers to │

│ │ │ │ │ │ │ │ the sending OS/4ðð│

│ │ │ │ │ │ │ │ record length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │DTAF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Data file │

│ │ │ │ │ SLRECL─12 │ │ │ SLRECL refers to │

│ │ │ │ │ │ │ │ the sending OS/4ðð│

│ │ │ │ │ │ │ │ record length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ This combination │

│ │ │ │ │ │ │ │ is not allowed. │

│ │ │ │ │ │ │ │ The sending file │

│ │ │ │ │ │ │ │ must also be │

│ │ │ │ │ │ │ │ a source file. │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│DTAF │ N/A │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │


│ │ │or │ │ SLRECL │ │ │ SLRECL refers │


│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL │ │RLRECL\X│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ V │ >= │ N/A │ >= │ specified. │

│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+4 │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ = │ N/A │ >= 9 │ SLRECL refers │


│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤




│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│DTAF │N/A │VSAM │ │ │RRECSIZE │ │ RRECSIZE refers │



│ │ │ │ │ │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. │

│ │ │ │ │ SLRECL │RLRECS\X │ │ RRECSIZE refers │

│ │ │ │ │ │ │ │ to the maximum │

│ │ │ │ │ │ │ │ record size. │

│ │ │ │ │ │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │SRCF │ N/A │ >= │ N/A │ N/A │ OS/4ðð Source file│

│ │ │ │ │ SLRECL+12 │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ This combination │

│ │ │ │ │ │ │ │ is not allowed. │


│ │ │ │ │ │ │ │ must also be │

│ │ │ │ │ │ │ │ a data file. │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│SAVF │ N/A │PS, │ │ RLRECL │ │ │ RBLKSIZE must not │


│ │ │or │ │ SLRECL │ │ │ SLRECL refers │


│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL │ │RLRECL\x│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │ │ │ RLRECL │ │RBLKSIZE│ RBLKSIZE can │

│ │ │ │ V │ >= │ N/A │ >= │ be specified. │

│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ SLRECL+4 │ │RLRECL+4│ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤




│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ VBS │ >= │ N/A │ >= 9 │ SLRECL refers │


│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤




│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘



┌─────────────┬────────────────────────────────────────────────────────────────┐



├──────┬──────┼──────┬──────┬───────────┬─────────┬────────┬───────────────────┤



├──────┼──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│SAVF │N/A │VSAM │ │ │RRECSIZE │ │ RRECSIZE refers │



│ │ │ │ │ │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ │ ├──────┼───────────┼─────────┼────────┼───────────────────┤


│ │ │ │ FB │ = │ = │ N/A │ SAM ESDS. │

│ │ │ │ │ SLRECL │RLRECS\X │ │ RRECSIZE refers │

│ │ │ │ │ │ │ │ to the maximum │

│ │ │ │ │ │ │ │ record size. │

│ │ │ │ │ │ │ │ SLRECL refers │

│ │ │ │ │ │ │ │ to the sending │

│ │ │ │ │ │ │ │ OS/4ðð record │

│ │ │ │ │ │ │ │ length. │

│ │ ├──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │SRCF │ N/A │ N/A │ N/A │ N/A │ Receiver is an │

│ │ │ │ │ │ │ │ OS/4ðð Source file│

│ │ │ │ │ │ │ │ This combination │

│ │ │ │ │ │ │ │ is not allowed. │


│ │ │ │ │ │ │ │ must also be │

│ │ │ │ │ │ │ │ a save file. │

│ ├──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤

│ │ │DTAF │ N/A │ N/A │ N/A │ N/A │ Receiver is an │

│ │ │ │ │ │ │ │ OS/4ðð Data file. │

│ │ │ │ │ │ │ │ This combination │

│ │ │ │ │ │ │ │ is not allowed. │


│ │ │ │ │ │ │ │ must also be │

│ │ │ │ │ │ │ │ a save file. │

│ ├──────┼──────┼──────┼───────────┼─────────┼────────┼───────────────────┤



│ │ │ │ │ 528 │ │ │ │

└──────┴──────┴──────┴──────┴───────────┴─────────┴────────┴───────────────────┘


Notes:

1. In the preceding figure rules for PS, LAB, or UNLAB data sets apply to Type PIif a single member without directory information is processed.

Record format conversion of Type PO data sets with directory information is notallowed. However, the receiving data set block size can be changed.Therefore, the following conversions are allowed:

� F to FB� FB to F� V to VB� VB to V.

2. If the sending file is a SAM/ESDS on a VSE VSAM data set, it has thefollowing attributes:

� Type VSAM� Record format FB.



Glossary

This glossary defines many of the terms andabbreviations used in this manual. If you do not findthe term you are looking for, refer to the index or to theDictionary of Computing, New York, McGraw-Hill, 1994.

Access Method Services . A utility program thatdefines VSAM data sets and allocates space for them,converts indexed-sequential data sets to key-sequenceddata sets with indexes, modifies data set attributes inthe catalog, facilitates data set portability betweenoperating systems, creates backup copies of data setsand indexes, helps make inaccessible data setsaccessible, and lists data set records and catalogentries.

ACF/VTAM* . Advanced Communications Function forthe Virtual Telecommunications Access Method.

active request . A request that is presently beingscheduled or for which the corresponding file transfer isin progress.

adaptive compression . A method by which theamount of storage required for data can be reduced byreplacing character strings that are repeated withreferences to a directory of such character strings.

added request . A request that has been added to therequest queue.

administrator query command . A type of commandthat causes NetView FTP to retrieve information aboutthe request queue or the requests in it; the informationretrieved is intended for the NetView FTP administrator.Contrast with user query command.

administrator query record . A record containing theinformation NetView FTP retrieves when anadministrator issues an administrator query command.Contrast with user query record.

adopted authority . When a program is created, it canspecify that the program always runs under the programowner’s user profile. A user does not need authorityspecifically given to him for the objects used by theprogram, but uses (adopts) the program owner’sauthority. The user has authority for the objects usedby the program only when he is running the programand other programs called by the program.

Advanced Communications Function for the VirtualTelecommunications Access Method . An IBMlicensed program that controls communication and theflow of data in an SNA network. It providessingle-domain, multiple-domain, and interconnectednetwork capability. VTAM* runs under MVS, VSE, andVM/SP and supports direct control application programs

and subsystems such as NetView FTP andVSE/POWER.

Advanced Function Feature . A set of extra functionsthat extend the capabilities of the NetView FTP V1 MVSbase product.

advanced peer-to-peer networking . Datacommunications support that routes data in a networkbetween two or more APPC systems that are notdirectly attached.

AFF. Advanced Function Feature.

AMS. Access Method Services.

APAR . Authorized Program Analysis Report.

APPC. Advanced Program-to-ProgramCommunication.

APPN. See advanced peer-to-peer networking.

automatic logon retry . NetView FTP’s method foreventually establishing a conversation with a remotesystem. It is used when a server cannot initiate aconversation with a server at a remote system because:

� All the servers at the remote system are busy withother transfers.

� None of the servers at the remote system has beenstarted.

� ACF/VTAM is temporarily unable to find a pathbetween the two servers.

The server at the local system automatically changesthe status of the request from active back to waiting ,and goes on to process the next request in the requestqueue (MVS, VSE, or VM) or request database(OS/400). Later, NetView FTP tries again to processthe request. It keeps trying until it succeeds in initiatinga conversation.

automatic session recovery . NetView FTP’s methodfor automatically reestablishing an interrupted session.

automatic transfer restart . NetView FTP’s method forautomatically restarting a file transfer that wasinterrupted. In the following situations, NetView FTP isnot able to recover a conversation:

� The queue handler or server at either system isterminated.

� The server at either system cannot allocate the filebeing transferred.

� A pre-transfer user-exit routine at either systemrejected the file transfer.


� There is a severe or prolonged conversationoutage.

However, when you create a request, you can specifythat, if one of these situations arises, NetView FTP is tochange the status of the request back to waiting . Theservers at your system will then periodically reprocessthe request until one of them succeeds in restarting thetransfer. After a server restarts the transfer, it resumestransferring the file from the last recorded checkpoint.

basic sequential access method . (1) An accessmethod for storing or retrieving data blocks in acontinuous sequence, using either a sequential accessor a direct access device. (2) In NPM, the method bywhich all PIUs collected for selected LUs can be loggedinto a sequential data set as they pass through VTAMprograms.

BIND. Bind Session.

Bind Session . In SNA, a request to activate a sessionbetween two logical units.

BSAM . Basic sequential access method.

character literal . A symbol, quantity, or constant in asource program that is itself data, rather than areference to data.

checkpoint . A point at which information about thestatus of a file transfer is recorded. If the file transfer isinterrupted, NetView FTP can use this information toresume the file transfer from a point near where theinterruption occurred instead of from the beginning ofthe file.

checkpoint data set . A synonym for checkpoint file.

checkpoint file . A file that contains information aboutthe current status of an active file transfer. If the filetransfer is interrupted, NetView FTP can use thisinformation to resume the file transfer from a point nearwhere the interruption occurred instead of from thebeginning of the file.

checkpoint record . A record of a checkpoint data setor file. One checkpoint record contains the informationneeded to restart one file transfer from a checkpoint.

checkpoint/restart data set . A deprecated term forcheckpoint data set.

checkpoint/restart record . A deprecated term forcheckpoint record.

CL. See control language.

class . See server class.

CLIST. Command list.

command control block . A control block that containsdetails of the queue handler command to be carried out.

command list . A list of commands and controlstatements that is assigned a name. When the name isinvoked (as a command) the commands in the list areexecuted.

completion user exit . Deprecated term forpost-transfer user exit.

compression . A technique for converting data into aform that requires less storage space and lesstransmission time than its original form. Contrast withdecompression. See also SNA compaction and SNAcompression.

condition code . A four-digit decimal value derivedfrom the value a server places in register 15 beforereturning control to the operating system. The digits ofthe condition code consist of the server return codeand, for a server running in single mode, thefile-transfer return code.

continuous mode . A server running mode in which aserver continues running after it has transferred a file.

control language . The set of all commands withwhich a user requests system functions.

control statement . A statement that controls or affectsthe running of a program. For example,NOTAFTER=(‘21:34’,‘87/12/25’) is a control statementthat assigns the value (‘21:34’,‘87/12/25’) to theparameter represented by the keyword NOTAFTER.

conversation . In SNA, a connection between twotransaction programs over an LU-LU session that letsthem communicate with each other while processing atransaction.

conversation level security . In SNA this term isknown as partner end-user verification.

cryptographic key . A parameter that determinescryptographic transformations between plaintext andciphertext.

current request . The request currently being createdor changed by the user of the NetView FTP panels.

DASD. Direct-access storage device.

data set control block . A control block containingspecifications for data sets that are to be created.

data control block parameters . The followingparameters: Record Format, Logical Record Length,and Physical Block Size.

DCB parameters . Data control block parameters.


decompression . A technique for convertingcompressed data back into its original form. Contrastwith compression.

default value . The value that is assigned to aparameter by a program if no value is specified by auser.

dependent LU . Any logical unit (LU) that receives anACTLU over a link. Such LUs can act only assecondary logical units (SLUs) and can have only oneLU-LU session at a time.

direct-access storage device . A storage device forwhich access time is effectively independent of thelocation of the data being accessed.

direct transfer . Transfer of data from one file toanother file without first storing the data in anintermediate file.

distribution-service component . A component ofNetView FTP VM that handles communication with thequeue handler (such as retrieving requests to beprocessed) and with the network (such as establishingconversations and transferring files). In NetView FTPVM, each server consists of one distribution-servicecomponent and up to 32 file-service components.

dynamic allocation . The allocation of a file when it isneeded, not in advance. Contrast with job allocation.

entry sequence . The order in which records arephysically arranged in auxiliary storage.

entry-sequenced data set . A data set whose recordsare loaded without respect to their contents, and whoserelative byte addresses cannot change.

ESDS. Entry-sequenced data set.

exclude members . To choose those members of aPDS that are not to be transferred. Contrast with selectmembers.

exit . A point in a program at which control is passed toanother program.

exit routine . A routine that receives control when aspecified event occurs.

file-service component . A component of NetViewFTP VM that handles file access and the taking ofcheckpoints. In NetView FTP VM, each server consistsof one distribution-service component and up to 32file-service components.

file transfer . The sending and receiving of thecontents of a file.

file-transfer completion message . A message, sentby a server to a user after a file transfer, that describesthe outcome of a file transfer.

file-transfer report . A file, sent by a server to a userafter a file transfer, that describes the outcome of a filetransfer.

file-transfer request . A list of parameters and theirvalues that tell NetView FTP (1) that it is to transfer afile from one system to another, and (2) about the filetransfer and the sending and receiving data sets.

finished request . A request for which thecorresponding file transfer has finished, whethersuccessfully or unsuccessfully.

file pool . A collection of minidisks managed by SFS.It contains user files and directories and associatedcontrol information. Many user’s files and directoriescan be contained in a single file pool.

FTP level . A character that represents the level ofsophistication of an FTP or NetView FTP program.

FTP V2. File Transfer Program Version 2 Release 2.

GDG. Generation data group.

generation data group (GDG) . A collection of datasets kept in chronological order; each data set is ageneration data set.

generation data set . One generation of a generationdata group.

HDAM. Hierarchic direct access method.

hex . Abbreviation of hexadecimal.

hierarchic direct access method . A database accessmethod that uses algorithmic addressability of recordsin a hierarchic direct organization.

hierarchic indexed sequential access method . Adata base access method that uses indexed access torecords in a hierarchic sequential organization.

HISAM. Hierarchic Indexed Sequential Access Method.

ICF. Intersystems Communications Function.

independent LU . A logical unit (LU) that does notreceive an ACTLU over a link. Such LUs can act asprimary logical units (PLUs) or secondary logical units(SLUs) and can have one or more LU-LU sessions at atime.

Intersystems Communications Function .Communications between application programs on anAS/400 system and an application program on a remote

Glossary 195

system are accomplished using the AS/400 systemintersystem communications function (ICF) and theunderlying support.

IMS/VS. Information Management System/VirtualStorage.

input field . An area on a panel in which data isentered.

JCL . Job control language.

job allocation . The allocation of a file by a serverstartup job. The allocation takes place when a server isstarted, which is before (sometimes long before) the filetransfer takes place. Contrast with dynamic allocation.

job control language . A control language used toidentify a job to an operating system and to describethe job’s requirements.

key sequence . In VSAM, the collating sequence ofdata records as determined by the value of the key fieldin each record.

key-sequenced data set . A VSAM data set whoserecords are loaded in key sequence and controlled byan index.

keyword . A part of a control statement that consists ofa specific character string.

KSDS. Key-sequenced data set.

LDS. Linear data set.

linear data set . A VSAM data set that contains databut no control information. A linear data set can beaccessed as a byte string in virtual storage. A lineardata set has no records and a fixed control interval sizeof 4096 bytes.

local . Pertaining to one’s own system.

local-request handler . A server subtask that canprocess a request submitted at the local system andcan initiate a conversation.

log file . A file to which a NetView FTP componentwrites messages.

logical unit . In SNA, a port through which an end useraccesses an SNA network. Each NetView FTP serveris a logical unit.

logical unit name . A name used to represent theaddress of a logical unit.

LU. Logical unit.

LU-LU session . In SNA, a session between twological units (LUs) in an SNA network.

manual transfer restart . NetView FTP’s method forallowing a user to restart a file transfer that wasinterrupted by adding to the queue a new request forthat file transfer.

master password . A password, set by the NetViewFTP system programmer, that lets those who specify itquery, modify, or delete any request in the requestqueue, regardless of whether or not it ispassword-protected, and regardless of who added it tothe queue.

message area . The area of storage to which NetViewFTP writes the messages it issues to an applicationprogram.

mode . The session limits and common characteristicsof the session associated with advancedprogram-to-program (APPC) devices managed as a unitwith a remote location.

mode description . A system object created foradvanced program-to-program (APPC) devices thatdescribes the session limits and the characteristics ofthe session, such as the maximum number of sessionsallowed, maximum number of conversations allowed,and other controlling information for the session.

MVS system . A system with MVS as its operatingsystem.

NetView FTP administrator . If someone knows themaster password, he is called a NetView FTPadministrator. A NetView FTP administrator can query,delete, modify, hold, or release any request regardlessof whether it is password-protected, and regardless ofwho submitted it.

NetView FTP application program . An applicationprogram that adds, queries, modifies, or deletes arequest, or that retrieves information about NetViewFTP.

NetView FTP batch job . A batch job that adds,queries, modifies, or deletes a request, or that retrievesinformation about NetView FTP.

NetView FTP MVS . NetView File Transfer Program forMVS.

NetView FTP partition . A VSE partition that containsthe main components of NetView FTP VSE.

NetView Performance Monitor . An IBM licensedprogram that collects, monitors, analyzes, and displaysdata relevant to the performance of a VTAMtelecommunication network. It runs as an online VTAMapplication program.


network . An interconnected group of nodes.

network job entry facility . A facility that uses thenetwork job-interface (NJI) protocols to allow acomputer system to communicate with other computersystems in a network.

NJE. Network job entry.

node . An endpoint in a link, or a junction common totwo or more links in a network. A deprecated term forserver group.

node ID . Deprecated term for server group.

node ID table . Deprecated term for server group table.

not-after time . The time after which NetView FTP isnot to process a request.

not-before time . The time before which NetView FTPis not to process a request.

NPM. NetView Performance Monitor.

numeric literal . A numeric character or string ofnumeric characters whose value is implicit in thecharacters themselves; for example, 777 is the literal aswell as the value of the number 777.

operational key . Deprecated term for cryptographykey.

originator ID . A string of characters that identifies thejob, started task, or user that added a request to therequest queue.

panel . A predefined image displayed on a terminalscreen.

panel flow . The way which panels are chainedtogether so that a user can move from one to another.

panel layout . The way which the text and the inputfields on a panel are arranged.

partitioned data set . A data set in direct accessstorage that is divided into partitions, called members,each of which can contain a program, part of aprogram, or data.

path information unit . In SNA, a message unitconsisting of a transmission header (TH) alone, or a THfollowed by a basic information unit (BIU) or a BIUsegment.

PDS. Partitioned data set.

PIU. Path information unit

post-conversation user exit . A user exit that passescontrol to a routine at the system at which the

file-transfer request originated. This routine is to runjust after the servers terminate their conversation.

post-transfer user exit . A user exit that passescontrol to a routine that is to run just after a servercloses a file that has been transferred. Formerly calleda completion user exit.

preparation user exit . Deprecated term forpre-transfer user exit.

pre-queuing user exit . A user exit that passes controlto a routine that is to run just after a request issubmitted to NetView FTP and just before NetView FTPadds the request to the queue. Formerly called arequest-queue user exit.

pre-transfer user exit . A user exit that passes controlto a routine that is to run just before a server opens afile that is to be transferred. Formerly called apreparation user exit.

process (a request) . To obtain and try to carry out (arequest).

program temporary fix . A temporary solution ofby-pass of a problem diagnosed by IBM as resultingfrom a defect in a current unaltered release of aprogram.

PTF. Program temporary fix.

QSAM. Queued sequential access method.

query (a request) . To ask for information about (arequest).

queued sequential access method . An extendedversion of the basic sequential access method (BSAM).When this method is used, a queue is formed of (1)input data blocks that are awaiting processing or (2)output data blocks that have been processed and areawaiting transfer to auxiliary storage or to an outputdevice.

remote . Pertaining to a system other than one’s own.

remote-request handler . A server subtask that canaccept a conversation initiated by a local-requesthandler at a remote system.

reason code . A value issued by a program that givesadditional information about a situation described by areturn code.

receiving data set . A data set in which a copy of a filethat has been sent using NetView FTP has beenplaced. Contrast with sending data set.

relative record data set . In VSAM, a data set whoserecords are loaded into fixed-length slots and are

Glossary 197

represented by the relative-record numbers of the slotsthey occupy.

report . Synonym for file-transfer report.

report recipient . A user to whom a server sends afile-transfer report.

request . Synonym for file-transfer request.

request class . A deprecated term for server class.

request control block . A control block that containssome or all of a file-transfer request. Data that doesnot fit in the RCB is put in the request control blockextension.

request control block extension . A control block thatcontains data that does not fit in the request controlblock.

request database . In NetView FTP/400 V3, thedatabase in which NetView FTP stores all requests.

request number . A number that the queue handlerassigns to a request when it adds the request to therequest queue and that is used to identify the request.

request password . A character string, assigned by auser to a request, that prevents users sharing thatuser’s originator ID from deleting or modifying thatuser’s waiting and active requests. If a user specifies arequest password for a request, another user with thesame originator ID must specify either the requestpassword or the master password to be able to deleteor modify the request while it is waiting, or to delete therequest while it is active.

request priority . A number, assigned by a user toeach request, that determines the order in which aserver is to process it. When a server is ready toprocess a request and several requests are eligible, theserver processes the request with the highest priorityfirst.

request queue . In NetView FTP for MVS, VSE, orVM, the file in which NetView FTP stores requests thathave been submitted for processing.

request queue directory . A directory of the contentsof the request queue.

request-queue user exit . Deprecated term forpre-queuing user exit.

request unit . A message unit that contains controlinformation, end-user data, or both.

RRDS. Relative record data set.

RU. Request unit.

return code . A value issued by a program thatdescribes the outcome of an operation performed bythat program.

resident session partner . An FTP V2 MVS or FTPV2 VSE server that runs continuously and can performan indefinite number of file transfers, however, these filetransfers must all be initiated by servers at remotesystems.

SAF. System authorization facility.

SAM. Sequential access method.

saved request . A request that has been created withthe NetView FTP panels and then been saved in anISPF table data set.

scheduling a request . Determining which request isto be obtained, obtaining it, and passing it to a server.

scroll amount . The amount that the list on a panel isscrolled up or down when you enter the UP or DOWNcommand.

select members . To choose those members of a PDSthat are to be transferred. Contrast with excludemembers.

sending data set . A data set, a copy of which is to betransferred using NetView FTP. Contrast with receivingdata set.

sequential access method . See basic sequentialaccess method.

server . A NetView FTP component that establishes oraccepts conversations and that transfers files.

server class . A number or letter, assigned by a userto a request, that specifies which servers can processthat request.

server group . A group of servers (logical units).

server group table . A data set that specifies whichservers make up each server group and that containsinformation about each server.

session . In SNA, a logical connection between twonetwork-addressable units.

SFS. Shared file system.

SFS directory . A group of files. SFS directories canbe arranged to form a hierarchy in which one directorycan contain one or more subdirectories as well as files.

Shared file system . A part of CMS that lets usersorganize their files into groups known as directories and


selectively share those files and directories with otherusers.

SMS. Storage Management Subsystem.

single mode . A server running mode in which a serverstops running after it has transferred a file (or attemptedto transfer a file and failed).

SNA. Systems Network Architecture.

SNA compaction . The transformation of data bypacking two characters in a byte that normally wouldonly hold one character.

SNA compression . The replacement of a string of upto 64 repeated characters by an encoded control byte toreduce the length of the string.

status . The state of a request in the request queue(MVS, VSE, or VM) or request database (OS/400). InNetView FTP for MVS, VSE, or VM, the possiblestatuses are waiting, active, and finished. In NetViewFTP/400, the possible statuses are held, waiting, active,finished, and failed.

Storage Management Subsystem . An MVSsubsystem that helps automate and centralize themanagement of DASD storage. SMS provides thestorage administrator with control over data class,storage class, management class, storage group, andACS routine definitions.

submit (a request) . To give (a request) to NetViewFTP so that NetView FTP can add it to the requestqueue.

symbolic constant . A data item that has anunchanging, predefined value.

Systems Network Architecture . The description ofthe logical structure, formats, protocols, and operatingsequences for transmitting information units through,and for controlling the configuration and operation of,networks. The layered structure of SNA allows theorigin and ultimate destination of information to beindependent of and unaffected by the SNA networkservices and facilities used to transfer that information.

table display panel . A panel that contains a scrollablelist.

user exit . A point in an IBM-supplied program at whicha user-exit routine is given control.

user-exit routine . An exit routine written by a user.

user query command . A type of command thatcauses NetView FTP to retrieve information about therequests in the request queue; the information retrievedis intended for users of NetView FTP. Contrast withadministrator query command.

user query record . A record containing theinformation NetView FTP retrieves when a user issuesa user query command. Contrast with administratorquery record.

user-written file handler . An exit routine, written by auser, that gains access to a file and passes its recordsto NetView FTP, or that retrieves the records fromNetView FTP and writes them to a file.

Virtual Storage Access Method . An access methodfor indexed or sequential processing of fixed- andvariable-length records on direct-access storagedevices. The records in a VSAM data set can beorganized (1) in logical sequence by means of a keyfield (key sequence), (2) in the physical sequence inwhich they are written in the data set, or (3) by meansof a relative-record number.

Virtual Telecommunications Access Method . SeeAdvanced Communications Function for the VirtualTelecommunications Access Method (ACF/VTAM).

VSAM. Virtual Storage Access Method.

VM system . A system with VM as its operatingsystem.

VSE system . A system with VSE as its operatingsystem.

VTAM. Virtual Telecommunications Access Method.See Advanced Communications Function for the VirtualTelecommunications Access Method (ACF/VTAM).

waiting request . A request that is waiting to beprocessed.

Glossary 199


Bibliography

The NetView FTP Library

This manual is part of a library of publications thatdescribe NetView FTP and explain how to use it. Thepublications in this library are:

NetView File Transfer Program for VSE:

NetView FTP Licensed Program Specifications,GH12-5485NetView FTP VSE User’s Guide, SH12-5673NetView FTP VSE Installation, Operation, andAdministration, SH12-5674NetView FTP Customization, SH12-5482NetView FTP Messages and Codes, SH12-5483NetView FTP Parameter Reference, SH12-6052

NetView File Transfer Program for VM:

NetView FTP General Information, GH12-5480NetView FTP Licensed Program Specifications,GH12-5485NetView FTP VM User’s Guide, SH12-5675NetView FTP VM Installation, Operation, andAdministration, SH12-5676NetView FTP Customization, SH12-5482NetView FTP Messages and Codes, SH12-5483

NetView File Transfer Program for OS/400:

NetView FTP General Information, GH12-54806

NetView FTP V1 for OS/400 Licensed ProgramSpecifications, GH12-5777NetView FTP V3 for OS/400 Licensed ProgramSpecifications, GH12-6176NetView FTP V1 for OS/400 Installation andUser’s Guide, SH12-5776NetView FTP V3 for OS/400 Installation andUser’s Guide, SH12-6177

NetView File Transfer Program Version 2 forMVS:

NetView FTP Licensed Program Specifications,GH12-5485NetView FTP V2 MVS User’s Guide,SH12-5656NetView FTP V2 MVS Installation, Operation,and Administration, SH12-5657NetView FTP Customization, SH12-5482NetView FTP Messages and Codes, SH12-5483NetView FTP Parameter Reference, SH12-6052

NetView File Transfer Program Server for AIX,NetView File Transfer Program Client for AIX:

NetView FTP for Workstations: AIX Installationand User’s Guide, SH12-6187NetView FTP Parameter Reference, SH12-6052

NetView File Transfer Program Server/2,NetView File Transfer Program Client/2NetView File Transfer Program Client for DOSand Windows:

NetView FTP for OS/2, DOS, and WindowsWorkstations: Installation and User’s Guide,SH12-6080NetView FTP Parameter Reference, SH12-6052

The unlicensed manuals with prefix SH are alsoavailable as softcopy on the following collection kits:

IBM Networking Softcopy Collection Kit, SK2T-6012IBM Online Library Omnibus Edition: MVSCollection, SK2T-0710IBM Online Library Omnibus Edition: VM Collection,SK2T-2067IBM Online Library Omnibus Edition: VSECollection, SK2T-0060IBM Online Library Omnibus Edition: AIX Collection,SK2T-2066

Related AS/400 PublicationsAS/400 Communications: Advanced Peer-to-PeerNetwork User’s Guide, SC21-8188

AS/400 Communications: AdvancedProgram-to-Program Communication Programmer’sGuide, SC21-8189

AS/400 System Operations: Operator’s Guide,SC21-8082

AS/400 Communications: Programmers Guide,SC21-9590

AS/400 Communications: User’s Guide, SC21-9601

AS/400 Programming: Control LanguageProgrammer’s Guide, SC21-8077

AS/400 Work Management Guide, SC21-8078

6 NetView FTP/400 V1 only.


Related System/370 PublicationsVTAM Programming for LU 6.2, SC31-6410

VTAM Programming, SC31-6409

VSE/VSAM Version 2.2 Commands and Macros,SC33-6532


Index

Special Characters*ADDBEG 122*ADDKEY 122*CTG 109*CTG, disposition 109*DELKEY 123*LAB 107*MERGE 122*MOD 109*MOD, disposition 110*NEW 97, 109*NEW, disposition 109*OLD 97, 109*OLD, disposition 109*PO 107*PS 107*REG 97*REG, disposition 110*REPKEY 123*SHR 109*SHR, disposition 110*UNLAB 107*VSAM 107

Aaccess control 108access method 9access parameters, SFS directory 129access rights 100active, server state 53adaptive compression 8, 93address, disk 127, 128address, internal 127administering NetView FTP/400 V3 51administrator 66administrator interface 51agent 2

parameters 85starting 29, 53

agent and all servers, stopping 54allocation

dynamic 101, 104job 101, 104

AMS parameters 121, 124APAR 145APLRDYDD 105APLSDYDD 105APLxDYDD 105APPC conversation security password 93

application programexample 76writing 76

application program, NetView FTP/400 V3 7AS/400-to-AS/400 line configuration 26AS/400-to-System/370 line configuration 26, 167AS/400-to-System/370 line description 167ASP threshold 14auditability 19AUT 100authorized program analysis report 145authorizing NetView FTP/400 users 23automatic

logon retry 15retry 92transfer restart 110

averagelength 117record multiplier 130record size 126

Bblock size, physical 111, 112blocks, directory 117

Ccanceling a remotely initiated file transfer 55catalog name, VSAM 124changing

a request to retrieve a file 42a request to send a file 41an LU directory entry 59requests 3

check 94checking requests 9CL commands 7, 71CL interface 71cluster

creation 121password 108

CMS file name 101CMS RECEIVE command 106commands

CL 7CMS RECEIVE 106TSO RECEIVE 106

communication configuration 26communication mode 28, 58completion message, file-transfer 6, 14, 106


componentsagent 2interfaces 2server 2

COMPRESS 93compression 8, 93, 163control statement 77copy file-transfer requests 45copying an LU directory entry 60count, volume 119CPU speed 163creating

a new administrator 67a request to retrieve a file 42a request to send a file 34names for receiving files 147

creation, file 121

Ddata

class 131organization 125security 15, 108

data set nameID 101name 101

data-set sequence number 120database, request 3DCB parameter 110DD name 104default disk 128deleting

an administrator 67an LU directory entry 60history file entries 69requests 3

deleting file-transfer requests 45density, tape 115device type 118direction, file-transfer 5directory access parameters, SFS 129directory blocks 117directory, LU 8disk

address 128default 128user ID 128

displayinga file-transfer report 43a request to retrieve a file 42a request to send a file 42log data 44

disposition*CTG 109*MOD 109

disposition (continued)*NEW 109*OLD 109*SHR 109

DLBL statement 101DSCB, model 115dynamic

allocation 101, 104file creation 121

Eentering data in NetView FTP/400 V3 panels 31, 49error recovery 16errors 145ESDS 125example

of an application program 76of using NetView FTP panels 137

exit-routine inputPPXIN1 95PPXIN2 95

EXPDATE 100, 120expiration date 100, 120

Ffailed file-transfer requests 47file

creation 121how NetView FTP creates names for receiving 147ID 104name 95, 104NetView FTP Version 2 MVS parameters 101NetView FTP VM parameters 101NetView FTP VSE parameters 101options 12, 97text description 99types 9

file type*DTAF 96*SAVF 96*SRCF 96

file-transferdirection 5request 3

file-transfer completion message 14, 106file-transfer report 14, 106

completion message 6report 6

file-transfer requestscopying 45deleting 45holding 47releasing 47renaming 46


filemode, internal 127files, what you need to know 9FILOPT 97finished status 6format, record 111

GGDG 115generation data group 115generation data set 115generic 134getting help from NetView FTP/400 V3 33glossary 193group ID, security parameter 108

Hhelp 33history file

deleting 69printing 68sample 69

hold request 88holding requests 3, 47how to

get help from NetView FTP/400 V3 33invoke NetView FTP/400 V3 33use NetView FTP 3

IICCF 106, 108ICF file DVG41I 165ID, file 101identifying remote systems 8improving performance with prestarted jobs 17increments 98indexed cluster 125information file entries 62, 63initial evaluation 145initial number of records 98input fields 31, 49installation prerequisites 21installing NetView FTP/400 V3 21interactive interface 7interface

administrator 51control language (CL) 71

internal address 127internal filemode 127interruption, restart from 92invoke an internal trace 53invoking NetView FTP/400 V3 33

JJES queue 106job allocation 101, 104job catalog, VSAM 124

Kkey length and offset 126keyword 74, 77KSDS 125KSDS option, VSAM 122

Lleft-adjusted volume serial number 119length, key 126length, logical record 112library 95LIKE 132limit scope of the request list 41line configuration 26, 167linear data set 125link

parameters, VM 128password 127, 128

localcomponents 51LU 5server 5

log data, displaying 44logical record length 111, 112logical record size 125logon retry, automatic 15LU directory 8, 28, 57LU directory entry 57

changing 59copying 60deleting 60renaming 61

LU name 5, 58LU nickname, remote 92

Mmachine requirements 161management class 132managing the LU directory 57master catalog, VSAM 124maximum increments 98maximum members 98maximum number of records 98maximum number of servers 85maximum record size 126MAXMBRS 98MAXREC 98

Index 205

MBROPT 97member 96, 97member name 96member options 97message, file-transfer completion 6, 14, 106messages and codes 18minidisk link and access 128mode description 28, 58mode name 58model

DSCB 110, 115name 121, 123password 123

Nname

data set 101DD 101, 104request 88VSAM catalog 124

names, receiving files 147naming conventions 153NetView FTP Version 2 MVS file parameters 101NetView FTP VM file parameters 101NetView FTP VSE file parameters 101NetView FTP/400 V3

application program 7panel 7, 31, 49parameters 77structure 2

network 1network load 163NEWPWD 89nickname of remote LU 58, 92nonindexed cluster 125not-before and not-after date and time 90notification 14, 106number of records per increment 98number of servers to start 86, 87

Ooffset, key 126operating system 58options 97

file 12member 12

order in which NetView FTP/400 V3 displays thepanels 32, 50

originator, request 7, 89

Ppanel flow 32, 50

panels, NetView FTP 7parameters

agent 85DCB 110defaults 155group ID 108NetView FTP/400 V3 77password 108pool ID 129receiving 79, 155request 78, 88sending 79SFS directory access 129subdirectory access 129top directory 129transfer 79, 92user ID 108VM 127VM link 128

passwordAPPC conversation security 15, 93link 127, 128model 123new 89RACF security 15request 7security parameter 108verify 89VM Link 15VSAM 108VSAM cluster 15

performance considerations 163period, retention 120physical block size 111, 112pool ID parameter 129pool size 163post-transfer data queue 173POWER LST queue 106POWER VM writer task 106PPXIN1 95PPXIN2 95prestarted jobs 17prestarted jobs, working with 56primary space quantity 117printing history file entries 68printing information file entries 62printing processing information 62priority, request 89problem evaluation 145processing information 63processing requests 5PURGE parameter 163


Qqueue, JES 106queue, VSE/POWER LST 106

RRACF 108RAVGREC 130, 131RBLKLEN 117RBLKSIZE 114RCDLEN 100RCMSID 103RDATACL 131RDATAID 124RDEN 115, 116RDIRBLK 117reader 106RECEIVE command

CMS 106TSO 106

receiving files, names for 147receiving parameters 79recipient of file-transfer report 14, 106record

format 111, 125length 100length, logical 112size, average and maximum 126

reference DD statement 133releasing requests 3, 47remote

check 94error messages 18LU 5LU nickname 58server 5system, identifying 8

remotely started components 55removing

information file entries 63restart file entries 64

renamingan LU directory entry 61file-transfer requests 46

report recipient 14, 106report, file-transfer 6, 14, 106reporting 6REQHLD 88REQNAME 88request

changing 3checking 9creating 34database 3deleting 3

request (continued)file-transfer 3holding 3name 88not-before and not-after date and time 90originator 7, 89parameters 78, 88password 7priority 89processing 90releasing 3states 2

restart 92automatic transfer 92, 110file entries removing 64from interruption 92transfer 16

restarting failed file-transfer requests 47restarts, maximum number of 86retention period 120retry

automatic 92automatic logon 15interval 86

RFILE 95RFILEID 102RFNAME 105RFTYPE 107RGDGMDI 115right-adjusted volume serial number 119RINDEXID 124RKEYS 126RKSDS 123RLIKE 132RLINKP 129RLRECL 114RMBR 96RMGMTCL 132RMODELID 123RMSERVER 92RMTCHK 94RPERIOD 120RQORG 89RQPTY 89RRECFM 112RRECORG 125RRECSIZE 126RREFDD 133RRNID 106RRUID 106RSECMOD 134RSECURP 109RSFSP 130RSPCPRIM 117RSPCSEC 117

Index 207

RSPCUNIT 117RSTORCL 135RTDISP 110RTRY 86RU size 163RUCATID 125RUNIT 118running mode remote server 105RVLRECL 125RVOLCNT 119RVOLSER 119

SSBLKSIZE 114SCHDL 91SCMSID 103SDLC line 167secondary space quantity 117security

access authority 15access rights 100APPC 15APPC conversation security 15APPC password 93model 134parameters 108RACF 15RACF security 15VM Link password 15VSAM cluster password 15

sending parameters 79sequence number, data set 120serial number, volume 118server

local 5parameters 87prefix 86remote 8running mode 105starting 53states 2stop mode 87stopping 54suffix 86, 88to start 87

server statesactive 53waiting 53

session 5setting

up the communication configuration 26up the LU directory 28

SFILE 95SFILEID 102

SFNAME 105SFS directory access parameters 129SFTYPE 107SIZE 98size, physical block 112SLINKP 129SLRECL 114SMBR 96SMS parameters 130SNA network 1space

parameters 116quantity, primary and secondary 117units 116

specifying parameters 74SRECFM 112SRVMODE 105SSECURP 109SSFSP 130start

a trace 53server 87

startingNetView FTP/400 V3 33servers 53the agent 29, 53the NetView FTP/400 V3 subsystem 67

startup file 65statement

control 77DLBL 101TLBL 101

states 2states of a server

active 53waiting 53

status 15, 16finished 6

step catalog, VSAM 124stop

a remotely started server 55, 56a trace 54

stoppingservers 54the agent and all servers 54

storage class 135structure of NetView FTP/400 V3 2subdirectory parameter 129submitting an APAR 145subsystem, starting 67SUCATID 125SUNIT 118SVOLSER 119


Ttape density 110, 115TEXT 99text description 99TLBL statement 101top directory 129trace

starting 53stopping 54

transfer parameters 79, 92transfer restart 16

automatic 110manual restart 92

TSO RECEIVE command 106type

device 118of sending and receiving files 107

typesof files NetView FTP can transfer 9of parameters 77

Uunits, space 116user exit 95user ID 108, 127, 128

disk 127, 128security parameter 108

user-exit input 173users, authorizing to use NetView FTP/400 23

Vvalue 34, 74, 77verifying the installation of NetView FTP/400 V3 29VM parameters 127volume count 119volume serial number 118, 122VRYPWD 89VSAM

catalog name 124KSDS option 122password 108

VSE/POWER LST queue 106VSE/POWER VM writer task 106

WWAITFILE 165waiting, server state 53what to do if an error occurs in NetView FTP/400

V3 145what you need to know about files 9working with prestarted jobs 56writing application programs 76

XxBLKSIZE 114xCMSID 103xFILE 95xFILEID 102xFNAME 105xFTYPE 107xLINKP 129xLRECL 114xRECFM 112xSECURP 109xSEQNO 120xSFSP 130xUNIT 118xVOLSER 119

Index 209

Your comments, please ...

NetViewFile Transfer ProgramVersion 3 for OS/400Installation and User's Guide

Publication No. SH12-6177-01

Use this form to tell us what you think about this manual. If you have found errors in it, or if you want toexpress your opinion about it (such as organization, subject matter, appearance) or make suggestions forimprovement, this is the form to use.

To request additional publications, or to ask questions or make comments about the functions of IBMproducts or systems, you should talk to your IBM representative or to your IBM authorized remarketer.This form is provided for comments about the information in this manual and the way it is presented.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your commentsin any way it believes appropriate without incurring any obligation to you.

If you mail this form to us, be sure to print your name and address below if you would like a reply.

You can also send us your comments using:

� A FAX machine. The number is: +49–7031–166609.

� Internet. The address is: [email protected].

� IBMLink. The address is: SDFVM1(GADLID).

� IBM Mail Exchange. The address is: DEIBM3P3 at IBMMAIL.

Please include the title and publication number (as shown above) in your reply.

Name Address

Company or Organization

Phone No.

Cut or FoldAlong Line

Cut or FoldAlong Line

Your comments, please ...SH12-6177-01 IBM

Fold and Tape Please do not staple Fold and Tape

PLACEPOSTAGESTAMPHERE

IBM Deutschland Entwicklung GmbHInformation Development, Dept. 0446Postfach 138071003 BoeblingenGermany

Fold and Tape Please do not staple Fold and Tape

SH12-6177-01

IBM

Program Number: 5733-196 (Version 3 Release 1)5798-TBG (Version 3 Release 6)

Printed in Denmark by IBM Danmark A/S

SH12-6177-ð1

DSMBEG323I STARTING PASS 2 OF 2.+++EDF248W Page check: document requires more passes or extended cross-reference to resolve correctly. (Page 135 File: DVGU4B07)DSMMOM397I '.EDFPGCK' WAS IMBEDDED AT LINE 320 OF '.EDFHEAD1'DSMMOM397I '.EDFHEAD1' WAS IMBEDDED AT LINE 31 OF 'DVGU4B07'DSMMOM397I 'DVGU4B07' WAS IMBEDDED AT LINE 46 OF 'DVGU4MST'

Documents

NetView File Transfer Program Version 3 for OS/400 IBMpublib.boulder.ibm.com/tividd/td/netviewFTP/SH12-6177-01/...NetView File Transfer Program Version 3 for OS/400 A C 12 H ff W g