HP T6553 D45, G08, H01, H02 Reference Manual

File Utility Program
(FUP) Reference
Manual

Abstract

This manual describes the command syntax and error messages for the File Utility
Program (FUP).

Product Version

T6553 D45, G08, H01, and H02.

Supported Release Version Updates (RVUs)

This publication supports 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.

Part Number Published

523323-014 August 2012

Document History

Part Number Product Version Published

523323-009 FUP D45, G08, and H01 July 2006
523323-010 FUP D45, G08, and H01 November 2006
523323-012 FUP D45, G08, and H01 October 2009
523323-013 FUP D45, G08, and H01 February 2011
523323-014 T6553 D45, G08, H01, and H02 August 2012

Legal Notices

 Copyright 2012 Hewlett-Packard Development Company L.P.
Confidential computer software. Valid license from HP 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 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.

Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its

subsidiaries in the United States and other countries.
Java is a registered trademark of Oracle and/or its affiliates.
Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The

Open Group are trademarks of The Open Group in the U.S. and other countries.
Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the

Open Software Foundation, Inc.

OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED
HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

OSF shall not be liable for errors contained herein or for incidental consequential damages in
connection with the furnishing, performance, or use of this material.

© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to
which it relates are derived in part from materials supplied by the following:

© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation.
© 1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc.
© 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. © 1985, 1987, 1988, 1989, 1990, 1991,
1992 International Business Machines Corpor a tion. © 1988, 1989 Massachusetts Institute of
Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989,
1990, 1991, 1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informationssysteme AG. © 1986,
1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation.

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.

Printed in the US

Hewlett-Packard Company—523323-014

i

File Utility Program (FUP)
Reference Manual

Glossary Index Examples Tables

Legal Notices
What’s New in This Manual ix

Manual Information

ix

New and Changed Information

ix

About This Manual xiii

Organization of This Manual xiii
Additional Information xiv
Notation Conventions xiv

1. FUP Overview

Starting a FUP Process 1-2

At the TACL Prompt 1-2
Interactively 1-3
From a Command File 1-3
Command Files 1-3
Run Options 1-4

Using FUP Custom Files 1-4

FUP Custom File Guidelines

1-4

FUP Custom File Example 1-5

Interrupting or Terminating a FUP Process

1-5

Entering a FUP Command

1-5

FUP Command Guideline

1-7

FUP Command Examples 1-7

Specifying Files

1-8

Listfile Parameter

1-8

Fileset-list Parameter 1-9
Fileset Parameter 1-9
Wild-Card Option

1-10

Qualified File Sets

1-11

Creating Files 1-19

Examples of Creating Files 1-19

Contents

File Utility Program (FUP) Reference Manual—523323-014

ii

1. FUP Overview (continued)

1. FUP Overview (continued)

Partitioning Files 1-20

Examples of Partitioning Files 1-20

Using DEFINEs With FUP 1-21

SPOOL DEFINEs 1-21
MAP DEFINEs 1-22
TAP E DEFINEs 1-22

Handling Different Types of Files 1-22

Handling File Formats 1-22
Moving Format 1 File Contents to Format 2

1-23

Handling OSS Files

1-24

Handling SQL/MP Files 1-24
Handling SQL/MX Files 1-27
Handling SMF Files 1-28

2. FUP Commands

! 2-4

! Guidelines 2-4
! Examples 2-4
Commands Related to ! 2-5

? 2-5

? Guidelines 2-5
Commands Related to ? 2-6

ALLOCATE 2-6

ALLOCATE Guidelines 2-6
ALLOCATE Examples

2-7

Commands Related to ALLOCATE 2-8

ALLOW

2-9

ALTER

2-9

ALTER Parameters for All File Types

2-10

ALTER Parameters for Files With Alternate-Key Fields 2-13
ALTER Parameters for Partitioned Files

2-15

ALTER Parameter for Unstructured Files

2-18

ALTER Guidelines 2-18
ALTER Examples 2-20
Commands Related to ALTER

2-20

BUILDKEYRECORDS

2-21

BUILDKEYRECORDS Guidelines 2-22
BUILDKEYRECORDS Example 2-23

Contents

File Utility Program (FUP) Reference Manual—523323-014

iii

2. FUP Commands (continued)

2. FUP Commands (continued)

Commands Related to BUILDKEYRECORDS 2-23

CHECKSUM 2-24

CHECKSUM Guidelines 2-24
CHECKSUM Examples 2-25

CONFIG[URE] 2-26

CONFIG[URE] Guidelines 2-31
CONFIG[URE] Examples 2-33
Commands Related to CONFIG[URE] 2-35

COPY: Copy Form

2-36

COPY: Copy Form Guidelines

2-51

COPY: Copy Form Examples 2-53
Commands Related to Copy: Copy Form 2-54

COPY : Display For m 2-55

Copy: Display Form Listing Format 2-56
Copy: Display Form Examples 2-57

CREATE 2-58

CREATE Guidelines 2-58
CREATE Examples 2-59
Commands Related to CREATE 2-61

DEALLOCATE 2-61

DEALLOCAT E Guidelines 2-61
DEALLOCAT E Example 2-62
Commands Related to DEALLOCATE 2-62

DISPLAYBITS

2-62

DUP[LICATE] 2-62

DUP[LICATE] General Guidelines

2-67

DUP[LICATE] Guidelines for Safeguard Files

2-69

DUP[LICATE] Examples

2-69

Commands Related to DUP[LICATE] 2-71

EXIT

2-71

EXIT Guidelines

2-71

EXIT Example 2-71

FC 2-71

FC Guidelines

2-72

FC Examples

2-73

Commands Related to FC 2-73

FILENAMES 2-73

FILENAMES Example 2-74

Contents

File Utility Program (FUP) Reference Manual—523323-014

iv

2. FUP Commands (continued)

2. FUP Commands (continued)

Commands Related to FILENAMES 2-74

FILES 2-75

FILES Guidelines 2-76
FILES Examples 2-76
Commands Related to FILES 2-76

GIVE 2-77

GIVE Guidelines 2-77
GIVE Examples 2-78

HELP

2-79

HELP Examples

2-79

HISTORY 2-80

HISTORY Guidelines 2-80
HISTORY Example 2-81
Commands Related to HISTORY 2-81

INFO 2-81

INFO Guidelines 2-84
INFO Listing Format 2-85
INFO Listing Format Example 2-97
INFO DETAIL Listing Format 2-98
INFO DETAIL Listing Format Examples 2-105
INFO STATISTICS Listing Format 2-112
INFO STATISTICS Listing Format Examples 2-113
INFO EXTENTS Listing Format 2-115
INFO EXTENTS Listing Format Examples

2-115

Commands Related to INFO 2-116

LICENSE (Super ID)

2-116

LICENSE (Super ID) Guidelines

2-117

LICENSE (Super ID) Examples

2-117

Commands Related to LICENSE (Super ID) 2-117

LISTLOCKS

2-117

LISTLOCKS Listing Format

2-119

LISTLOCKS Guidelines 2-121
LISTLOCKS Example 2-122

LISTOPENS

2-123

LISTOPENS Listing Format

2-124

LISTOPENS Guidelines 2-126
LISTOPENS Examples 2-128

LOAD 2-130

Contents

File Utility Program (FUP) Reference Manual—523323-014

v

2. FUP Commands (continued)

2. FUP Commands (continued)

LOAD Guidelines 2-134
LOAD Examples 2-136
Commands Related to LOAD 2-137

LOADALTFILE 2-137

LOADALTFILE Guidelines 2-138
LOADALTFILE Example 2-139
Commands Related to LOADALTFILE 2-139

OBEY 2-139

OBEY Guidelines

2-139

OBEY Example

2-140

PURGE 2-140

PURGE Guidelines 2-142
PURGE Examples 2-143
Commands Related to PURGE 2-145

PURGEDATA 2-145

PURGEDATA Guidelines 2-146
PURGEDATA Example 2-146
Commands Related to PURGEDATA 2-146

RELOAD 2-147

RELOAD Guidelines 2-151
RELOAD Example 2-153
Commands Related to RELOAD 2-153

RELOCATE 2-153

RELOCATE Guidelines

2-154

RELOCATE Example 2-154

RENAME

2-154

RENAME Guidelines

2-155

RENAME Example

2-155

REPORTWIDTH 2-155
RESET

2-156

RESET Guidelines

2-157

RESET Examples 2-157
Commands Related to RESET 2-158

RESTART

2-158

RESTART Guidelines

2-159

RESTART Examples 2-159
Commands Related to RESTART 2-159

REVOKE (Super ID) 2-160

Contents

File Utility Program (FUP) Reference Manual—523323-014

vi

2. FUP Commands (continued)

2. FUP Commands (continued)

REVOKE (Super ID) Guidelines 2-161
REVOKE (Super ID) Examples 2-161
Commands Related to REVOKE (Super ID) 2-161

SECURE 2-162

SECURE Guidelines 2-164
SECURE Examples 2-165
Commands Related to SECURE 2-165

SET 2-166

SET Parameters for All File Types

2-167

SET Parameters for All Structured Files

2-171

SET Parameters for Key-Sequenced Files 2-171
SET Parameters for Partitioned Files 2-172
SET Parameters for Files With Alternate-Key Fields 2-175
SET Parameters for Unstructured Files 2-177
SET Parameter for Files on SMF Virtual Disks 2-178
SET Guidelines 2-178
SET Examples 2-180
Commands Related to SET 2-181

SHOW 2-182

SHOW Guidelines 2-184
SHOW Examples 2-184
Commands Related to SHOW 2-185

STATUS 2-185

STATUS Guidelines

2-186

STATUS Examples 2-187
Commands Related to STATUS

2-187

SUBVOLS

2-187

SUBVOLS Examples

2-188

SUSPEND 2-188

SUSPEND Guidelines

2-189

SUSPEND Example

2-189

Commands Related to SUSPEND 2-189

SYSTEM 2-189

SYSTEM Guidelines

2-190

SYSTEM Examples

2-190

Commands Related to SYSTEM 2-191

TRUST 2-191

TRUST Guidelines 2-192

Contents

File Utility Program (FUP) Reference Manual—523323-014

vii

2. FUP Commands (continued)

2. FUP Commands (continued)

TRUST Examples 2-192

VOLS 2-193

VOLS Example 2-193

VOLUME 2-193

VOLUME Guidelines 2-194
VOLUME Examples 2-194
Commands Related to VOLUME 2-195

3. FUP Messages
A. DEFINE Tables
B. FUP Command Summary
C. FUP Command Syntax Summary
Glossary
Index

Examples

Example 2-1. COPY Command Listing Format 2-56
Example 2-2. INFO Listing Format 2-85
Example 2-3. INFO Listing Format 2-97
Example 2-4.

Short INFO for SQL/MX Table Using ANSI Names 2-97
Example 2-5. Short INFO for OSS Files With POSIX ACL 2-98
Example 2-6.

DETAIL Format for SQL Tables and Indexes and for Enscribe and

OSS Files 2-99
Example 2-7. DETAIL Format for SQL/MP View 2-104
Example 2-8. INFO STATISTICS Listing Format 2-112
Example 2-9.

INFO EXTENTS Listing Format 2-115
Example 2-10.

FUP LISTLOCKS DETAIL Listing Format 2-120
Example 2-11. FUP LISTOPENS Listing Format 2-125

Tables

Table 1-1. File Format Codes 1-23
Table 1-2. FUP Commands and SQL/MP Files 1-25
Table 1-3. FUP Commands and SQL/MX Files 1-27
Table 2-1. Response to ALLOW ABENDS ON or OFF 2-28
Table 2-2. System File Code Definitions 2-88

Contents

File Utility Program (FUP) Reference Manual—523323-014

viii

Tables (continued)

Tables (continued)

Table 2-3. Extent-Size Rounding 2-179
Table A-1. How FUP Input Options Work With TAPE DEFINEs A-1
Table A-2. How FUP Output Options Work With TAPE DEFINEs A-2
Table B-1. FUP Control Commands B-1
Table B-2. FUP Informational Commands B-2
Table B-3. FUP Security Management Commands B-2
Table B-4. FUP File Management Commands B-2

File Utility Program (FUP) Reference Manual—523323-014

ix

What’s New in This Manual

Manual Information

File Utility Program (FUP) Reference Manual

Abstract

This manual describes the command syntax and error messages for the File Utility
Program (FUP).

Product Version

T6553 D45, G08, H01, and H02.

Supported Release Version Updates (RVUs)

This publication supports 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.

Document History

New and Changed Information

Changes to the 523323-014 manual:



Updated the table File Format Codes on page 1-23.



Added a new section Unique Features of EKS Files on page 1-28.



Updated the option, NOPURGEUNTIL [ timestamp ] on page 2-12.



Updated the section COPY Form on page 2-37.



Added RELOCATE option to CONFIG command on page 2-26.



Updated the section COPY: Copy Form Examples on page 2-54.



Updated the section Copy: Display Form Examples on page 2-58.

Part Number Published

523323-014 August 2012

Part Number Product Version Published

523323-009 FUP D45, G08, and H01 July 2006
523323-010 FUP D45, G08, and H01 November 2006
523323-012 FUP D45, G08, and H01 October 2009
523323-013 FUP D45, G08, and H01 February 2011
523323-014 T6553 D45, G08, H01, and H02 August 2012

What’s New in This Manual

File Utility Program (FUP) Reference Manual—523323-014

x

New and Changed Information



Updated the section DUP[LICATE] General Guidelines on page 2-70.



Updated the section GIVE Guidelines on page 2-78.



Updated the section RELOAD Guidelines on page 2-152.



Updated the syntax for RESET on page 2-158.



Updated the section REST ART Guidelines on page 2-161.



Updated the section REVOKE (Super ID) on page 2-163.



Updated the section REVOKE (Super ID) Guidelines on page 2-164.



Updated the section SECURE on page 2-166.



Updated the section SECURE Guidelines on page 2-168.



Updated the table FUP Security Management Commands on page B-2.

Changes to the 523323-013 manual:



Updated these parameters for enhanced key-sequenced files information:



ALTER Parameters on page 2-16.



DUP[LICATE] Parameters on page 2-66.



SET Parameters on page 2-178.



SET Parameters for Files with Alternate-Key Fields on page 2-181.



Updated these guidelines for enhanced key-sequenced files information:



ALLOCATE Guidelines on page 2-7.



ALTER Guidelines on page 2-20.



COPY form Guidelines on page 2-53.



CREATE Guidelines on page 2-60.



DEALLOCATE Guidelines on page 2-63.



INFO Guidelines on page 2-86.



LOAD Guidelines on page 2-137.



SET Guidelines on page 2-184.



Updated ALTER Parameters for Partitioned Files on page 2-17.



Updated LICENSE (Super ID) information on page 2-117.



Updated the LICENSE (Super ID) Guidelines information on page 2-118.



Updated the syntax for RELOAD command on page 2-148.

What’s New in This Manual

File Utility Program (FUP) Reference Manual—523323-014

xi

Changes to the H06.08 Manual



Added the COMPACT option to the RELOAD command on page 2-152.



Updated the syntax for SET command for Key sequences files on page 2-171.



Added the option LOCKLENGTH to SET Parameters for Key-Sequenced Files on
page 2-177.



Updated SET Guidelines for SET LIKE command information on page 2-184.

Changes to the 523323-012 manual:



Updated the CONFIG[URE] command with the DISPLAYALLNUM
environment-option on page 2-26.



Updated the COPY command with the KEY64 {record-spec} control-option on
page 2-36.



Updated the extent size information in the note on page 2-60.



Updated the System File Code Definition for the file code 128 on 2-90.



Updated the RECLAIM information of the RELOAD command on 2-151.



Added the SOURCEDATE option to the RELOCATE command on page 2-154.



Updated the RESET command with the DISPLAYALLNUM environment-option on
page 2-159.



Updated the SET Parameters for Unstructured Files information on page 2-183.



Updated the SHOW command with the DISPLAYALLNUM environment-option on
page 2-188.

Changes to the H06.08 Manual



Added the open state, B (Broken) and it’s description under INFO Listing Format
on page 2-87.



Updated the note on page 2-89 about the appearance of plus sign (+) to include
support for H-series RVUs.



Added a new file code 547 on page 2-94.



Consolidated the file codes, 550-565 on page 2-94, in one row with the definition
SQL/MX files.



Updated the VERSION information on page 2-101 and added a reference to a
separate manual for more information on SQL/MX versioning.



Added a new note on pages 2-191 and 2-194 about passing filenames in
uppercase while using SPI interface.

What’s New in This Manual

File Utility Program (FUP) Reference Manual—523323-014

xii

Changes to the G06.29 Manual

Changes to the G06.29 Manual



Added a new note on page 2-89 about the appearance of plus sign (+) when an
OSS file is protected by POSIX access control list (ACL) .



Added an example of FUP short INFO for OSS files with POSIX ACL on page

2-99.



Added a note on page 2-151 about the RELOAD operation on ORSERV object
using the SHARE option.

Changes to the H06.05 Manual



Documented that FUP supports fully-qualified SQL/MX ANSI names for the
commands — INFO, LISTLOCKS, LISTOPENS, and RELOAD on page 1-1.



Documented that FUP has a limitation that the command line cannot exceed 132
characters and provided tips on how to use longer ANSI names on page 1-1.



Added a note on using two separate commands for ANSI names and Guardian
names on page 1-1.



Added missing file codes and the corresponding definitions in Table 2-2 on
page 2-90.



Added the TYPE variable and its description to the key column example on page

2-102.



Added a note on page 2-102 that the key column TYPE and LENGHT is not
displayed for SQL/MX objects .



Updated these commands to document the FUP support for SQL/MX ANSI names:



INFO on page 2-82



LISTLOCKS on page 2-118



LISTOPENS on page 2-124



RELOAD on page 2-148



Removed the sentence about specifying the same pri-extent-size and sec­extent-size for all partitions under pri-extent-size

, sec-extent-size on

page 2-178.



Added new error messages on page 3-33 through 3-37 that might occur when
using SQL/MX ANSI names for the commands - INFO, LISTLOCKS, LISTOPENS,
and RELOAD.



Updated the syntax diagrams for:



INFO command on page C-6



LISTLOCKS command on page C-6

What’s New in This Manual

File Utility Program (FUP) Reference Manual—523323-014

xiii

Changes to the H06.05 Manual



LISTOPENS command on page C-6



RELOAD command on page C-8

What’s New in This Manual

File Utility Program (FUP) Reference Manual—523323-014

xiv

Changes to the H06.05 Manual

File Utility Program (FUP) Reference Manual—523323-014

xiii

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.

Organization of This Manual

Section or
Appendix Title Description

1 FUP Overview

Provides an overview of the FUP software. The overview
includes instructions for starting or interrupting FUP
processes, entering FUP commands, and specifying files
within FUP. The section defines FUP concepts that are
common to most of the FUP commands, including file sets
and list files. This section also demonstrates how to use
DEFINEs with FUP and how to handle HP NonStop
SQL/MP and HP NonStop SQL/MX.

2 FUP Commands

Presents the syntax for each of the FUP commands.

3 FUP Messages

Explains the error and warning messages issued by FUP
and supplies the recommended recovery methods for
each incident.

A DEFINE Tables

Contains reference tables that summarize how FUP input
and output options work with DEFINEs.

B FUP Command

Summary

Categorizes all the FUP commands described in Section

2.

C FUP Command

Syntax Summary

Provides a syntax summary of all FUP commands.

About This Manual

File Utility Program (FUP) Reference Manual—523323-014

xiv

Additional Information

Additional Information

For more information about FUP and its associated components, see:

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.

Manual Description

5200 Optical Storage Facility
(OSF) Reference Manual

Describes the FUP commands that require special
considerations when used with the 5200 OSF (for D­series RVUs only)

Enscribe Programmer’s Guide Provides descriptions of structured disk files and the file

attributes specified in FUP commands.

File Utility Program (FUP)
Management Programming
Manual

Explains how to execute commands from within an
application program by using the Subsystem
Programmatic Interface (SPI).

Guardian Disk and Tape
Utilities Reference Manual

Explains tape handling procedures and describes the
BACKCOPY, BACKUP, DCOM, DSAP, RESTORE, and
TAPECOM utilities.

Guardian Procedure Errors
and Messages Manual

Describes any file-system (or other) errors referenced by
number in the FUP error messages.

Guardian User’s Guide Provides task-oriented instructions for using FUP and

DEFINEs. It also includes a basic FUP introduction.

SQL/MP Reference Manual 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.

SQL/MX Reference Manual Describes the syntax of SQL language elements.
Safeguard User’s Guide Describes the basic security tasks that FUP requires.
TACL Reference Manual Describes the RUN command options and all the other

TACL commands and functions.

SQL/MX Glossary Describes terms specific to SQL/MX.

About This Manual

File Utility Program (FUP) Reference Manual—523323-014

xv

General Syntax Notation

UPPERCASE LETTERS. 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.

Items not enclosed in brackets are required. For example:

file-name

computer type. Computer type letters within text indicate C and Open System Services

(OSS) keywords and reserved words. Type these items exactly as shown. Items not
enclosed in brackets are required. For example:

myfile.c

italic computer type. Italic computer type letters within text indicate C and Open

System Services (OSS) variable items that you supply. Items not enclosed in brackets
are required. For example:

pathname

[ ] Brackets. Brackets enclose optional syntax items. For example:

TERM [\system-name.]$terminal-name
INT[ERRUPTS]

A group of items enclosed in brackets is a list from which you can choose one item or
none. 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. For example:

FC [ num ]
[ -num ]
[ text ]

K [ X | D ] address

{ } Braces. 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. For example:

LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }

ALLOWSU { ON | OFF }

| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in

brackets or braces. For example:

INSPECT { OFF | ON | SAVEABEND }

About This Manual

File Utility Program (FUP) Reference Manual—523323-014

xvi

Notation for Messages

… Ellipsis. 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. For example:

M address [ , new-value ]…
[ - ] {0|1|2|3|4|5|6|7|8|9}…

An ellipsis immediately following a single syntax item indicates that you can repeat that
syntax item any number of times. For example:

"s-char…"

Punctuation. Parentheses, commas, semicolons, and other symbols not previously

described must be typed as shown. For example:

error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name

Quotation marks around a symbol such as a bracket or brace indicate the symbol is a
required character that you must type as shown. For example:

"[" repetition-constant-list "]"

Item Spacing. 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. In this example, no
spaces are permitted between the period and any other items:

$process-name.#su-name

Line Spacing. 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:

ALTER [ / OUT file-spec / ] LINE
[ , attribute-spec ]…

Notation for Messages

This list summarizes the notation conventions for the presentation of displayed
messages in this manual.

Bold Text. Bold text in an example indicates user input typed at the terminal. For example:

ENTER RUN CODE
?123
CODE RECEIVED: 123.00

The user must press the Return key after typing the input.

About This Manual

File Utility Program (FUP) Reference Manual—523323-014

xvii

Notation for Messages

Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or

returned exactly as shown. For example:

Backup Up.

lowercase italic letters. Lowercase italic letters indicate variable items whose values are

displayed or returned. For example:

p-register
process-name

[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For

example:

Event number = number [ Subject = first-subject-value ]

A group of items enclosed in brackets is a list of all possible items that can be
displayed, of which one or none might actually be displayed. 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. For
example:

proc-name trapped [ in SQL | in SQL file system ]

{ } Braces. A group of items enclosed in braces is a list of all possible items that can be

displayed, of which one is actually displayed. 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. For example:

obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }

process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown. }

| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in

brackets or braces. For example:

Transfer status: { OK | Failed }

% Percent Sign. 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. For example:

%005400
%B101111
%H2F
P=%p-register E=%e-register

About This Manual

File Utility Program (FUP) Reference Manual—523323-014

xviii

Notation for Management Programming Interfaces

Notation for Management Programming Interfaces

This list summarizes the notation conventions used in the boxed descriptions of
programmatic commands, event messages, and error lists in this manual.

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. 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

!o. 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.

File Utility Program (FUP) Reference Manual—523323-014

1-1

1 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. You can use FUP to
create, display, and duplicate files, load data into files, alter file characteristics, and
purge files.

FUP supports these types of Enscribe disk files:



Key sequenced



Entry sequenced



Relative



Unstructured (including text files)

FUP provides information about these types of HP NonStop Open System Services
(OSS), SQL/MX, and SQL/MP files:



Tables



Indexes



Partitions



Views



Object programs

FUP supports fully qualified SQL/MX ANSI names for the commands - LISTLOCKS,
LISTOPENS, INFO, and RELOAD. 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. 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.

Note. FUP does not support mixing of both SQL/MX objects (using their ANSI names) and
Guardian objects in the same command. Therefore, the user must use two separate
commands, one for Guardian names and another for ANSI names.

Note. For more information about Enscribe files and structured query language (SQL) files,
see the Enscribe Programmer’s Guide, the SQL/MP Reference Manual, the SQL/MX
Reference Manual , and the Guardian User’s Guide .

FUP Overview

File Utility Program (FUP) Reference Manual—523323-014

1-2

Starting a FUP Process

Starting a FUP Process

Access to FUP is available through the HP Tandem Advanced Command Language
(TACL), the standard command interface in the Guardian environment. 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

To enter FUP commands at the TACL prompt, type the term FUP, followed by the
command you want, and press the RETURN key:

The FUP command (INFO *) in this example instructs FUP to list the file information of
each file in your current subvolume. After FUP executes the command, control of the
terminal returns to TACL. A separate FUP process starts and completes for each
command you enter.

Topic 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. For a description of command files and run options, see From a Command
File on page 1-3.

1> FUP INFO *

FUP Overview

File Utility Program (FUP) Reference Manual—523323-014

1-3

Interactively

Interactively

Entering FUP commands within FUP (interactively) saves time if you are going to enter
a series of commands. Type the term FUP (without any commands or options) at the
TACL prompt, and press the RETURN key to start an interactive FUP process:

The FUP process is ready to receive commands interactively when its sign-on banner
and prompt (a hyphen) are first displayed. You can then type a FUP command at each
subsequent FUP prompt:

After FUP executes the command, the FUP prompt reappears. Type another FUP
command at the subsequent prompt, or use the EXIT command to return control of the
terminal from FUP to TACL:

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). This example shows a command file (ALLSUBS):

-- FUP commands for obtaining a list of all

-- subvolumes in $DISK1, $DISK2, and $DISK3

--

-- Last modified 5/17/01

-­SUBVOLS $DISK1 -- Contains manufacturing files
SUBVOLS $DISK2 -- Contains administrative files
SUBVOLS $DISK3 -- Contains all other files

The example command file (ALLSUBS) uses a FUP command (SUBVOLS) to list the
subvolumes in three different disk volumes ($DISK1, $DISK2, and $DISK3). It also
includes comment lines to help identify the file and explain the operations that are
performed.

1> FUP
File Utility Program - T6553D45 - (13OCT2000) SYSTEM \WEST
Copyright Tandem Computers Incorporated 1981, 1983, 1985-2000

-

-INFO *

-EXIT

Note. You can enter two dashes (--) or a less-than symbol (<) to indicate a comment. FUP
ignores any text that follows these punctuation marks until the end of the command line.

FUP Overview

File Utility Program (FUP) Reference Manual—523323-014

1-4

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).

Type the term FUP and the command file and run option you want, and press
RETURN:

In this example, the FUP process starts when you use a command file (ALLSUBS) and
run option (IN). 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.

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.

FUP Custom File Guidelines



The FUPLOCL file must be in the current system subvolume, $SYSTEM.SYSnn
(or $SYSTEM.SYSTEM). FUPLOCL lets you set a site-standard FUP environment.



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.

Note. For more information about the TACL RUN command, see the TACL Reference Manual.

1> FUP / IN ALLSUBS /

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.

FUP Overview

File Utility Program (FUP) Reference Manual—523323-014

1-5

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.

FUP Custom File Example

To save the current CONFIGURE options to a file that can be executed with FUP
OBEY or as a FUPCSTM file:

-SHOW /OUT FUPCSTM/ CONFIGURE AS COMMANDS

Interrupting or Terminating a FUP Process

To terminate a FUP process after it has started, use CTRL-Y.
To interrupt a FUP process, press the BREAK key.

Entering a FUP Command

For descriptions of the syntax for each FUP command, see Section 2, FUP

Commands. The basic command structure (including run options) is:

User Entry Results

CTRL-Y 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.

BREAK 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.

FUP [ / run-options / ] [ command ]

FUP Overview

File Utility Program (FUP) Reference Manual—523323-014

1-6

Entering a FUP Command

run-options

are any of the available options for the TACL RUN command. They must be
separated from each other by commas, and enclosed on the command line with
slashes (/). 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 Enscribe­structured 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
TA CL 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 1-21.

command

is a FUP command. You can enter only one FUP command in a TACL command. If
you need additional screen space to enter the command, end the command line
with an ampersand (&) and press RETURN. 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 TA CL.