Status: AVAILABLE |
In order to read or download file utility program fup reference manual ebook, you need to create a FREE account.
Download Now! |
eBook includes PDF, ePub and Kindle version
| ✔ Register a free 1 month Trial Account. |
| ✔ Download as many books as you like (Personal use) |
| ✔ Cancel the membership at any time if not satisfied. |
| ✔ Join Over 80000 Happy Readers |
Product Version T6553 D45, G08, H01, H02, and L01. Supported Release Version Updates (RVUs) This publication supports L15.02 and all subsequent L-series RVUs, J06.14 and all subsequent J-series RVUs, H06.25 and all subsequent H-series RVUs, G06.23 and all subsequent G-series RVUs, and D46.00 and all subsequent D-series RVUs, until otherwise indicated by its replacement publications. To use increased Enscribe limits, the minimum RVUs are H06.28 and J06.17 with specific SPRs. Valid license from HP required for possession, use or copying. Consistent with FAR and, 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 HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. Links to third-party websites take you outside the HP website. HP has no control over and is not responsible for information outside HP.com. Acknowledgements Microsoft and Windows are trademarks of the Microsoft group of companies. Intel, Itanium, Pentium, and Intel Inside and the Intel Inside logo 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.Product Version T6553 D45, G08, H01, H02, and L01.
http://ctkupavna.ru/upload/eureka-model-5843-manual.xml
Updated the LICENSE (Super ID) Guidelines information on page Updated the SECURE Guidelines information on page Added a note to the TRUST command section on page Updated the TRUST Guidelines information on page Changes to the manual: Updated the attribute START file-id on page 14. Updated the table File Format Codes on page Added a new section Inserting Partitions in Enscribe Key-Sequenced File on page 24. Added a new note on pages and about passing filenames in uppercase while using SPI interface. Added an example of FUP short INFO for OSS files with POSIX ACL on page Added a note on page about the RELOAD operation on ORSERV object using the SHARE option. Updated the syntax diagrams for: INFO command on page C-6 LISTLOCKS command on page C-6 xiv 19 What s New in This Manual Changes to the H06.05 Manual LISTOPENS command on page C-6 RELOAD command on page C-8 xv 20 What s New in This Manual Changes to the H06.05 Manual xvi 21 About This Manual The File Utility Program (FUP) is a component of the standard RVU. This reference manual provides an overview of the FUP software and presents the detailed syntax for its commands. This manual will help you manage disk files, nondisk devices (printers, terminals, and tape drives), and processes (programs) running on an HP NonStop server. As a reader of this manual, you should be familiar with the Guardian file-system terminology. EKS files with increased limits support 17 to 128 partitions along with larger record, block, and key sizes. LKS2 files with increased limits and format 2 standard queue files with increased limits support larger record, block, and key sizes. When a distinction is not required between these file types, key-sequenced files with increased limits are used as a collective term. The overview includes instructions for starting or interrupting FUP processes, entering FUP commands, and specifying files within FUP.
http://www.souz-himki.ru/userfiles/eureka-model-5197-manual.xml
The section defines FUP concepts that are common to most of the FUP commands, including file sets and list files. A DEFINE Tables Contains reference tables that summarize how FUP input and output options work with DEFINEs. B C FUP Command Summary FUP Command Syntax Summary Categorizes all the FUP commands described in Section 2. Provides a syntax summary of all FUP commands. Explains how to execute commands from within an application program by using the Subsystem Programmatic Interface (SPI). Explains tape handling procedures and describes the BACKCOPY, BACKUP, DCOM, DSAP, RESTORE, and TAPECOM utilities. Describes any file-system (or other) errors referenced by number in the FUP error messages. Provides task-oriented instructions for using FUP and DEFINEs. It also includes a basic FUP introduction. Describes the SQLCI commands used on SQL files. Because this function is similar to the FUP process, this manual also describes using FUP at the SQLCI prompt. Describes the syntax of SQL language elements. Describes the basic security tasks that FUP requires. Describes the RUN command options and all the other TACL commands and functions. Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual.Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. For example: myfile.c italic computer type.
http://dev.pb-adcon.de/node/18475
Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ); If there is no space between two items, spaces are not permitted. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ENTER RUN CODE?123 CODE RECEIVED: The user must press the Return key after typing the input.Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up.Lowercase italic letters indicate variable items whose values are displayed or returned. Brackets enclose items that are sometimes, but not always, displayed. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
A percent sign precedes a number that is not in decimal notation. The notation precedes an octal number. The B notation precedes a binary number. The H notation precedes a hexadecimal number. UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type!r.!o. The!r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.!r The!o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.!o Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.FUP software is designed to help you manage disk files, nondisk devices (printers, terminals, and tape drives), and processes (running programs) on a NonStop system.
You can use FUP to create, display, and duplicate files, load data into files, alter file characteristics, and purge files. The syntax for the ANSI names is same as mentioned in the Unified Syntax Proposal. FUP reports information only about the named base table, and not dependent objects. FUP has a limitation that the command line cannot exceed 132 characters. Therefore, the user must use two separate commands, one for Guardian names and another for ANSI names. To start a FUP process, use any of these methods: Enter FUP, followed by a FUP command, at the TACL prompt. Enter FUP and then use the FUP commands interactively. Enter FUP, followed by a command file (followed by a TACL IN run option). At the TACL Prompt Page Starting a FUP Process 1-2 Using FUP Custom Files 1-4 Interrupting or Terminating a FUP Process 1-5 Entering a FUP Command 1-5 Specifying Files 1-8 Using DEFINEs With FUP 1-21 Handling Different Types of Files 1-22 Note. For information about entering FUP commands, see Entering a FUP Command on page 1-5. For descriptions of each FUP command and its corresponding syntax, see Section 2, FUP Commands. After FUP executes the command, control of the terminal returns to TACL. A separate FUP process starts and completes for each command you enter. 1-2 31 FUP Overview Interactively Interactively Entering FUP commands within FUP (interactively) saves time if you are going to enter a series of commands. Type another FUP command at the subsequent prompt, or use the EXIT command to return control of the terminal from FUP to TACL: -EXIT From a Command File Starting a FUP process with a command file is useful if you frequently run the same series of FUP commands. You can also process FUP commands within an interactive FUP session using the OBEY command. Command Files To create a command file that contains FUP commands, use a text editor (such as TEDIT). It also includes comment lines to help identify the file and explain the operations that are performed. Note.
You can enter two dashes (--) or a less-than symbol ( 32 FUP Overview Run Options Run Options The TACL environment includes a set of predefined commands including the TACL RUN command. You must use a run option when you start a FUP process with a command file. The two run options that FUP uses most often are IN (for specifying an input file) and OUT (for an output file). Note. For more information about the TACL RUN command, see the TACL Reference Manual. The command in this example writes to the terminal because there is no OUT file. After FUP executes the last command in the command file, control of the terminal returns to TACL. Caution. For software product revisions (SPRs) earlier than T6553ABQ, FUP can cause a processor halt if it receives a bad startup message. This situation occurs mainly when FUP is started programmatically and the FUP STARTUPMESSAGE is accidentally corrupted, or when FUP is started through SCF after the DEFAULT STARTUP MESSAGE gets corrupted when a SYSTEM \system-name is executed. To avoid this situation, install T6553ABQ or a later SPR. Using FUP Custom Files FUP reads two files (FUPLOCL and FUPCSTM) before it issues its first prompt. This allows you to create a customized FUP environment before entering any commands. Both these files are standard FUP command files that contain ASCII text with valid FUP commands. The FUPCSTM file must be in the user s logon subvolume. FUPCSTM lets individual users set their own FUP environment. Although FUP executes each command in the FUPLOCL and FUPCSTM files and can execute any FUP command, custom files are most useful for setting environment commands (such as CONFIGURE and SET) for a FUP session. FUP executes any commands from the FUPLOCL file (if present) before it executes any commands from the FUPCSTM file (if present). If you are running FUP on a remote node, FUP looks for the custom files in the appropriate subvolumes on the remote node.
1-4 33 FUP Overview FUP Custom File Example By default, FUP does not echo the commands for either file. To start echoing, specify CONFIGURE ECHO OBEY in either file. If there are no existing custom files when FUP begins, default custom files are automatically created for your security. Custom files must be EDIT files. Errors encountered during the processing of a custom file could cause the FUP session to terminate. User Entry CTRL-Y BREAK Results Terminates a FUP process from the FUP prompt or a PURGE command from the PURGE prompt, and stops the execution of COPY and LOAD commands during input from the terminal. Aborts any FUP commands that generate listings (including the FILES, INFO, SUBVOLS, and COPY commands), and the PURGE command prompts. Three responses are possible: FUP prompt FUP recognized the break and terminated the command. TACL prompt TACL recognized the break, but FUP continues in the background. Nothing or a delay FUP cannot break when BREAK is pressed. FUP should recognize the BREAK after a brief period. If FUP does not stop, use the TACL STOP command from another TACL session. Pressing the BREAK key while the FUP prompt is displayed or while FUP is executing a nonlisting command, returns control of the terminal to TACL but the FUP process continues. Entering a FUP Command For descriptions of the syntax for each FUP command, see Section 2, FUP Commands. Although each option is available when you run FUP from the TACL prompt, only one (the OUT run option) is also available within FUP. These run options are used most often with the FUP process: IN filename names a disk file, nondisk device, or process from which FUP reads commands. Any IN disk file that you specify must be an EDIT file, unstructured file (132 byte records), or Enscribe-structured file. You cannot specify an SQL file as an IN disk file. If you omit this option, FUP uses the IN file name that is in effect for the current TACL process usually the home terminal.
OUT listfile names a nondisk device, process, or a disk file to which FUP directs its listing output (unless you use the OUT option of a subsequent FUP command to direct the output somewhere else). You must use a Guardian file name, a SPOOL DEFINE, or MAP DEFINE as the OUT list file to run FUP. Any specified OUT disk file must be an EDIT file, unstructured file, or Enscribestructured file. You cannot specify an SQL file as an OUT disk file. You can use this option to specify output to a TACL variable. If you omit this option, FUP uses the OUT list file that is in effect for the current TACL process which is usually the home terminal. If listfile does not exist, FUP creates it as an EDIT file with a maximum record length of 132 characters. If listfile does exist, FUP appends output to it. If listfile is an unstructured disk file, each of its records is 132 characters long, and any partial lines are blank-filled to column 132. For a description of using a SPOOL DEFINE for listfile, see Using DEFINEs With FUP on page command is a FUP command. You can enter only one FUP command in a TACL command. Continue the command on the next line at the new TACL prompt. If you type FUP followed by command, the FUP process terminates after executing the command and returns control of the terminal to TACL. 1-6 35 FUP Overview FUP Command Guideline If you type FUP without command, you must terminate the FUP process using the EXIT command after you finish your FUP activity. FUP Command Guideline If you enter conflicting options, FUP scans the options and uses the last one entered: DUP A, B, OLD, NEW, SOURCEDATE, SAVEID The FUP process uses the NEW option (not the OLD option) and the SAVEID option (not the SOURCEDATE option). If you use related options (such as SAVEALL, SAVEID, or SOURCEDATE), FUP uses the last option entered and cancels the previous entry.
While the command is executing, FUP displays any information about the ongoing process and then returns you to the FUP prompt (hyphen) when the process is complete. The different types of files in the Guardian environment include disk files (containing data, code, or text), nondisk devices (terminals, printers, or tape drives), spooler files (code 129), and processes (programs that are running). Disk file names have four parts: node, volume, subvolume, and file identifier. Three common syntax terms appear throughout the FUP commands. Each of these terms provides a way to specify the file or files you want to affect with a FUP command. The syntax terms are: listfile fileset-list fileset Note. For information on when FUP commands do not apply to SQL files, see the command descriptions in Section 2, FUP Commands. Listfile Parameter The listfile parameter refers to a nondisk device, a process, an existing disk file, or a spooler file (code 129) to which you direct the output of a FUP command. It always appears with the OUT keyword in the syntax descriptions for the TACL RUN command and in the FILENAMES, FILES, HELP, INFO, LISTLOCKS, LISTOPENS, RELOAD, SHOW, STATUS, SUBVOLS, SUSPEND, and VOLS commands for FUP. If you omit this option, FUP uses the OUT list file that is in effect for the current TACL process usually the home terminal. 1-8 37 FUP Overview Fileset-list Parameter If a list file does not exist, FUP creates it as an EDIT file with a maximum record length of 132 characters. If a list file does exist, FUP appends output to it. If the list file is an unstructured disk file, each of its records is 132 characters long, and any partial lines are blank-filled to column 132. You can specify a SPOOL DEFINE for listfile. For a description of using a SPOOL DEFINE, see Using DEFINEs With FUP on page If you enter only a partial file name, FUP expands it using the current default node, volume, and subvolume names.
Fileset-list Parameter The fileset-list parameter refers to one or more file sets. It can contain up to ten different sets of files enclosed in parentheses. It can be one file, all the files in a subvolume, all the files on a volume, a subset specified by the wild-card option, or a subset produced by a qualified file set. The file or files can be fully qualified or can include wild cards or qualifiers.The NonStop SQL relational database System Software Library Copyright 2013 Hewlett-Packard Development Copyright 2014 KB Systems, Inc., Herndon, Virginia, USA. Printed in the United States of America. No part of this manual may be Software Release 5.7.1 March 2012 With the scale that a NonStop system provides, this task November 2004 (First Edition) Part Number 373652-001 Software Release 6.0 November 2011 All rights reserved.Software Release 6.2 January 2011 Replication Server 15.5 All rights reserved. This publication pertains to Sybase Published in the USA. UBA is designed for IMC Confidential computer Portions of this software are derived User s Guide Release 5.1 All rights reserved. Limitation of liability This document is provided as-is. Information and SmartList Builder User s Guide With Excel Report Builder All rights reserved. Complying with all applicable copyright laws is the responsibility VERITAS Software Copyright 2006, Oracle. All rights reserved. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. Software Release 5.8.0 November 2012 All rights reserved. Interlink The information contained herein is subject All rights reserved. Published User Guide All rights reserved.
Sage, the Sage logos, and the Sage product and service names mentioned herein are registered trademarks or trademarks This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, Product notice This user guide describes features VERITAS Software It provides guidelines, suggestions, and ideas on the following topics: User Guide The software described in this guide is furnished To use this website, you must agree to our Privacy Policy, including cookie policy. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and, 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. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Warranty Microsoft and Windows are trademarks of the Microsoft group of companies. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. UNIX is a registered trademark of The Open Group.This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz.
1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California. This manual will help you manage disk files, nondisk devices (printers, terminals, and tape drives), and processes (programs) running on an HPE NonStop server. Changes to the manual: Added a note on unstructured-buffer-size in the following sections: ALTER Parameter for Unstructured Files on page 53 CREATE Guidelines on page 85 Updated MAX num-records for key-seq-option in LOAD Guidelines on page 156. Updated MAX num-records in LOADALTFILE on page 159. SET Parameters for Unstructured Files on page 194. Changes to the manual: This manual is updated to support L-series RVU. Updated LICENSE (Super ID) Guidelines on page 142. Updated SECURE Guidelines on page 182. Added a note to the TRUST on page 207 command section. Updated TRUST Guidelines on page About This Manual 9 Changes to the manual: Updated the attribute START file-id under Qualified File Sets on page 22. Added a new section, Inserting Partitions in Enscribe Key-Sequenced File on page 33. Updated the default value of primary extent and secondary extent in Unique features of Key-Sequenced File with Increased Limits on page 37. Updated sec-partition-num in ALTER Parameters for Partitioned Files on page 51. Updated the syntax and added Aggregate EOF for INFO on page 105. Updated the example for INFO DETAIL Listing Format on page 124. Added Aggregate EOF and FILE Label details for INFO DETAIL Listing Format on page 124. Updated INFO DETAIL Listing Format Examples on page 130. Updated Max num-records in the key-seq-option under LOAD Guidelines on page 156. Udpated REVOKE (Super ID) Guidelines on page 179 and SECURE Guidelines on page 182. Updated block-length and record-length values in SET Parameters for All Structured Files on page 188. Updated KEYLEN and KEYOFF in SET Parameters for Key-Sequenced Files on page 189. Updated sec-partition-num in SET Parameters for Partitioned Files on page 190.
Changes to the manual: Added a new section, Unique Features of EKS Files on page 37. Updated COPY: Copy Form on page 66. Updated COPY: Copy Form Examples on page 81. Updated Copy: Display Form Examples on page 84. Updated GIVE Guidelines on page 102. Updated RELOAD Guidelines on page 171. Updated the syntax for RESET on page 174. Updated RESTART Guidelines on page 177. Updated REVOKE (Super ID) on page 178. Updated REVOKE (Super ID) Guidelines on page 179. Updated SECURE on page 180. Related Documentation 11 12 Publishing History Part Number Product Version Published FUP D45, G08, and H01 August T6553 D45, G08, H01, and H02 April T6553 D45, G08, H01, and L01 February T6553 D45, G08, H01, and L01 June T6553 D45, G08, H01, and L01 March Publishing History 13 FUP Overview The File Utility Program (FUP) is a component of the standard RVU. FUP software is designed to help you manage disk files, nondisk devices (printers, terminals, and tape drives), and processes (running programs) on a NonStop system. To use longer ANSI names, FUP users need to: 1. Use MXCI SHOWDDL or MXCI SHOWLABEL to get the Guardian names. 2. Run FUP on one or more of the Guardian names. FUP supports Storage Management Foundation (SMF) logical file names. Topic Starting a FUP Process on page 14 Using FUP Custom Files on page 16 Interrupting or Terminating a FUP Process on page 16 Entering a FUP Command on page 17 Table Continued FUP Overview 13 14 Topic Specifying Files on page 19 Using DEFINEs With FUP on page 30 Handling Different Types of Files on page 31 Starting a FUP Process Access to FUP is available through the HPE Tandem Advanced Command Language (TACL), the standard command interface in the Guardian environment. NOTE: For information about entering FUP commands, see Entering a FUP Command on page 17. For descriptions of each FUP command and its corresponding syntax, see FUP Commands on page 39. For a description of command files and run options, see From a Command File on page 15.
A separate FUP process starts and completes for each command you enter. Interactively Entering FUP commands within FUP (interactively) saves time if you are going to enter a series of commands. It also includes comment lines to help identify the file and explain the operations that are performed. After FUP executes the last command in the command file, control of the terminal returns to TACL. From a Command File 15 16 CAUTION: For software product revisions (SPRs) earlier than T6553ABQ, FUP can cause a processor halt if it receives a bad startup message. If you are running FUP on a remote node, FUP looks for the custom files in the appropriate subvolumes on the remote node. By default, FUP does not echo the commands for either file. Entering a FUP Command For descriptions of the syntax for each FUP command, see FUP Commands on page 39. Any specified OUT disk file must be an EDIT file, unstructured file, or Enscribe-structured file. Entering a FUP Command 17 18 If listfile does not exist, FUP creates it as an EDIT file with a maximum record length of 132 characters. For a description of using a SPOOL DEFINE for listfile, see Using DEFINEs With FUP on page 30.You can enter only one FUP command in a TACL command. If you type FUP followed by command, the FUP process terminates after executing the command and returns control of the terminal to TACL. If you type FUP without command, you must terminate the FUP process using the EXIT command after you finish your FUP activity. Specifying Files FUP commands make it easy to: Create, display, and duplicate files Load data into files Alter file characteristics Purge files Before you use FUP to create or manage files, become familiar with the various file types and the methods used to specify them. NOTE: For more information on the different types of Enscribe-structured files, see the Enscribe Programmer s Guide. NOTE: For more information on file-naming conventions, see the Guardian User s Guide.