DOCSLIB.ORG

Chapter 1. Customizing Netview FTP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chapter 1. Customizing Netview FTP NetView IBM Customization SH12-5482-06 NetView IBM Customization SH12-5482-06 Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page v. Seventh Edition, December 1994 This is a major revision of, and obsoletes, SH12-5482-05. This edition applies to Release 1 Modification Level 1 of NetView File Transfer Program for VSE (5686-013) Release 1 Modification Level 1 of NetView File Transfer Program for VM (5684-048) Release 2 Modification Level 1 of NetView File Transfer Program for MVS Version 2 (5685-108) and to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters. 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 the address below. IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you may address your comments to the following address: IBM Deutschland Entwicklung GmbH Information Development, Dept. 0446 Postfach 1380 71003 Boeblingen Germany When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1988, 1994. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Notices . v Programming Interfaces . v Trademarks and Service Marks ............................ vi About This Book ................................... vii Abbreviations and Special Terms .......................... vii Chapter 1. Customizing NetView FTP ....................... 1 Special Considerations for MVS/XA or MVS/ESA .................. 2 User-Written File Handler .............................. 2 Pre-Queuing User-Exit Routine ........................... 2 Pre-Transfer User-Exit Routine ........................... 2 Post-Transfer User-Exit Routine ........................... 2 Post-Conversation User-Exit Routine ........................ 2 Chapter 2. Writing a User-Written File Handler ................. 3 Invoking a User-Written File Handler ......................... 3 Coding a User-Written File Handler .......................... 4 Considerations when Implementing a User-Written File Handler ........ 5 Coding the OPEN Function ............................. 6 Coding the GET Function .............................. 7 Coding the PUT Function .............................. 9 Coding the POINT Function ............................ 10 Coding the CLOSE Function ............................ 11 Designing a User-Written File Handler without Checkpointing .......... 13 Designing a User-Written File Handler with Checkpointing ............ 14 Checkpointing for the OPEN Function ...................... 14 Checkpointing for the PUT Function ....................... 15 Specifying Checkpoint Record Key Data ..................... 16 Specifying Checkpoint Record Information .................... 17 Writing a Checkpoint Record to the Checkpoint File .............. 18 Implementing Restart from Checkpoint for an Automatic Session Recovery (LU 0) . 19 Implementing Restart from Checkpoint for a Transfer Restart ........ 20 Using the User-Written File-Handler Interfaces ................... 23 Using the User File-Handler Parameter List ................... 23 Using the CALL Argument List .......................... 31 Presenting Information Parameters to the User-Written File Handler .... 32 Using the Registers ................................. 33 Sequence of Function Calls for a User-Written File Handler ........... 34 Normal File Transfer ................................ 34 Restarted File Transfer ............................... 35 File Transfer with Automatic Session Recovery (LU 0) ............ 36 Migrating a User-Written File Handler to NetView FTP V2.2 MVS ........ 37 Chapter 3. Writing a Pre-Queuing User-Exit Routine ............. 39 What the Pre-Queuing User-Exit Routine Does .................. 40 Modifying a Request Password .......................... 40 Modifying a Server Class .............................. 41 Modifying a Request Priority ............................ 41 Copyright IBM Corp. 1988, 1994 iii Modifying a Server Group Name or Remote LU Name ............ 41 Modifying the Wait Time .............................. 42 Changing Parameters . 42 Coding the Pre-Queuing User-Exit Routine ..................... 43 Using the Application Program Parameter List (APL) ............. 43 Using the Application Program Parameter List Extension (APX) ....... 43 Using the Registers ................................. 43 Specifying Return Codes .............................. 44 Chapter 4. Writing a Pre-Transfer User-Exit Routine ............. 45 What the Pre-Transfer User-Exit Routine Does .................. 47 Changing Parameters . 48 Coding a Pre-Transfer User-Exit Routine ...................... 52 Calling the Pre-Transfer User-Exit Routine ................... 52 Using the Application Program Parameter List (APL) ............. 53 Using the Application Program Parameter List Extension (APX) ....... 53 Passing User-Specific Information ........................ 53 Using the Registers ................................. 53 Specifying Return Codes .............................. 54 Passing Messages to the Transfer Program ................... 55 Using the Trace Facility .............................. 55 Chapter 5. Writing a Post-Transfer User-Exit Routine ............ 57 What the Post-Transfer User-Exit Routine Does .................. 58 Changing Parameters . 58 Coding a Post-Transfer User-Exit Routine ..................... 58 Calling a Post-Transfer User-Exit Routine .................... 58 Using the Application Program Parameter List (APL) ............. 59 Passing User-Specific Information ........................ 60 Using the Registers ................................. 60 Specifying Return Codes .............................. 61 Passing Messages to the Transfer Program ................... 61 Using the Trace Facility .............................. 61 Migrating DVGJOBS to NetView FTP V2.2 MVS .................. 61 Examples of Using DVGJOBS in NetView FTP MVS ............. 63 How DVGJOBS Uses the Value of the Exit Routine Input Parameter .... 63 How DVGJOBS Modifies Submitted Jobs .................... 64 How to Submit a Job That Has Just Been Transferred ............ 66 The DVGEXJOB Sample Post-Transfer User-Exit Routine for NetView FTP VSE . 66 What DVGEXJOB Does .............................. 66 How to Install DVGEXJOB ............................. 67 How to Invoke DVGEXJOB ............................ 67 Syntax of the User-Exit Routine Input Parameter ................ 67 How DVGEXJOB Works in NetView FTP VSE ................. 70 How DVGEXJOB Uses the Value of the Exit Routine Input Parameter ... 70 Post-Transfer User-Exit Routine for NetView FTP VM to Run a REXX EXEC . 71 Installing DVGEXEC . 71 Functions Performed by DVGEXEC ....................... 71 Invoking DVGEXEC . 72 Creating a Spool File Using the Pre- and Post-Transfer User-Exit Routines .. 73 Using the Spool-File Routine DVGSPOOL (NetView FTP VM) ........ 73 Using the Spool-File Routine DVGMXXMT (NetView FTP V2 MVS) ..... 75 iv NetView FTP Customization Chapter 6. Writing a Post-Conversation User-Exit Routine ......... 79 When a Post-Conversation User-Exit Routine Is Called .............. 79 What a Post-Conversation User-Exit Routine Can Do ............... 79 Changing Parameters . 80 How the Transfer Program Handles Actions of the Post-Conversation User-Exit Routine . 80 Considerations when Coding a Post-Conversation User-Exit Routine ...... 81 Chapter 7. Communicating with User-Exit Routines ............. 83 Sequence of Calls to User-Exit Routines ...................... 84 Exceptions to the Calling Sequence ......................... 84 Data Areas for Communicating between User-Exit Routines ........... 88 Rules for Modification of Data Areas ......................... 89 Exceptional Situations in Data Area Flow ...................... 91 Calling Sequence and Data Flow .......................... 91 Chapter 8. Considerations when Designing User-Exit Routines ...... 93 Accessing Data Sets Involved in a File Transfer .................. 93 Combining User-Exit Routines ............................ 93 How the Pre-Transfer and Post-Transfer User-Exit Routines Work Together . 94 Sequence of Calls for User-Exit Routines ...................... 94 Case 1: File-Transfer Request Is Obtained by the Sending Transfer Program (LU 6.2) . 95 Case 2: File-Transfer Request Is Obtained by the Receiving Transfer Program (LU 6.2) ................................. 98 Chapter 9. Writing a Security/Statistics Collection User-Exit Routine .. 101 Chapter 10. Issuing Messages from User-Exit Routines .......... 103 The Message Area .................................. 103 Number of Messages ............................... 104 Length of Message ................................ 104 Text of Message .................................. 104 Messages for a Nonzero Return Code ...................... 105 Chapter 11. Using the Trace Facility ...................... 107 Invoking a Trace ................................... 109 Chapter 12. Using the APL ............................ 111 Layout of the APL .................................
Load more

Recommended publications
  • Allgemeines Abkürzungsverzeichnis
    Allgemeines Abkürzungsverzeichnis L.
    [Show full text]
  • Networking Standards Mark Davies, Digital Equipment Corporation
    N92-12499 Networking Standards Mark Davies, Digital Equipment Corporation ABSTRACT The enterprise network is currently a multivendor environment consisting of many defacto and proprietary standards. During the 1990s, these networks will evolve towards networks which are based on international standards in both the LAN and WAN space. Also, you can expect to see the higher level functions and applications begin the same transition. The Open Network Advantage Market Requirements OPEN NETWORKS!!! Multi-protocol, multi-platform, multi-vendor networks working together International AND defacto standards Effortless communications within and between enter- prises Ability to move to standards at own pace What is an Open System? Defined as: A vendor-neutral computing environment: - compliant with International and defacto standards - permits system and network interoperability or software applications portability - includes consistency of data and human access - satisfies one or more of a business's functional requirements Standards Benefits from networks based on international and defacto standards o Vendor independence o Applications portability o Investment protection o Improved communications leading to increased productivity o Network flexibility 13DSDDED Network Architectures: DECnet, OSI, TCP/IP DECnet OS) IP Application Application Internet Applications Protocols Presentation DMA Session Control Session Transport Transport Transport (NSP) (TP 0,2,4) (TCP / UDP) Network Network Network (CLNS) (CLNS/CONS) (IP) Data Link Data Link Data Link
    [Show full text]
  • Decnet-Plusftam and Virtual Terminal Use and Management
    VSI OpenVMS DECnet-Plus FTAM and Virtual Terminal Use and Management Document Number: DO-FTAMMG-01A Publication Date: June 2020 Revision Update Information: This is a new manual. Operating System and Version: VSI OpenVMS Integrity Version 8.4-2 VSI OpenVMS Alpha Version 8.4-2L1 VMS Software, Inc., (VSI) Bolton, Massachusetts, USA DECnet-PlusFTAM and Virtual Terminal Use and Management Copyright © 2020 VMS Software, Inc. (VSI), Bolton, Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. Intel, Itanium and IA-64 are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group. The VSI OpenVMS documentation set is available on DVD. ii DECnet-PlusFTAM and Virtual
    [Show full text]
  • Database Language SQL: Integrator of CALS Data Repositories
    Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 NIST Database Language SQL Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 September 1992 U.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary TECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan National Institute of Standards and Technology Information Systems Engineering Division Gaithersburg, MD 20899, USA CALS Status Report on SQL and RDA - Abstract - The Computer-aided Acquisition and Logistic Support (CALS) program of the U.S. Department of Defense requires a logically integrated database of diverse data, (e.g., documents, graphics, alphanumeric records, complex objects, images, voice, video) stored in geographically separated data banks under the management and control of heterogeneous data management systems. An over-riding requirement is that these various data managers be able to communicate with each other and provide shared access to data and
    [Show full text]
  • Application Layer
    APPLICATION LAYER The application layer in the OSI model is the closest layer to the end user which means that the application layer and end user can interact directly with the software application. The application layer programs are based on client and servers. The Application layer includes the following functions: • Identifying communication partners: The application layer identifies the availability of communication partners for an application with data to transmit. • Determining resource availability: The application layer determines whether sufficient network resources are available for the requested communication. • Synchronizing communication: All the communications occur between the applications requires cooperation which is managed by an application layer. Services of Application Layers o Network Virtual terminal: An application layer allows a user to log on to a remote host. To do so, the application creates a software emulation of a terminal at the remote host. The user's computer talks to the software terminal, which in turn, talks to the host. The remote host thinks that it is communicating with one of its own terminals, so it allows the user to log on. o File Transfer, Access, and Management (FTAM): An application allows a user to access files in a remote computer, to retrieve files from a computer and to manage files in a remote computer. FTAM defines a hierarchical virtual file in terms of file structure, file attributes and the kind of operations performed on the files and their attributes. o Addressing: To obtain communication between client and server, there is a need for addressing. When a client made a request to the server, the request contains the server address and its own address.
    [Show full text]
  • Ciena Acronyms Guide.Pdf
    The Acronyms Guide edited by Erin Malone Chris Janson 1st edition Publisher Acknowledgement: This is the first edition of this book. Please notify us of any acronyms we may have missed by submitting them via the form at www.ciena.com/acronymsguide. We will be happy to include them in further editions of “The Acronyms Guide”. For additional information on Ciena’s Carrier Ethernet or Optical Communications Certification programs please contact [email protected]. Table of Contents Numerics ..........................1 A .......................................1 B .......................................2 C .......................................3 D .......................................5 E .......................................7 F........................................9 G .....................................10 H .....................................11 I .......................................12 J ......................................14 K .....................................14 L ......................................14 M ....................................15 N .....................................17 O.....................................18 P .....................................20 Q.....................................22 R .....................................22 S......................................23 T .....................................26 U .....................................28 V .....................................29 W ....................................29 X .....................................30 Z......................................30
    [Show full text]
  • 2018–2019 Johns Hopkins Engineering for Professionals
    The Johns Hopkins University 3400 North Charles Street Engineering Baltimore, MD 21218 for Professionals Part-Time and Online Graduate Education in Engineering and Applied Sciences 2018–2019 Part-Time Graduate Programs ep.jhu.edu Dear Students, Technological advances occurring at a breathtaking pace are impacting every aspect of society. In this environment, the most successful engineers are those committed to seek- ing the resources they need to remain at the forefront of their professions. They know it is crucial not only to be well versed in the latest technologies, but also to understand how their fields are evolving, what the consequences of these changes will be, and the knowledge and skills they will need to remain ahead of the curve. The Whiting School of Engineering provides motivated working engineers around the world with the tools and experiences necessary to advance and deepen their educa- tions in ways that have a direct positive impact on their professional lives. The breadth of our degree and certificate programs, the real-world experience of our faculty, and our state-of-the-art instructional methods enable us to provide students with unparalleled opportunities—all of which come with the prestige and value of a Johns Hopkins education. Here, you will learn from instructors who are advancing and redefining their fields, including experienced professionals from the renowned Johns Hopkins Applied Physics Labora- tory, as well as outstanding members of the Johns Hopkins University faculty. These dedicated instructors understand how engineering joins the theoretical with the practical in order to implement solutions to today’s grand challeng- es, and they continually improve and update their course and project content to include the very latest in both the theoretical understanding and the applications of their areas of expertise.
    [Show full text]
  • The US Government's Open System Environment Profile OSE/1 Version
    C NIST Special Publication 500-21 Computer Systems APPLICATION PORTABILITY PROFILE Technology (APP) The U.S. Government's U.S. DEPARTMENT OF COMMERCE Technology Administration Open System Environment Profile National Institute of Standards and Technology OSE/1 Version 2.0 Nisr NAT L !NST."OF STAND i TECH R.I.C. llllllllllllllllllll NIST PUBLICATIONS AlllDM QEETfll APPLICA TION PORTABILITYPROFILE j)JT)) The U S. Government's ^ k^Open System Environment IL Profile OSE/1 Version 2.0 -QG 100 .U57 #500-210 1993 7he National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . needed to improve product quality, to modernize manufacturing processes, to ensure product reliability . and to facilitate rapid commercialization ... of products based on new scientific discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's competitiveness; advance science and engineering; and improve public health, safety, and the environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national standards of measurement, and provide the means and methods for comparing standards used in science, engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government. As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and applied research in the physical sciences and engineering and performs related services. The Institute does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.
    [Show full text]
  • IT Acronyms at Your Fingertips a Quick References Guide with Over 3,000 Technology Related Acronyms
    IT Acronyms at your fingertips A quick references guide with over 3,000 technology related acronyms IT Acronyms at your Fingertips We’ve all experienced it. You’re sitting in a meeting and someone spouts off an acronym. You immediately look around the table and no one reacts. Do they all know what it means? Is it just me? We’re here to help! We’ve compiled a list of over 3,000 IT acronyms for your quick reference and a list of the top 15 acronyms you need to know now. Top 15 acronyms you need to know now. Click the links to get a full definition of the acronym API, Application Programmer Interface MDM, Mobile Device Management AWS, Amazon Web Services PCI DSS, Payment Card Industry Data Security Standard BYOA, Bring Your Own Apps SaaS, Software as a Service BYOC, Bring Your Own Cloud SDN, Software Defined Network BYON, Bring Your Own Network SLA, Service Level Agreement BYOI, Bring Your Own Identity VDI, Virtual Desktop Infrastructure BYOE, Bring Your Own Encryption VM, Virtual Machine IoT, Internet of Things Quick Reference, over 3000 IT acronyms Click the links to get a full definition of the acronym Acronym Meaning 10 GbE 10 gigabit Ethernet 100GbE 100 Gigabit Ethernet 10HD busy period 10-high-day busy period 1170 UNIX 98 121 one-to-one 1xRTT Single-Carrier Radio Transmission Technology 2D barcode two-dimensional barcode Page 1 of 91 IT Acronyms at your Fingertips 3270 Information Display System 3BL triple bottom line 3-D three dimensions or three-dimensional 3G third generation of mobile telephony 3PL third-party logistics 3Vs volume, variety and velocity 40GbE 40 Gigabit Ethernet 4-D printing four-dimensional printing 4G fourth-generation wireless 7W seven wastes 8-VSB 8-level vestigial sideband A.I.
    [Show full text]
  • DRIVE/WINDOWS V1.1 SQL Statements For
    Preface DRIVE/WINDOWS allows you to access the SQL database system using SQL statements. While this directory gives you a brief description of the syntax of the DRIVE SQL statements for UDS, a detailed description is provided in the "SQL for UDS/SQL V1.0 Language Reference Manual" [13]. This directory describes the DRIVE SQL statements for UDS of the DRIVE/WINDOWS version 1.1 for BS2000 and SINIX. Complex statement sections which occur in both DRIVE and SQL statements are described separately in the chapter on "Metavariables" in the "DRIVE/WINDOWS V1.0: System Directory" [3]. Additional DRIVE SQL metavariables which are not included in this chapter are described in this statement directory under "UDS metavariables". The term "with the TP monitor" refers to UTM mode in BS2000. SQL return codes are accepted by UDS/SQL and output by DRIVE/WINDOWS as error messages in the form DRI9xxx. For their meaning, refer to the "SQL for UDS/SQL (BS2000) V1.0: Language Reference Manual" [13]. U20073-J-Z145-2-7600 1 UDS/SQL statements CLOSE Close the cursor CLOSE closes a cursor that you declared with the DECLARE statement for a query expression and opened with the OPEN statement. The cursor declaration is retained. You must open the cursor using the OPEN or RESTORE statement before accessing the cursor again using the FETCH statement. An open cursor is closed at the end of a transaction. In program mode, cursors can only be referenced in the source file in which they were declared. CLOSE cursor cursor Name of the cursor you wish to close.
    [Show full text]
  • HP FTAM/9000 Programmer's Guide Is to Introduce You to the File Transfer, Access and Management (FTAM) Concepts You Must Know to Write FTAM Applications
    HP FTAM/9000 Programmer’s Guide Edition 5 B1033-90014 HP 9000 Networking E0597 Printed in: U.S.A. © Copyright 1997, Hewlett-Packard Company. Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty. A copy of the specific warranty terms applicable to your Hewlett- Packard product and replacement parts can be obtained from your local Sales and Service Office. Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies. HEWLETT-PACKARD COMPANY 3000 Hanover Street Palo Alto, California 94304 U.S.A. Use of this manual and flexible disk(s) or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited. Copyright Notices. ©copyright 1983-97 Hewlett-Packard Company, all rights reserved.
    [Show full text]
  • The Architecture of Open
    Preface By Professor Brian Warboys, University of Manchester It is now some 20 years since the foundations of the VME architecture were laid. The original objectives were to produce an architecture which would be flexible enough to allow for the many changes that were inevitable in the market, in the enabling technologies and in the end-user demands for IT systems. At the same time it was imperative that the architecture should be constraining enough to control the very long development process that long life implies. The result was essentially to define a simple but powerful approach which has basically remained unchanged during its long life. This is not a tribute to the remarkable foresight of the many people who contributed to that design but rather confirmation of the long known but often forgotten maxim that the best solution to mastering complexity is by the formulation of simple rules. The basic rules, which are enshrined in the architecture, have not had to be reformulated but merely extended in order to produce an architecture which meets the modern demands of Open Client-server systems. The essential architectural simplicity which guided the development of a complex Operating System throughout the 70's and 80's is as applicable in the 90's. Moreover this approach has been thoroughly tested over the last twenty years and there should be no doubt in anybody's mind about the capability of the OpenVME architecture to manage the complex design issues which confront modern Client-server systems. A splendid side effect of this text is that, for the first time, it enumerates, in a readily digestible form, the thinking behind the VME architecture.
    [Show full text]