Job Management Partner 1/File Transmission Server/FTP Description, Reference and Operator's Guide
This manual describes the functions of and explains how to operate Job Management Partner 1/File Transmission Server/FTP (referred to hereafter as JP1/FTP).
The IPF version of JP1/FTP is not supported.
Intended readers
This manual is intended for users who use JP1/FTP to transmit files.
Organization of this manual
This manual is organized into the following chapters:
- 1. Overview of JP1/FTP
- Chapter 1 provides an overview of the functions of JP1/FTP and describes its features and operating procedures.
- 2. Installation and Setup
- Chapter 2 describes how to install and set up JP1/FTP in preparation for using JP1/FTP.
- 3. File Transmission by JP1/FTP
- Chapter 3 describes how to use JP1/FTP to transmit files.
- 4. JP1/FTP Operations Management
- Chapter 4 describes the Operations-Manager function of JP1/FTP.
- 5. Linkage with Other JP1 Programs
- Chapter 5 describes how to set up and operate the JP1 programs that can be linked with JP1/FTP.
- 6. Commands
- Chapter 6 describes the commands provided by JP1/FTP.
- 7. API Library
- Chapter 7 describes the API library provided by JP1/FTP.
- 8. Messages
- Chapter 8 describes the messages that are displayed by JP1/FTP.
- 9. Troubleshooting
- Chapter 9 describes how to handle problems that can occur in JP1/FTP.
Related publications
This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):
- Job Management Partner 1/Automatic Job Management System 3 Linkage Guide (3020-3-S12(E))
- Job Management Partner 1/Base User's Guide (3020-3-R71(E))
- Job Management Partner 1/Integrated Management - Manager Configuration Guide (3020-3-R77(E))
- Job Management Partner 1/Software Distribution Administrator's Guide Volume 1 (3020-3-S81(E)), for Windows systems
This manual uses the following abbreviations for product names:
Abbreviation Full name or meaning HP NNM HP Network Node Manager Starter Edition Software version 7.5 or earlier JP1 Job Management Partner 1 JP1/AJS3 JP1/AJS - Manager Job Management Partner 1/Automatic Job Management System 3 - Manager JP1/AJS - View Job Management Partner 1/Automatic Job Management System 3 - View JP1/FTP Job Management Partner 1/File Transmission Server/FTP JP1/IM JP1/IM - Manager Job Management Partner 1/Integrated Management - Manager JP1/IM - View Job Management Partner 1/Integrated Management - View JP1/SD Job Management Partner 1/ Software Distribution Windows Windows Server 2003 Microsoft(R) Windows Server(R) 2003, Enterprise Edition Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition Microsoft(R) Windows Server(R) 2003, Standard Edition Microsoft(R) Windows Server(R) 2003, Standard x64 Edition Windows Server 2003 Windows Server 2003 (IPF) Microsoft(R) Windows Server(R) 2003, Datacenter Edition for Itanium-based Systems Microsoft(R) Windows Server(R) 2003, Enterprise Edition for Itanium-based Systems Windows Server 2008 Microsoft(R) Windows Server(R) 2008 Enterprise Microsoft(R) Windows Server(R) 2008 Standard Microsoft(R) Windows Server(R) 2008 R2 Datacenter x64 Edition Microsoft(R) Windows Server(R) 2008 R2 Enterprise x64 Edition Microsoft(R) Windows Server(R) 2008 R2 Standard x64 Edition Windows Server 2008 Windows Server 2008 (IPF) Microsoft(R) Windows Server(R) 2008 for Itanium-based Systems
- A version of JP1/FTP that is run on Windows Server 2003 (IPF) or Windows Server 2008 (IPF) may be referred to as the IPF version.
This manual also uses the following abbreviations:
Abbreviation Full name or meaning API Application Programming Interface DNS Domain Name System IPF Itanium(R) Processor Family LAN Local Area Network NIC Network Interface Card RFC Request for Comments SNMP Simple Network Management Protocol TCP/IP Transmission Control Protocol/Internet Protocol WAN Wide Area Network
This manual uses the following conventions in diagrams:
Conventions: Fonts and symbols
Font and symbol conventions are classified as:
- General font conventions
- Conventions in syntax explanations
These conventions are described below.
General font conventions
The following table lists the general font conventions:
Font Convention Bold Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, and explanatory labels. For example, bold is used in sentences such as the following:
- From the File menu, choose Open.
- Click the Cancel button.
- In the Enter name entry box, type your name.
Italics Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
- Write the command as follows:
copy source-file target-file
- Do not delete the configuration file.
Code font A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
- At the prompt, enter dir.
- Use the send command to send mail.
- The following message is displayed:
The password is incorrect.
Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):
MakeDatabase ... StoreDatabase temp DB32In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.
Conventions in syntax explanations
Syntax definitions appear as follows:
StoreDatabase [temp|perm] (database-name ...)
The following table lists the conventions used in syntax explanations:
Example font or symbol Convention StoreDatabase Code-font characters must be entered exactly as shown. database-name This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command. SD Bold code-font characters indicate the abbreviation for a command. perm Underlined characters indicate the default value. [] Square brackets enclose an item or set of items whose specification is optional.
If multiple items are enclosed, either omit all or select one of them.
Example:
[A] means either nothing or A must be specified.
[B|C] means either nothing or B or C must be specified.| Only one of the options separated by a vertical bar can be specified at the same time.
Example:
A|B|C means A, B, or C.... An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary. () Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable. {} One of the items or sets of items enclosed in curly brackets must be selected. Inside the curly brackets, the items or sets of items are delimited by a vertical bar (|).
Example:
{A|B|C} means that A, or B, or C must be specified.(( )) Double parentheses enclose the range of values that can be specified. << >> Double angle brackets enclose the default value.
Conventions: KB, MB, GB, and TB
This manual uses the following conventions:
- 1 KB (kilobyte) is 1,024 bytes.
- 1 MB (megabyte) is 1,0242 bytes.
- 1 GB (gigabyte) is 1,0243 bytes.
- 1 TB (terabyte) is 1,0244 bytes.
The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:
- Version 1.00 (or 1.0) is written as 01-00.
- Version 2.05 is written as 02-05.
- Version 2.50 (or 2.5) is written as 02-50.
- Version 12.25 is written as 12-25.
The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.
All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.