Digital PDFs

DEC-XV-UPPUA-A-D

May 1975

114 pages

Original

33MB

Document:	PIP XVM Utility Manual
Order Number:	DEC-XV-UPPUA-A-D
Revision:
Pages:	114
Original Filename:	http://bitsavers.org/pdf/dec/pdp15/XVM/DEC-XV-UPPUA-A-D-PIP_XVM_UTILITY_MANUAL.pdf

OCR Text

PIPXVM
UTILITY MANUAL
DEC-XV-UPPUA-A-D

digital equipment corporation · maynard. massachusetts

First Printing, December 1975

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may be used or copied only in accordance with the terms of such
license.
Digital Equipment Corporation assumes no responsibility for the use or
reliability of its software on equipment that is not supplied by
DIGITAL.

1975 by Digital Equipment Corporation

The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM

DECsystem-lO
DEC tape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8

MASSBUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-IO
TYPESET-ll

CONTENTS
PAGE

PREFACE
CHAPTER

CHAPTER

INTRODUCTION

1.1
1.2
1.3
1.4

PIP PROGRAM
MANUAL ORGANIZATION AND USE
WRITING CONVENTIONS
PIP STARTUP PROCEDURES

CO~.AND

2.1
2.2
2.2.1
2.2.2
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7

PIP COMMAND STRING, GENERAL DESCRIPTION
TYPES OF PIP COMV~NDS
Destination/Source Commands
Single-Device Commands
COMMAND STRING ELEMENTS
Command String Delimiters
Standard XVM/DOS I/O and Storage Devices
Primary Operations
Optional Functions
Specifying UFD's
Specifying Data Modes
PIP UFD and File Protection Codes

PIP OPERATIONS, DETAILED DESCRIPTIONS AND
EXAMPLES OF USE

3.1
3.2

INTRODUCTION
N:
DIRECTORY SETUP OR INITIALIZATION
OPERATION
Create/Initialize Current UFD
Setting up the UFD Protection Code
Deletion of UFD's
Initialization of DECtape Directories
(S) Switch: Setting up DECtape Directories
with tQ Areas
L:
DIRECTORY LIST OPERATION
List UFD for Current or Specified UIC
(M) Switch: List MFD
(L) Switch: List Monitor SYSBLK
(p) Switch: List UFD with File Protection
Codes and RIB Pointers
List DECtape Directories
List Selected File
T:
FILE TRANSFER COMMANDS
Required Data Mode Specifications
System Device File Protection Codes
File Transfers to Disk
UFD to UFD File Transfers
Device to Device File Transfers
Transfer of Keyboard Inputs to Output
Devices

3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6

1-1
1-1
1-2
1-2

STRING FORMATS AND BASIC OPERATIONS

iii

2-1
2-2
2-2
2-3
2-6
2-6
2-7
2-7
2-9
2-11
2-11
2-13

3-1
3-1
3-1
3-3
3-4
3-5
3-5
3-6
3-7
3-8
3-8

3-9
3-10
3-11
3-13
3-15
3-15
3-16
3-17
3-18

3-19

Contents (Cont)

Page
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
3.5.8
3.6
3.7
3.7.1
3.7.2
3.7.3
3.8
3.8.1
3.8.2
3.8.3
3.9
3.9.1
3.9.2
3.9.3
3.10
3.11
3.11.1
3.11.2
3.12
CHAPTER

CHAPTER

FILE TRANSFERS WITH OPTIONAL FUNCTIONS
(G) Switch: Parity/Checksum Error
Correction Facility
(E) and (C) Switches: Tab-to-Space,
Space-to-Tab Conversion
(N) Switch: Directory Initialization
During Transfer
(W) Switch: Combining Files During
Transfers
Inputting and Combining Files from Paper
Tape:
(W) Switch
Card Input and Card File Modification
Operations:
(Q), (C), (T) Switches
(T) Switch: Delete Trailing Spaces
(V) Switch: Vertical Forms Control on
Output
V: VERIFY OPERATION
S: SEGMENT FILE OPERATION
S, Segment File Command
T Command Requirements for S Operations
Source File to Multiple Paper Tapes
Segmentation Operations
D: DELETE FILE OPERATION
Deletion of Files from UFD's
Deletion of DECtape Files
(X) Switch:
Deletion of Truncated Files
R: FILE RENAME OPERATION
Renaming Files
Setting File Protection Codes
Setting Directory Protection Codes
B: BLOCK COPY OPERATION
C:
COpy MASS STORAGE OPERATION
Adding Files, Copy Operation
Copy with Directory Initialization
U:
UPDATE STORAGE ALLOCATION TABLES
OPERATION

MIC PIP OPERATIONS

4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4

GENERAL PIP MIC OPERATIONS
SPECIFIC MIC FUNCTIONS
N Operation
L, List Directory Operation
Delete Truncated Files from System
I, Initialize Operation

PIP ERROR DETECTION PROCEDURES AND MESSAGES

5.1
5.1.1
5.1. 2
5.2
5.3

INTRODUCTION
User Command String Errors
Operational Errors
PIP ERROR MESSAGES
CORRECTION AND RECOVERY CO~~DS

QUICK REFERENCE TABLES

6.1
6.2
6.3
6.4

INTRODUCTION
OPTIONS VERSUS PRIM~RY OPERATIONS
PIP COMMAND STRING FORMAT CHARTS
PIP USER OPERATION TABLES
iv

3-21
3-21
3-22
3-23
3-24
3-26
3-26
3-27
3-28
3-28
3-30
3-30
3-30
3-33
3-33
3-34
3-36
3-36
3-36
3-37
3-38
3-38
3-39
3-41
3-42
3-43
3-44

4-1
4-1
4-1
4-2
4-2
4-2

5-1
5-1
5-2
5-2
5-7

6-1
6-1
6-1

6-1

Contents (Cont)

Page
APPENDIX A

USE OF VT15 GRAPHICS DISPLAY SYSTEM

A-1

APPENDIX B

USE OF VP15A DISPLAY DEVICE

B-1

APPENDIX C

XVM/DOS TERMS AND ACRONYMS

C-1

FIGURES
Page
Figure

2-1
2-2
6-1
6-2

Destination/Source Command String Format
PIP Single Device Commands, General Format
Destination/Source Command String Format
PIP Single Device Commands, General Format

2-4
2-5
6-4
6-5

TABLES
Page
Table

1-1
2-1
2-2
2-3
2-4
2-5
3-1
3-2
5-1
5-2
6-1
6-2
6-3
6-4
6-5
6-6

General Keyboard Command Characters
Command String Delimiters
PIP Command Device Mnemonics
PIP Primary Operations, Summary
PIP Optional Functions
Data Modes and Data Mode Indicators
Legal Data Mode and Function Switch
Combinations for Transfer Operations
Legal Combinations of Function Switches
in Transfer Operations
PIP Error Messages
User Correction and Recovery Commands
Available Options Versus Primary Operations
Directory Operations
List Operations
File Modification Operations
File Transfer Operations
COPY Operations

1-3
2-6
2-7
2-8
2-9
2-12
3-15
3-21
5-3

5-7
6-3
6-6
6-8

6-10
6-12
6-14

LIST OF ALL XVM MANUALS

The following is a list of all XVM manuals and their DEC numbers, including the latest version available.

Within this manual, other XVM

manuals are referenced by title only.

Refer to this list for the

DEC numbers of these referenced manuals.
BOSS XVM USER'S MANUAL

DEC-XV-OBUAA-A-D

CHAIN XVM/EXECUTE XVM UTILITY MANUAL

DEC-XV-UCHNA-A-D

DDT XVM UTILITY MANUAL

DEC-XV-UDDTA-A-D

EDIT/EDITVP/EDITVT XVM UTILITY MANUAL

DEC-XV-UETUA-A-D

8TRAN XVM UTILITY MANUAL

DEC-XV-UTRNA-A-D

FOCAL XVM LANGUAGE MANUAL

DEC-XV-LFLGA-A-D

FORTRAN IV XVM LANGUAGE MANUAL

DEC-XV-LF4MA-A-D

FORTRAN IV XVM OPERATING ENVIRONMENT MANUAL

DEC-XV-LF4EA-A-D

LINKING LOADER XVM UTILI'rY MANUAL

DEC-XV-ULLUA-A-D

MACll XVM ASSEMBLER LANGUAGE MANUAL

DEC-XV-LMLAA-A-D

MACRO XVM ASSEMBLER LANGUAGE MANUAL

DEC-XV-LMALA-A-D

MTDUMP XVM UTILITY MANUAL

DEC-XV-UMTUA-A-D

PATCH XVM UTILITY MliliUAL

DEC-XV-UPUMA-A-D

PIP XVM UTILITY MANUAL

DEC-XV-UPPUA-A-D

SGEN XVM UTILITY MANUAL

DEC-XV-USUTA-A-D

SRCCOM XVM UTILITY MANUAL
UPDATE XVM UTILITY MANUAL
VP15A XVM GRAPHICS SOFTWARE MANUAL

DEC-XV-USRCA-A-D
DEC-XV-UUPDA-A-D
DEC-XV-GVPAA-A-D

VT15 XVM GRAPHICS SOFTWARE MANUAL

DEC-XV-GVTAA-A-D

XVM/DOS KEYBOARD COMMAND GUIDE

DEC-XV-ODKBA-A-D

XVl'l/DOS READER'S GUIDE AND
IvlASTER INDEX

DEC-XV-ODGIA-A-D

XVM/DOS SYSTEM MANUAL

DEC-XV-ODSAA-A-D

XVM/DOS USERS MANUAL

DEC-XV-ODMAA-A-D

XVM/DOS V1A SYSTEM INSTALLATION GUIDE

DEC-XV-ODSIA-A-D

XVM/RSX SYSTEM MANUAL

DEC-XV-IRSMA-A-D

XVM UNICHANNEL SOFTWARE MANUAL

DEC-XV-XUSMA-A-D

vii

PREFACE
This manual describes and illustrates the features provided by the
XVM Utility program PIP.

This utility program operates only within

the XVM Disk Operating System (XVM/DOS) monitor environment.
In the preparation of this manual it was assumed that the reader is
familiar with the contents of the XVM/DOS USERS MANUAL and with the
general operating procedures for the XVM equipment.

CHAPTER 1
INTRODUCTION
1.1

PIP PROGRAM

The PIP XVM (PIP) Utility Program enables the system user to perform
the following major functions via keyboard commands:
a)

Interchange information between system peripheral I/O
devices, the system disk device and peripheral I/O devices;
and between user file areas located on the system disk
device.

Perform verification and modification procedures on information being transferred.

Initialize, list and modify file directories of directoried
disk and other directoried devices.

This manual is primarily concerned with disk-oriented operations.
PIP, however, may be used with all other standard XVM I/O and mass
storage devices; limitations and differences in operation are indicated where applicable.

There are specific operations on magtape

which PIP does not perform, such as create and list a file directory.
Users of magtape should also read the MTDUMP XVM Utility Manual to
learn how to perform these special functions using the MTDUMP XVM
Utility Program.
1.2

MANUAL ORGANIZATION AND USE

This manual is intended for users who are familiar with:
a)

the general system operating procedures (i.e., use of
equipment and system startup procedures) ;

the elements, structure, and use of the XVM/DOS monitor
as described in the XVM/DOS Users Manual

Introductory information and detailed descriptions of PIP operations
and their applications are given in Chapters 1 through 5.
contains quick-reference tables.

1-1

Chapter 6

Introduction
New users of PIP should familiarize themselves with the contents of
Chapters 1 through 5; thereafter, they need only refer to Chapter 6
for concise information.
XVM/DOS terms used in this manual, their acronyms and descriptions,
are presented in Appendix C.
1.3

WRITING CONVENTIONS

Table 1-1 lists a group of commonly used keyboard command and control
characters together with (a) their functions as recognized by PIP
and (b) their representations in listing and, in this manual, in
text and examples.
1.4

PIP STARTUP PROCEDURES

Once a user has completed the system log-in procedures, PIP may be
called into core by the entry of the name "PIP".

When loaded, PIP

outputs the following message on the console printer:
$PIP
PIP XVM Vxxnnn
>

followed by a right angle (»

"ready" symbol.

User commands are entered immediately after the ready symbol.

Once

an operation has been initiated, the user must not attempt to make
any further entries until PIP prints the ready symbol.

The only

exception to this is when the user wishes to abort the current operation.

The entry of:
a)

CTRL P (iP) aborts the current operation and
returns control to PIP;

CTRL C (+C) aborts the current operation and
returns control to the monitor.

1-2

Introduction

Table 1-1
General Keyboard Command Characters

ACTUATED
KEY OR KEY
COMBINATION

PRINTED
RESPONSE &
TEXT SYMBOLS

FUNCTION INITIATED BY ENTRY

RUBOUT

Causes deletion of the last
entered character.

CTRL U

@
Response
Text
- tu

Causes deletion of the last
entered line.

CTRL P

Restarts PIP or continues on
interrupted input or output
operations on a non-directoried
device

CTRL C

Causes control to be returned
to the Moni tor.

CTRL R

Enables processing to be resumed
when a Device Not Ready (IOPS4)
error has been corrected.

CTRL D

Terminates input from the console keyboard.

SHIFT 0
or
UNDER BAR

Divides PIP command string into
Output and Input sections (see
section 2).

RETURN

Non-printing
(Text symbol is ) )

Initiates a carriage return/
line feed operation.
Normally
used to terminate command strings.

ALT MODE

Non-printing
(Text symbol is ®)

Causes control to be returned
to the Monitor on completion of
the current operation.
The monitor performs a carriage return/
line feed operation and announces
itself.

1-3

CHAPTER 2
COMMAND STRING FORMATS AND BASIC OPERATIONS

This Chapter describes the basic PIP command string formats and the
elements which comprise them.

Included are lists and descriptions of

the operations provided the user by PIP.
2.1

PIP COMMAND STRING, GENERAL DESCRIPTION

PIP command strings are limited to a maximum of 72 characters and a
single console device input line and no provision is made for command string continuation lines.

The items which may be specified

in a PIP command string are:

Item

How Specified

Primary operation to
be performed

Identified by an assigned single alphabetic character (e.g., T for Transfer).
Refer to Table 2-3 for a description
of each Primary Operation and its command character.

Any storage or I/O
device(s) involved

Identified by an assigned 2 or 3character alphanumeric mnemonic (e.g.,
DT for DECtape).
Refer to Table 2-2
for a listing of the standard DOS system storage devices and the mnemonic
assigned to each.

The names of any
files involved

Identified by an assigned (user or
system) 6-character filename plus a
3-character extension.
Refer to the
XVM/DOS User's Manual for descriptions
of filenaming considerations.

Optional Functions
(i.e., Data Modes and/or
secondary operations)
to be included

Identified by an assigned alphabetic
character enclosed in parentheses
e.g., (A).
Refer to Table 2-4 for
a description of each optional function
and its assigned command character.
One or more functions may be specified
e.g., (A) or (AN).

2-1

Command String Formats and Basic Operations

Item

How Specified

Optionally defined
Protection codes

Identified by a numeric normally enclosed in parentheses; only one code
may be specified in a command.
If an
optional function is specified, the
protection code and command character(s)
should be placed within the same set
of parentheses (e.g., (1) or (AI)).
Refer to paragraph 2.3.7 for a description of protection codes.

Required User File
Directory (UFD)
Identification

UFD's in commands are identified by
their assigned 3-character mnemonic
(UIC) enclosed within angle brackets
(e. g., < ABC> ) i refer to paragraph
2.3.5 for a detailed description.

2.2

TYPES OF PIP COMMANDS

There are two basic types of PIP commands:
a)

Destination/Source commands, and

Single-Device commands.

These command categories are described, individually, in paragraphs
2.2.1 and 2.2.2.
2.2.1

Destination/Source Commands

Commands of this type are used to specify PIP operations which involve the transfer of data between two devices or device areas.
Such commands consist of two sections separated by a + delimiter:
[DESTINATION]+[SOURCE]
The elements within these sections specify where the data to be transferred is to be found [SOURCE] and where it is to go [DESTINATION] •
The major operation to be performed is always the first character in
any PIP command string; optional operations may be specified in
either section of this type of command.
ing command string:

2-2

For example, in the follow-

Command String Formats and Basic Operations

the destination section consists of:

The elements of this section specify:
a)

= a Transfer operation is to be performed
the disk device is to receive the Transferred
data
NOTE
When disk is specified, it
represents the current UFD.

DESTFL,-,SRC

the name of the disk file into which the
Transferred data is to be written.

The SOURCE section of the above command string consists of:

The elements of this section specify:
a)

DTl =

FILEA SRC

the data to be transferred resides on the tape
mounted on DECtape Unit #1
the name of the DTI file which contains
the data to be transferred.

Figure 2-1 illustrates the format of the most complex form of the
destination/source type of command string.

This figure also lists:

the PIP operations which require the format illustrated,

permitted device mnemonics,

permitted switch options.

2.2.2

Single-Device Commands

Commands of this type are used to specify PIP operations which involve only a single device and a file or set of files.

Such a com-

mand must specify the operation to be performed and the device involved.

Where needed, filenames and option switches may also be

added to the command string.

For example, the command:

2-3

Command String Formats and Basic Operations

specifies that:

a delete (D) operation is to be performed,

the device containing the item to be deleted is
DECtape Unit #l (DT1) ,

the item to be deleted is file FILEA SRC.

JESFL L...J

SRC

~ (Ci)

+- DTn

'-----'

OPERATION

DESTINAilON

COr"J~AND

-1- -

CHARACTER

DESTl:,ATIO'i

=.ilc

T:-<1:1S:(::l

I_~)ptional

di.::::·C',~tcrl'

List

Copy mass

~~,~

storaq..:..'
Renar:~.--·

FILE

OPTION

4-S0URCE
SCURCE
FILE
DE'll c~ LJ ~Lil("nam" LJ ex!:.~

'-'.'r=-

LJ (:01",,":.'''''2 LJ · ~ :c) LJ S_\11 TCH (!3..L

JEVl CE

rJ.L-'
~. i 1 ·'

B:sck copy

:-:'C>I1-

~:ri':':1tt;~1

co:::~~as

:' i':J

~~O.!:-

t.:)

;,:S(2

\.:;or:w..as

sepdrate m'Jltiple f:ile
names ap.d ex-

ck:-

Sf' p,J-

:-:~ : ::~i.p=- ·_ ·

11<'1: :\':S

TER~lI NATOR

)~ Retc:r::
control
to PIP
AL-~~10DE

c::--:"lC'!'.~ i.~i!;;-·

pp : .:

:tJ..:1PC::'-

"'::".Ei:JC·

p~:::c;.

::noni tor

O':'rF' JECtape '-1ni t

c:::

'~\.: l" ' ''~YP0

C:u-J reader
DTn= DECtape ~nit

L':':--,.-,::'- pri:-.:"-;r

M~n=

:~'f<

:..=

= ~'F15A CR~ J~sp!ay

DP~=

Magtape unit
DK = DECdisk

DECdisk

~iskpac~

:"-)~':1--

~~ i t

RKn== Disk cartridge

D':'s ~:!?acr:

:l;.i::

RKn:-: Di sk cartr idge uni t

u~it

= Plotter

:)Qta

~locle

Function s\·;i ~ch.cs

S\~'i tcht-~s

---.--

::':OPS B:"nary

tabs to spaces
Flag bad parity :ines

I::-,a~Je

CO:"'..T,Ter:

:l.J'PS
B

:-::

Ret.'..:rn
cont.rol
to the

clrhl

Con~ert

T~SCI I

Alpha-

nUi:lQric
';::::la:=1C

;):'<"'1='

r.:~:tiplE~

spaces

tabs

Binal"Y
T:{

:...:

Sc'cn::'f:'::1t !ilt:s

- ~l~w I)ir~ct:0r~'
Sn:: :::: ~QW directory with C~R~ Q
aroa.
Size e)f area (nn) ::::
8, :2, 16, 20, 24, 28, or 32
(E Ivorcls) ~~ operation only.
j)~;:a;'llt :::: currc::t size of

sy~;terl.

F -

Irlscrt

For~ Feed every 55
10
('r after .EJEC~
Inpc:t mc:st be
Df:lc~C' tr,3.i lirhl sPdces }
in punc~1ed
:;c·let.c sequc::ce nUl::bers
card forrr,dt

l~.n~s

Req~est

the

a listing of

sys tE'::: !>IF :'J

Heq; lest a listing 0::- the
system SYSBLK directory
p = R;q~0St CFD listing with
RIB data

Vertical Control

Figure 2-1
Destination/Source Command String Format

2-4

Command String Formats and Basic Operations
Figure 2-2 illustrates the format of the most complex form of a SingleDevice PIP command.

Also listed in Figure 2-2 are:

the operations which require the illustrated format,

permitted device mnemonics,

permitted switch options.

DTn

OPERA nON
COMMAND

DEVICE

FI LEA,FI LEB
FILE(S)

'----' (A)

INVOLVED

CHARACTER '---.J MNEMON 1C L-J ~-"",-e_·1 ~ '---.J

N
V

I
U

New directory
Verify file
Delete
Initialize
Update
PR
DTn
DK
DPn
MTn
RKn

.,J

OPTION
SW ITCH (E S)

Use commas to separate
multiple filenames and
extensions.

TERMINATOR
~

-Return control
to PIP
ALT MODE
Return control
to Monitor

Paper Tape Reader
DECtape unit
DECdisk
Diskpack unit
Magtape unit
Disk cartridge unit

A
B
S

Snn
K
X

lOPS ASCII Data mode
lOPS Binary Data mode
New directory with a
core-sized tQAREA.
New directory with a
user-specified tQAREA.l
delete UFO.
delete all truncated
files.

Figure 2-2
PIP Single Device Commands, General Format

lDECtape only

2-5

Command String-Formats and Basic Operations

2.3

COMMAND STRING ELEMENTS

The basic elements which comprise the PIP command strings (i.e., delimiters, mnemonics, format requirements, etc.) are described in the
following paragraphs.

Also described are the major user capabilities

offered by PIP, sub-functions which may be carried out within the
context of major PIP operations, and how UFD's, data modes and protection codes are specified in PIP commands.
2.3.1

Command String Delimiters

Delimiters are flags which are set to separate elements of a command
string.

The delimiters used in PIP commands are listed and their

uses described in the following table.
Table 2-1
Command String Delimiters

L-I

In This Manner:

Use Delimiter:
(space)

Separate major command string
elements

(back
arrow)
(underbar)

Separate destination and
source sections of a command
string

dest.

(colon)

In RENAME command, separates UFD name from specified UFD protection code

<JAN:r1>

Separate device mnemonic
and filename

DTl:FILEA

Separate filenames within
a command string list

DTIL-IFILEA,FILEB,FILEC

(comma)

J-

source

TL-IDK+DTlL-lFILEAL-ISRC

Specify number of tapes
or files involved in an
operation when names are
not needed
Separate filename and filename extension or data mode
option

PRL-It, (READ 3 tapes)

(angle

Identify non-current UFD's

<JOE>

) (parentheses)

Identify option switches or
specified protection codes

(A)

Separator to indicate a
range of numbers

100-150

(semicolon)

DTl:FILEA,FILEB;SRC

< > brackets)

(dash)

2-6

Command String Formats and Basic Operations

2.3.2

Standard XVM/DOS I/O and Storage Devices

The I/O and storage devices for which the XVM/DOS Monitor contains
interfacing software are listed, together with their required command
mnemonics, in the following table.
Table 2-2
PIP Command Device Mnemonics

Required Mnemonic

Peripheral Device

DK
DPn

DECdisk (RF15)
Diskpack (RP~2)
Disk cartridge (RK~5)
DECtape
Magnetic tape
Teletype
Line Printer
Card Reader
Paper Tape Reader
Paper Tape Punch
Graphics Display
XYll/XY3ll Plotters
Printer/Plotter

RKn
DTn
MTn
TT
LP
CD
PR
PP
VT

XY
LV

NOTE
The letter n in the above table indicates
"unit number". For example, DECtape unit
#1 of a system is specified as DTI.
If no
unit number is specified in the mnemonic
for a multi-unit device, the numeric ~ is
assumed.
For example, the mnemonic DP is
equivalent to DP~.
2.3.3

Primary Operations

The major capabilities provided by PIP are referred to as primary
operations.

Transfer, the user-directed interchange of files between

storage devices, and List, the printing of user-specified user and
monitor directories, are two examples of PIP primary operations.
In a PIP command, the primary operation is identified by a single
alphabetic letter entered as the first character of the command
string.

For example, in the command:

the letter "T" specifies the transfer operation (Le., FILEA SRC
is to be transferred from DTI to the current UFD on DK).

2-7

Command String Formats and Basic Operations
All PIP primary operations are listed and described briefly in
Table 2-3.
Table 2-3
PIP Primary Operations, Summary
The Primary

is identified
by the

and performs the

OPERATION

COMMAND CHARACTER

TRANSFER

Transfer named data files between
peripheral I/O devices.

VERIFY

Check a named file for parity or
checksum errors.

SEGMENT

Divide a file into a specified
number of segments (16 maximum) and
store each segment as a separate
named file.

LIST

Provide listings of system directories.

NEW DIRECTORY

Either clear an existing directory
or, if one does not exist, establish a new one.

DELETE

Delete files from User File Directories.

RENAME

Rename files and change protection
codes for the file or the UFD in
which it is listed.

COPY, Mass Storage

Copy the contents of one mass
storage medium onto another.

BLOCK COPY

Copy the contents of one or more
selected data storage blocks contained by one device onto another
medium. Block copy to the disk may
be performed only by the MIC user.

INITIALIZE

Enable the system manager to clear
all disk bit maps and restore the
MFD to its original state. This
co~nand may be used only by the
MIC user.

UPDATE

Update the monitor'S Bad Allocation
Table (BAT) and Storage Allocation
Table (SAT) whenever defective storage blocks are detected on the disk.

FUNCTION

2-8

Command String Formats and Basic Operations
2.3.4

Optional Functions

PIP primary operations may be executed alone or they may include
one or more "optional functions".
The optional functions are used to specify parameters (such as data
modes) and secondary operations (such as parity checks) which are to be
carried out during the execution of the primary operations.

An optiona l

function is identified by an alphabetic letter enclosed in parentheses
which is entered as a switch in a PIP command.

Switch (A) which spec-

ifies that lOPS ASCII data is to be handled in the performance of the
primary operation and switch (Y) which indicates that a file segmentation operation is to be performed during the primary operation are
two examples of optional functions and their switches.

The use of

switch (A) in the following command:

specifies that the data contained by FILEA is in lOPS ASCII form.
All PIP optional functions are listed and described in Table 2-4.
Table 2-4
PIP Optional Functions
CO!v'l~ND

OPTION

FUNCTION

CHARACTER

lOPS ASCII
Data Mode

(A)

lOPS Binary

(B)

Image Alphanumeric

(I)

Dump

(D)

Image Binary

(H)

Bad Parity &
Checksum Check
& Correction

(G)

Outputs error messages and the
lines containing errors detected.
Corrective actions are permitted.

Tab to Space
Conversion

(E)

Causes all tabs found in the data
handled to be expanded into a
seri e s of spaces.

Convert Multiple
Spaces to Tabs

(e)

Causes each group of two or more
spaces encountered during the primary operation to be contracted to
a TAB.

Specifies the type of data (i.e.,
format) handled by the primary
PIP operation.

2-9

Command String Formats and Basic Operations
Table 2-4 (Cont)
PIP Optional Functions

OPTION

COMMAND
CHARACTER

FUNCTION

Segment Files

(Y)

Indicates that the file being transferred is to be segmented.

Combine Files

(W)

Combines two or more separate files
into a single file.

Form Feed

(F)

Causes a form-feed and a RETURN character to be inserted after the detection of each .EJECT statement or after
every 55
lines.
10

Delete Trailing

(T)

Causes all trailing spaces to be deleted from alphanumeric data being
handled during the primary operation.

Delete Sequence
Numbers

(Q)

Used for punched card input, this
option causes all input sequence numbers to be deleted.

Reserve QAREA with (Snn)
New Directory

Used for DECtape devices only, this
option initializes any existing directory or establishes a new directory,
and causes a CTRL Q area to be allocated on the device. The size of
the allocated area may be specified
(i.e., nn) by the user.

New Directory

(N)

Performs the same function as the N
primary operation.
It either clears
an existing directory or, if one
does not exist, establishes a new one.

List MFD

(M)

List SYSBLK

(L)

Enables standard UIC users to obtain
a listing of all unprotected UFD's
contained by the device (disk). The
MIC user will obtain a listing of all
UFD's contained by the device.
Enables the user to obtain a listing
of the system SYSBLK directory.

List UFD with
Auxiliary Data

(P)

Causes file RIB data to be added to a
UFD listing.

Delete UFD

(K)

Removes UFD entry from MFD.

Delete All
Truncated
Files

(X)

Causes all truncated files contained
by the current or specified UFD to
be deleted.

Vertical Forms
Control

(V)

File Protection
Codes

(N)

Translates standard FORTRAN IV vertical form control characters to those
that can be interpreted by the line
printer handler.
Specifies a protection code if a code
other than the default is desired for
the output files.

2-10

Command String Formats and Basic Operations
2.3.5

Specifying UFD's

Whenever a user logs in to the XVM/DOS Monitor prior to calling PIP,
he specifies a user identification code, e.g.,
$LOGIN RPK
This code (in this example, RPK) is taken to be the name of the UFD
(User File Directory) used in operation to and from disk whenever a
UFD is not specified in a command.
rent UFD.

It is called the default or cur-

Whenever a UFD which is not current is referenced in a PIP command
string:
a)

its UIC (identifying code) written within angle
bracket delimiters (e.g., <xxx» must be added
to the command.

the UIC must be inserted immediately after the
mnemonic representing the device on which its
UFD resides.

For example, the command:

>T~DK~<JAN>+DTl~FILEA~SRC)
specifies that FILEA SRC on DECtape unit #1 is to be transferred to
the non-current UFD "JAN" located on the disk device.
2.3.6

Specifying Data Modes

PIP operations which involve the interchange of data require that the
form of the data being handled (i.e., its data mode) be indicated in
the initiating command string.
Data modes in PIP are specified either by the filename extension of
the file being transferred or by an equivalent data mode option
switch.

The Data Mode indicators recognized by PIP are listed in

the following table (Table 2-5).
The available PIP data mode switches and their uses are:
a.

(A) lOPS ASCII Switch - Files containing data in
lOPS ASCII form require the use of the PIP (A)
data mode switch. ASCII files are identified by
the extensions: 1)
SRC or
2)
a 3-character extension where the
third character is numeric (e.g.,
004) •

(B) lOPS Binary Switch - Files ,containing da~a in lOPS
Binary form must be handled uS1ng the (B) sW1tch. The
filename extension BIN is used to identify binary files.

IRe fer to the XVM/DOS Users Manual for detailed descriptions of data
modes.
2-11

Command String Formats and Basic Operations
c.

(I) Image Alphanmaeric Switch - The (I) switch is required during transfer of Image Alphanumeric files
and, as the name Image implies, maintains the File data
in its exact form as read from the source file.
The (I)
switch must specifically be used when copies of paper
tapes in either HRM or RIM hardware reader modes (MACRO
.ABS or .FUIJL paper tape) are required.

(II) Image Binary Switch - Binary files (extension BIN)
to be maintained in their exact form must be transferred
using the (H) data mode switch.

(D) Dump Mode Switch - Files containing data in an absolute binary form (extension ABS) must be handled using
the (D) mode switch.

The specific combinataions of data mode switches and optional function
switches which are permitted in each of the PIP primary operations are
given in Section 3.

Table 2-5
Data Modes and Data Mode Indicators
DATA MODES
lOPS
ASCII
SRC
FILENAME

lOPS
BINARY

DUMP

IMAGE ALPHA/ IMAGE
NUMERIC
BINARY

I
I

BIN

EXTENSIONS
ABS
Numeric

(Al

(B)
OPTION
SWITCHES

- '.

CD l

(I)

(H)

Files that contain more than one data mode per file cannot be manipulated
using PIP.

The XYll plotter handler, XYA., accepts consecutive write

commands in a combination of both lOPS ASCII and

rops BINARY modes.

Further, a user program could create a mixed-mode file on a mass storage device.

2-12

Command String Formats and Basic Operations
DATA MODE SWITCHES VS. FILENAME EXTENSIONS
From Table 2-5 it can be seen that switch options

(A),

(B) and (D)

specify the same data modes as filename extensions SRC, BIN, and
ABS.

Only one data mode indicator is needed in a command string;

if the filename extension is given, its corresponding data mode
switch is not required; conversely, the extension is not needed if
the switch is given.

To illustrate:
IS EQUIVALENT TO:

THE COMMAND

TL....IDKL....IFILEA+DT2L....10LDFILL....ISRC) a)

TL....IDKL....IFILEA+DT2L....10LDFILL....I(A)~

T~DKL....IFILEA+DT2L....10LDFILL....IBIN) b)
TL....IDKL....IFILEA+DT2L....10LDFILL....IABS ~ c)

TL....IDKL....IFILEA+DT2L....10LDFILL....I(B»)

Files with extensions used by PIP to determine data modes must not
actually be of another mode.

PIP will refuse to transfer the file if

the data mode derived from the command string does not match that in
the first header word of the file.

For example, FILEl BIN should be

a file written in lOPS binary mode (~ in bits 14-17 of the first header
word).

It should not have been written, for example, in lOPS ASCII

(2 in bits 14-17) and then had its extension changed to BIN.
2.3.7

PIP UFD and File Protection Codes

In performing PIP operations which involve User Directories and/or the
files which they contain, the user must be aware of the UFD and file
protection codes involved.

These codes determine the accessibility

of the UFD's and of the files which they contain.
New Protection codes may be assigned by the user or, by default, by
the system.

Existing codes may be modified using PIP command R.

(refer to Section 3).
UFD's may be assigned the following codes:
DIRECTORY PROTECTION CODES

unprotected:

any user may access, manipulate
the contents, and delete an unprotected UFD.

protected:

only the user logged in under
the UIC of the UFD (or the MIC)
may write into a protected UFD.
NOTE

The Default value for UFD directory protection
codes is always 1.

2-13

TL....IDKL....IFILEA+DT2L....10LDFILL....I(D)~

Command String Formats and Basic Operations
Files may be assigned any of the following protection codes:
FILE PROTECTION CODES
PERMITTED

OPERATIONS

CODE

READ

WRITE

PROTECTION GIVEN

yes

unprotected

yes

write protected

none
given

SYSTEM DEFAULT VALUE

protected
l

NOTE
File protection codes are valid only when the
UFD in which they are located is protected
(code 1).

lThe system default value for file protection codes is set by the system manager (MIC) during the initial configuration of the system (i.e.,
system generation) .

2-14

CHAPTER 3
PIP OPERATIONS, DETAILED DESCRIPTIONS AND EXAMPLES OF USE
3.1

INTRODUCTION

This Chapter contains descriptions of the PIP operations which may
be performed by the standard (UIC) DOS system user.

The PIP opera-

tions unique to the system manager (MIC) are described in Chapter 4.
3.2

DIRECTORY SETUP OR INITILIZATION OPERATION

The New Directory, N, operation permits the user to:
a)

create a new UFD for the currently logged-in UIC
or a specified UIC,

initialize an established UFD for the current UIC
or a specified UIC,

initialize and change the protection code of the
UFD for the current or a specified UIC,

delete the UFD of the current or a specified UIC
from the system (i.e., remove its name from the
MFD) ,

initialize the directories of peripheral filestructured mass storage devices.

WARNING
Each time the N command is used, all of the
files on the directory involved are DELETED.
Care must be taken to ensure that needed files
are not lost.

lutility program MTDUMP must be used to initialize directories on Magtape units (NTn).
Refer to the MTDUMP XVN Utility Manual for a
description of MTDUMP and its use.
3-1

PIP Operations, Detailed Descriptions and Examples of Use
Each of the preceding functions and the command format required for its
execution are described in Sections 3.2.1 through 3.2.5.
3.2.1

Create/Initialize Current UFD

The command:

is used either to:
a)

establish a User File Directory (UFD) for the current
UIC, or

initialize (delete all files from) an existing UFD set
up for the current UIC.

For example, if the current UIC is "GEP" the new or initialized UFD
resulting from the above command has the format:

~ /.-

\ \(' I}- 7'5

DIRECTORY LISTING
1147 FREE BLKS
o US ER FI L ES
o USER BLKS

CGEP)

UFO's set up or initialized using the basic N command (i. e., N,-,OK~))
are automatically assigned a default protection code of 1

(write

operation permitted only to the current UIC) .
The current UIC can use the basic N command to set up UFO's under
other UIC codes by specifying another UIC in the N command. For
example, the current UIC "JAN" can set up a UFO under the UIC "ABC"
with the command:

UFD's set up in the above manner are automatically assigned a protection code of

(unprotected).

Any unprotected UFD located on the disk being accessed may be initialized by the current user if he knows and specifies its UIC.

For

- ',
3-2

PIP Operations, Detailed Descriptions and Examples of Use

example, an unprotected UFD with a UIC

of "SCR" is initialized by

the command:

3.2.2

Setting up the UFD Protection Code

UFD protection codes may be specified in

the N command to:

set a desired protection code for a new current or
specified UFD,

change the protection code of an

existing UFD.

The command formats used for these functions are:
a)

> NUDKU(X)~

for current UIC UFD.

>NuDKLf AAA > u(X))

for specified UFD's.

where:
(X)

< AAA >

represents the desired protection code
represents the specified UIC.

The UFD protection codes are:
1

protected

write operations only permitted
by the UIC or the system MIC.

unprotected

read/write operations permitted
to all users.

The following are examples of the uses of the above N command formats:
a.

The command:

creates or initializes the current UFD with a directory protection code of ~ (unprotected).
b.

The command:

3-3

PIP Operations, Detailed Descriptions and Examples of Use

creates (or initializes) the UFD "ABC" with a specified protection code of I (unprotected).
Remember,
if this type of command is used, the current user
cannot access the specified UFD since it will be
protected.
The R command, Section 3.9.3 should be used to change
the protection code of an existing UFD unless the
UFD is to be initialized (all files deleted).
3.2.3

Deletion of UFD's

The PIP N command permits the user to delete the UFD of the current
UIC and specified unprotected (code

UFD's from the system (i.e.,

remove their names from the MFD).
The "delete" function is set up by the addition of the "K" function
switch to the basic N command, as follows:

>NL-.lDKL-.I(K»)

deletes the UFD of the current UIC

>NL-.lDK L-.I<XXX>L-.I(K»)

deletes the UFD of a specified UIC
«XXX » •

For example, assume the following Master File Directory (MFD) as being
current:

Cu r rent dat e

24-NO V- 7.5

MF D DIR ECTORY LISTING
- - - - - - - Number of f r ee device blo c ks
575 3 FREE BLKS
47 USER FILES
Numb e r of u s e r fi les on dev ice
6 12 USER BlKS
Number o f devi ce bloc ks occu pie d
ABl
NON ( 0)
0
0 ~
by fi le s
XYZ
NON ( 0)
0
0
Ent ries of unp r otected UFD ' s
\
\
UFD prote c tion code

UFD UI C 'e

NOTE
Listings of the current MFD as shown above
are obtained using the PIP List (L) operation.
The commands:

>N~DK~<ABL>~(K»)
>N~DK~ <XYZ >a......I(K»)
Delete the unprotected and non-current UFD's ABL and XYZ from the disk.
Their deletion is illustrated by the resultant MFD:

3-4

Pip Operations, Detailed Descriptions and Examples of Use

e4- NOV-7!)

MFD DIRECTORY LISTING
5753 FREE BLKS

47
t) j 2

3.2.4

USER FILES
lJSER BLKS

Initialization of DECtape Directories

The directories of DECtape storage devices may also be initialized
using the N command.

The command format is:

> N device mnemonic and unit number)
For example, the command:

initializes the directory of the tape mounted on DECtape unit 1.
NOTE
When a DECtape is initialized, the tape's File
Bit Map blocks are cleared and the Directory
Block is set up to indicate that only the File
Bit Map and Directory Blocks are occupied.
3.2.5

(S) Switch:

Setting up DECtape Directories with tQ Areas

The optional function switch (S) added to DECtape N commands both
initializes the device directory and causes a CTRL Q area (tQAREA)
to be reserved on the DECtape for core tQ-dump operations as performed by the QDMP XVM utility program.

The (S) switch is the only

switch permitted in N DECtape commands.

The basic command format

is:

>N~device mnemonic & unit number~(S»)
The (S) switch used:
a)

alone

indicates that the size of the reserved
tQAREA should be the same as the current
system core size.
For example, the command:

3-5

in a system running in 16K of core establishes
a 16K tQAREA (word locations) on the tape
mounted on DECtape unit #1.
b) with a one or two digit number (i.e.,

(5nn»,

specifies the size of the tQAREA to be reserved
on the tape mounted on the DECtape unit.
For example, the command:
DTI

(524)

causes a QAREA, 24K in size, to be reserved
on the tape mounted on DECtape unit #1.
3.3

DIRECTORY LIST OPERATION

The List, L, operation enables the user to obtain copies of both disk
and DECtape directories in:
a)

punched tape form,

printed form, or

as a CRT display.

Copies of directories which contain only selected file entries may
also be obtained.
The basic command format used in L operations is:
>LL-Ilisting device+source device.)
where:
a)

the listing device may be the:
])

console teleprinter (TT)

line printer (LP),

3)
4)

paper tape punch (PP)
optional CRT display devices (refer to
Appendices A and B)

XY plotter

(LV)

the source device may be any directoried mass storage
device within the system (i.e., DK, RKn, DTn, DPn).

The

exceptions are magtape directories which cannot be listed
with PIP; r·1TDUMP must be used.

3-6

PIP Operations, Detailed Descriptions and Examples of Use
Three optional switches may be used within an L command; they are:
a)

(M), list Monitor MFD table

(L), list Monitor SYSBLK table

(P), used only in UFD list operations, this switch causes
additional file protection and file storage information
to be included in the requested listing.

The various list operations which may be performed, the required L
commands for each, and examples of the listings obtained are described
in Sections 3.3.1 through 3.3.6.
3.3.1

List UFO for Current or Specified UIe

The UFD for a current UIe located on a disk device may be listed
using the basic L command format.
For example, assuming a current UIe of "GEP", the command:

produces a printout of the UFO with a format similar to the following:

ZI;-:'JCV-75

DIRECTOHY LISTING
(GEP)-----1131 FR EE BLKS - - - - - - - - - 3 USER FILES
6 USER BLKS - - - - - - ,- /,- :~'/-T; )
PARTA SRC
PARTB
PARTC

SR C
SRC

CURRENT DATE
DIRECTORY IDENTIFICATION CODE (UIC)
NUMBER OF FREE BLOCKS ON THE DEVICE
NUMBER OF USER FILES CONTAINED BY THE UFD
NUMBER OF DEVICE BLOCKS OCCUPIED BY
THE UFD FILES

:>: -::;~:~- 2;~ - DIRECTORY USER FILE ENTRIES
~ ~ DATE USER FILE WAS ENTERED INTO UFD

3"':"-',;,-"J-!:J

~ NUMBER OF DEVICE BLOCKS OCCUPIED BY FILE

FILE FILENAME AND EXTENSION

The current user may also obtain a listing of any unprotected UFO
in the system by specifying its identifying UIe in the L command.
For example, the command:

causes the printout of the unprotected disk UFO identified by the
UIe "JAN".

3-7

PIP Operations, Detailed Descriptions and Examples of Use

3.3.2

(M) Switch:

List MFD

A listing of a disk Master File Directory (MFD) may be obtained by
the addition of the (M) switch to the L command.

For example, a line

printer listing of a DECdisk MFD is produced by the command:
\

> L.....,LP+DK....., (M)~

The listing produced \vould have a format similar to the following:
~/1-r\'C1,J-75

- - - - - - - - - - CURRENT DATE

MFD DIRECTORY LI8TING
I 147
EE RLKS
52 USER FILES
1616 USER BLKS
TUJ(
1003(0)
6
PIP
2532(0)
1

NUMBER OF FREE BLOCKS ON THE DEVICE
NUMBER OF USER FILES ON THE DEVICE
NUMBER OF DEVICE BLOCKS OCCUPIED BY USER
114)
FILES
76 - - - USER FILE DIRECTORIES

NUMBER OF DEVICE BLOCKS OCCUPIED BY
~
SPECIFIED UFD FILES
NUMBER OF FILES CONTAINED BY THE SPECIFIED UFD
FILE PROTECTION CODE

NUMBER OF FIRST DEVICE BLOCK OCCUPIED BY UFD

UFD IDENTIFIER (UIC under which it was created)
NOTE
MFD listings obtained by standard users (UIC's)
list only the unprotected UFD entries. Only
the system manager (MIC) can obtain a complete
list of both protected and unprotected UFD's.
3.3.3

(L) Switch:

List Monitor SYSBLK

The addition of the (L)

switch to a list command made to the disk

device containing the operating system results in a printout of the
system block (SYSBLK) table on the selected listing device.

For

example, assuming a DK system device, the command

produces a listing of the system SYSBLK on the system line printer,
with a format and contents similar to the following:

3-8

PIP Operations, Detailed Descriptions and Examples of Use

SYSRLK LI STI NG
NAME

.SYSLD

DOS15
tQAREA
B05S15

40
101
301
317
334
353
372
427
431

EDIT

EDITVP
EDITVT
PIP
QFILE
Mt-CRO
CREf
C~AIN
:'-L\

DllMP
DTCOPY

PATCH
UPDATE
SR CCOM
STRAN
891RAN

MTDUMP
SGEN

T1B

4~4

471
512
547
554
5?7
567
602
615
626
637
651
706

FA
SA
PS
100 17400
o
33 1352 14526 1742
200
5 77773
o
16 12411 71640 54020
15 12001
5636 12002
17 10277 7340 10551
17 10302 7335 10553
1526 16111
1671
35
2 17041
437 17045
33 2630 15005 2630
5 15450 2137 15451
7600 10037 7600
21
2323
35 2176 15441
5 15300 2337 15300
755 16701
3 16662
10 12700 3453 12700
13 12370 5247 12371
13 12674 4743 12777
11 13607 4030 13671
11 13562 4055 13644
12 13167 4450 13260
35 5740 10163 6004
7573 10044 7750
21
NB
40

l....----------l ...----~
PROGRAM NAME

Program size,
Number of
number of
blocks
word locations
allotted
to program
Program
First core
Number of
starting
first device
address ocaddre3s
cupied when
block ocprogram is
cupied by
loaded
program

SYSBLK supplies a complete listing of the language and utility programs contained by the system; the names listed in SYSBLK are the
keyboard commands required to call (i.e., load) the listed program
into core.
3.3.4

(P) Switch:

List UFD with File Protection Codes and RIBI
Pointers

The optional switch (P) added to an L command causes file protection
code, file starting block number, and RIB data to be added to each

IRetrieval Information Block, contains pointers to the non-contiguous
file storage blocks (refer to the XVM/DOS Users Manual, for a
complete description of this table).

3-9

PIP Operations, Detailed Descriptions and Examples of Use

file entry contained by the UFD.

For example, assuming the UIC "JAN"

to be current, the command:

produces the following printout:

2~ - ~OV -75

CURRENT DATE
UFD IDENTIFIER
1125 FFi EE BLKS
FREE DEVICE BLOCKS
I USER FI LES
NUMBER OF USER FIL ES
~' IJSER BL}{S - - - - - - - - - NUMBER OF USER FILE DEVICE B L OCKS
CR CFL BIN
2 2.f\ -/liO I/-75 - - - USER FILE ENTRY

DIRECTOR) LISTING

(JAN)

To illustrate the use of the (P) switch, the command:

produces the following printout:
NOTE
Only the information added by the {F} option
is indicated.

DIRECTORY [ISTING

(JAN)

1125 FREE BLl'S
I IJS["P FILES
'; USER BLKS
r:RDfL BJ N
2553(2)

~~ l'-N O\j -75

2552

, - - - - - - - - 11
/

til

--L

POINTER TO THE F I RST RIB WO RD I N B LOCK
PO INTER TO DE VICE BL OCK CON TAI NIN G F ILE R IB
TABLE

" - - - - CURRENT FILE PROTECTION CODE
BLO CK OF F ILE

3.3.5

List DECtape Directories

The directory of any DECtape storage device within a system can be
listed using the basic L command.

For example, the command:

>L L-ITT+-DT 1 )

causes the directory of the tape mounted on DECtape Unit #1 to be
listed on the console printer.

Directory listings have a format

similar to that of the following example:

3-10

PIP Operations, Detailed Descriptions and Examples of Use

CURRENT DATE

DIrECTOPY LISTING
1062 FPFF. RLKS

NUMBER OF FREE BLOCKS ON DECTAPE
NUMBER OF USER FILES ON DECTAPE
NUMBER OF DECTAPE BLOCKS OCCUPIED
BY DIRECTORY AND FILE MAPS (also
by Monitor if a system DECtape)
DIRECTORY FILE ENTRIES

U~EP

FILES
10 SYSTEf>1 RLKS
NUFIL SPC
1
FI L FA SP C
2
FIU:8 SRC
.3
FIU:C SPC
4
I')

TESTI SPC
\.TFST~ SP

()

NUMBER OF BLOCKS OCCUPIED BY FILE
FIRST BLOCK OCCUPIED BY FILE
FILENAME AND EXTENSION

Option switches (M) and (P) are illegal for devices other than disk
devices (i.e., DK, RKn and DPn).

The (L) switch, however, may be

used with DECtape if the DECtape contains an ADSS operating system.
3.3.6

List Selected File

The directory entries of specific files or groups of files in a current UFD, a specified UFD, or a device directory may be listed selectively by adding elements to the L command.
To list the directory entry for a specific file, add its filename
and extension to the L command.

For example, assuming the following

UFD to be current:

;) LJ.- ::C:\/-75

(GEP)

DIRECTORY LISTING
1131 fREE RLKS
5 USER FILES
15

PARTA
PARTB
PARTC
CRDFL
TESTl

USER BLKS

SRC
SRC
SRC

1
1
1

? il- NC' IJ-75
2.4-i'·}n\J-75

BIN

001

2. /1 - \1011- 75
21:- '\\CI}-75

}

DIRECTORY HEADER

}

FILE ENTRY LIST

:2 1\-f',,]C\l-75

3-11

PIP Operations, Detailed Descriptions and Examples of Use

the command:

produces the following line printer listing:

~;~ - ~:()1}-75

DIRECTORY LISTING
CGEP)
1131 FREE BLKS
5 USFR FILES
15 USER BLKS
TESTI
001
10 ?'''-~JQI/-75

}

NOTE THAT THE HEADER REMAINS
UNCHANGED
DIRECTORY ENTRY OF SELECTED
FILE

All files within a directory which have a common filename extension
may be listed as a selected group.

The required L command format is:

>L~listing dev.~#XXX+source

dev.,

)

where:
a)

# indicates the function,

xxx is the common filename extension.

For example, assuming the UFD "GEP" to be current, the command:

produces the following line printer listing:

2 L: - f',; :', II - 7 ':'

DIRECTORY LISTING
II~~I FREE BLKS
5 USER FI L ES
1 ~'5 USER BLKS

(GEP)

P f\R TA

SR C

2, /1- f.' C' ','- '/

PARTB
PARTC

SRC
SR C

2/'-i~C\.'-"/

?/:- i\'J'j-7

}
}

3-12

NOTE THAT THE INFORMATION CONTAINED BY THE DIRECTORY HEADER
IS UNCHANGED

LIST OF FILE ENTRIES WHICH HAVE
THE COMMON EXTENSION "SRC".

PIP Operations, Detailed Descriptions and Examples of Use

The (Pl optional switch may be used in "selected file (s)" L commands.
mand:

For example, assuming the UFD "GEP" to be current, the com-

produces the following line printer listing:
:::!J - ";r: V-75
DIRECTORY LISTING
(GEP)
1131 ffiEEBLKS
5 USER FILES
15 USER BLKS
TESTI
!2I01
2542(2)

NOTE THE ADDITION OF THE FILE FIRST
BLOCK NUMBER, PROTECTION CODE,
POINTER TO THE FILE'S RIB AND FIRST
RIB BLOCK.
2551

Files may also be "selectively listed" from DECtape directories by
using the device mnemonic and unit number (i.e., DTn) as the command
"source device".
3.4

The (P) option cannot be used in DECtape L commands.

FILE TRANSFER COMMANDS

The transfer of files between standard I/O devices is carried out by the
liT" operation.

During a basic T operation, data is read from a source

device and is written into a named area (file) on a specified destination device.

In addition to basic Read/Write transfers, PIP permits

performance of more complex operations by the use of optional function switches.

For example, transfer operations may include such

optional functions as:
a.

the correction of parity errors,

the conversion of tabs to spaces and vice-versa,

the segmentation of large files or the combination
of small files into a single file to be performed
as part of the T operation.

The T command string format is described in detail in Section 2.
ever, as a reminder, the basic elements are:

est.
>T L-I device:

L.J

mnemon1.C

For example:

3-13

How-

PIP Operations, Detailed Descriptions and Examples of Use

The following items should be observed when structuring a "T" command:
a.

During transfers between directoried devices, the
filename extension of the source file or an equivalent
data mode switch must be given to ensure that PIP can
find the source file.
For example:

>T~DK~FILEA~DT I~SOURCE~SRC)
b.

During single file transfers, the destination file is
named only if the name is to be different from that of
the source file.
For example:

>T~DK~DTI~SOURCE~SRC)

results in the contents and name of DTI file "SOURCE
SRC" being added to the current UFD.
2.
results in the contents of DTI file "SOURCE SRC" being
transferred to the current UFD under' the name "NUFIL
SRC".
c.

More than one file may be transferred in one T operation:
the files, however, must be in the same data
mode.
In multi-file transfers, the listed filenames
must be separated by commas; the common extension
(BIN, ABS, or SRC) or an equivalent data mode switch
is required only once in the series.
For example:
>T&...IDK&...ITESTA, TESTB-<-DT I ...... FI LEA , FILEB ...... SRC)
transfers two files from DTI into two differently names
file areas of the current UFD, both with the extension
SRC.
Although an extension ending in a numeric (~~l, for
example) will automatically imply lOPS ASCII, it cannot
be used as a common extension for all files in the series
by specifying it only once.
For example:

>T~DK~TESTA,TESTB+DTl ...... FILEA,FILEBL-I~~l~
transfers FILEA SRC to the disk as TESTA SRC and FILEB
as TESTB SRC.

L-I~~l

During multiple file transfers in which the source names
are to be retained on the destination device, commas
must be used on the destination side of the command.
The commas indicate to PIP the number of files involved;
the number of commas used must be one less than the number of source files.
For example, the command:
>T ...... DKL-I"

DTI ...... FILEA,FILEB,FILEC ...... SRC)

effects the transfer of three files from DTI to the
current UFD.
Note the use of two commas, one less
than the nurrber of source files specified.

3-14

PIP Operations, Detailed Descriptions and Exampl

Whenever optional switches are added to a T command,
they may be placed on either side of the dividing
symbol (Le.,

>T~DT~(N) + DK~FILEA~(A))
3.4.1

Required Data Mode Specifications

In transfer operations, the form of the data being handled must be indicated in the corrmand string either by a Data Mode Option switch or by
the Filename extensions used.
The use of data mode switches or filename extensions in command strings
is described in Section 2.3.6.

The specific combinations of data mode

switches and optional function switches permitted within the Transfer
command are listed in Table 3-1.

Table 3-1
Legal Data Mode and Function Switch Combinations
for Transfer Operations
DATA MODE
SWITCHES

A -------

FUNCTION
C
W
y

SWITCHES
NSF

x-x -x-x-x - x -x-x -x - x

I
I
I
B------------- X
X- X
I
I
I-----------------X-X

H - - - - - - - - - - - - - - - - - - x-x

D-----------------X-X
3.4.2

System Device File Protection Codes

During file transfer operations between disk storage devices or UFD's,
the user may specify a protection code for the transferred file.

(File

protection codes are listed and described in Section 2.3.7.
For example, assuming that the UFD "JAN" is current:

DIPECTORY LISTING
2263 FR EE RLKS
o USER FILES
o USER BLKS

(JAN)

and that the system file protection code default value is 2, the following series of commands:

3-15

PIP Operations, Detailed Descriptions and Examples of Use

>T~DK+DTl~SEGA

(A).)

>T~DK+DTl~SEGB

(AI»)

>L~LP+DK~(P»)
transfers files "SEGA" and "SEGB" from

the tape mounted on DEC tape

unit #1 and lists the directory "JAN" with the applicable file protection and RIB data:
:'l; - ~l::,V- 75

DI RE CTORY LISTING
(JAN)
2260 FREE BLKS
2 USER FILES
2 USER BLKS
SRC
1313(2)
SEGA
SRC
1312(1)
SES8

24 - ~~V -7 5

1313

?4 - ~U")\/-7 5

1312

~ fil e prot ec tion c ode
A,s shown in the directory, file SEGA was assigned the default protecti.on code while file SEGB was assigned the specified value (Le., 1).
3.4.3

File Transfers to Disk

Files may be transferred to disk devices from any standard input or
mass storage device within the system.

An entry for each file trans-

ferred is listed in the current or specified UFD.

Files may be trans-

ferred:
a)

as a complete copy of the source file including the
same filename;

with the same filename but a specified file protection code;

with a new name specified for the destination file.

Sample illustrations of the above functions appear below.

CAl >T DK<-DT I TEST! 001

t ransfe r f ile , kee p same name and
ac cep t system de f au lt f ile pro tection code .

(Bl >T DK <-DT I

tr an sfer fil e, keep s ame name bu t
sp ecify de sir ed f ile pro t ection
c ode .

TE ST2 00 2 (I)

3-16

PIP Operations, Detailed Descriptions and Examples of Use

(Cl >T DK DESTFL<-DTI

TESTI

001

8a-NOV-7~

DIRECTORY LISTING
(GEP)
5717 FREE BLKS
,3 USER FI LES
,33 USER BLKS
TESTI
001
1605(2)
TEST2
002
1652(1)
DESTFL SRC
1700(1)

-.L.1

Filename extension

(I)transfer file~ rename file and
specify desired file protection code.

10
13
10

~ 1: - ';1()\/-75

?4-~'rV-75

?1J-N(I\J-75

1650
1676
1716

66
10

Protection code

UFD to UFD File Transfers

3.4.4

Files may be read from:
a)

unprotected UFD's (code ~);

Example command:

>T~DK~+DK~>JAN>~TEST1~(A»)

protected UFD's (Code 1) if the file protection code of
the desired file permits the operation;
Example command:

>T~DK *" DK~<JAN>~FILEA'-'(B»)
c)

the current UFD and written into another, unprotected
(code ~) UFD;
Example command:

>T~DK~<JAN> + DK~EXAMP~ (A»)

one file of the current UFD into a second, differently
named, file of the current UFD.
Example command:

>T~DK~NUFIL + DK~OLDFILL ,-,(A»)
NOTE
UFD and file protection codes of input
files need not be considered in transfer
operations with the current UF'D.
Files may be written into:
a)

unprotected UFD's (code ~);
Example command:

>T~DK~<JAN> + DK:.....ITEST1 ,-,(A»)
b)

the current UFD or a specified file within the current
UFD.
Example command:

>T~DK~TEST1 .... DK'-'<JAN>~PATCH ..... (A»)
3-17

PIP Operations, Detailed Descriptions and Examples of Use
In addition to the above, transfer operations may be carried out between
files of the current UFD including the creation of a new file from another file within the UFD.

For example, assuming the following UFD as

current:
? /' - ~J() V- 75
DIRECTORY LISTING
1500 FREE BLKS
3

24
TEST!
TEST2
CONTS

(GEP)

USER FILES
USER BLKS

001
002
SRC

5214(2)
5234(2)
5261(2)

10
13
1

? 4 - 'WV-75
? 4- ~JO\}-75
2 11 - ")0 V- 75

5232
5257
5212

10
66

The command:

creates a new file "COUNTS SRC" from file "CaNTS SRC", giving the new
file a protection code of 1.
The operation performed results in the following UFD:
~ 4- \JOV-75

DIRECTORY LI f,fI NG
1476 FR EE BLKS

(GEP)

4 USER FILES
USER BLKS
001
5214(2)

25
TESTI
TEST2
CONTS

002
SRC

5234(2)
5261(2)

JUNIS SRC

5~1)

New file

10
13
1
1

;""LJ - ~.!r\l -7 5

::'/1 - \)O\J - 75
?, I, - ~.1 OV-75
~~ 1:.- \lC\/-75

5232
5257
5212
5263

10
66

o
o

Speci f ied Protection code

The capability of performing transfer operations within current UFO's
simplifies these operations and enables the user to take full advantage
of the interactive speeds of disk devices.
3.4.5

Device to Device File Transfers

The read/write

transfer of files between non-disk mass storage devices

and/or I/O devices is performed using the same types of commands as
described in
words

the preceding paragraphs.

Protection codes and user pass-

(Ule's), however, are not required since these items are unique

to disk file structures.

Typical examples of device to device command

strings are:
3-18

PIP Operations, Detailed Descriptions and Examples of Use

DECtape 2 to DECtape 1 transfer:

>T~DTl~NEWFIL+DT2~OLDFIL~(A))
b)

Papertape Reader to DECtape 1 transfer:

>T~DTl~NEWFIL~SRC

(A)
(I)

+ PRJ

NOTE
When inputting information from paper tape,
it is recommended that the (I) data mode
switch be used if the contents of the tape
are unknown.
c)

DECtape 1 to Line Printer (listing):
>T~LP+DTl~NEWFIL~(A))

3.4.6

Transfer of Keyboard Inputs to Output Devices

The PIP transfer "T" command may be used to transfer console terminal
keyboard (device TT) entries (line by line) to output devices as they
are typed.

This capability is useful in the creation of ASCII source

paper tapes or the entry of personal comments at the beginning or end
of line printer listings.

The user, however, should consider that the

text editorial and correction features provided by PIP are minimal
and that the service program EDIT provides complete editorial functions.
Once started, transfer operations of this type must be terminated by
a CTRL D (tD entry).

The CTRL D entry must be made on a separate line,

since any data on the same line as CTRL D will be deleted from the
output.
Examples:
a)

To punch a paper tape via keyboard entries, use:
\

>T~PPL-J (A)+TT ,J

To enter data directly from the keyboard into the current
UFD, use the following (note that a file is named in the
command to receive the keyboard inputs) :

3-19

PIP Operations, Detailed Descriptions and Examples of Use

>T OK KEYBD... TT (A)

Keyboard-to-Disk
Transfer Command

THIS IS AN EXAMPLE OF THE MANNER I N WHICH DATA CAN
BE ENTERED INTO A FILE ON THE DISK DIRECTLY
FROM THE CONSOLE KEYBOARD.
THE EDITORIAL COMMANDS FOR CHARACTER RUBBOUT
AND LINE DELETI0N MAY BE USED IN THIS MODE OF
OPERATION. FOR EXAMPLE
• TITAL'\LE EXANP"MP
A CTRL D ENTRY MUST BE MADE TO TERMINATE
THE KEYBOARD ENTRY MODE OF OPERATION.

Inpu ta
from
Keyboard

>T TT ... DK KEYBD SRC

FiZe to TeZeprinter
Command

THIS IS AN EXAMPLE OF THE MANNER IN WHICH DATA CAN
BE ENTERED INTO A FILE ON THE DISK DIRECTLY
FROM THE CONSOLE KEYBOARD.
THE EDITORIAL COMMANDS FOR CHARACTER RUBBOUT
AND LINE DELETION MAY BE USED IN THIS MODE OF
OPERATION. FOR EXAMPLE
• II TLE EXAMP
A CTRL D ENTRY MUST BE MADE TO TERMINATE
THE KEYBOARD ENTRY MODE OF OPERATION.
Note the change in the .TITLE line as
compared with the previous example
where rubouts were used.

3-20

TeZeprinter
Ziating of
Fi Ze
KEYBD SRC

PIP Operations, Detailed Descriptions and Examples of Use
3.5

FILE TRANSFERS WITH OPTIONAL FUNCTIONS

As stated in Section 3.4, PIP option Function Switches may be included
in

"T" conunands to provide the use of a broad variety of secondary

operations during file transfers.

The legal switches and switch com-

binations permitted in T conunands are given in Table 3-2.

Table 3-2
Legal Combinations of Function Switches in
Transfer Operations

NSF

E---+-l-+-t-~-~-t-t
G

c
W

I x+~-k-k-~-!-~-k

--x-~-x#~-k-~-k-~
I
I
I
I
i
I I I

I I
N---X-X-X-X-X

X-X-X-X-X

I
I I I
S ---X-X-X-X-X

X+X-X-X-X-X-X-X-X

Y ---X-X-X

--~-~-1-~-tx
1-x
----~-k-~-x-x-X -X+ ~
I

Q -----X-X-X--X

I
x-x

The operations provided by the use of switch functions are described
in Sections 3.5.1 through 3.5.8.
3.5.1

(G) Switch:

Parity/Checksum Error Correction Facility

During data mode (A) or (B) File Transfer operations, PIP checks the
parity and checksum of the file(s)

involved.

If an error is detected,

PIP interrupts the transfer and outputs on the console printer the
message:
PARITY ERR
or
CKSUM ERR

3-21

PIP Operations, Detailed Descriptions and Examples of Use
depending on the error found.

During (A) mode transfers, each parity

error message output is followed by a listing of the line containing
the error.

Such errors detected during a Transfer without the (G)

switch cannot be corrected.
However, the addition of the (G) switch to (A) mode commands provides
the user with the following options when a parity or checksum error
is found:
a.

Accept the line containing the error as it is, by entering
a ..J (RETURN) ;
(PIP does not pass the parity error even if the line is
accepted; it will change the incorrect parity bit to
ensure even parity)

Delete the line containing the error by typing D and
proceed;

Replace the line by typing in a new correct line which
is terminated by~;

Abort the transfer by typing CTRL P ( P) to restart PIP
or CTRL C ( C) to return to the Monitor.

The (G) switch may only be used in lOPS ASCII data mode (A) operations.
The following is a typical example of the use of the (G) switch :

COMMAND ; input c ontent s of pape r
tape to file PARITY of cu rr en t UF D
and per for m pari ty ch ec k wit h (G )
func tio ns.

>T DK PARITY (AG)~PR --------~
PARITY ERROR
---,
BEGIN.INIT 1,lBEGIN -------~ ERROR MESSAGE
~ L I NE III ER ROR - u ser en ters a RETUR N
>
It o a ccep t l ine as is .
PARITY ERROR _________________
.ENTER ,F"ILNAt1
~ SECOND ERROR MESS AGE
>
• ENTER 1,FILNAM
LI NE IN ER ROR
PARITY ERROR
TAG

>TAG

• \I}}U IE 1,2,@UF,34

• I-/RITE 1,2,BUF, 34

l 1t

l u ser ent ers new l ine wi t h co rr ectio n .
THI RD ER ROR MESSAG E

' ---I

~
3.5.2

(E) and (C) Switches:

u s er ente r s n eW l i ne with c orr ection .

Tab-to-Space, Space-to-Tab Conversion

Listing devices mayor may not have tabbing mechanisms; therefore,
it is sometimes necessary to convert file tab and space delimiters to
meet the needs of the listing devices.

3-22

" -' -" ~

PIP Operations, Detailed Descriptions and Examples of Use
a)

(E) Switch - the addition of switch (E) to a "T"
command string causes all Horizontal Tab codes
in the transferred file to be converted to the
number of spaces required to achieve the same
spacing of the printed material as would be obtained if a Tab were present.
The (E) switch may only be used in data mode (A)
transfer.
Following is a typical example of a T
command incorporating an (E) switch:
> T....... TT+-DTl ....... FILEA ....... (AE»)

(e) Switch - the addition of switch (e) to a "T"
command string causes any group of two or more
continguous spaces to be converted to a Horizontal
Tab code in the transferred file according to the
following rule:
i)

a tab character is output for each
tab-stop position which is reached
or exceeded by the group of spaces.

ii)

any spaces occurring after the last
tab stop position, which was reached
by the group of contiguous spaces, are
output.

The effect of this operation is that a printout
of the resulting file will look as if the e switch
had not been invoked. The file itself is, however,
shorter as the spaces have been corrected to tabs,
and output should be faster depending on the output
device.
Note that any group of spaces which fails to reach
at least one tab stop position will result in the
output of just that set of spaces without any tab
characters. Note further, that any group of spaces
ending at a tab stop position will result in the
output of tab characters without any spaces.
The (e) switch may only be used in data mode (A)
operations.
The following is a typical example of a T command
incorporating a (e) switch:

3.5.3

(N) Switch:

Directory Initialization During Transfer

In addition to being a Primary PIP operation, the New Directory ~
command may also be used as an optional function to be carried out in
the context of ot,her operations.

The (N) option may be used to initial-

ize directories on both disk and DEetape mass storage devices.
Switch (N), when used in a transfer to disk operation, initializes
the UFD associated with the current user.
3-23

PIP operations, Detailed Descriptions and Examples of Use
--'"
Used in a transfer to a non-existent UIC, the (N) switch causes a UFD
to be set up under the specified UIC.

The transferred file then appears

as the first entry in the new UFD.
Transfers made to DECtape devices by T commands containing the (N)
switch initialize the DECtape directory and write the transferred file(s)
onto the tape.
The following example illustrates the use of the (N) switch in T
commands.
Assuming the file TESTI

~~l

to be present in the current UFD, the

command:

sets up a new UFD under the UIC "XYZ" and transfers the file TESTI ~~l
into the new UFD as its first entry as follows:
2L:-~!o\j-75

DIRECTORY LISTING
eXYZ)
1 <1 f)5 FR EE RLKS
1 USER F"ILES
J 0 USER BLKS
TEST]
00]
10 ';',1I-"!:)V-"15

UFD's established in this manner are automatically given a UFD protection code of "0", that is, unprotected.
3.5.4

(W) Switch:

Combining Files During Transfers

The (W) combine file switch, when incorporated into a T command, enables
the user to read two or more files from a source device and write them,
in the indicated sequence, into a single file on the destination device.
The (W) switch may be used with data mode switches (A), lOPS AdCII and
(B), lOPS Binary.
During (W) operations, PIP pauses and outputs a tP

(when input is from

a non-directoried device) at the console teleprinter after each file is
transferred.

The user must respond with a tP entry to continue the

transfer operation.
For example, the command:

>T~DT1~COMTST+DT2~TEST1,TEST2,TEST3~(BW»)
3-24

PIP Operations, Detailed Descriptions and Examples of Use
results in the binary files TESTl, TEST2, and TEST3 being written into
the file COMTST on device DTI.

With a source file, the pseudo-operators

.EOT or .END which occur at the end of all but the last of the files
being combined are deleted to enable the resultant file to be processed
as a single continuous file.
The following is an example of a combine files

(W), transfer operation:

2LI-~!O\.l-75

DIRECTOPY LISTING
6163 FREE RLKS

(GEP)

LISTING OF CURRENT UFD

2 USER FILES
2 USER BLKS
SEGA

SPC

:::11- '!()1J-75

SEGB

SRC

~ L1- '110V-7'5

>T DK EXAMP SRC (AWh·DK SEGA

2 4- ~)O\j-75
DIPfCTrpy LI~:TINr,
611')2 FREE RLKS
3 USER FILES
:3 IJSEP nLKS
SFGA
SP C
SEGR
SP C
EYAjI1P
SPC

~L!-Nn\}-75

.IODEI} 1,2
.INIT 1,1,r.EGIN
.ENTER 1,FILNAM

.WRITE
.EOT

COMBINE FILES COMMAND

LISTING OF CURRENT UFD
SHOWING NEW FILE IIEXAMp lI
CREATED BY COMBINING FILES
IISEGA II AND IISEGBII.

? 11 - ~lO\j-75
211-'W\,I-75

• EDT

TAG

SPC

( m:n

• TITLE EXAM?

r.EGIN

SRC,~EGR

1,2,RUF,34

}

LISTING OF FILE IISEGA II

}

LISTING OF FILE IISEGB II

3-25

PIP Operations, Detailed Descriptions and Examples of Use

.TITLE EXAM?
.IODF.V 1,2
DEGIN

.INn i,i,[lEGIN
.ENTEP i ,F'ILNM'

LISTING OF .NEW FILE "EXAMP"

.WRITE 1,2,RUF,34

TAG

.EOT
In the new file, EXAMP, the .EDT which was at the end of file SEGA
has been omitted.
3.5.5

Inputting and Combining Files from Paper Tape:

(W) Switch

The (W) option with a transfer operation permits the user to input files
from separate paper tapes and to combine the files into a single named
file on a specified destination device.
The procedure required is:
1)

The first tape to be read should be loaded into the
paper tape reader (PR).

The user must specify in the command string the number of paper tapes to be read.
This is done by following the source device mnemonic (i.e., PR) by N-l
commas (,) where N is the total number of tapes to
be read.
For example, the command:
> T....... DTl ....... NUFILE ....... (AW)+-PR ....... , , ,,)

specifies that five (5) paper tapes (4 commas) are
to be read in lOPS ASCII data mode and combined into
a single file (NUFILE SRC) located on DECtape unit #1.
3)

The termination of the command string causes the first
paper tape to be read.
PIP pauses after each tape is
read to permit the user to place the next tape in the
reader.
A pause is indicated by the printing of "tP"
at the console printer.

Until the last tape is read, the user must enter
CTRL P (tP) after loading each new tape to continue
the input operation. PIP determines which is the
last tape to be read from the number specified in the
command string and terminates the operation after
the last tape is read.

3.5.6

Card Input and Card File Modification Operations:

(Q),

(C),

(T) Switches
The transfer operation may be used to input source files from punched
cards.

The format of the data being input from cards may be modified

by adding one or more of the following switches to the T command:

3-26

--'-

PIP Operations, Detailed Descriptions and Examples of Use

(Q) Switch - The addition of a (Q) switch causes
the information input from card columns 73 through
80 (card sequence numbers) to be deleted. This
switch may be used only in an (A) data mode transfer operation and only on information which is in
a card format.
That is, the Q switch may be used
during the transfer of files, the contents of which
are still in card format, as well as during the input of data from the card reader. Examples of the
command strings used are as follows:
a)

To modify input from card reader

T~DTl~FILEA~(AQ)+CD~
b)

To modify file data format during storage
device transfer operations:

T~DTl~FILEA+DTl~SOURCE~{AQ»)
2)

(C) Switch - The (C) switch (spaces-to-tabs) may
be combined with the (Q) switch to further modify
the contents of files being input or transferred.
The following is an example of a command string
containing both the (C) and (Q) switches:

T~DTI~FILEA+DT2~SOURCE~{AQC»)
3)

(T) Switch - The (T) switch (delete trailing
spaces) may be combined with the (Q) switch
to further modify the contents of files being
input or transferred. The following is an
example of a T command string:

T~DTI~FILEA+DT2~SOURCE~(AQT»)
NOTE
The Q switch cannot be used to modify the
contents of files which have been previously modified by the use of either or both
the (C) and (T) switches since the contents
would no longer be in a card format.
3.5.7

(T) Switch:

Delete Trailing Spaces

The (T) option switch may be added to transfer commands used to input
data from a card reader or to transfer files containing data in a
punched card format (i.e., BO-character ASCII data groups).

The use

of the (T) switch causes PIP to locate and insert a RETURN

(J) charac-

ter immediately after the last non-blank character in each file
input) card-format data group.

(or

The (T) switch thus deletes the trail-

ing spaces which ~esult from inputting the unused portions of the original punched card sources.

3-27

PIP Operations, Detailed Descriptions and Examples of Use

3.5.8

(V) Switch:

Vertical Forms Control on Output

The (V) options switch may be added to transfer commands to translate the
first character of each record to a special character which, when interpreted by the line printer (LP) handler, the terminal handler (TT) or
by the VP15A handler (VP) will produce forms control functions.

The

translation will occur according to the FORTRAN conventions shown below:
Character Found

Translated To
FF, 14

'1 '
'+'
'0 '
anything else

8
DLE, 2°8
DCl, 21
8
LF, 12
8

Meaning to LP Handler
Ship to top of form
Overprint
Double space
Single space

If, for example, a FORTRAN program writes a listing file to disk rather
than to the line printer (which might be temporarily out of service) ,
the file may be transferred at a later time to the printer as follows:
+T LP+DK .TM~~ OTS(AV»)
3.6

VERIFY OPERATION

lOPS ASCII or Binary files may be checked for parity and checksum errors
by using the PIP Verify V operation.
Data mode switches (A) lOPS ASCII and (B) lOPS Binary are the only
optional PIP switches permitted with V operations.
The verification command string requires:
a)

the ~ operation control character;

the mnemonic of the device containing the file to
be examined;

the filename and extension of the file being checked;

data mode switch (A) or (B). As in the T command,
the mode switches may be dropped if the extensions
SRC or BIN are used; conversely, these extensions
may be dropped when the mode switches are indicated.
A 3-character extension where the last character
is numeric also defaults (A). Note that in multiple
file verifications, all files must be of the same
data mode (i.e., all lOPS ASCII or all lOPS Binary).

3-28

PIP Operations, Detailed Descriptions and Examples of Use
COMMAND STRING EXAMPLES:
a)

the command:

V~DKL-IFILEA~{A»)
will verify the file FILEA SRC listed in the UFD of
the current user (UIC).
b)

the command:

V~PR~{B»)
verifies the contents of an lOPS Binary paper
tape mounted in the paper tape reader.
c)

the command:
V~DT3L-1FILEA,FILEB, FILECL-I(A)..J

verifies three ASCII files contained on DECtape unit 3.
If either a parity or a checksum error is detected during a Verify
operation, the message:
"PARITY ERR"
or

"CHKSUM ERR"

is output at the console printer by PIP.
A Verify, V, operation is interrupted only for the printing of error
messages, it continues the verify operation until the entire file has
been examined.
During verification of IOPS ASCII files

(mode (A»

the line containing

each detected error is printed at the console printer immediately after
the error message printout.

The following is an actual example of the

error message/error line printout obtained during the verification of
an ASCII file.
(A)
V PR
PARITY
ERROR
START
WIZJ
PAR I TY ERROR

JMP

TE-----

Lines in the fiZe whioh
oontain a deteoted eppop

PARITY ERROR
@::!

PAR ITY ERROR
IZJ-------TFLP

3-29

PIP Operations, Detailed Descriptions and Examples of Use
Read Section 3.5.1 for a method of correcting lines with parity errors
in lOPS ASCII files.
3.7

SEGMENT FILE OPERATION

PIP provides commands which enable a single lOPS ASCII file located on
either a directoried device (e.g., DT, OK, DP, RK, MUT) or a paper tape
to be segmented into, up to 16 individual files or tapes.

The PIP

segmentation operation is initiated by an S (segment file) command followed immediately by a T (transfer) command containing a (Y) option
switch.
NOTE
The (Y) switch may only be used with data
mode switch (A), (lOPS ASCII).
3.7.1

S, Segment File Command

The S command enables the user to specify up to 16 "segmentation
points" within a file that is to be segmented.
A segmentation point is defined as a group of from 1 to 5 characters
which identify a specific line within a file.

The characters of a

segmentation point must appear in the FIRST five character positions
of a line.
Each segmentation point indicates to PIP that all lines of the file
from the beginning of the file or the preceding segmentation point,
up to but not including the current segmentation point, are to be
transferred as a single file.
The format of the S command string is as follows:
S~SEG1,SEG2, ... ,SEG15,SEG16

As shown above, commas must be used as delimiters between the specified
segmentation points.
3.7.2

T Command Requirements for S Operations

The T command used in file segmentation operations must:
a)

contain a

(Y)

switch;

3-30

PIP Operations, Detailed Descriptions and Examples of Use

name a corresponding destination file for each segment of the source file;
NOTE
The number of destination filenames required in a T command is equal to the
number of S command segmentation points
plus 1.

contain the source device mnemonic and source filenames and extensions.

immediately follow the S command.

During S operations:
a)

PIP examines the file line-by-line for the segmentation points specified in the S command.

As each segmentation point is found, PIP appends the
.EOT pseudo-op to the defined segment and transfers
it to the corresponding destination file.

Assuming the following file present in the current UFD:

BEGI N
Til G

PUF
Ll ::.
FItNAM

• TI TLE EXM1P
.IODEI/ 1,2
.INIT l,l,BEGIN
• ENTER l, FI L NAM
.WRITE l,2,BUF,34
.CLOSE 1
• EXI T
Ll-./2*1000+2; 0
.ASCII 'HE,I!'<l75>
.SIXBT 'DTIO DAT'
.END BEGIN
• EOT

the manner in which file EXAMP may be divided into three segments,
with each segment a separate named file, is shown in the following
example:
>S BEGIN,TAG

SEGMENTATION SAND T
COMMANDS
>T DK PARTA,PARTB,PARTC CAY)+-DK SEGEX SRC
tP
tP
tP
tP

3-31

PIP Operations, Detailed Descriptions and Examples of Use

TT~DK

LIST CURRENT UPD
2Li-~lOV-75

DI REC TORY Ll STI NG
151.121 FREE BLKS
4 USER FILES

CGEP)

4 USER BLKS
PAViA
PARTS
PARTC

SFGEX

SRC
SRC
SRC
SR C

;".'1- 'J'::V-75

? /f - ')0 V- 75
2 Ll- ~J()\J-75
24-'·IQV-75

LIST SEGMENT A

>T TT+-DK PAR Ttl. CA)

• II TLE EXAMP
.10DEV 1,2
• EOT

TT+-DX PARTB

CA)

LIST SEGMENT B
BEGIN

.INIT 1,1,BEGIN
.ENTER
• EOT

I,FILNAM

>T TT+-UK PARTC CA)

LIST SEGMENT C
TAG

a\JF

.WRITE 1,2,BUF,34
.CLOSE 1

• EXIT
Ll-./ 2* 112J12l12l+2; 121
.ASCII

'HEJ!'<175>

L 1 =,
FILNAM

,SIXBT 'DTIO OAT'
.END BEGIN

.EOT

3-32

PIP Operations, Detailed Descriptions and Examples of Use
3.7.3

Source File to Multiple Paper Tapes Segmentation Operations

The segmentation of a file and the outputting of each segment onto separate paper tapes is performed in a manner similar to that described
in Sections 3.7.1 and 3.7.2. The use and format of the S command is
the same, but the T command differs as follows:
No destination filenames need be used in the T command;
nowever, a series of commas must then be used to indicate the number of paper tapes required.
For example, the commands needed to segment file EX AMP (refer to previous examplet onto 3 paper tapes are:
>S BEGIN,TAG)

>T~PP~,,~(Y)+DK~EXAMP~SRC)

The operations performed by PIP when outputting file segments onto
paper tape are similar to those described in Section 3.7.2.
When a file is segmented and the segments are output onto paper tapes:

3.8

An .EOT pseudo-operation is appended to the end of
each segment except for the last.

With the exception of the last output tape, PIP
pauses after each segment tape has been punched
and causes a tP (CTRL p) message to be printed
at the console printer. The pause permits the
user to remove each tape before the next one is
punched.

The user must enter CTRL P (tP) to continue the
segmentation operation after each pause.

When the last tape is punched, control is returned
to PIP from the segmentation operation.

DELETE FILE OPERATION

The Delete operation enables the user to delete files from user directories.

The basic command format is:
>Dudevice containing file(s)ufilenameuextension )

for example:

3-33

PIP Operations, Detailed Descriptions and Examples of Use
More than one filename may be listed in a D command; however, they
must be separated by commas.

For example:

NOTE
The complete name (filename and extension) of
the file(s) must be specified exactly as entered
in the directory from which they are to be deleted.
If more than one file in a directory has
the same name, PIP will delete the first file of
the specified name which it finds.
One option switch,

(X), is permitted in the Delete command.

This switch

deletes all truncated files from the current or a specified (unprotected)
UFD.

The following are · examples of the use of the (X) switch:
a)
b)

3.8.1

>D~DK~(X»)
>D~DK~<AAA>~(X»)

for current UFD;
for specified UFD.

Deletion of Files from UFD's

When a file is deleted from a UFD, its entry is removed from the user
directory and the quantities given in the Directory listings (i.e.,
FREE BLKS, USER BLKS and USER FILES) are adjusted to reflect the deletion.
Files are deleted from the current UFD by using the basic D command.
For example, assuming the following directory as current:
2, b - ~Kl v- 75
DIR ECTORY LI STI NG
5751 FREE RLKS
2

USER

(JAN)

FI LES

11 USER BLKS
TEST]
0 01
10
MI N
SR C
1

:' 11-

')OIl-75

::; LI - 'J(1 V-75

the command

results in the deletion of the file "TESTI ~~l" as illustrated in the
following listing of JAN:

3-34

PIP Operations, Detailed Descriptions and Examples of Use

2 4- NOV-75
DI RECTOPY LISTING
5761 FR EE BLKS
1 USER FILES
USER BLKS
MIN
SRC

(JAN)

~1.J - NO V-7 5

More than one file may be deleted from a directory during a D operation.

The deletion of four files by a single D command is shown in

tlie following:

2!j - ~I0\} -7 5

DIRECTORY LISTINQ ( GEP)
2251 FREE BLKS
10 USER FILES
10 USER BLKS
SEGS
SRC
1 ? 11 - ~JO 'J-7 5
SEGA
SRC
1 ~ IJ - ~10\} -7 5
EXAMP SRC
1 ~ b. - !\)QV-75
TTYFL SRC
1 ? 4 - ~1n \i-7 5
PARTA SRC
1 :: LJ -II.JO\}-75
TTYFLS SRC
1 ~,4 - ': OV-75
PARTS SRC
1 ~ 11 - ':0 1)-75
PARTC SRC
1 ;~ !J - \10 \1- 7 5
>0

DK SESS SRC,SEGA SRC,TTYrL SRC,TTYrLB SRC

Origina l UFD

Delet e Comm and

24 -~]r;V -7 5

DIRECTORY LISTING
2255 FREE BL KS
4 USER FILES
4 USER BLKS
EXAMP SRC
PARTA SRe
PARTS SRe
PARTe SRe

(GEP)
Revised UFD
~~ - ~ r V - 75

~f - ~~V -7 5
~/r - r,' nll-7 5
~h - ~ nv-7 5

NO TE
The protection code assigned each individual
file is overridden by the UFD protection code.
If the UFD is unprotected (code ~) any file it
contains may be deleted b y other users of the
system regardless of the protection code of
the individual file.

3-35

PIP Operations, Detailed Descriptions and Examples of Use
3.8.2

Deletion of DECtape Files

When a file is deleted from a DECtape directory, all references to the
file are removed from the directory and the File Bit Map blocks.
The command format is the same as that described for the basic operation.
For example, to delete a file from device DTl, use the command:
>DL...IDTIL...lfilenameL...lextension)
D will also delete (that is make inactive) files on magtape.
3.8.3

(X) Switch:

Deletion of Truncated Files

The use of the (X) optional switch in a liD" command deletes all truncated
files contained by the current UFD or any specified non-current UFD
(unprotected). For example, assuming the following UFD as being current:
:.:. 11- ~JC V-75

DIRECTORY L1STING
5372 FREE BLKS

2 USER FILES
3 USER BLKS
SEGEX SRe
3
• TF'lL! EDT*
0

CGEP)

24 - Nr V-75
~ 1. - ~~ () \J-7 '3

the command:

causes the truncated file ".TFILI EDT*" to be deleted from the UFD.
The resulting UFD appears as:
;" .~ - '.l r \)- 75
DIRECT ORY Ll SIl NG CGEP)
543 () mEr<: BLKS
1 USER rr LF.S
3 USER 8LKS
SEGEX SRC
3 ?~ - ~nV -7 5

3.9

FILE RENAME OPERATION

The PIP R operation enables the system user to:
a)

Change filenames within current UFD'S, specified
UFD's and DECtape and magtape directories;

3-36

PIP Operations, Detailed Descriptions and Examples of Use
b)

change the protection code for the current or specified UFD's~

change the protection codes of files within the current or specified UFD's.

The basic format for the R command is:
R

directory device

new name

ext directory device

old name

e xt

The "directory device" must be the same on both sides of the backarrow
(+).

This is the device which contains the file to be operated upon

by the R command.
3.9.1

Renaming Files

Files within the current UFD or located in DECtape directories may be
renamed using the basic R command.

For example, assuming the following

UFD to be current:
2 Ll - Nc/V -7 5

DIRECTORY LIS TING
5436 FREE BLKS
X[V]PLE

(GEP)

1 USER FILES
-3 USER BLKS
SRe

Original
3

~~4 _1'::1\; - 75

UFD

The filename "XMPLE" is changed to "SEGEX" by the following:

>R DK SEGEX SRC ~DK XMPLE SRC
>L TT ...DK
~ I! - NCl V- 7:i

DIRECTORY LISTING
5436

1 USER FIU:S
3 USER BLKS

SEGEX

CGEP)

l'REE BlKS

SRC

Revis ed
UFD

" 1'_" 0 1.1-75

Note that the file creation date also changes.
Truncated files cannot be renamed.
an lOPS

If an attempt is made to do so,

error results.

Files on DECtape and magtape are renamed using the same command format
as shown for disk (UFD) files.

3-37

PIP Operations, Detailed Descriptions and Examples of Use

3.9.2

Setting File Protection Codes

R commands may be used to change both the name and protection codes
for disk files.

The format for this function is:

where (#1 is the specified file protection code (see Section 2.3.7 for
codes1.
For example, assume that the revised UFD of the preceding example is
still current, the file protection code of file "SEGEX SRC" is changed
from 2 to 1 in the following manner:
>R DK SEGEXI SRC~DK SEGEX SHC (1)--------------------

R command

>L TT ... DK (P)
:' 1:- ~!(1\)-75
DIRECTORY LISTING (GEP)
5436 FREE BLKS
1 USER FILES
3 USER BL!(S
SEGEXI SHC
2201(1)

UFD listing
showing new
file protection code and

3.9.3

new file names.
3

?,1I-'!0V-75

2205

Setting Directory Protection Codes

R commands may specify a new protection code for the current or a
specified UFD.

The following command format is required for this

function.
>Rudiskd XXX: Z> )

where:
11

XXX is the 3-character UIC of the UFD involved

: is the required delimiter for this function

3-38

PIP Operations, Detailed Descriptions and Examples of Use

Z is the protection code to be assigned to the
specified UFD: ~ = unprotected; 1 = protected.

For example:

>L TT.-DK (M)
::',11 - ~,!OV -75

O-:t'i gi na Z
MFD indicat es
th at no u nprot e cted
UFD ' s ar e
in th e s y stem

MFD DIRECTORY LISTING
2255 FREE BlKS
43 USER FILES
515 USER BlKS

>L TI.-DK (M)
:~Jl- ~,: OV -75

MFD DIRECTORY lISTING
2255 FREE BL KS
43 USER FILES
515 USER BlKS
GEP
1003(0)
4
The standard protection rules apply here:

Revised MFD
showing th e
u npr ote ct ed
UFD "GEP "

a user cannot change the

protection code of a UFD that is protected if that UFD is not current.
Note, however, that a non-current unprotected UFD can be changed to
protected and thus become unaccessible to the renaming user.
3.10

The PIP

BLOCK COPY OPERATION
B

operation enables the user to copy the contents of selected

storage blocks or ranges of blocks from one device into specified
blocks of another similarly structured device.

For this operation

the user must specify:

the destination device and the storage blocks which
are to receive the copied information,

the source device and the specific blocks which are
to be copied.

The command format required is:
>BwDest.Dev.wList of Rec. Blocks+Source Dev.uList of Blocks to be copied)

The blocks to receive data and those which are to be copied are identified by their respective octal numbers.
3-39

PIP Operations, Detailed Descriptions and Examples of Use

A series of non-consecutive blocks (either source or destination) is
specified by listing their octal numbers, in sequence, separated by
commas (required delimiter).

For example:

l~l,

specifies that the contents of blocks
to be copied into blocks
1~7

to 55, and

2~~

5~,

55, and

1~7

and

2~~

of DTI (i.e.,

on DT2 are
l~l

5~,

6~).

A series of consecutive blocks (either source or destination) may
be specified as a range of numbers.

The range is specified by list-

ing the first and last block numbers of the series separated by a
dash (-), the required delimiter.

For example:

specifies that blocks l~~, l~l, 1~2, 1~3, 1~4 and 1~5 of DT2 are to
be copied into blocks

5~,

51, 52, 53, 54 and 55 of DTI.

When data is to be copied from and written into the same blocks on
both source and destination devices, only one set of block numbers
is required.

For example:

>BuDT1Ul ,3-5+-DT2 )
and
>BuPTl+DT2Ul,3-5 )
specify that blocks 1, 3, 4 and 5 are to be copied from DT2 into blocks
1, 3, 4 and 5 of DTI.

UIC block copy operations are permitted between the following devices:
a)

Disk Area to DEC tape

permitted for the ulc user.

DEC tape to DECtape

permitted for any system user.
Option switches (N) and (S) may
be included in B commands for
this type of operation.

In all block copy operations, the data transferred (copied) is automatically verified.

3-40

PIP Operations, Detailed Descriptions and Examples of Use

3.11

COPY MASS STORAGE OPERATION

The PIP C operation provides the system user with the ability to:
a)

add the contents of one device to that of another device

copy the complete contents of one directoried device
onto another similarly-structured device.

The format for the C command is:

>C~destination device+source device)
The following option switches may be added to the C command:
a)

(N) New Directory switch
Permits destination device directory to be initialized
during C operation. Note that this switch is illegal
to magtape.

(S) Initialize with QAREA switch
Initializes the directory of the destination DECtape and
establishes a QAREA on the tape prior to the copy
operation.

(H) Image Mode switch
H mode copy is a total replacement operation in that
each block on the destination device is replaced LY
the corresponding block of the source device.
This
form of copy, therefore, may be used only between
the following like devices:
RK to RK, DP to DP, DT
to DT; it is most useful for copying DECtapes. As
each block is written onto the destination device,
a word-by-word comparison is made between the destination block and source block to ensure accuracy.
If an error occurs, the number of the block containing
the error is output on the console printer and the
copy continues.
Once the copy operation is complete
the blocks which contain errors may then be recopied
using the Block Copy (B) function; this eliminates
having to repeat the entire device copy operation.
All available free core is used during H Mode Copy
operations; the more core that is available the
faster the copy operation.
It is therefore advantageous, prior to calling PIP, to assign only those
handlers needed for the copy operation using the A
(Assign) monitor command. For example, the fastest
possible copy operation between DECtapes is achieved
by assigning handler DTE to all positive .DAT slots.

3-41

PIP Operations, Detailed Descriptions and Examples of Use
3.11.1

Adding Files, Copy Operation

The use of the basic C command results in files being copied from the
source device and added to the contents of the destination device.
For example, the command:

causes the files on DT2 to be added to the contents of DT1.
files on the disk are not transferred during a copy.

Truncated

The basic copy

(i.e., add-on) operation is permitted between:
DEVICES

Tape to Disk

OPERATION PERFORMED
integrates all DECtape or magtape files into the current UFD.
A typical command is:
> C L..,IDKL..,I+ DT 1)

Disk to Tape

integrates all files contained by the
current UFD onto the specified magtape or DECtape. A typical command
is:

UFD to UFD

copy operations (i.e., the integration of files) may be carried out
between the current UFD and an unprotected UFD.
For example, the command:
>CL..,IDKL..,I<JAN>+DK)
adds the files of the current UFD
to the UPD "JAN".
Copy operations may also be performed between the current UFD and
a protected UFD; however, truncated
files and files with a protection
code of 3 are not copied.

DECtape to DECtape

integrates all files from the source
device onto the destination device.
A typical command is:
>CL..,IDTI+DT2 )
NOTE
If the destination device cannot
store all of the input files, all
possible files are copied and an error message printed at the console
teleprinter.

3-42

PIP Operations, Detailed Descriptions and Examples of Use
Assuming a current UFD containing the file "XMPLED SCR", the following
is an example of a basic copy (i.e., C) operation:
24-~OV-75

OIRECTORY ~iSTING
1Ii'J66 FREE 8LKS
1 USER F'Il.ES
10 SVSH:M 8U<S

EOTST

SRO

DIRECTORY BEFORE
COPY OPERATION

DT~

COpy CONTENTS OF CURRENT
UFD ONTO DTP
2 4- ~~O\j-75

DIRECTORY l.tSTING
1062 FREE BLKS
2 USER F'Il.ES
1~ SYSTEM BLKS
EDTSi SRC
1
XMPl.ED SRC
2

DTP DIRECTOR Y AFTER
COpy OPERATION

2
4

A technical note on the copy command:

all transfers are done in Dump

mode regardless of the true mode of the file.

Therefore, PIP can trans-

fer, under one copy command, files of different data modes.
3.11.2

Copy with Directory Initialization

Switches (N) and (S) may be added to C commands to initialize the directory of the destination device (illegal to magtape) .
The (N) switch is used in the following manner:
a)

Copy to System Device
Operations

When added to a basic C command, the (N) switch either
initializes the UFD for the
current or specified UIC or,
if no UFD exists, creates a
new UFD.
For example, the command:
>C~DK < JAN>~(N)+DT1~

first initializes the UFD for
UIC "JAN" or, if none exists
creates one. Then the files
contained by DTl are incorporated into the UFD for "JAN".
b)

DECtape to DECtape copy

When added to a DECtape to
DECtape C command, the (N) switch
initializes the directory of the
destination device before the
copy operation is carried out.
3-43

PIP Operations, Detailed Descriptions and Examples of Use

The (S) switch is permitted only for DECtape copy operations.

This

switch initializes the directory of the destination DECtape and
establishes a QAREA on the tape prior to the copy operation.
When the (S1 switch is used alone, the tQAREA reserved on the initialized device has the same size as the core available in the system.
For example, the command:

will:
a)

initialize

the directory of DTl,

reserve a tQAREA on DTl equivalent in size to the
core contained by the system,

copy the contents of DT2 onto DTl.

Two digits may be added to the (S) switch (i.e.,
4K (i.e.,

4~96-word)

(Snn) to indicate in

units the size of the tQAREA to be reserved).

This size is normally specified in 8K units starting at 24K (minimum
XVM/DOS core requirement).

For example, the command:

>CuP TlU(S32)+DT2 )
initializes the directory on DTl, causes a 32K tQAREA to be reserved
on DTl and copies the contents of DT2 onto DTl.
3.12

UPDATE STORAGE ALLOCATION TABLES OPERATION

It is possible for areas on disk devices to be faulty or damaged
in such a manner that they cannot be read from or written on.
When a faulty area is detected, the Monitor outputs an error
message which describes the condition and lists the block number of
the bad area.
On the detection of faulty read/write disk areas, the current user
must delete the current file where the error was indicated, then
utilize the PIP UPDATE operation to:
a)

Cause the system Storage Allocation Table (SAT)
to be updated to reflect the removal of the faulty
blocks from "available storage".

3-44

PIP Operations, Detailed Descriptions and Examples of Use
b)

Update the system Bad Allocation Table (BAT) with
the numbers of the detected faulty blocks.
If no
BAT exists, the table is created by the update operation.

The command string format for a PIP U operation is:

where N may:
a)

be the octal number of one faulty block or a series
of numbers identifying a list of non-sequential faulty
blocks.
For example, the command:

>U~DK~1~1-1~5,115)
updates the BAT and SAT to indicate that disk storage blocks 1~1-1~5 and 115 are faulty.
b)

Indicate a range of numbers which describes a series
of continguous blocks which are found to be faulty.
For example, the command:

>U~DK~1~1-1~5)
updates the BAT and SAT to indicate that disk storage blocks l~l through 1~5 are faulty.
On completion of each UPDATE operation, PIP outputs the message
n BAD BLOCKS IN SYSTEM
on the console printer.

The letter "n" represents an octal number

which indicates the total number of bad blocks on the disk.

3-45

CHAPTER 4
MIC PIP OPERATIONS
4.1

GENERAL PIP MIC OPERATIONS

The system manager, when logged in under the Monitor Identification
Code (MIC), can perform all of the operations described in Chapter 3.
He is required to specify only the UFO or device involved.

For ex-

ample, to transfer a file between UFO's the MIC enters a command similar to the following:

>T~OK~<JAN>~OESTFL+OK~<GEP>~SOURCE~(A»)
If a UFO is not specified, PAG (for page mode systems) or BNK (for
bank mode systems is used.
Protection codes, file or UFO, do not apply to the MIC.
4.2

SPECIFIC MIC FUNCTIONS

The following paragraphs describe PIP operations which are unique to
the MIC or give different results to the MIC user.
4.2.1

N Operation

The MIC user may initialize any user UFO or OECtape directory in the
system by specifying the directory's UIC or device/unit mnemonic in
the command.
a)

For example:

>N~OK~<JAN)
clears all files from the UFO identified by the UIC "JAN".

>N~OT1)
clears the directory of OECtape unit #1.
WARNING
The command " N OK " issued by the MIC,
initializes either the PAG (page mode) or
BNK (bank mode) system UFOs.
If either of
these UFO's is initialized, critical system programs are lost which must be restored for successful operation.

4-1

MIC PIP Operations

4.2.2

L, List Directory Operation

The only difference between the UIC and MIC "L" operations is that in
listing the MFD, the MIC user obtains a complete listing of all UFD's
in the system, regardless of their respective protection codes.
For example, the listing obtained by the command:
\

(M);)

a) by a standard user (UIC) ~L'-'JO V-75

MFD DIRECTORY LISTING
5766 FR EE RLKS
52 USER FILES
6 4 1 US ER BL K S

b) by the MIC 2 /1-'cOV-75

MFD VIRECTORY LISTING
5766 FR EE ELKS
52 USER F"ILES
641 USER RLKS
BNJ<

1000(1)

157

PAG

1001(1)
1002(1)
NO N ( 1 )
1240(1)
15t)6(1)
1573(1)

5
30
0
1
1
6

160
247
0
4
I
26

NO N ( 1 )

lOS
SCR

WAD
J AN
TMP
GEP

4.2.3

Delete Truncated Files from System

A Delete command with an (X) option switch issued by the MIC will delete all truncated files from all UFD's contained by the operating
system.

4.2.4

The command required is:

Initialize Operation

The use of this operation clears all of the device bit maps and initializes the MFD.

Initialization of the HFD sets it to a default state.

The contents of the disk are lost.

This con~and is most useful for

4-2

MIC PIP Operations
initialization of disk packs.

The form of the command is:

4-3

CHAPTER 5
PIP ERROR DETECTION PROCEDURES AND MESSAGES
5.1

INTRODUCTION

This Chapter describes the error detection, reporting and corrective
procedures employed in PIP operations.

Only the error messages and

procedures output and followed by the PIP program are described.

complete list of system error messages (lOPS) is given in Appendix D.
PIP error detection and reporting operations are concerned primarily
with:
a)

the detection of errors in the user command string,

the detection of errors during the performance of
the user-requested operation.

5.1.1

User Command String Errors

When each input command string is terminated, PIP immediately scans
the entered string for such items as:
a)

format errors,

b)
c)

error in function requested,
Conflicts in requested function,

completeness of information.

Errors in the command string are normally handled in the following
manner:
a)
b)

a message identifying the error found is printed on the
console teleprinter,
the command string entered is retyped by PIP, on a separate
line up to the point where the error was detected. PIP
outputs a question mark (?) at the point of the error,
the user may enter CTRL P or carriage return to abort the
operation or may complete the command string from the ?
symbol on, entering the needed correct information. Note
that it is not necessary to type a space after the ?
Example:

5-1

PIP Error Detection Procedures and Messages

T DK?FILE SRC+DT1)
The latter should initiate the requested operation if no
further error exists.

EXAMPLE:
the following is an example of the detection, reporting
and correction of a command string error:
Command String Entry
Error Message

L TT .... <11IC!<>
IllEGAL OF\lICE OR UNIT
L n .... ?!1K <\liCK>
I

\\------------ Corrections entered by User

PIP reprint to Error Po£nt (?)

In the above example, the user forgot to enter a source device mnemonic
(i.e., DK).

PIP detected the error, output an error message and that

part of the command line up to the error (i.e.,

>L~TT+?) i

the user

chose to complete the operation and entered the needed data (i.e.,
DK < WCK>)

to complete the string and initiate the desired operation.
NOTE
In correcting errors involving a source
filename, it is necessary to respecify
the file data mode.

5.1.2

Operational Errors

PIP also detects and reports errors found during the performance of
the requested function. Parity errors, checksum errors, the inability
of PIP to find a referenced filename, and protection code violations
fall into this category. These errors are reported by PIP by messages
output on the console teleprinter.

The following is an example of an

operational error:
>T rw <GF:?> F:XA!"T'r, ~PC""PP)
PA P TTY !"PO OP

Command

\ \ . - - - - - - - - - - An error was detected on the input
tape

PIP restarts itself after outputting the error message.
5.2

PIP ERROR MESSAGES

The messages output by PIP on the detection of command string or operational errors are listed and described in Table 5-1.

5-2

Table 5-1
PIP Error Messages
Printed Message
1)

CHKSUM ERR

Interpretation
An error has occurred in the transfer of data;

retry

transfer.
STRING TOO LONG

COV~D

DATA MODE MISMATCH

The command string entered exceeds 72 characters.

'U
H

DEV ILL FOR OPTION FUNCTION

The data mode derived from the command string does not
match the mode specified in bits 14-17 of the first header
word.
The transfer is aborted.

1'1
1'1

Change function or device.

(1)

Retype from error.

1'1

t:J

·.n
I
'.;.)

DEVICE NOT IN +.DAT

Return to the monitor and use the A (Assign) command to
assign the device involved to any positive .DAT slot.

DISK FULL

Device has no further storage available.

FILE ALREADY PRESENT

There is already a file present under the new file name
and extension supplied in a 'R' function.
The operation
is aborted.

(1)
()

1-'-

::1

1'1

o()
(1)

1'1

9)
10)

FILE NAME TOO LONG

FILE NOT ON INPUT DEVICE
FILE STRUCTURE CONTAMINATED

Filenames are restricted to a maximum of 6 characters plus
a 3-character extension:
the user has exceeded this limit.
Retype from error.
There is no file under the specified name on the directoried input device. Retype from error.
The file structure on the device (i.e., disk) is faulty;
this error indicates that the system bit map(s) is (are)
incorrect.

11)

ILL BLK #

Improper block number (i.e., too large, or negative)
specified in command.
Retype command.

12 )

ILL cr1D STRUCTURE

The command string entered was not properly ordered or
structured.
Retype the correct command.

(1)

{/l

III

::1
0.

{/l
{/l

III
.0
CD
{/l

Table 5-1 (Cont)
PIP Error Messages

Printed Message
13)

ILL CNT

Interpretation
This error message is printed only in DECtape Directory
listings. When output, it will appear immediately after
the directory line "SYSTEM BLKS" (for example: jO SYSTEM
BLKS ILL CNT).
This message indicates that an illegal
number of system blocks have been detected. The user, on
detection of this error message, should immediately attempt
to transfer any files contained by the DECtape involved
onto another DECtape. The files should be transferred
one at a time.
The faulty DECtape should be initialized
to clear the error condition.

'"d
H

'"d

tr1

I-!
I-!

I-!

14)
15 )

ILL DEV/UNIT
ILL FUNCTION

"'"

Illegal device mnemonic specified in command string.
Retype from error.
The function specified in the command string entered (i.e.,
first character) is not a legal PIP function.
Retype
from error.

()

f-O.

::l

'"d
I-!

()

16 )

1 7)

ILL FUNCTION FOR UIC

ILL P CODE

The operation specified is not permitted at the level of
the current user.
For example, a standard user (UIC) cannot employ the (H) switch in a copy to system device operation. The requested operation is not performed.
Specified directory code is illegal (i.e., something other
than ¢ or 1) or the directory just read has an illegal
protection code. Retype from error.

C
I-!
CD
CIl

::l
0.

CIl
CIl

18)

ILL SWITCH

An optional switch entered in the command is not permitted
in the primary operation being performed. Retype from
error.

19)

ILL TERMINATOR

Command improperly terminated:
legal. Retype from error.

20)

ILL UFD ENTRY SIZE
OR
ILL MFD ENTRY SIZE

The size of an entry (i.e., filename or UFD) in the d1rectory involved is illegal. This error indicates that
the system is faulty.

only RETURN or ALT MODE is

)

CD
CIl

Table 5-1 (Cont)
PIP Error Messages
Printed Message
21)

Interpretation
User has given an improper code; the UIC must be a 3character code within angle brackets (i.e., <XXX». Retype
from error.

ILL UIC

22)

INPUT LINE TOO LONG

Input commands are limited to one physical line of 72
characters; the user has attempted to exceed this limitation.

tr::l
11
11

23)

NEED BLK #

No block number was given in an UPDATE command; enter required octal number.

24 )

25 )

NEED DATA MODE

User must enter the proper data mode switch.
error.

NULL FILE NAME ILL

A filename must be specified; a nullname is not acceptable.
Retype from error.

In
I
V1

26)

Retype from

Current user has attempted an operation which violates the
established protection code of a UFD or a file.
The operation is aborted.

P VIOLATION

lrt5'
(l)

1-'-

o
::s

o
o(l)

C
11
(l)

til

27)

File being processed contains a parity error. During T,
transfer operation, this message may be accompanied by a
printout of the line which contains the error. The user
must correct the indicated line (Use ,(G) switch in a
Transfer, T, operation or the Editor).

PARITY ERR

::s

~
til
til

28)

29)

READ-COMP ERROR ON BLK:

S FUNCTION NOT DONE

XXXXX

During H mode or Block (B) copy operations, PIP compares
the newly written data blocks against the original blocks
and outputs this message if they are different. The operation goes to completion.
A segmentation operation requires the entry of an S command
followed by a T command. This message indicates the S command was not entered before the T command with the Y
switch.

o(l)
til

Table 5-1 (Cont)
PIP Error Messages
Printed Message

Interpretation

STRINGS 1-16 ACCEPTED

30)

If a Segment (S) operation divides a file into more than
16 segments, PIP will load segments 1-15 to their respective destination files.
All remaining segments are put
into the 16th file and this message is printed.

SWITCH CONFLICT

31)

Two or more switches entered in the command cannot be used
together. Retype from error.

32 )

SYSBLK NOT ON DEV

Device specified is not the system device.
tion is aborted.

33 )

TOO FEW FILES

34)

TOO MANY FILES

These error messages indicate that the number of files on
the destination side of the command does not match the
number given on the source side. All matching files have
been transferred; transfer the rest via a new command.

The List opera-

t>J
t-1
t-1

o
t-1

t:l

m
rt
m
()

I
0\

TOO MANY FILES OR BLOCKS

35)

The limit of 28 10 in either case was exceeded. Retype the
command, giving 28 or fewer block numbers of file names.

rt
.....
o

::1

t-1

()

m
0-

c:
t-1

36)

Indicates that a File Directory (UFD) has not been established
for the current user. The user should employ the PIP N
command to set up a UFD under his identification code (i.e.,
UIC) •

UIC NOT IN MFD

37)

This message indicates that the file last read has an
illegal protection code. The requested operation will be
carried out; however, an error message of this type indicates that the system is faulty, or that an illegal default
protection code was specified at SGEN time.

WARNING - FILE HAS ILL P CODE

)

::1
0-

en
en

PIP Error Detection Procedures and Messages

5.3

CORRECTION AND RECOVERY COMMANDS

If a user detects an error in the command string before it is terminated,
he may
a)

delete the incorrect character,

negate the line entered (prior to terminator)
and restart on a new line.

If an error is detected in the user's command string by PIP, he may
a)

respond to the PIP error report and command string
printout by correctly completing the command;

abort the task by entering a CTRL P or RETURN.

The commands which permit the above procedures are listed and described
in Table 5-2.
Table 5-2
User Correction and Recovery Cornmands
To:
1)

Which is Echoed on
the Teleprinter as:

Delete a character from
the command string
NOTE

Characters are deleted one per entry starting from the last entered character and proceeding to the left.
2)

Negate (delete) line
entered

CTRL U

l'WTF

The CTRL U entry must be made before the
line is terminated.
3)

Abort the current task
and/or return control to
PIP

CTRL P
or
RFTURl\;

Nonprir'.ting

I'\OTE

CTRL P entries arc also requested by rIP
during paper tape input and file scg~cnta
tion operations to continue operations after
a tape or file segment 11as been transferred.
4)

Abort the current task
and/or return control to
the nloni.tor

CTEL C

S-7

t('

PIP Error Detection Procedures and Messages

Table 5-2 (Cont)
User Correction and Recovery Commands
Which is Echoed on
the Teleprinter as:
5)

Continue the requested
operation after a "DEVICE
NOT READY" condition has
been corrected for a
PDP-15 or XW1 device (not
needed for a UC15 device).

CTRL R

S-2

CHAPTER 6
QUICK REFERENCE TABLES
6.1

INTRODUCTION

This Chapter contains tabularized data intended as an aid to recall for
users who are familiar with the contents of Chapters 2 and 3.

Tables

are supplied which describe the Primary PIP Operations, PIP Optional
operations, optional functions permitted within each primary operation,
and the PIP command structure, plus a series of tables describing specific operations which may be carried out using PIP facilities.

In some

cases, the tables presented in this section are duplicates of those
contained in earlier sections of the manual; this redundancy is necessary
to make this section a complete single source of information.
6.2

OPTIONS VERSUS PRIMARY OPERATIONS

The matrix Table 6-1 illustrates the optional PIP function switches
permitted in each of the PIP primary operations.
6.3

PIP COHMAND STRING FORMAT CHARTS

Figure 6-1 illustrates the general format of the Destination/Source
command strings; Figure 6-2 illustrates the general format of the
Single-Device Command Strings.
6.4

PIP USER OPERATION TABLES

Tables 6-2, 6-3, 6-4, 6-5, and 6-6 describe the operations which may
be performed by the standard user (UIC); they contain:
a)

a description of the operation,

the optional switches which may be used,

an example of a command string for each operation
described.

6-1

Quick Reference Tables
No attempt is made to describe all possible operation/switch combinations or applications.

However, the user is provided with sufficient

commands to meet his own requirements if he has familiarized himself
with Chapters 2 and 3 of this manual.
The User Operation Tables are organized according to the following
functional areas:
Function Described
6-2

Directorv Operations, how to set up, list, modify,
and operate with disk (UFD) and DEC tape directories.

6-3

List Operations, how to obtain printouts of directory and file information.

6-4

File Modification Operations, how to modify and
manipulate files and file contents.

6-5

File Transfer Operations, how to transfer files
between system storage devices.

6-6

Copy Operations, how to copy device contents,
large groups of files or data blocks from system
mass storage devices.

6-2

Quick Reference Tables

Table 6-1
Available Options Versus Primary Operations
PRIMARY OPERATIONS
I
U
r.:!

I:t:;
r.:!

rx..

:>-l

rz.l

I:t:;

H
Q

r.:!

:>-lr.:!

Ul
H

!3:I:t:;H

t9
r.:!

:>-l
Po<

rx.. rx..

r.:!

[>:j

0
H

12 U

r.:!

:>-l
Po<

r.:!?r.:!

r.:!

.:C

r.:!

.:C
Q

Po<
p

SWITCHES

(Al

lOPS ASCII Data Mode

(B)

lOPS Binary Data Mode

(Cl

Space to Tab Conversion

DESCRIPTIONS

(Dl

Dump Mode

(~l

Tab to Space Conversion

(p)

Insert Form Feed

(G)

Correct Bad Parity

(H) 1

(Il

(N)

(Snn)

(T)

Delete Trailing Spaces

(Q)

Delete Sequence Numbers (cards)
----'-

(W)
(Y) 3

Combine Files

(V)

Segment Files
Vertical Forms Control

Image Alphanumeric Mode
X

(K)
(M)

Image Binary Mode

New Directory

New Directory with CTRL Q area

Delete Current UFD
List Unprotected UFDs
Delete Truncated Files

X
X

(X)

(pl

List Current UFD & RIB data

(L)

List SYSBLK

lLegal only with DECtape, Disk Pack or Disk cartridge copy operations.
2 Lega l only when the current password is the MIC.
3Transfer, T, commands which include a Y option switch must be immediately preceded by an S, segment command string.

6-3

DESTFL L...J

SRC

~ (G)

DTn '---'

DATA

L-.-J

SRC}

OPERATION
COMMAND
DESTINATION
DESTINATION FILE
OPTION ~SOURCE
SOURCE
FI LE
CHARACTER LJ
DEVI CE
LJ (filename LJ ex t) LJ SWI TCH (S)
DEVI CE LJ (filename LJ ext)
T
L
C
R

I
Trans fe r f il e
List directory
Copy mass
storage
Rename file
Block copy

Optional for nonfil e oriented devices.
Use
commas to separate multiple

TERMINATOR

lJse commas to

separate multiple f ile
names and extensions.

file names and
extensions

PR - Paper tape reader
TT
Teletype
CD
Card reader
DTn= DECtape unit
MTn= Magtape unit
DK = DECdisk
DPn= Diskpack unit
RKn= Disk cartridge unit

PP = Paper tape punch
DTn= DEC tape unit
TT = Teletype
LP = Line printer
I1Tn= l1agtape
DK = DECdisk
VP = VP15A CRT display
DPn= Diskpack unit

)= Return
control
to PIP
ALTMODE =
Return
control
to the
monitor

RKn= Disk cartridge unit

Function Switches

Data Mode Switches
A
B
I

lOPS ASCII
lOPS Binary
Image Alphanumeric

Figure 6-1

Image Binary
Dump

convert tabs to spaces

Flag bad parity lines
convert multiple spaces to
tabs
W
Combine files
Y
Segment files
N
New Directory
Snn = New directory with CTRL Q
area.
Size o f area (nn) =
8, 12, 16, 20, 24, 28, or 32
(K words) N operation only.
Default = current size of
system.
F
Insert Form Feed every 5510
lines or after .EJECT
T
Delete trailing spaces } Input must be
in punched
Q
Oelete sequence numbers
card format
Request a listing of
M
the system MFD
Request a listing of the
L
system SYSBLK directory
Request UFD listing with
P
RIB data
G

Destination/Source Command String Format

6-4

-""".

Quick Reference Tables

L-J

DTI

FILEA,FILEB

L...J

(A)

)

OPERATION
COMMAND
DEVICE
FILE(S) INVOLVED
OPTION
CHARACTER L-...J MNEMONIC L..J FilenameL....JExt.
L-J SWITCH (S)

N=new directory
V=verify file
D=delete
I=ini tiali ze
U=update

Use commas to separate
multiple filenames and
extensions.

TERMINATOR

)-Return control
to PIP
ALT MODE
Return control
to DOS
Monitor

PR=Paper Tape reader
DTn=DECtape unit
DK=DECdisk
DPn=Diskpack unit
MTn=Magtape unit
RKn=Disk cartridge unit

A
B
S
Snn
K
X

IOPS ASCII Data mode
IOPS Binary Data Mode
new directory with a coresized tQAREA
new directory with a
user-specified sized
tQAREA
delete UFD
delete all truncated files

Figure 6-2
PIP Single Device Commands, General Format

6-5

Table 6-2
Directory Operations
IN ORDER TO;

USE OPERATIONS:

AND OPTIONS:

IN THIS MANNER:

Initialize the
existing UFD or
create a new UFD
for the current
UIC

N, New directory

None

>NuD K )

Initialize the
existing UFD or
create a new UFD
for the current
UIC during a T
transfer

T, Transfer

eN) , (NA) ,(NB)

>TuDKt.PESTFL+-DTluSOURCEu(NA))

3)
0\

I
0\

r:::

1-'.

Initialize or
create a UFD
for the current
UIC with a specified UFD protection code

N with code
specified

Delete a file
from the current
UFD

D, Delete

Rename a file in
the current UFD

R, Rename

(None)

:;0

>NuD Ku(.0') )

(l)

HI
(l)

(l)

::s

o(l)

1-3
OJ

None

Note:
None

Rename a file
in the current
UFO and set its
protection code

R, Rename

Change protection code of the
current UFD

R, Rename

None

Filename extension is required.

>RuDKUNEWNAMuBIN+-DKuPLDNAMuBINU(3) )
Note:

None

f-'

(l)

>RuDKu NEWNAMJUN+-DKL.J>LDNAMJ3IN)
Note:

>DuDKuDESTFLuBIN )

Protection code is specified within
parentheses.

>RuDKl1< JOE: .0'> )

)

Table 6-2 (Cont)
Directory Operations

IN ORDER TO:

USE OPERATIONS:

AND

Initialize the
directory of a
directoried
device

N, New directory

None

Initialize DECtape directory
and set up a
tQAREAof:

N, New directory

OPTIO~S:

IN THIS MANNER:
>NuD Tl )
Note:

illegal to magtape

lOJ

-..J

1-'-

System core size

(S)

>NUDTlU (S) )

Specified size

(Snn)

>N UDTlU(S32) )

;.;'

6iHI

(1)

List contents of
directories:

I-f

(1)

::J

MFD

L, List

(M)

>LUTT+-DKu(M) )

UFD

L, List

None

>LUTT +- DK )

DEC tape

L, List

None

>LUTTUDTl)

List contents of
unprotected, noncurrent UFD

L, List

None

>LUTT+-DKu< JOE> )

()
(1)

Note:

illegal from magtape

0f-'
(1)

11)

[Jl

Table 6-3
List Operations

IN ORDER TO:
-_._---

USE OPERATIONS:

IN THIS MANNER:

AND OETIONS:

List the system
MFD

L, List

eM)

>LuLP+DKu(M) )

List the UFD of
the current UIC

L, List

None

>LUTT + DK )

List the contents
of an unprotected
non-current UFO

L, List

None

>LUTT+DKU< JPE> )

List the system
SYSBLK

L, List

I~·0

:>;'

(L)

>LUTT+DKU(L) )

(l)

List current UFO
with File Protection Codes and
RIB information

L, List

List directories
of DECtapes

L, List

None

>LUTT+DTl)

List a selected
file entry from
the current UFO
or device directory

L, List

None

>LUTTLfILNAMJJHN+OK)

List a selected
file entry from an
unprotected noncurrent UFO

L, List

None

>LuTTLfILNAMuPRC+DKufJOE»

I
(Xl

(P)

>LUTT+DKU (P) )

t;
(l)

::s

(l)

1-3
PI

)

Table 6-3 (Cont)
List Operations

IN ORDER TO:

USE OPERATIONS:

AND OPTIONS:

IN THIS MANNER:

List all file
entries having
tfie same
extension from
al

the current
UFD or device
directory, or

L, List

None

>LUTTU#SRC+-DK )

an unprotected
non-current
UFD

L, List

None

>LUTTU#BIN+-DKu< JOE> ~

c
.....
o

;.;'

0\
I
-0

CD
11
CD

::s
o
CD

>-:1

III

.....
CD
til

Table 6-4
File Modification Operations
IN ORDER TO:

USE OPERATION:

AND OPTIONS:

IN THIS MANNER:

Rename a file

R, Renam e

None

>RwPKuNEWNAMuBIN+DKwPLDNAMuBIN )
Note: Filename extension is required.

Rename and set
the protection
code for a file

R, Rename

None

>RUDKuNEWNAMuBIN+DKwPLDNAMuBINU(3})
Note: Filename extension is required.

Delete

D, Delete

None

>DUDKuFILEAUBIN )

a file:

from current
UFD

s::

1-'-

bl
cl
0'
I
I-'

from unprotected UFD
from mass
storage device directory

()

;:>;'

D, Delete

None

>DuDKU JOE >uFILEAuBIN )
Note: Filename extension is required.

D, Delete

None

>DuDT1uFILEAuBIN)

::s

()

Delete all truncated files from
a UFD which is:

t-3

I-'

CD
til

current

D, Delete

(X)

>DuDKu(X) )

specified

D, Delete

( X)

>DLPKLi ABC >u(X) )

Convert multiple
spaces to tabs

T, Transfer

(C),

(CA)

>TuLP "pESTFL+-DTIJlOURCEu (CA) )

Convert tabs to
spaces

T, Transfer

(E),

(EA)

> T~P"pESTFL+DTIJlOURCEU(EA))

Detect and Correct
File Parity and
Checksum errors

T, Transfer

(G),

(GA)

>TwPKwPESTFL+DTIJlOURCEU(GA»

Delete Trailing
Spaces from file
contents

T, Transfer

(T),

(TA)

> TuDK~DESTFL+DTluSOURCEU(TA))

)

Table 6-4 (Cont)
File Modification Operations

IN ORDER TO:

USE OPERATIQN:

AND OPTIONS:

Delete sequence
numbers from file
(card input or
card format data
files only)

T, Transfer

(Q),

(QA)

>TuDTluDESTFLu0~lu(Q}+CD

10)

Combine separate
files into one
file

T, Transfer

(W)

(B)

>TuPTluLIBRu(WB)+DT2ufILAuBIN,FILBuBIN)

(A)

IN THIS MANNER:
)

lItI.-

s::

1-'()

;;0;'

111

Segment a file
into 2 to 16
separate:

::0

(I)

Hl
(I)

()'\

files

......

S, Segment +

None

T, Transfer

(Y) ,

>SuTAG,TAGB,TAGC)
(YA)

>TuDTlufILA,FILB,FILC,FILDu(YA)+DT2uSOURCE)

(I)

::l
()
(I)

>-:l
OJ

papertapes

S, Segment +

None

>SuTAGA,TAGB,TAGC)

0'
f-'

(I)

12)

Verify a file
for parity and/or
checksum errors

[Jl

T, Transfer

(Y) ,

(YA)

>TuPP u " 'u(YA)+DTlu.SOURCE)

V, Verify

(A) ,

(B)

>V~KuFILEAu(A)

)

Table 6-5
File Transfer Operations

IN ORDER TO:

USE OPERA'J:'IQN-,-

AND OPTIONS:

IN THIS MANNER:

Transfer a file
to the current
UFD

T, Transfer

(A) or (B)

> TuPKuDESTFL~DTluP°URCEu(A))

Transfer a file
to a selected noncurrent UFD when
protection code
permits

T, Transfer

(Al or (B)

> TuDK~JOE > DESTFL+DTluSOURCEu(Al)

Transfer a file
from a current
UFD to a specified,
non-current unprotected UFD

T, Transfer

Transfer console
keyboard entries,
line-by-line, to
a system output
dev ice

T, Transfer

3J.

(J'I

~
1-'"
()

(';'

(A) or (B)

i(i

> TuDK~JOE > DESTFL+DKuPOURCEu(A))

t-h

(!)

11
(!)

::s
()

(!)

I-'
I\.)

(A) only

t-3

>TuLPu(A) ~TT )
Note: cnd input with a tD

~
I-'
(!)
(Il

Transfer file and:
al

Convert spaces
to tabs

T, Transfer

> TuTT~DTluPOURCEu(CAl)

Convert tabs to
spaces

T, Transfer

(E) or (EA) only

> TuTT~DTluPOURCEU(EA))

Enable parity
or checksum
error to be
detected

T, Transfer

(G) or (GA) only

>TuDTlu~DT2uPOURCEu(GA))

)
J

)

Table 6-5 (Cont)
File Transfer Operations

IN ORDER TO:
dl

USE OPERATION:

Initialize the
directory of a
directoried
device

T, Transfer

initialize or
create a UFD
for the current
UIC

T, Transfer

Combine two or
more files into
one file

T, Transfer

Delete sequence
numbers from card
reader inputs

T, Transfer

AND OPTIONS:

IN THIS MANNER:

Note:

(N) or (NA) or (NB)
>TuDTluDESTFL+DT2uSOURCEu(N~))
illegal to magtape

Note:

(N) or (NA) or (NB)
>TwPKuDESTFL+DTluSOURCEu(NA1)
illegal to magtape

1-'()

;;0;'

::0

(l)

f)
(J'I

I
I-'

(W) or (WA) or (WB)

>TwPKuPESTFL+DT2uA,B,Cy(WA»)

'"I

(l)

:::s

()
(l)

HI
(l)

or (QA)
(QAC)
(QAT)

(Q)

>TLPTlwPESTFLU(QA) +CD )

>-,3

III

I-'
(l)
{JJ

Table 6-6
COpy Operations

IN ORDER TO:

USE OPERATION:

AND OPTIONS:

IN THIS l\IANNER:

Copy the contents
of a specific device
storage block

B, Block copy

None

>BJJTl u S,0, 5l+DT2 u l,0l, 1,02 )

Copy the contents
of a specific series
(i.e., range) of
device storage blocks

B, Block copy

None

>BuDTluS,0-S5+DT2ul,0,0-l,05 )

I~.
()

Copy the contents
of one or more blocks
and:

C1l

0'>

I
I-'

J:>.

B, Block copy
initialize the
directory of the
destination device

initialize the
B, Block copy
DECtape directory and reserve
a tQSAVE area
equal to core size

initialize DECtape directory
and specify size
of tQSAVE area
to be reserved

Add (copy) the files
on one device to
those of a second
device

Copy and add files
from one device to
another device and:

(N)

>BuDTluS,0-5S(N)+uPT2ul,0~-1,05)

(S)

>BuDTIU5, 6, 7 u (S) +DT2U5~, 51,52)

B, Block copy

(Snn)

>B u DTl u 5,6,7 u (S32)+DT2 u 5,0,51,52)

C, Copy

None

>CJJK+DTl)

I~
\[
III

APPENDIX A
USE OF VTl5 GRAPHICS DISPLAY SYSTEM
PIP users may employ the VTl5 display unit as either a listing or a
general purpose display device.
PROCEDURE
a)

Before PIP is loaded, the command:
$VTL-ION)
must be issued to the monitor to set up the display system
use.

fo~

Once PIP is loaded, the user need only type CTRL X to activate
the display function.
For all practical purposes, the CTRL
X (tX) command causes the VT Display to take the place of the
console printer unit.
Command characters entered at the console keyboard are echoed both by the console printer and on
the VT Display screen; all other information normally output
to the printer (i.e., error messages, listings, etc.) is displayed on the VT display screen only.

To discontinue the VT Display function, the user must issue a
second CTRL X command.
This action returns the display/print
function to the console printer. The display unit, however,
remains on and continues to display the information contained
before the second CTRL X command was issued.

To clear the VT15 Display screen, the user must actuate the
rightmost display control pushbutton (see CONTROLS) and enter
a RETURN at the keyboard.

To turn the VTl5 Display off (i.e., deactivate the CTRL X
feature) the user must return control to the monitor (CTRL C)
and enter the command:
$VTL-IOFF ..J

VTl5 CONTROLS AND DISPLAY MODES
CONTROLS
The VT15 Display console contains a horizontal strip of six square
push-to-light pushbuttons which are used in display operations.

These

pushbuttons are unmarked since their function is determined by software
and may vary according to the particular program (system or user) which
is in control of the system.

A-I

APPENDIX B
USE OF VP15A DISPLAY DEVICE
In XVM/DOS systems which have a VP15A Storage Tube Display, the PIP
user may use the display device as a listing device.

He may list

system and device directories and files in the following manner:
a)

Listing Directories - System and device directories may be
displayed on the VP15A by specifying the display's device
mnemonic (VP) as the destination device in an L, List, command.

For example, to cause the current UFD to be displayed

in its most complete version, the user would issue the command:

Listing Files - The contents of files may be displayed on the
VP by specifying it as the destination device in a T, Transfer,
command.

For example, to display the file TEST1 001 on the

VP, the user would issue the command:

DISPLAY CONTROLS
The VP15A display unit is provided with two pushbutton controls, BRASE
and VIEW which are located on the right front panel of the CRT enclosure.

'I'hese controls are used in the following manner:

ERJ.SE

When operated, it causes the current display to
erased from the display.

VIEW

The normal brightness of displayed data fades after
90 seconds unless renewed; this control enables the
user to renew (brighten) the display when desired.
vJARNING

The same display should not be maintained on the CRT
for a period exceeding 15 minutes; if this occurs,
the phosphor of the display CRT may be damaged.

B-1

Use of VP15A Display Device

DISPLAY MODES
The VP15A CRT is capable of displaying fifty-six 72-character lines.
If the data file to be displayed exceeds the 56-line display capacity,
the display will operate in either a SCAN or PAGE mode depending on
the type of handler installed in the system (VPA or VPA.S) for the
l
VP15A .
SCAN Mode
When the VPA device handler is installed in the operating system, the
VP15A display operates in a SCAN mode.

In this mode, each time the

display screen is filled it is erased, automatically, after the 56th
list is written and is refilled from the display file.

This fill-erase-

rewrite cycle is continued until the screen is completely or partially
filled and no more data is in the file to be displayed.

The last dis-

play is not erased but remains and may be renewed (brightened) manually
by the viewer when necessary.
PAGE Mode
When the VPA.S version of the handler is installed in the operating
system, the VPl5A Display operates in a PAGE mode.

In this mode

the erase-rewrite operations of the display are controlled by the
manual operation of the Accumulator zero switch

(ACS~).

Each time

the display is filled, the full screen (i.e., page) is not erased
and rewritten with the next set of available display file data if
the

ACS~

switch is actuated.

This feature permits the user to

manually advance through a file page-by-page.

IT he type of VP15A handler available in the operating system will be
that selected by the System Manager during the configuration of the
system.

D-2

APPENDIX C
XVM/DOS TERHS AND ACRONYHS
Terms unique to the XVH/DOS Software System which are used in the PIP
manual are listed and described in the following table.
for each term are also given.

The acronyms

Detailed descriptions of the items iden-

tified by the following terms are given in the XVM/DOS Users Hanual.
~

ACRONYH

DEFINITION

Bad Allocation Table

BAT

A device (disk) table which indicates, in storage blocks, any
faulty disk areas in which data
cannot be stored.

Master File Director

MFD

A master device (disk) file directory which contains pointers
to all user directories (UFD's)
within a disk device.

Honitor Identification Code

MIC

The master system password which
permits full access to all files
within the system. This code
identifies the system manager
and should be used only by him.

Storage Allocation Table

SAT

The device (disk) table which
stores busy, not-busy indicators
for the disk storage area.

SYSBLK

The system table which contains
the names, locations, and loading and starting parameters for
all system programs within the
operating system.

User File Directory

UFO

File directories for each user
who establishes disk file storage areas within the system.

User File Directory Table

UFDT

The system directory table which
maintains the relationship between the system's .DAT slots
and each unique user identification code (UIC).

System Block

C-l

XVM/DOS Terms and Acronyms

TERM

ACRONYM

User Identification Code

UIC

DEFINITION
A password entered by a user to
uniquely define himself and any
files which he may enter. If
necessary, a user may enter more
than one UIC to establish several unique sets of files.
Since
only one user may employ the system at anyone time, the current
UIC is the last logged-in UIC.

C-2

INDEX
Abort operation, 1-2
Acronyms, C-l
Adding files, 3-40
ALT mode, 1-3
At symbol (@) usage, 1-3

Back arrow (+) delimiter, 2-2
Backslash (\) usage, 1-3
Bad Allocation Table (BAT)
update, 3-43
Bank mode, 4-1
Block copy operation, 3-37

Card input, 3-25
Change filename, 3-34
Character deletion, 1-3
Characters, keyboard command,
1-3
Checksum errors, 3-20, 3-27, 5-2
Combining files during transfers,
3-23
Commands, destination/source,
2-2
Command string
description, 2-1
elements, 2-6
errors, 5-1
format, 2-4
Command types
destination/source, 2-2
single-device, 2-3
Continuation lines, 2-1
Control characters, 1-3
Copy mass storage, 3-39
Create current UFD, 3-1
CRT display, B-1
CTRL C (tC), 1-2
CTRL keys, 1-3
CTRL P (tP), 1-2
CTRL Q area (tQAREA), 3-5
CTRL X, A-l

Data modes, 2-1, 2-11, 2-12,
2-13
Data mode specifications, 3-14
Data transfer, 2-2
see also File transfers
DECtape directories,
initialization of, 3-4
listing of, 3-10

Delete operation, 3-31
Deletion of
characters, 1-3
DECtape files, 3-34
files from UFDs, 3-32
lines, 1-3
trailing spaces, 3-26
truncated files, 3-34, 4-2
UFDs, 3-3
Delimiters, 2-6
Destination/source commands, 2-2
Devices, 2-1, 2-7
Device to device file transfers,
3-17
Directoried devices, file transfers between, 3-13
Directory initialization, 3-41
Directory initialization during
transfer, 3-22
Directory list operation, 3-5
Directory protection codes, 3-36
Directory setup, 3-1
Display device, VP15A, B-1
Display system, VT15 graphics, A-l
Dump mode, 2-12, 3-41

ERASE pushbutton, B-1
Error corrections, 5-7
Error detection, 5-1
Error messages,
PIP, 5-3
system, D-l

Filename, 2-1, 2-3
extensions, 2-13
File protection codes, 2-13, 2-14,
3-14, 3-36
Files, deletion of, 3-34
File transfer commands, 3-12
File transfers,
card input, 3-25
device to device, 3-17
to disk, 3-15
keyboard input to output device,
3-18
paper tape input, 3-25
source file to multiple paper
tapes, 3-31
UFD to UFD, 3-16
Functions, optional, 2-9
Function switches, 3-20

Index-l

INDEX
Horizontal tab codes, 3-21

Image alphanumeric data mode,
2-12
Image binary data mode, 2-12
Initialization of
current UFD, 3-1
DECtape directories, 3-4
MFD, 4-2
new directory, 3-1
Input/output devices, 2-7
Input, termination of, 1-3
lOPS ASCII data mode, 2-11
lOPS binary data mode, 2-11

Keyboard command characters, 1-3
Line deletion, 1-3
List DECtape directories, 3-10
List directory operation, 4-2
List (L) operation, 3-5
List MFD, 3-7
List monitor SYSBLK, 3-8
List selected file, 3-10
List UFD, 3-6
List UFD with file protection
codes, 3-9

Master File Directory (MFD)
listing, 3-7
Mnemonics, 2-7
Monitor Identification Code
(MIC) , 4-1

New directory (N) operation, 3-1

Paper tape input, 3-25
Parity/checksum error correction,
3-20
Parity errors, 3-27, 5-2
Primary operations, 2-7
summary of, 2-8
Protection codes, 2-1, 2-14, 3-2,
3-36
violations of, 5-2
Pushbuttons,
VP15A, B-1
VT15, A-2

Q-dump operations, 3-5

Renaming files, 3-35
Restart PIP, 1-3
RETURN, 1-3

SCAN mode, VP15A, B-2
SCROLL mode, VT15, A-2
Segmentation point, 3-28
Segment file operation, 3-28
Selected file, listing of, 3-10
Single-device commands, 2-3
Single file transfers, 3-13
Source file to multiple paper
tapes segmentation operations,
3-31
Space, delete trailing, 3-26
Space delimiters, 3-21
Space-to-tab conversion, 3-21
Startup procedures, 1-2
Storage Allocation Table (SAT)
update, 3-42
Storage device, 2-7
Switch combinations, 3-14, 3-20
Switches, data
(A),
(B),

Operation, abort, 1-2
Operational errors, 5-2
Optional functions, 2-1, 2-9
Options, 6-3
Option switches, 2-3
Output to paper tape, 3-31

2-11
2-11

(D), 2-12
(H), 2-12
(I), 2-12
Switches, function
(C), 3-21, 3-22, 3-25, 3-26
(E), 3-21
(G), 3-20
(K),

3-4

(L), 3-6, 3-8, 3-10
(M), 3-6, 3-7, 3-10
(N), 3-22, 3-41
(P), 3-6, 3-9, 3-10, 3-12
(Q), 3-25

Page mode, 4-1
VP15A, B-2
VT15, A-2

Index-2

INDEX
Switches, function
(S), 3-5, 3-41
(T), 3-25
(V), 3-25
(W), 3-23, 3-25
Symbols in text, 1-3
SYSBLK listing, 3-8
System error messages, D-l
System file protection code,
3-14

UIe block copy, 3-38
Updating tables, 3-42
User File Directory (UFD), 2-11,
2-13
deletion, 3-3
file deletion, 3-32
initialization, 4-1
listing, 3-6, 3-9
protection code, 3-2

Verify operation, 3-27
Vertical forms control, 3-26
VIEW pushbutton, B-1
VP15A display device, B-1
VT15 graphics display system,
A-I

Tab delimiters, 3-21
Tables, 6-1
Tab-to-space conversion, 3-21
Terminate input, 1-3
Terms, XVM/DOS, e-l
Trailing spaces, deletion of,
3-26
Transfer files
see File transfers
Truncated files, 3-35, 3-40

Writing conventions, 1-2

XVM/DOS terms, C-l
UFD to UFD file transfers, 3-16

Index-3

PIP XVM
Utility Manual
DEC-XV-UPPUA-A-D

READER'S COMMENTS
NOTE:

This form is for document corrments only. Problems
with software should be reported on a Software
Problem Report (SPR) form.

Did you find errors in this manual?

If so, specify by page.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.

Is there sufficient documentation on associated system programs
required for use of the software described in this manual? If not,
what material is missing and where should it be placed?

Please indicate the type of user/reader that you most nearly represent.
[] Assembly language programmer
[]

Higher-level language programmer

[]

Occasional programmer (experienced)

[] User with little programming experience
[]

Student programmer

[]

Non-programmer interested in computer concepts and capabilities

Name

Date ___________________________

Organization __________________________________________________________________
Street ________________________________________________________________
City ____________________________ State _____________ Zip Code _______________
or
Country
If you require a written reply, please check here.

[]

-------------------------------------------------------------Fold lIere---------------------------------------------------________.

-----------------------------------------------. Do Not Tear - Fold lIere and Staple -----------------------------------------------

FIRST CLASS
BERM IT NO. 33
MAYNARD, MASS.
BUSINESS REPLY MAIL
NO POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES

Postage will be paid by:

Software Communications
P. O. Box F
Maynard, Massachusetts 01754

digital equipment corporation

PRINTED IN U.S.A.