DOCSLIB.ORG

IBM I Version 7.2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM I Version 7.2 IBM i Version 7.2 Networking File Transfer Protocol IBM Note Before using this information and the product it supports, read the information in “Notices” on page 157. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1998, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents FTP on IBM® i.........................................................................................................1 What's new for IBM i 7.2..............................................................................................................................1 PDF file for File Transfer Protocol................................................................................................................1 Scenarios: FTP..............................................................................................................................................1 Scenario: Transferring a file from a remote host...................................................................................2 Scenario: Securing FTP with SSL............................................................................................................3 Configuration details.........................................................................................................................4 Creating and operating a local CA on the MyCo system.............................................................4 IBM i FTP: Enabling SSL for MyCo's FTP server..........................................................................5 Exporting a copy of MyCo's local CA certificate to a file.............................................................6 Creating an *SYSTEM certificate store on TheirCo's system..................................................... 6 Importing MyCo's local CA certificate into TheirCo's *SYSTEM certificate store......................6 Specifying MyCo's local CA as a trusted CA for TheirCo's FTP client.........................................7 Configuring the FTP server on IBM i............................................................................................................ 7 Configuring FTP server in System i Navigator........................................................................................8 Configuring FTP servers for graphical FTP clients and Web tools........................................................ 8 File and directory entries in IBM i format.........................................................................................9 File and directory entries in UNIX-style format............................................................................... 9 Configuring anonymous FTP................................................................................................................ 11 Preparing for anonymous FTP........................................................................................................ 12 Writing exit programs for anonymous FTP.....................................................................................13 Creating an IBM i user profile: ANONYMOUS................................................................................ 14 Creating a public library or directory..............................................................................................14 Installing and registering exit programs........................................................................................ 14 Installing exit programs............................................................................................................ 15 Registering exit programs......................................................................................................... 15 Securing FTP on IBM i................................................................................................................................15 Preventing FTP server access on IBM i................................................................................................16 Preventing the FTP server from starting automatically on IBM i.................................................. 16 Preventing access to FTP ports on IBM i........................................................................................16 Controlling FTP access on IBM i.......................................................................................................... 17 Using SSL to secure the FTP server on IBM i.......................................................................................18 Creating a local CA on IBM i........................................................................................................... 19 Associating a certificate with the FTP server on IBM i.................................................................. 19 Requiring client authentication for the FTP server........................................................................ 20 Enabling SSL on the FTP server......................................................................................................21 Securing FTP clients with TLS or SSL...................................................................................................21 Securing FTP with Kerberos authentication........................................................................................ 23 Managing access using FTP exit programs..........................................................................................25 Managing access using System i Navigator.........................................................................................26 Monitoring incoming FTP users............................................................................................................26 Managing the FTP server........................................................................................................................... 27 Starting and stopping the FTP server.................................................................................................. 27 Setting the number of available FTP servers.......................................................................................27 Improving FTP server performance with configurable subsystem support.......................................28 Using the FTP client on the IBM i platform............................................................................................... 28 Starting and stopping a client session.................................................................................................28 Server timeout considerations.............................................................................................................32 Transferring files with FTP................................................................................................................... 32 Running FTP in unattended mode using a batch job on IBM i ........................................................... 33 Simple example: Batch FTP............................................................................................................33 iii Complex example: Batch FTP........................................................................................................ 35 Example: Creating a CL program to start FTP.......................................................................... 35 Example: Creating the FTP input file (FTCPDMS).....................................................................36 Example: CL program for submitting the FTPBATCH job.........................................................38 Example: Checking the FTP output file for errors.................................................................... 38 FTP reference information.........................................................................................................................41 FTP server subcommands on i5/OS.................................................................................................... 41 FTP client subcommands on IBM i...................................................................................................... 60 FTP exit programs................................................................................................................................ 95 Request validation exit point: client and server............................................................................ 96 Example: FTP client or server Request Validation exit program in CL code............................97 Example: FTP Server Request Validation exit program in ILE RPG code................................ 99 VLRQ0100 exit point format................................................................................................... 103 FTP server logon exit point...........................................................................................................107 Example: FTP Server Logon exit program in CL code............................................................ 109 Example: FTP Server Logon exit program in C code.............................................................. 110 Example: FTP Server Logon exit program in ILE RPG code................................................... 117 TCPL0100 exit point format....................................................................................................119 TCPL0200 exit point format....................................................................................................123
Load more

Recommended publications
  • What Is Peer-To-Peer File Transfer? Bandwidth It Can Use
    sharing, with no cap on the amount of commonly used to trade copyrighted music What is Peer-to-Peer file transfer? bandwidth it can use. Thus, a single NSF PC and software. connected to NSF’s LAN with a standard The Recording Industry Association of A peer-to-peer, or “P2P,” file transfer 100Mbps network card could, with KaZaA’s America tracks users of this software and has service allows the user to share computer files default settings, conceivably saturate NSF’s begun initiating lawsuits against individuals through the Internet. Examples of P2P T3 (45Mbps) internet connection. who use P2P systems to steal copyrighted services include KaZaA, Grokster, Gnutella, The KaZaA software assesses the quality of material or to provide copyrighted software to Morpheus, and BearShare. the PC’s internet connection and designates others to download freely. These services are set up to allow users to computers with high-speed connections as search for and download files to their “Supernodes,” meaning that they provide a How does use of these services computers, and to enable users to make files hub between various users, a source of available for others to download from their information about files available on other create security issues at NSF? computers. users’ PCs. This uses much more of the When configuring these services, it is computer’s resources, including bandwidth possible to designate as “shared” not only the and processing capability. How do these services function? one folder KaZaA sets up by default, but also The free version of KaZaA is supported by the entire contents of the user’s computer as Peer to peer file transfer services are highly advertising, which appears on the user well as any NSF network drives to which the decentralized, creating a network of linked interface of the program and also causes pop- user has access, to be searchable and users.
    [Show full text]
  • File Formats
    man pages section 4: File Formats Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–3945–10 September 2004 Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Ecaccess User Guide
    ECaccess User Guide User Support Operations Department Version 3.3.0 May 2009 c Copyright 2009 European Centre for Medium-Range Weather Forecasts Shinfield Park, Reading, RG2 9AX, United Kingdom Literary and scientific copyrights belong to ECMWF and are reserved in all countries. The information within this publication is given in good faith and considered to be true, but ECMWF accepts no liability for error, omission and for loss or damage arising from its use. CONTENTS Contents 1 Introduction 3 2 Ecaccess concepts 4 2.1 ECaccess gateway ......................................... 4 2.2 Using an ECaccess gateway ................................... 5 2.3 Plugins ............................................... 5 3 Security authentication 7 3.1 ECaccess certificate ........................................ 7 3.2 ECcert command ......................................... 7 4 Unattended file transfers initiated from ECMWF 10 4.1 Target location ........................................... 10 4.2 ECtrans command ......................................... 11 4.2.1 Transfer to a Member State host via gateway ....................... 12 4.2.2 Transfer from a Member State host via gateway ...................... 12 5 Shell commands 14 5.1 Environment ............................................ 14 5.2 Access to Shell commands .................................... 15 5.3 General information ........................................ 15 5.4 File management ......................................... 15 5.5 Batch job management .....................................
    [Show full text]
  • Argus Research (July 2020)
    EQUITY RESEARCH REPORT July 13, 2020 MOLECULAR DATA INC. (NCM: MKD) Founded in 2013, China-based Molecular Data operates an e-commerce platform that KEY STATISTICS connects and serves participants of the Chinese chemicals industry across the value chain. Key Stock Statistics COMPANY HIGHLIGHTS Recent price (7/7/20) $2.40 * MKD: Connecting China’s Chemical Industry Value Chain 52 week high/low $11.80/$0.57 ADS Outstanding (M) 115 * In our view, Molecular Data has assembled a comprehensive network that can capture value across multiple previous pain points in China’s fragmented chemicals industry. Market cap (M) $276.0 Dividend Nil * After several years of organically building platform capabilities to include financial services, warehousing, logistics and software as a service (SaaS) offerings, Molecular Yield Nil Data should now be able to diversify its revenue stream beyond its core chemical direct e-commerce sales. This should lead to enhanced profit margins and, ultimately, sustainable Sector Overview profitability. Sector Materials * At the end of 2019, Molecular Data completed an initial public offering that yielded net Sector % of S&P 500 2.5% proceeds of approximately $55 million. As a result, we view the company as well posi- tioned to invest in its integrated e-commerce platform with new higher-margin services, and to pursue the acquisition of new capabilities and services globally. Financials ($M) * Although we expect near-term financial results to be impacted by the COVID-19 outbreak, Cash & Mkt Securities 8.3 which forced many customers and suppliers to halt operations throughout the first half of Debt 2.0 2020, we are encouraged by continued robust traffic on the Molbase platform.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • Supplementary Material for Traditional Agricultural Practices and the Sex Ratio Today Alberto Alesina1,2, Paola Giuliano3,2,*, Nathan Nunn1,2
    Supplementary Material for Traditional agricultural practices and the sex ratio today Alberto Alesina1,2, Paola Giuliano3,2,*, Nathan Nunn1,2 1 Harvard University. 2 NBER. 3 UCLA. *Correspondence to: [email protected] The Supplementary Material provides details on the data sources and the robustness of the analysis for the results derived in the paper. Additional details on the Ethnographic Atlas The Ethnographic Atlas was constructed by George Peter Murdock. It contains ethnographic information for 1,265 ethnic groups worldwide. The period in which the information was collected varies by ethnicity, with the earliest observation dates coming from ethnicities in the Old World (where early written evidence is available) and the most recent information dating around the 20th century, for those parts of the world without a written history and directly observed by anthropologists. All societies are observed prior to industrialization. In total, 23 ethnicities are observed during the 17th century or earlier, 16 during the 18th century, 310 during the 19th century, 876 between 1900 and 1950, and 31 after 1950. For nine ethnicities, an exact year is not provided. The variable v39 classifies each ethnic group as being in one of the following three categories: (1) the plough was absent, (2) the plough existed at the time the group was observed, but it was not aboriginal, and (3) the plough was aboriginal, having existed prior to contact. Using this information, we construct an indicator variable that equals one if the plough was ever adopted during the pre-industrial period (whether aboriginal or not) and zero otherwise. Of the 1,156 ethnicities for which information exists, for 997 the plough was absent, for 141 the plough was adopted (and aboriginal), and for 18 it was adopted, but after European contact.
    [Show full text]
  • Resource Management: Linux Kernel Namespaces and Cgroups
    Resource management: Linux kernel Namespaces and cgroups Rami Rosen [email protected] Haifux, May 2013 www.haifux.org 1/121 http://ramirose.wix.com/ramirosen TOC Network Namespace PID namespaces UTS namespace Mount namespace user namespaces cgroups Mounting cgroups links Note: All code examples are from for_3_10 branch of cgroup git tree (3.9.0-rc1, April 2013) 2/121 http://ramirose.wix.com/ramirosen General The presentation deals with two Linux process resource management solutions: namespaces and cgroups. We will look at: ● Kernel Implementation details. ●what was added/changed in brief. ● User space interface. ● Some working examples. ● Usage of namespaces and cgroups in other projects. ● Is process virtualization indeed lightweight comparing to Os virtualization ? ●Comparing to VMWare/qemu/scaleMP or even to Xen/KVM. 3/121 http://ramirose.wix.com/ramirosen Namespaces ● Namespaces - lightweight process virtualization. – Isolation: Enable a process (or several processes) to have different views of the system than other processes. – 1992: “The Use of Name Spaces in Plan 9” – http://www.cs.bell-labs.com/sys/doc/names.html ● Rob Pike et al, ACM SIGOPS European Workshop 1992. – Much like Zones in Solaris. – No hypervisor layer (as in OS virtualization like KVM, Xen) – Only one system call was added (setns()) – Used in Checkpoint/Restart ● Developers: Eric W. biederman, Pavel Emelyanov, Al Viro, Cyrill Gorcunov, more. – 4/121 http://ramirose.wix.com/ramirosen Namespaces - contd There are currently 6 namespaces: ● mnt (mount points, filesystems) ● pid (processes) ● net (network stack) ● ipc (System V IPC) ● uts (hostname) ● user (UIDs) 5/121 http://ramirose.wix.com/ramirosen Namespaces - contd It was intended that there will be 10 namespaces: the following 4 namespaces are not implemented (yet): ● security namespace ● security keys namespace ● device namespace ● time namespace.
    [Show full text]
  • ERDA User Guide
    User Guide 22. July 2021 1 / 116 Table of Contents Introduction..........................................................................................................................................3 Requirements and Terms of Use...........................................................................................................3 How to Access UCPH ERDA...............................................................................................................3 Sign-up.............................................................................................................................................4 Login................................................................................................................................................7 Overview..........................................................................................................................................7 Home................................................................................................................................................8 Files..................................................................................................................................................9 File Sharing and Data Exchange....................................................................................................15 Share Links...............................................................................................................................15 Workgroup Shared Folders.......................................................................................................19
    [Show full text]
  • HP ESA-L1500A Spectrum Analyzer Programmer's Guide
    Programmer’s Guide HP ESA-L1500A Spectrum Analyzer HEWLETT@’ r!!a PACKARD HP Part No. E4411-90003 Printed in USA January 1997 0 Copyright Hewlett-Packard Company 1997. All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. 1400 Fountaingrove Parkway, Santa Rosa CA, 95403-1799, USA The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, in- cluding but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, per- formance, or use of this material. The following safety symbols are used throughout this manual. Familiarize your- self with the symbols and their meaning before operating this instrument. CAUTION Caution denotes a hazard. It calls attention to a procedure that, if not correctly performed or adhered to, would result in damage to or destruction of the instrument. Do not proceed beyond a caution until the indicated conditions are fully understood and met. WARNING: Warning denotes a hazard. It calls attention to a procedure which, if not correctly performed or adhered to, could result in injury or loss of life. Do not proceed beyond a warning note until the indicated conditions are fully understood and met. WARNING: This is a Safety Class 1 Product (provided with a protective earthing ground incorporated inthe power cord). The mains plug shall only be inserted in a socket outlet provided with a protective earth contact.
    [Show full text]
  • Transferring Files Using HTTP Or HTTPS
    Transferring Files Using HTTP or HTTPS Cisco IOS Release 12.4 provides the ability to transfer files between your Cisco IOS software-based device and a remote HTTP server using the HTTP or HTTP Secure (HTTPS) protocol. HTTP and HTTPS can now be specified as the targets and source locations in Cisco IOS command-line interface (CLI) commands that use file system prefixes such as the copy command. • Finding Feature Information, page 1 • Prerequisites for Transferring Files Using HTTP or HTTPs, page 1 • Restrictions for Transferring Files Using HTTP or HTTPs, page 2 • Information About File Transfers Using HTTP or HTTPs, page 2 • How to Transfer Files Using HTTP or HTTPs, page 2 • Configuration Examples for the File Transfer Using HTTP or HTTPs, page 9 • Additional References, page 10 • Feature Information for Transferring Files Using HTTP or HTTPS, page 12 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Transferring Files Using HTTP or HTTPs To copy files to or from a remote HTTP server, your system must support the HTTP client feature, which is integrated in most Cisco IOS software images.
    [Show full text]
  • FTP Plug-In User Guide 2017.1 May 2017 Copyright © 2001-2017 Perforce Software
    FTP Plug-In User Guide 2017.1 May 2017 Copyright © 2001-2017 Perforce Software. All rights reserved. Perforce software and documentation is available from www.perforce.com. You can download and use Perforce programs, but you can not sell or redistribute them. You can download, print, copy, edit, and redistribute the documentation, but you can not sell it, or sell any documentation derived from it. You can not modify or attempt to reverse engineer the programs. This product is subject to U.S. export control laws and regulations including, but not limited to, the U.S. Export Administration Regulations, the International Traffic in Arms Regulation requirements, and all applicable end-use, end-user and destination restrictions. Licensee shall not permit, directly or indirectly, use of any Perforce technology in or by any U.S. embargoed country or otherwise in violation of any U.S. export control laws and regulations. Perforce programs and documents are available from our Web site as is. No warranty or support is provided. Warranties and support, along with higher capacity servers, are sold by Perforce Software. Perforce Software assumes no responsibility or liability for any errors or inaccuracies that might appear in this book. By downloading and using our programs and documents you agree to these terms. Perforce and Inter-File Branching are trademarks of Perforce Software. All other brands or product names are trademarks or registered trademarks of their respective companies or organizations. Any additional software included within Perforce
    [Show full text]
  • How Is Dynamic Symbolic Execution Different from Manual Testing? an Experience Report on KLEE
    How is Dynamic Symbolic Execution Different from Manual Testing? An Experience Report on KLEE Xiaoyin Wang, Lingming Zhang, Philip Tanofsky University of Texas at San Antonio University of Texas at Dallas Outline ๏ Background ๏ Research Goal ๏ Study Setup ๏ Quantitative Analysis ๏ Qualitative Analysis ๏ Summary and Future Work "2 /27 Background ๏ Dynamic Symbolic Execution (DSE) •A promising approach to automated test generation •Aims to explore all/specific paths in a program •Generates and solves path constraints at runtime ๏ KLEE •A state-of-the-art DSE tool for C programs •Specially tuned for Linux Coreutils •Reported higher coverage than manual testing "3 /27 Research Goal ๏ Understand the ability of state-of-art DSE tools ! ๏ Identify proper scenarios to apply DSE tools ! ๏ Discover potential opportunities for enhancement "4 /27 Research Questions ๏ Are KLEE-based test suites comparable with manually developed test suites on test sufciency? ๏ How do KLEE-based test suites compare with manually test suites on harder testing problems? ๏ How much extra value can KLEE-based test suites provide to manually test suites? ๏ What are the characteristics of the code/mutants covered/killed by one type of test suites, but not by the other? "5 /27 Study Process KLEE tests reduced KLEE tests program manual tests coverage bug finding quality metrics "6 /27 Study Setup: Tools ๏ KLEE •Default setting for ๏ GCOV test generation •Statement coverage •Execute each program collection for 20 minutes ๏ MutGen •Generates 100 mutation faults for each program
    [Show full text]