HP 3000 Manuals HP 3000 Manuals
HP 3000 Computer Systems FCOPY Reference Manual HP Part No. 32212-90003 Printed in U.S.A. Edition Third Edition E1290
________________________________________________________________________ |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, INCLUDING, 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 use of this | |material. | | | |Hewlett-Packard assumes no responsibility for the use or reliability | |of its software on equipment that is not furnished by Hewlett-Packard.| | | |This document contains proprietary information which is protected by | |copyright. All rights are reserved. No part of this document may be | |photocopied, reproduced, or translated to another language without the| |prior written consent of Hewlett-Packard Company. | ________________________________________________________________________ Copyright (c) 1989, 1990 by Hewlett-Packard Company Printed 19901201 Print History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions. Edition Date Software Version --------------------------------------------------------------------------------------- MPE V/E First Edition October 1989 G.03.08 MPE XL First Edition October 1989 A.30.00 Second Edition April 1990 A.40.00 Third Edition December 1990 B.30.00 Preface This manual is designed to serve a wide variety of users, from the occasional MPE V/E or MPE XL user to the experienced system operator. Because FCOPY runs in almost exactly the same way on MPE V/E and MPE XL, this manual is used for both systems. MPE V/E and XL systems both support a KSAM tofile that consists of a pair of key and data files. It is referred to on MPE V/E as KSAM V/E or KSAM/3000, and on MPE XL as CM KSAM. MPE XL also supports a single file format, called KSAM XL. This single file KSAM structure is available on MPE XL only. FCOPY access to both types of KSAM files is described in this manual. Manual Organization The information in the manual is presented as follows: Chapter 1 Introduction describes how to use the manual. Chapter 2 Using FCOPY gives an overview of the FCOPY command and lists the FCOPY functions. Chapter 3 FCOPY Applications and Examples provides instructions for using FCOPY and gives examples of typical transactions. Chapter 4 FCOPY Syntax summarizes the syntax of the FCOPY command and the FCOPY functions. Chapter 5 FCOPY Functions describes each of the FCOPY functions in detail. Chapter 6 Using FCOPY with Terminal Peripherals discusses terminal peripheral file designators, terminal settings, and copying files between peripherals. Appendix A FCOPY Messages contains all the FCOPY error, warning, and status messages. Appendix B Default File Definition Values summarizes the values that FCOPY uses to open fromfiles or tofiles. Appendix C Code Conversion Tables contains three tables showing ASCII/EBCDIC, JIS/BCDIK, and ASCII/BCDIC code conversions. How to Use This Manual The manual is organized into three major parts. * Chapters 1 through 3 explain how to use FCOPY. Chapter 3 contains several examples, so you might look at chapter 3 when you have a specific task to perform, and follow an example before carrying out your task. Read these chapters first if you are a new FCOPY user. * Chapters 4 through 6 contain the FCOPY syntax and descriptions of all the FCOPY functions. Use these chapters as a reference guide if you want to look up the syntax for an FCOPY function. * The appendices contain FCOPY message descriptions, default file definitions and code conversion tables. Use these chapters for general reference and for information when troubleshooting or converting codes. If you have any general comments about this edition, find any technical errors, or encounter any situations that you would like to see as examples in future editions, please fill in and mail the Reader Comment Card at the front of the manual. Additional Information You may also find the following manuals useful: * MPE V General User's Reference Manual for MPE V/E. * MPE V/E Commands Reference Manual (32033-90006) or MPE XL Commands Reference Manual (32650-90003). * MPE Intrinsics Reference Manual (30000-90010) for MPE V/E or MPE XL Intrinsics Reference Manual (32650-90028) for MPE XL. * MPE File System Reference Manual (30000-90236) for MPE V/E or Accessing Files Programmer's Guide (32650-90017) for MPE XL. * KSAM/3000 Reference Manual (30000-90079) for KSAM/3000 files on MPE V/E and for CM KSAM files on MPE XL. * Using KSAM XL (32650-90168) for KSAM XL files on MPE XL. * Native Language Support Reference Manual (32414-90001) for MPE V/E or Native Language Programmer's Guide (32650-90022) for MPE XL. * MPE XL Error Message Manual Volumes 1 and 2 (32650-90066 and 32650-90152) for MPE XL. Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm com_mand comnand italics In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND filename bold italics In a syntax statement, a word in bold italics represents a required parameter that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND (filename) punctuation In a syntax statement, punctuation characters (other than brackets, braces, vertical bars, and ellipses) must be entered exactly as shown. In the following example, the parentheses and colon must be entered: (filename):(filename) underlining Within an example that contains interactive dialog, user input and user responses to prompts are indicated by underlining. In the following example, yes is the user's response to the prompt: Do you want to continue? >> yes { } In a syntax statement, braces enclose required elements. When several elements are stacked within braces, you must select one. In the following example, you must select either ON or OFF: COMMAND {ON } {OFF} Conventions (continued) [ ] In a syntax statement, brackets enclose optional elements. In the following example, OPTION can be omitted: COMMAND filename [OPTION] When several elements are stacked within brackets, you can select one or none of the elements. In the following example, you can select OPTION or parameter or neither. The elements cannot be repeated. COMMAND filename [OPTION ] [parameter] [...] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...] In the example below, you only use the comma as a delimiter if parameter is repeated; no comma is used before the first occurrence of parameter: [parameter][,...] |...| In a syntax statement, horizontal ellipses enclosed in vertical bars indicate that you can select more than one element within the immediately preceding pair of brackets or braces. However, each particular element can only be selected once. In the following example, you must select A, AB, BA, or B. The elements cannot be repeated. {A} |...| {B} ... In an example, horizontal or vertical ellipses indicate where portions of an example have been omitted. _ In a syntax statement, the space symbol _ shows a required blank. In the following example, parameter and parameter must be separated with a blank: (parameter)_(parameter) The symbol indicates a key on the keyboard. For example, RETURN represents the carriage return key or Shift represents the shift key. CTRLcharacter CTRLcharacter indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously. Conventions (continued) base prefixes The prefixes %, #, and $ specify the numerical base of the value that follows: %num specifies an octal number. #num specifies a decimal number. $num specifies a hexadecimal number. If no base is specified, decimal is assumed. bits (bit:length) When a parameter contains more than one piece of data within its bit field, the different data fields are described in the format bits (bit:length), where bit is the first bit in the field and length is the number of consecutive bits in the field. For example, bits (13:3) indicates bits 13, 14, and 15: most significant least significant |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| | 0| | | | | | | | | | | | |13|14|15| |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| bits (0:1) bits (13:3)