DEC 11 UPPA A D_PIP_Aug73 D PIP Aug73

DEC-11-UPPA-A-D_PIP_Aug73 DEC-11-UPPA-A-D_PIP_Aug73

User Manual: DEC-11-UPPA-A-D_PIP_Aug73

Open the PDF directly: View PDF PDF.
Page Count: 72

DEC-ll-UPPAA-A-D
DOS/BATCH
File Utility Package
(PIP)
Programmer's Manual
FOR
THE
DOS/BATCH OPERATING
SYSTEM
Monitor
Version
V~9
August
1973
For
additional
copies,
order
No.
DEC-ll-UPPAA-A-D
from
Digital
Equipment
Corporation,
Software
Distribution
Center,
Maynard,
Massachusetts
01754.
First
Printing,
May
Second
Printing
September
Revised,
October
Revised,
January
Revised,
July
Your
attention
is
invited
to
the
last
two
pages
of
this
document.
The
"How
to
Obtain
Software
Infor-
mation"
page
tells
you
how
to
keep
up-to-date
with
DEC's
software.
The
"Reader's
Comments"
page,
when
filled
in
and
mailed,
is
beneficial
to
both
you
and
DEC;
all
conwents
received
are
considered
when
docu-
menting
subsequent
manuals.
Copyright
0
1971,
1972,
1973
by
Digital
Equipment
Corporation
Associated
Document:s:
DOS/BATCH
Monitor
Programmer's
Manual,
DEC-II-OMPMA-A-D
DOS/BATCH
User's
Guide,
DEC-II-OBUGA-A-D
DOS/BATCH
Assembler
(MACRO-II)
Programmer's
Manual,
DEC-II-LASMA-A-D
DOS/BATCH
FORTRAN
Compiler
and
Object
Time
System
Programmer's
Manual,
DEC-II-LFRTA-A-D
DOS/BATCH
System
Manager's
Guide,
DEC-II-OSMGA-A-D
DOS/BATCH
Debugging
Program
(ODT-IIR)
Programmer's
Manual,
DEC-II-UDEBA-A-D
DOS/BATCH
Linker
(LINK)
Programmer's
Manual,
DEC-II-ULKAA-A-D
DOS/BATCH
Librarian
(LIBR)
Programmer's
Manual,
DEC-II-ULBAA-A-D
DOS/BATCH
Text
Editor
(EDIT-II)
Programmer's
Manual,
DEC-II-UEDAA-A-D
DOS/BATCH
File
Compare
Program
(FILCOM)
Programmer's
Manual,
DEC-II-UFCAA-A-D
DOS/BATCH
File
Dump
Program
(FILDMP)
Progranmer's
Manual,
DEC-II-UFLDA-A-D
DOS/BATCH
Verification
Program
(VERIFY)
Programmer's
Manual,
DEC-II-UVERA-A-D
DOS/BATCH
Disk
Initializer
(DSKINT)
Progranmer's
Manual,
DEC-II-UDKIA-A-D
1971
1971
1972
1973
1973
The
following
are
trademarks
of
Digital
Equipment
Corporation,
Maynard,
Massachusetts:
CDP
COMPUTER
LAB
COMTEX
COMSYST
DDT
DEC
DECCOMM
DECTAPE
DIBOL
DIGITAL
DNC
EDGRIN
EDUSYSTEM
FLIP
CHIP
FOCAL
GLC-8
IDAC
IDACS
INDAC
KAID
LAB-8
ii
LAB-8/e
LAB-K
OMNIBUS
OS/8
PDP
PHA
PS/8
QUICKPOINT
RAD-8
RSTS
RSX
RTM
SABR
TYPESET 8
UNIBUS
PREFACE
This
manual
describes
the
~eatures
and
operation
of
version
V~~9
of
the
File
utility
Package
(PIP)
for
DOS/BATCH.
The
manual
assumes
familiarity
with
the
DOS/BATCH
Monitor.
The
file
utility
Package
is
called
PIP
(Peripheral
Interchange
Program)
for
compatibility
with
similar
programs
on
other
DEC
systems.
Features
provided
by
PIP
include
file
transfers
from
one
device
to
another,
file
deletions,
file
renaming,
and
directory
listings.
Appendix
B,
"Helpful
Hints",
contain
valuable
information
on
possible
solutions
to
problems
that
can
arise
while
becoming
familiar
with
PIP.
This
software
is
furnished
to
purchaser
under
a
license
for
use
on
a
single
computer
system
and
can
be
copied
(with
inclusion
of
DEC's
copyright
notice)
only
for
use
in
such
system,
except
as
may
otherwise
be
provided
in
writing
by
DEC.
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
manual.
Digital
assumes
no
responsibility
for
the
use
or
reliability
of
its
software
on
equipment
that
is
not
supplied
by
DIGITAL.
iii
CONTENTS
CHAPTER 1 INTRODUCTION
1.1
CALLING
PIP
1.2
RECOVERING
FROM
ERRORS
1.3
RETURNING
TO
THE
DOS
MONITOR
1.3.1
Interactive
Environment
1.3.2
Batch
Stream
CHAPTER 2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
CHAPTER 3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.2
3.3
3.4
3.5
3.6
3.7
CHAPTER 4
4.1
4.2
4.2.1
4.2.2
4.3
COMMAND
STRINGS
GENERAL
COMMAND
STRING
FORMATS
DEVICE
SPECIFICATION
FILENAME
SPECIFICATION
FILENAME EXTENSION
SPECIFICATION
ASTERISK
FEATURE
USER
IDENTIFICATION
CODE
SPECIFICATION
SWITCH
SPECIFICATIONS
FILE
MANIPULATION
FILE
TRANSFERS
File
Copy
Operation
Fast
Copy
and/or
Verify
Operations
File
Merge
Operation
File
Transfer
Modes
Contiguous
Files
Transfers
from
the
Teleprinter
RENAMING
FILES
DELETING
FILES
INSPECTING
FILES
SUPERSEDE OPERATION
FILE
PROTECTION
CODES
ALLOCATING A CONTIGUOUS
FILE
DIRECTORY MANIPULATION
ENTERING USER
IDENTIFICATION
INTO DIRECTORY
DIRECTORY
LISTINGS
Full
Directories
Brief
Directory
Listings
FREE BLOCKS
v
1-1
1-2
1-3
1-3
1-3
2-1
2-2
2-3
2-3
2-4
2-5
2-5
3-1
3-1
3-2
3-3
3-4
3-5
3-7
3-8
3-9
3-10
3-10
3-11
3-13
4-1
4-2
4-2
4-6
4-9
4.4
DECTAPE
AND
RKII
DISK
INITIALIZATION
4.4.1
DECtape
4.4.2
RK11
Disk
4.5
RECOVERING
FILES
CHAPTER 5
5.1
5.2
5.3
5.4
5.5
CHAPTER 6
6.1
6.2
6.3
6.4
6.5
CHAPTER 7
APPENDIX A
APPENDIX B
APPENDIX C
INDEX
MAGTAPE
OPERATION
GENERAL
MAGTAPE
INFORMATION
REWIND
REWIND/UNLOAD
ZERO
(INITIALIZATION)
MAGNETIC
TAPE
FORMAT
CASSETTE TAPE OPERATION
GENERAL
CASSETTE TAPE INFORMATION
REWIND
ZERO
(INITIALIZATION)
CASSETTE TAPE
FORMAT
READ-AFTER-WRITE VERIFICATION
ERROR MESSAGES
SUMMARIES
HELPFUL HINTS
PROGRAMMING
CAUTIONS
vi
4-9
4-9
4-10
4-11
5-1
5-2
5-3
5-3
5-3
6-1
6-1
6-2
6-2
6-2
7-1
A-I
B-1
C-l
X-I
CHAPTER 1
INTRODUCTION
The
File
Utility
Package
performs
transfers
of
data
files
from
standard
PDP-II
I/O
devices
to
other
standard
PDP-II
I/O
devices
and
performs
simple
editing
and
control
functions
as
well.
PIP,
~eripheral
Interchange
~rogram,
handles
all
standard
data
formats
used
in
the
DOS/BATCH
system.
The
major
features
provided
by
PIP
are
as
follows:
•
Transfer
a
file
or
group
of
files
from
one
device
to
another
with
output
being
either
linked
or
contiguous
(refer
to
section
3.l.5);
•
Merge
a
group
of
input
files
into
a
single
(new)
output
file;
•
Allocate
a
contiguous
file
on
disk
or
DECtape;
•
Rename
an
existing
file;
•
Cause
an
input
file
having
the
same
name
as
a
file
on
the
output
device
to
replace
that
output
file
-
also
a
switch
to
turn
this
mode
on
or
off;
•
Delete
a
file
or
group
of
files;
•
Selectively
perform
an
operation
on
each
file
of
a
group
of
files;
•
Change
the
protection
code
on
a
file;
•
Print
filename,
file
size,
creation
date,
and
protection
code
of
each
file
in
a
disk,
DECtape,
cassette,
or
magtape
directory.
•
Print
a
listing
of
the
filenames
on
disk,
DECtape,
cassette,
or
magtape
directory.
•
List
the
number
of
free
blocks
remaining
on
the
device
specified;
•
Zero
(initialize)
a
disk
(except
RP~3),
DECtape,
cassette,
or
magtape;
•
Perform
fast
copy
and/or
verify
operations
for
DECtape.
•
Perform
read-after-write
verification
for
cassette
tape.
1.1
CALLING
PIP
The
user
must
be
logged
into
the
Operating
System
before
run-
ning
PIP.
Any
previous
program
in
core
must
be
removed
with
the
KILL
command.
(The
user
should
be
familiar
with
the
Operating
System
1-1
con~ands
before
attempting
to
use
PIP;
particularly
the
RUN,
LOGIN,
KIIIL,
and
FINISH
commands.)
In
response
to
the
System
Monitor's
dollar
sign
character,
the
user
can
type
the
RUN
PIP
command.
For
example:
$RUN
PIP
PIP
Vxx
(xx
is
PIP
version
number)
!
Following
the
RUN
command,
PIP
is
called
into
core,
prints
its
version
number
and
a
number
sign.
The
number
sign
indicates
that
PIP
is
ready
to
accept
a command
string.
Following
completion
of
a command,
PIP
prints
another
number
sign
and
awaits
further
commands.
NOTE
A
convention
followed
throughout
this
manual
is
the
underlining
of
all
Monitor
and
system
program
printout
to
differentiate
it
from
user-typed
commands,
which
are
not
under-
lined.
Large
sections
of
system
program
continuous
output
(such
as
directory
listings)
are
not
underlined.
All
commands
are
termi-
nated
with
the
nonprinting
RETURN
key,
causing
a
carriage
return/line
feed
operation.
1.2
RECOVERING
FROM
ERRORS
When
using
PIP,
the
user
may
receive
an
error
message
from
time
to
time.
An
A
error
message
issued
by
the
Monitor
indicates
a
need
for
operator
intervention.
In
the
event
an
A
error
occurs,
the
user
should
consult
the
DOS/BATCH-ll
Progrannner's
Manual
for
a
description
of
the
error
and
then
correct
the
error
condition
and
give
the
CONTINUE
command.
For
example::
#DT1:ABC<PR:
A002
063320
!CONTINUE
#
(high-speed
reader
is
out
of
tape,
RAD5~
representations
of
standard
devices
are
shown
in
Appendix
A.)
(put
tape
in
reader
and
give
CONTINUE
command)
(operation
has
been
performed)
1-2
An S
error
message
indicates
some
improper
condition
detected
by
PIP.
Many
S
errors
are
correctable
and
recoverable.
In
the
event
an
S
error
message
occurs,
the
user
should
consult
Chapter
7
of
this
manual
for
the
meaning
of
the
error
and
take
corrective
action
accord-
ingly.
A
typical
problem
is
a
bad
command
string,
as
is
shown
below.
!DT0:EN
8242 000000
!DT0:/EN
#
(the
slash
for
the
switch
is
absent)
(meaningless
command;
no
action
taken)
(retype
the
command
correctly)
(operation
is
performed
and
PIP
is
ready
to
accept
another
command)
An F
error
message
indicates
a
fatal
condition
has
occurred.
If
an
F
error
message
occurs
when
using
PIP,
the
user
must
perform
a
Monitor
BEGIN
or
RESTART
command
before
entering
another
PIP
command.
(See
the
description
of
error
messages
and
of
actions
to
take
in
the
Appendix
portion
of
the
DOS/BATCH
Monitor
Programmer's
Manual.)
1.3
RETURNING
TO
THE
DOS/BATCH MONITOR
1.3.1
Interactive
Environment
To
exit
from
PIP
to
the
DOS
Monitor,
type
CTRL/C
(hold
down
the
CTRL
key
while
typing
the
C
key).
This
returns
control
to
the
DOS
Monito~
at
which
time
the
KILL
command
should
be
given
prior
to
running
another
(system
or
user)
program.
Unless
you
wish
to
abort
the
current
operation,
you
should
not
type
CTRL/C
and
KILL
until
after
PIP
has
responded
with
a
#.
1.3.2
Batch
Stream
When
PIP
is
running
from
the
batch
mode,
the
batch
command
$KILL
terminates
PIP,
stops
all
I/O,
and
closes
all
files.
Processing
continues
at
the
next
command
prefixed
by
a
dollar
sign
($).
No
arguments
are
specified
for
$KILL.
The
$KILL
command
can
be
entered
from
the
console
keyboard
to
abort
the
current
job
while
in
batch
mode;
for
example,
typing
in
the
following
sequence
aborts
the
current
job:
tc
.KILL (CTRL/C
was
typed;
tc
is
echoed)
1-3
The
following
batch
commands
also
force
a KILL
sequence:
$CHANGE
$FINISH
$GET
$JOB
$RUN
Refer
to
the
Batch
User's
Guide
for
details.
1-4
CHAPTER 2
COMMAND
STRINGS
All
commands
to
PIP
are
processed
by
the
Operating
System's
Com-
mand
String
Interpreter
(CSI).
This
ensures
a
uniform
command
format
among
the
various
system
programs
operating
under
DOS/BATCH.
This
Chapter
briefly
describes
the
command
string
format
'of
PIP.
2.1
GENERAL
COMMAND
STRING
FORMATS
The
most
general
format
of
a
PIP
command
string
is:
output
file<input
file(s}
A
single
input
or
output
file
is
completely
specified
by
the
fol-
lowing
information:
where:
dev:filnam.ext[uic]
dev:
filnam
ext
[uic]
is
the
device
on
which
the
file
currently
resides
or
will
reside
following
a
transfer;
is
the
name
of
the
file
(if
any);
is
the
filename
extension
(if
any);
and
is
the
user
identification
code
(if
specified).
For
example:
DT0:MACRO.OBJ[200,200J
2-1
Either
an
output
or
an
input
file
specification
can
be
followed
by
a
switch
specification
in
the
command
string.
A
switch
specifica-
ticm
indicates
that
some
special
PIP
action
is
to
be
performed.
(See
Table
2-1
for
a
list
of
PIP
switches.)
The
switch
specifications
are
of
two
forms:
/sw
or
/sw:n
where:
/
sw
:n
signals
a
PIP
switch
specification
indicates
the
two
letter
switch
code
indicates
a
decimal
or
octal
value
(sup-
portive
argument
required
by
some
switches)
PIP
commands
can
take
a
variety
of
formats,
depending
upon
the
act~ion
desired.
Some
PIP
actions
are
caused
when
a
switch
is
the
only
specification
in
the
command
string.
Other
PIP
actions
are
caused
by
a
file
specification
followed
by
one
or
more
switch
speci-
fications
in
the
command
string.
Examples
of
typical
command
strings
are
shown
throughout
the
manual.
2.2
DEVICE
SPECIFICATION
The
device
specification
consists
of
two
letters,
followed,
where
necessary,
by
an
octal
digit
indicating
one
of
multiple
units,
and
terminated
by
a
colon.
(The
standard
device
specifications
are
shown
in
Appendix
A.)
An
octal
digit
is
required
in
the
device
specifica-
tion
to
distinguish
between
units
on
multiple-unit
devices.
For
ex-
ample,
DT1:
and
DT2~
could
be
used
to
specify
two
DECtapes
on
the
same
controller.
When
no
digit
is
indicated
for
a
device,
unit
~
is
assumed
by
the
system.
2-2
When
no
device
is
specified
for
a
file,
the
desired
device
is
assumed
to
be
the
last
device
specified
on
that
side
(input
or
output)
of
the
angle
bracket
«).
For
example:
!DKl:<DTl:FILEl,FILE2
where
FILEI
and
FILE2
are
on
OECtape
unit
1.
When
no
device
has
been
specified
on
the
current
side
of
the
<,
the
system
disk
is
assumed
to
be
the
default
I/O
device
(except
for
/OI,
/BR,
and
/FR
switches
where
the
teleprinter
is
the
default
out-
put
device
and
the
System
disk
is
the
default
input
device).
For
example,
/OI
will
list
the
current
user's
system
disk
directory
on
the
teleprinter.
2.3
FILENAME SPECIFICATION
A
filename
specification
consists
of
from
one
to
six
letters
or
digits
or
an
asterisk.
All
characters
in
excess
of
six
are
ignored.
The
asterisk
feature
is
described
in
section
2.5.
Examples
of
file-
names
are
shown,
below:
SEVENLE
A34B
FILE
*
is
interpreted
as
SEVENL
indicates
all
(filenames
or
extensions)
Null
fields
in
a
command
are
ignored,
e.g.
!SY:<DKl:A",B
causes
files
A
and
B
to
be
read
from
the
OKI
disk
to
the
system
disk
as
properly
as
if
the
superfluous
commas
were
not
present,
i.e.,
filenames
are
separated
by
a
comma.
2.4
FILENAME EXTENSION
SPECIFICATION
The
filename
extension
specification
consists
of
a
period
followed
by
one
to
three
letters
or
digits,
or
an
asterisk.
The
asterisk
feature
is
described
in
section
2.5.
Extensions
may
be
used
to
specify
the
format
in
which
a
certain
file
is
stored,
the
version
of
a
particular
file,
or
any
other
information
the
user
desires.
Examples
of
filenames
used
with
filename
extensions
are
shown
below:
2-3
FORT.lA
ABC.PAL
FILE.TMP
MODS.flfll
MODS.flfl2
MAT.*
all
files
with
the
name
MAT
Filename
extensions,
where
associated
with
a
filename,
must
be
used
to
specify
that
particular
file,
unless
the
asterisk
feature
is
used.
A
filename
extension
may
not
be
used
without
a
filename
(except
with
an
asterisk
substituted
for
a
filename,
as
described
below).
2.5
ASTERISK
FEATURE
The
asterisk
(*)
character
can
be
used
in
a command
string
to
replace
either
the
filename
or
filename
extension
specification.
The
asterisk
can
be
read
as
lIall
files
ll
with
the
filename
or
filename
extension
indicated.
For
example:
*.TMP
indicates
all
files
with
the
extension
.TMP
FILE.*
indicates
all
files
with
the
name FILE
The
asterisk
can
appear
in
both
positions:
*.*
which
denotes
all
files
on
the
specified
device
belonging
to
the
user
identification
code
specified
(or
the
current
user
UIC
if
no
Ule
is
specified).
Except
where
noted
in
this
manual,
the
asterisk
feature
can
be
used
in
all
transfer
operations,
all
directory
listing
operations,
deletion
operations,
protection
operations
and
rename
operations.
PIP
can
reference
all
files
with
null
extensions
through
use
of
the
asterisk
feature.
For
example,
to
delete
all
files
with
null
(no)
extensions,
the
command
is:
!*./DE
2-4
2.6
USER IDENTIFICATION
CODE
SPECIFICATION
The
User
Identification
Code
(UIC)
specification
consists
of
a
pair
of
1-
to
3-digit
octal
numbers,
each
of
which
may
have
a
value
between
11
and
376
(~-l~
are
reserved
for
special
use),
separated
by
a
comma,
and
enclosed
within
square
brackets.
(The
left
and
right
square
brackets
are
typed
using
SHIFT/K
and
SHIFT/M
on
ASR-33's.)
The
left
number
specifies
a
user
group
and
the
right
number
specifies
a
particular
user
within
a
group.
The
User
Identification
Code
is
used
in
connection
with
file
storage
and
file
protection
(see
section
3.6)
1.
When a UIC
does
not
appear
in
a
command
string,
the
UIC
specified
in
the
last
LOGIN
com-
mand
is
assumed.
The
asterisk
feature
is
allowed
in
the
UIC
for
cer-
tain
switches
(see
sections
4.2.1
and
4.2.2.)
Examples
of
acceptable
UIC's
are
shown
below.
Explicit
non-current
UIC
specification
and/or
the
asterisk
feature
are
allowed
in
the
UIC
field
for
functions
that
do
not
disturb
another
user's
area
or
for
functions
that
are
not
explicitly
prohibited
by
the
other
user.
For
example,
if
the
user
is
logged
in
under
account
200,200,
the
following
actions
are
legal:
1.
See
section
4.2.1.
2.
See
section
4.2.2.
3.
!SY:FILE.EXT<SY:OTHER.EXT[30,50J
if
OTHER.
EXT
is
not
protected
from
other
user
groups.
The
following
actions
are
illegal:
1.
!SY:FILE.EXT[30,40J<SY:FILE2.EXT
2.
!SY:[*,*J<SY:NAME.EXT
3.
!SY:FILE.EXT<SY:PROT.EXT[30,60J
if
PROT.EXT
is
protected
from
other
user
groups.
Examples
of
acceptable
UIC's
are
shown
below.
[2~~,2~~]
[2~¢,2¢1]
[2¢¢,244]
[l~¢,l¢¢]
[376,376]
three
users
in
one
group
lCassette
tape
does
not
have
UIC
specifications
implemented.
2-5
Switch
Code
/AL
/BR
/CO
IDE
/DI
/EN
/FA
IFB
/FC
/FR
lIN
/PR
/RE
/RU
/RW
ISU
Switch
Name
Allocate
Brief
Directory
Contiguous
Delete
Directory
Enter
Formatted
ASCII
Formatted
Binary
Fast
Copy
Free
Inspect
Protect
Rename
Rewind/
Unload
Rewind
Supersede
Table
2-1
PIP
Switch
Options
Operation
Allocates
a
blank
contiguous
file
List
only
filenames
and
extensions
in
the
directory
of
the
device(s)
specified.
Create
a
contiguous
output
file.
Delete
the
file(s)
specified
List
the
directory
or
a
subset
thereof
for
the
device(s)
specified.
This
includes:
filenames,
extensions,
file
size,
creation
date,
and
protection
code
for
each
file
Enter
the
user
identification
code
spec-
ified
into
the
Master
File
Directory
of
the
specified
devLce.
Transfer
file(s)
indicated
in
formatted
ASCII
mode
Transfer
file(s}
indicated
in
formatted
binary
mode
Transfer
all
files
from
one
DEC
tape
to
another
List
the
number
of
free
blocks
on
the
device(s}
specified
List
all
files
for
confirmation
before
per-
forming
action
so
that
user
can
proceed
or
bypass.
Change
the
protection
on
the
file(s)
indicated
to
the
value
given
Rename
the
file
indicated
to
the
name
given
Rewind
the
magtape
or
cassette
tape
unit
specified
and
turn
that
unit
off-line
Rewind
the
magtape
unit
specified
Cause
the
input
file
having
the
same
name
as
a
file
on
output
device
to
replace
that
output
file
2-6
Switch Switch
Code
Name
JUA
Unformatted
ASCII
JUB
Unformatted
Binary
JUN
Unlock
jVE
Verify
jW
Verified
write
jZE
Zero
Table
2-1
(cont'd)
Operation
Transfer
file(s)
indicated
in
unformatted
ASCII
mode
Transfer
file(s)
indicated
in
unformatted
binary
mode
Unlock
the
User
File
Directory
to
recover
the
file
specified
Verify
that
blocks
on
two
DECtapes
are
alike,
otherwise
print
differences
Verify
a
write
operation
by
reading
the
block
after
writing
it
Initializes
the
file
structure
on
the
device(s)
specified
2.7
SWITCH
SPECIFICATIONS
The
switch
specification
consists
of
a
slash
followed
by
two
letters,
and
is
optionally
followed
by
a
value
specification
of
octal
or
decimal
digits
separated
from
the
switch
code
by
a
colon.
Switch
names
can
be
of
any
length;
but,
only
the
first
two
charac-
ters
are
significant.
Nontransfer
operations
in
PIP
are
selected
by
use
of
switches.
If
more
than
one
switch
is
used,
each
switch
is
preceded
by
a
slash.
A summary
of
the
switch
options
is
shown
in
Table
2-1.
When
present,
a
switch
must
follow
any
file
or
UIC
specification;
that
is,
a
switch
cannot
appear
before
the
filename,
extension,
or
UIC
of
the
file
on
which
the
switch
is
to
operate.
However,
some
switches
may
be
specified
without
any
file
specification
at
all.
Some
options
require
a
numeric
value
to
be
associated
with
the
switch.
Whether
the
value
is
octal
or
decimal
depends
upon
the
switch.
For
example:
jPR
is
the
switch
to
change
the
file
protection
code.
The new
protection
code
is
preceded
by
a
colon
as
follows:
#DTl:ABC/PR:155
2-7
which
changes
the
protection
code
of
file
ABC
on
DECtape
unit
1
to
155.
Refer
to
section
3.6
for
a
description
of
protection
codes
and
their
uses.
In
general,
PIP
switch
options
can
be
grouped
into
two
cate-
gories:
action
switches
and
qualifying
switches.
Action
switches
are
generally
associated
with
some
action
or
operation.
Only
one
act:ion
switch
can
be
used
in
anyone
PIP
command.
The
action
switches
are
as
follows:
IAL
IBR
IDE
101
lEN
IFC
IFR
IPR
IRE
IRU
IUN
IVE
IZE
Allocate
Brief
Directory
Delete
Directory
Enter
Fast
Copy
Free
Protect
Rename
Rewind
and
Unload
Unlock
Verify
Zero
Qualifying
switches
are
used
to
give
PIP
particular
information
about
how
to
perform
an
operation.
These
switches
can
be
used
in
con.junction
with
other
switches
in
a
single
command
string.
The
qualifying
switches
are:
ICO
IFA
IFB
lIN
IRW
Isu
IUA
IUB
IVE
/VW
Contiguous
Formatted
ASCII
Formatted
Binary
Inspect
Rewind
Supersede
Unformatted
ASCII
Unformatted
Binary
Verify
Verified
Write
Another
type
of
distinction
which
is
made
among
switches
is
that
some
can
be
used
alone,
some
operate
upon
a
single
file
designation,
and
some
require
both
an
input
and
an
output
specifi-
cation,
as
follows:
2-8
Used
Used
with
One
or
More
Used
with
Both
an
Input
Alone
File
Oesi~nations
and
OutEut
Oesisnation
IBR IBR
IBR
IOI IOI IOI
IAL
IFA
IOE
lEN
lEN
IFR
IFR
IPR
IPR
IRE
IRE
IUN
IRW
ICO
IFR
IFB
IZE IZE
IUA
Isu
IUB
lIN
Ivw
2-9
CHAPTER 3
FILE
MANIPULATION
3.1
FILE
TRANSFERS
The
transferring
of
files
between
devices
is
a
primary
function
of
PIP.
PIP
uses
the
device
independent
features
of
the
Operating
System
and
can
either
copy
a
file
directly
onto
another
device
or
merge
several
files
from
the
same
or
different
devices
into
a
single
file
on
one
device.
3.1.1
File
Copy
Operation
In
the
simplest
case,
PIP
can
transfer
a
file
from
one
peripheral
onto
another.
For
example,
to
list
a
file,
transfer
a
copy
of
the
file
to
the
line
printer:
#LP:<DT2:FILE1.PAL
#LP:<MT1:FILE2.PAL
!LP:<FILE3.
PAL
where
FILE1.PAL
is
on
DECtape
where
FILE2.PAL
is
on
magtape
where
FILE3.PAL
is
on
the
system
disk
The
following
command
transfers
the
data
on
a
paper
tape
from
the
high-speed
reader
and
creates
a
file
named
INPUT.TST
on
the
system
disk:
!t.INPUT.TST<PR:
The
following
command
duplicates
a
paper
tape:
!t.
PP
:
<PR:
Ther~
can
be
only
one
output
file
designation
in
a
PIP
command,
although
there
can
be
any
number
of
input
files
(limited
only
by
the
teleprinter
line
length).
For
example,
to
copy
three
files
(ONE.PAL,
TWO.
PAL,
and
THREE.PAL)
from
the
system
disk
onto
DEC
tape
unit
~,
type:
!t.DT:<ONE.PAL,TWO.PAL,THREE.PAL
3-1
In
the
case
shown
above,
the
files
are
copied
directly
to
DECtape
unit
$J,
using
the
same
filenames
as
on.
disk.
In
order
to
later
change
the
filenames,
the
RENAME
(/RE)
switch
can
be
used:
#DK:<DTl:FILEl,PR:ABC,MT:DEF.$J$Jl
!DAVEl/RE<FlLEl
The
first
command
transfers
three
files
onto
the
RKII
disk
unit
$J~
FILEI
from
DECtape
unit
I,
ABC
from
the
paper
tape
reader,
and
DEF.~~l
from
magtape
unit~.
Each
file
retains
its
original
name.
Note
the
ability
to
indicate
the
name
of
a
file
from
the
high-speed
paper
tape
reader.
The
second
command
REnames
the
file
FILEl
on
DK~:
to
DAVEI.
3.1.2
Fast
Copy
and/or
Verify
Operations
The
FAST
COPY
(/FC)
and
VERIFY
(/VE
or
/FC/VE)
operations
are
applicable
only
to
DECtape.
Input
and
output
device
types
must
be
the
same~
unit
number:3
must
be
different.
The
S260
or
S23l
error
message
\~ill
result
if
the
preceding
two
conditions
are
not
met.
The
format
of
these
operations
is
illustrated
in
the
three
command
strings
shown
below.
or
or
tL
DT
l:<DT2:/FC/VE
tLDTl:
<D
'
r2:
/FC
tLDTl: <DT2:
/VE
PIP-II
allocates
the
largest
amount
of
core
memory
available
for
the
transfer
buffer
(buffers
in
the
case
of
VERIFY
operations);
l30
that
the
larger
the
main
memory,
the
faster
the
operation.
On
28K
machines,
for
example,
a
DECtape
can
be
copied
in
about
1:wo
minutes
~
verifying
it
takes
2
1/4
minutes.
3-2
The
VERIFY
operation
as
shown
above
can
be
performed
alone.
If
the
data
on
the
two
devices
differ,
a
message
indicating
the
block
and
word
in
disagreement
is
printed
at
the
console
in
the
following
octal
format:
Block
Word
N M
3.1.3
File
Merge
Operation
When
there
are
several
input
files
involved
in
a
transfer,
the
files
can
be
transferred
individually,
as
the
previous
examples
illustrate,
or
they
can
be
merged
into
a
single
output
file.
When
no
output
filename
is
specified
on
the
output
device,
input
files
are
copied
without
combining:
!DT3:<ABC,DT2:RASP,PR:DEF
Three
files
are
copied
onto
DECtape
unit
3;
one
from
the
system
disk,
one
from
DECtape
unit
2,
and
one
from
the
high-speed
paper
tape
reader.
Each
retains
the
same name
given
on
the
input
side.
When
a
filename
is
specified
on
the
output
device,
all
input
files
are
combined
to
create
a
single
new
output
file.
In
order
to
combine
the
three
files
shown
above
into
a
single
file
named
MERGE,
the
following
command
is
used:
!DT3:MERGE<ABC,DT2:RASP,PR:DEF
Numerous
variations
on
this
operation
are
possible.
One
or
more
of
the
input
files
can
be
specified
as
being
under
another
UIC,
input
files
can
be
on
the
same
or
different
devices,
etc.
An
operation
to
merge
a
single
file
is
equivalent
to
creating
another
copy
of
that
file
with
a
different
name,
e.g.
#ABC<DT1:FILEl
takes
FILEl
on
DECtape
unit
1
and
puts
it
on
the
system
disk
under
the
name
ABC.
1-1
3.1.4
File
Transfer
Modes
The
modes
of
transfer
under
the
Operating
System
are
either
form-
atted
or
unformatted,
either
ASCII
or
binary.
Refer
to
the
DOS/BATCH
Monitor
Programmer's
Reference
Manual
for
further
details
on
the
modes
of
transfer.
In
PIP,
the
mode
of
transfer
of
any
file
is
determined
by
the'
format
switch
specified
in
the
command
string.
If
a
format
switch;
is
not
specified
in
a
command
string,
the
mode
assumed
for
the
trans~er
is
unformatted
binary
(unformatted
ASCII
if
either
device
does
not
I
support
binary).
This
means,
for
example,
that
files
transferred;
from
paper
tape
without
a
mode
specification
include
blank
frames,
lea4er
and
trailer
tape.
Files
transferred
in
this
way
may
be
larger
than
necessary.
3-4
A
switch
specified
in
the
command
string
may
be
used
to
force
a
particular
mode
of
transfer.
The
switches
that
specify
format
are
IFA,
IFB,
IUA,
and
IUB.
Only
one
type
of
format
switch
shall
be
specified
in
a
command.
The
switch
can
be
used
with
both
input
and
output
files.
For
example,
to
transfer
the
files
ABC.DAT
and
ABC.TST
in
formatted
binary
mode:
or
!DT4:<ABC.DAT/FB,ABC.TST/FB
!DT4:/FB<ABC.DAT,ABC.TST
In
the
case
of
the
paper
tape
reader,
use
of
these
switches
guards
against
putting
the
tape
in
the
reader
backwards.
For
example,
if
the
paper
tape
were
in
backwards,
the
command:
#SPRMAN.OBJ<PR:/FB
would
cause
PIP
to
print
a
S202
error
message
on
the
teleprinter.
3.1.5
Contiguous
Files
Contiguous
files
are
handled
differently
by
the
Operating
Sys-
tem
than
are
regular,
linked
files.
Blocks
of
contiguous
files
are
guaranteed
to
be
physically
adjacent,
whereas
linked
files
are
generally
separated
by
a
minimum
fixed
distance
(called
the
interleave
factor)
to
take
advantage
of
the
rotational
delay
inherent
in
a
disk.
Con-
tiguous
files
are
generally
used
for
random
accessing
of
data,
a
feature
which
is
impossible
with
linked
files.
Unless
otherwise
specified,
file
transfers
will
produce
linked
files.
The
Ico
switch
is
used
to
specify
an
output
file
as
contiguous.
Three
cases
exist
where
use
of
the
Ico
switch
is
valid.
The
first
two
cases
apply
to
a
merge
operation
and
a
copy
operation.
For
each
operation,
a
new
filename
is
specified
in
the
output
field
3-5
of
the
command
string.
The
leo
switch
must
be
specified
in
the
out-
put
side
of
the
command
string
if
the
new
file
is
to
be
created
as
a
contiguous
file,
as
shown
below.
1.
A
merge
operation
where
the
new
file
is
to
be
made
contiguous.
For
example,
#SY:FILEME.RGE/CO<DKl:FILl,DTl:FIL2
2.
A
copy
operation
where
the
new
file
is
to
be
made
contiguous.
For
example,
#SY:FILB/CO<DKl:FILA
(see
Note)
NOTE
In
the
case
where
the
output
file
is
explicitly
named,
the
leo
switch
must
be
on
the
output
side.
In
both
of
the
above
cases,
it
makes
no
difference
whether
the
input
filE~(s)
is
contiguous
or
linked.
The
output
file
must
be
designated
contiguous
with
the
leo
switch.
The
third
case
applies
to
a
simple
transfer
operation
wherle
no
new
filename
is
specified
explicitly
but
the
new
output
file(s)
is
to
be
made
or
is
to
remain
contiguous.
In
this
case,
the
leo
switch
must
be
given
on
the
input
side
of
the
command
string
for
the
file(s)
desired
to
be
contiguous
on
the
output
device.
For
example,
!SY:<DKl:FILl/CO,FIL2,FIL3/CO
Both
FILl
and
FIL3
are
created
as
contiguous
files
on
the
output
device.
FIL2
is
created
as
a
linked
file,
whether
or
not
it
is
linked
or
contiguous.
The
same
applies
to
the
simplest
case.
For
example,
!SY:<DKl:FILA/CO
FILA
is
created
as
a
contiguous
file
on
the
output
device.
If
the
leo
switch
is
not
used,
FILA
would
be
created
as
a
linked
file
on
the
out-
put
device,
whether
or
not
is is
linked
or
contiguous
on
the
input
device.
All
other
uses
of
the
leo
switch
are
invalid.
A
contiguous
file
is
denoted
in
a
full
directory
listing
by
a C
following
the
number
of
blocks
for
that
file.
3-6
3.1.6
Transfers
from
the
Teleprinter
Occasionally,
the
user
may
wish
to
transfer
a
file
from
the
teleprinter
keyboard
to
another
device.
This
is
accomplished
as
fol-
lows:
#PP:<KB:
Subsequent
characters
typed
at
the
keyboard
are
output
to
the
high-speed
paper
tape
punch.
(Punching
is
performed
in
bursts
as
the
tape
punch.buffer
fills.)
To
indicate
an
end-of-file
with
such
an
operation
(i.e.
to
stop
transferring
data
to
the
punch),
the
DOS
convention
is
to
type
CTRL/C
followed
by
the
END
command.
In
order
to
execute
the
command,
the
terminal
must
be
in
Monitor
mode.
Consequently,
the
sequence
is:
tc
.END
(type
CTRL/C)
(followed
by
the
RETURN
and
LINE FEED
keys
respectively)
The
terminal
LINE FEED
keying
is
necessary
to
force
control
back
to
PIP
after
the
END
command
is
executed.
PIP
returns
with
a
number
sign
(#)
when
the
above
sequence
is
completed.
This
same
sequence
is
necessary
when
transferring
from
the
low-speed
paper
tape
reader.
However,
it
is
necessary
to
indicate
the
end-of-file
from
the
user
keyboard;
the
END
PT
command
is
given
in
this
case.
If
the
user
types:
#DF:FILEIN.MAC<PT:
It
is
necessary
to
type:
tc
.END
PT
(type
CTRL/C)
(followed
by
the
RETURN
key
and
LINE FEED
key
respective-
ly;
no
colon
is
used
after
PT)
after
the
tape
has
been
read
and
the
low-speed
reader
stops.
Note:
Binary
transfers
are
not
allowed
from
the
low-speed
paper
tape
reader.
3-7
3.2
RENAMING
,FILES
The
RENAME
switch
is
provided
to
allow
the
user
a
means
of
changing
the
name
of
a
file.
The
general
form
of
the
command
is:
new
filename<old
filename
with
IRE
on
either
side
of
the
left
angle
bracket.
If
no
device
is
specified,
the
system
disk
is
assumed;
for
example:
!MAIN.OBJ/RE<TESTX.OBJ
changes
the
name
of
the
system
disk
file
TESTX.OBJ
to
MAIN.OBJ.
When
renaming,
it
is
mandatory
that
the
same
device
be
used
on
both
sides
of
the
left
angle
bracket.
The
following
is
allowed:
!DT:FILE1<FILE2/RE
The
device
for
FILE2
is
assumed
to
be
the
DECtape.
The
same
com-
mand
could
be
written
as:
!DT:FILE1<DT:FILE2/RE
If
the
IRE
switch
is
omitted
in
the
command
string,
the
opera-
tion
performed
is
a
copy
operation
which
duplicates
the
input
file
on
the
same
device,
but
under
another
name.
In
this
case
two
copies
of
the
file
would
exist
on
the
same
device.
For
example:
!DT:FIL;El<DT:FILE2
3-8
copies
FILE2
into
FILEI,
both
on
DECtape
unit~.
No
error
message
is
given
since
the
command
is
for
a
valid
transfer
operation.
Only
one
file
at
a
time
can
be
renamed.
3.3
DELETING
FILES
The
DELETE
switch
is
provided
to
allow
the
user
a
means
of
deleting
one
or
more
files.
The
simple
form
of
the
command
consists
of
a
file
designator
followed
by
the
/DE
switch.
For
example:
ftDT:MAIN.LDA/DE
which
deletes
the
file
MAIN.LDA
from
DECtape
unit
~.
Several
files
can
be
deleted
by
specifying
a
sequence
of
filenames
before
the
DELETE
switch.
For
example:
ftAB,DT:CD,DTl:EF.OBJ/DE
deletes
three
files
on
three
different
devices.
The
DELETE
switch
supports
the
asterisk
in
the
filename
and/or
extension
fields
of
the
file
specifications.
The
asterisk
is
interpreted
as
"all",
as
in
*.PAL
meaning
all
files
under
the
current
VIC
with
an
extension
of
.PAL.
For
example:
ftDTl:*.LDA/DE
deletes
all
files
with
the
extension
.LDA
from
DECtape
unit
1.
ft*. * /DE
deletes
all
files
under
the
current
VIC
from
the
system
disk.
Files
can
be
deleted
from
cassette
tape
without
destroying
adjacent
files.
For
example:
#CTI:FILE.MAC/DE
3-9
TO
delete
all
files
from
a
DECtape,
magtape,
or
cassette
tape,
it
is
reconunended
that
the
Zero
switch
be
used,
since
that
operation
is
much
faster
(see
Sections
4.4.1
and
5.4).
3.4
INSPECTING
FILES
The
INSPECT
switch
(lIN)
is
an
auxiliary
switch
which
instructs
PIP
to
type
out
the
name
of
each
eligible
file,
followed
by
a
question
mark,
before
executing
the
main
operation.
The
user
can
then
perform
the
operation
on
that
particular
file,
by
typing
a Y
(for
yes)
followed
by
the
RETURN
key;
or
he
may
bypass
the
file
by
simply
typing
the
RE'I'URN
key.
In
general,
lIN
is
used
with
file
transfers
and
with
the
ISu,
IDE
and
IRE
switches
and
is
particularly
useful
when
used
in
conjunc-
tion
with
asterisk-type
commands.
For
example:
!.*.*/DE/IN
which
allows
the
user
to
edit
(accept
or
reject)
the
contents
of
a
whole
directory.
To
continue:
ABC.OBJ?
Y
DEF.PAL?
etc.
;Delete
this
file
;00
not
delete
this
file
In
the
examples
above,
typing
Y
at
the
console
caused
the
deletion
of
file
ABC.OBJ.
PIP
listed
another
filename;
the
RETURN
key
was
typed,
file
is
left
intact;
PIP
lists
another
file,
etc.
3.5
SUPERSEDE OPERATION
When
used
on
the
input
side
of
a
transfer
conunand,
the
SUPERSEDE
switch
(/SU)
causes
any
input
file
having
the
same
name
as
a
file
on
the
output
device
to
replace
that
output
file.
Input
files
not
existing
on
the
output
device
will
simply
be
transferred
as
usual.
The
ISU
switch
will
not
delete
an
output
file
if
the
input
file
to
3-10
replace
it
is
not
present
on
the
input
device.
In
this
instance,
an
S
error
condition
will
be
given
and
PIP
will
proceed
to
transfer
any
remaining
files.
The
command
is
normally
used
in
association
with
specific
filenames
specified
only
on
the
input
side
of
the
command
string:
!dev:<devl:A,B,C/SU
or
for
asterisk-type
transfers
#dev:<devl:*.*/SU
If
the
filename
specification
appears
in
the
output
side
of
the
command
string
and
the
file
already
exists
on
the
output
device,
the
transfer
is
not
made
and
an
S257
error
occurs,
e.g.,
the
command
dev:'A<devl:A/SU.
In
addition
to
its
use
as
a
stand-alone
command,
one
can
evoke
a
supersede
mode
with
a
/SU:ON
command
which
will
remain
in
effect
until
the
mode
is
turned
off
with
a
/SU:OFF
or
until
the
program
is
killed
through
a
return
to
the
Monitor.
The
Monitor's
BEGIN
command
does
not
affect
the
mode.
Enabling
the
mode
in
this
way
obviates
entering
an
/SU
switch
following
each
command.
3.6
FILE
PROTECTION
CODES
The
PROTECT
switch
is
provided
to
allow
the
user
a
means
of
changing
the
protection
of
a
file.
It
is
not
applicable
to
cassette
tape.
The
protection
code
is
specified
as
an
octal
value
argument
to
the
switch
and
is
treated
as
three
fields
corresponding
to
owner,
user
group,
and
all
others.
Each
field
is
assigned
an
octal
digit
as
described
in
Figure
3-1.
The
general
form
of
this
command
is:
dev:filnam.ext/PR:value
such
as:
!FILE3/
PR
:355
which
changes
the
protection
code
of
FILE3
to
355.
The
protection
switch
works
for
DECtape
and
disk:
3-11
!DT0:FILE4/PR:155
as
well
as:
!DKl:ABC.DAT/PR:300
r------------~------,---------------------------------------------------
_____________________
__
Owner:
User
Group
Code
~
1
2
or
3
4
or
5
6
or
7
l216151413121ll~
'---....--J
~~
Owner
User
Group
All
Others
Bit
6 = 1 =
Owner
cannot
write
on
or
delete
the
file.
This
is
a
safeguard
to
prevent
inadvertent
deletion
or
over-writing.
Bit
7 = 1 =
Protect
the
file
from
automatic
deletion
on
FINISH
(not
implemented)
and
all
others:
Function
Delete
Write
Read
Run
yes
yes
yes yes
no
yes yes
yes
no
no
yes
yes
no
no
no
yes
no
no
no
no
Yes
indicates
-that
the
operation
is
allowed.
For
example,
if
a
file
belongs
to
user
[23,10],
a
protection
code
of
3
will
allow
user
[12,4]
to
read
or
run
but
not
delete
or
write
on
it.
No
indicates
that
the
operation
is
not
allowed.
Figure
3-1.
File
Protection
Codes
3-12
3.7
ALLOCATING A
CONTIGUOUS
FILE
Whenever
it
is
necessary
to
load
a
contiguous
file
from
paper
tape,
a
blank,
contiguous
file
is
first
created.
The
ALLOCATE
switch
provides
a
means
of
creating
a
blank,
contiguous
file.
This
option
requires
a
filename
and
a
decimal
integer
value
(being
the
number
of
64-word
segments
of
storage
to
be
allocated).
For
example:
!DF:FILE/AL:10
allocates
640
contiguous
words
of
file
storage
on
the
RFll
disk.
A
subsequent
PIP
command:
#FILE<PR:
causes
the
paper
tape
to
be
read
into
the
contiguous
file
previously
created.
The
ALLOCATE
switch
can
be
used
to
create
a
contiguous
file
on
disk
or
DECtape.
Note
that
the
segments
allocated
are
always
64
words
and
do
not
depend
upon
the
block
size
of
the
device.
For
example,
!DK0:FILE/AL:100
creates
a
blank
contiguous
file
named
FILE
on
device
DK~.
Since
an
RKll
device
contains
256
words
per
block,
the
allocated
file
contains
25
blocks,
each
256
words
in
length.
Each
block
contains
four
64-word
file
segments.
The
number
25
followed
by
C
is
shown
as
the
number
blocks
of
the
file
on
the
full
directory
listing
for
the
device
on
which
the
contiguous
file
was
created.
For
example:
!DK0:FILE/DI
DIRECTORY
DK0:
[200,200J
24-AUG-72
FILE
25C
24-AUG-72 <233>
3-13
Whenever
it
is
necessary
to
create
an
empty,
contiguous
file,
the
characters
:E
are
appended
to
the
command
string.
For
example:
!DF:FILE1/AL:l~:E
allocates
640
contiguous
words
of
file
storage
on
the
RFll
disk
as
normally.
However,
pointers
are
set
in
the
UFO
file
entry
such
that
the
space
is
apprently
empty.
A
file
allocated
in
this
manner
can
accept
partial
sequential
output
(through
a
Monitor
.OPENC
call).
The
pointers
are
updated
to
reflect
the
end
of
the
actual
data
entered
in
part
of
the
allocated
space.
The
same
file
can
subse-
quently
be
extended
(through
a
Monitor
.OPENE
call)
within
the:
un-
filled,
allocated
space.
3-14
CHAPTER
4
DIRECTORY
MANIPULATION
A
significant
number
of
PIP
features
center
around
the
manipu-
lation
of
files
within
directories
and
of
the
directories
themselves.
4.1
ENTERING
USER
IDENTIFICATION
INTO
THE
MASTER
FILE
DIRECTORY
The
User
Identification
Code (UIC)
must
appear
in
the
Master
File
Directory
(MFD)
before
a
user
is
able
to
create
his
own
files
on
the
disk
or
DECtape.
This
code
is
generally
entered
into
the
MFD
by
using
the
ENTER
switch
in
PIP,
although
the
DOS
system
'building
program
creates
a few
fundamental
User
File
Directories
(UFD's).
Refer
to
the
DOS/BATCH
System
Manager's
Guide
for
further
details.
The
UIC
of
the
current
user
of
the
system
is
passed
to
the
Opera-
ting
System
by
the
LOGIN
command.
For
example:
$LOGIN
11,11
sets
the
current
UIC
to
[11,11].
In
using
the
ENTER
switch,
the
UIC
of
the
current
user
is
obtained
from
the
system
and
written
into
a
spare
slot
in
the
MFD.
The recommended
sequence
is
then:
$LOGIN
uie
$RUN
PIP
PIP
Vxxx
tLfEN
The
LOGIN
UIC
code
is
now
a
valid
UIC
on
the
system
disk.
In
order
to
enter
a
UIC
onto
the
system
disk
other
than
the
one
used
in
the
LOGIN
command,
the
UIC
can
be
specified
as
follows:
PJ
200,213
J/EN
which
enters
the
UIC[2~~,2l3]
onto
the
system
disk.
If
no
spare
slots
exist
in
the
MFD1,
PIP
prints
a
fatal
error
message,
and
no
attempt
is
made
to
extend
the
MFD.
lSee
Section
C.2
for
the
number
of
UIC
slots
available
on
the
UFD.
4-1
This
procedure
is
not
always
necessary
for
DECtapes
because
the
ZERO
switch
enters
the
UIC
of
the
current
user
when
the
directory
is
initialized
(see
section
4.4.1).
If
a
user
other
than
the
one
originally
zeroing
the
DECtape
wishes
to
access
files
on
the
tape,
he
must
enter
his
UIC
on
the
DECtape
or
explicitly
reference
the
UIC
field
of
the
original
user
during
each
reference.
For
example,
if
the
DECtape
on
unit
I
had
been
originally
zeroed
and
filled
by
UIC
[5~,5~],
user
UIC
[2~~,2~~]
could
reference
those
files
by
logging
in
under
[2~~,2~~]
and
giving
the
following
command:
!DTl:
lEN
In
general,
then,
an
ENTER
operation
performs
one
of
two
services:
for
DECtapes
it
allows
any
user
to
access
all
files
on
the
DEC
tape
as
though
he
had
initialized
the
DECtape;
and
on
the
disk
it
creates
a
UFD
for
the
current
(logged
in)
UIC
(or
the
UIC
specified),
allowing
that
user
to
store
files
on
the
system
disk
with
whatever
protection
is
desired.
4.2
DIRECTORY
LISTINGS
A
listing
of
the
directory
of
all
or
certain
selective
files
on
any
file
structured
device
can
be
printed
on
the
teleprinter
or
line
printer;
(PIP
assumes
the
teleprinter
unless
another
device
is
specified
in
the
command
string).
The
information
listed
in
a
directory
is
a
subset
of
all
the
information
in
the
UFD
entry
for
each
file.
4.2.1
Full
Directories
A
full
directory
(/DI)
l·isting
contains:
two
title
lines
to
identify
the
device,
UIC,
and
the
data
which
are
followed
by
all
filenames
and
extensions;
the
number
of
blocks
per
file
(followed
by
a C
if
the
file
is
contiguous),
file
creation
date,
and
file
protection
code
(enclosed
within
angle
brackets);
plus
the
total
number
of
blocks
and
file
for
that
UIC.
For
example:
4-2
#/DI
DIRECTORY
DF0:
[50,50J
22-FEB-72
MONLIB
508c
00-XXX-70 < 377>
LINKll.OVR
72C
22-FEB-72 <233>
PIP
.LDA
77 22-FEB-72 <233>
LINKOB.LDA
107 22-FEB-72 <233>
LINKll.LDA 63 22-FEB-72 <233>
EDITll.LDA 56 22-FEB-72 <233>
PALIIR.OVR
40C
22-FEB-72 <233>
PALOB
.LDA
107 22-FEB-72 <233>
ODTIIR.OBJ 53 22-FEB-72 <233>
PALIIR.LDA
65
22-FEB-72 <233>
FORTRN
90 22-FEB-72 <233>
LIBRll.LDA
35
22-FEB-72 <233>
FORTRN.OVR
204c
22-FEB-72 <233>
FORCOM.DGN
68c
22-FEB-72 <233>
FORRUN.DGN
40C
22-FEB-72 <233>
FORLIB.OBJ 604 22-FEB-72 <233>
EAELIB.OBJ 604 22-FEB-72 <233>
ADD4B
.PAL 66 22-FEB-72 <233>
DEFIN
.OBJ 5 22-FEB-72 <233>
DVB07
.PAL 33 22-FEB-72 <233>
PALSYM.PAL
85 22-FEB-72 <233>
FORTOV.12K
300C 22-FEB-72 <233>
FORTRN.12K
118 22-FEB-72 <233>
LINKOB.OBJ
154 22-FEB-72 <233>
LINK11.0BJ 94 22-FEB-72 <233>
EDIT11.0BJ 85 22-FEB-72 <233>
PALOB
.OBJ 138 22-FEB-72 <233>
PALSYM.OBJ
17 22-FEB-72 <233>
PALIIR.OBJ 77 22-FEB-72 <233>
TOTL
BLKS:
3965
TOTL
FILES:
29
Notice
that
the
system
device
(DF~:
in
this
case)
was
assumed
and
the
user
was
logged
in
under
UIC[5~,5~].
Whenever
a
file
is
transferred
onto
disk,
,cassette
tape,
or
DECtape,
the
date
in
the
directory
reflects
the
date
on
which
the
transfer
took
place,
~
the
date
on
which
the
file
was
created.
The
full
directories
of
multiple
devices
can
be
obtained:
4-3
!DF:,DTl:/DI
DIRECTORY
DF0:
;~4-JUL-71
fllONLIB
LINKll.0VR
PIP
.LDA
ODTIIR.OBJ
F'ORTRN.OVL
FORTEN
LINKOB.LDA
LINK
.LDA
EDIT
.LDA
PALOB
.LDA
PAL
.LDA
PAL11R.CVR
LIBR
.LDA
FORCOM.DGN
EAELIB.LDA
EAELIB.OBJ
TOTAL
BLKS:
TOTL
FILES:
D-IREC1'ORY
DTl:
24-JUL-71
FORLIB.OBJ
EAELIB.OBJ
IOL01 .OBJ
DEFIN
.OBJ
DVTB06.PAL
508c
36c
70
51
152C
118
96
58
56
107
65
40C
41
112C
555
555
2620
16
135
136
1
1
7
FREE
BLKS:
282
FREE
FILES: 51
[50,50J
[l,lJ
00-xXX-70
17-JUL-71
17-JUL-7l
17-JUL-7l
24-JUL-7l
24-JUL-7l
17-JUL-7l
17-JUL-7l
17-JUL-7l
17-JUL-71
17-JUL-7l
17-JUL-7l
17-JUL-7l
17-JUL-7l
19-JUL-7l
19-JUL-7l
01-JUL-7l
01-JUL-7l
01-JUL-7l
01-JUL-7l
01-JUL-7l
<377>
<233>
<233>
<233>
<233>
<233>
<233>
<233>
<233>
<233>
<233>
<233>
<233>
<00 >
<233>
<233>
<233>
<233>
<233>
<233>
<233>
When a
full
DECtape
or
cassette
tape
directory
is
obtained,
the
li.sting
is
concluded
with
the
total
number
of
free
blocks
and
files,
whereas
with
a
disk
the
number
of
used
blocks
and
files.
are
reported.
The
full
directory
listing
can
be
limited
to
produce
a
partial
list
of
specified
files
on
one
or
more
devices.
The
following
example
illustrates
the
use
of
the
asterisk
to
list
only
those
files
with
the
extensions
specified
on
the
two
devices
specified:
4-4
!DF:*.OVR,*.OBJ,DTl:*.PAL/DI
DF.0:
LINKll.OVR 36c
17-JUL-71
<233>
PALIIR.OVR
4.0c
17-JUL-71
<233>
ODTIIR.OBJ 51
17-JUL-71
<233>
EAELIB.OBJ 555
19-JUL-71
<233>
DT1:
DVTB.06.PAL
7 .01-JUL-71 <233>
Notice
that
the
UIC,
date,
and
number
of
blocks
and
files
for
that
UIC
are
not
reported
in
partial
/DI
listings.
Directory
information
about
a
particular
file
can
be
obtained
by
specifying
the
filename
and
extension
with
the
/OI
switch.
For
example:
!FTN.0.0.0.0VL/DI
DK.0:
FTN.0.0.0.0VL
l.0C
15-JUL-71
-<
233 >
This
obtains
all
information
about
FTN~~~.OVL
if
it
is
in
the
DK~:
directory.
(If
the
file
is
not
in
the
directory,
there
is
no
listing,
and
no
error
message.)
Any
UIC
directory
on
any
device
can
be
listed
by
specifying
that
UIC
in
the
command
to
PIP.
For
example,
if
a
user
is
logged
in
under
UIC
2~~,2~~,
he
can
give
the
following
command
(the
results
are
shown
below)
:
!DK1:[5.0,5.0J/DI
4-5
DIRECTORY.OK1:
[50,50J
21-JUL-71
FORCorl]
.
DGN
27C
01-JUL-71
<233>
FORTHN.08K
23
01-JUL-71
<233>
IVK08K.LDA 27
01-JUL-71
<233>
OVL18K.LDA
26
01-JUL-71
<233>
OVL28K.LDA
23
01-JUL-71
<233>
OVL38K.LDA
26
01-JUL-71
<233>
OVL48K.LDA
28
01-JUL-71
<233>
OVL58K.LDA
28
01-JUL-71
<233>
OVLC8K.LDA
25
01-JUL-71
<233>
FORTRN.12K 23
01-JUL-71
<233>
OVL0
.LDA
27
01-JUL-71
<233>
OVL1
.LDA
26
01-JUL-71
<233>
OVL2
.LDA
23
01-JUL-71
<233>
OVL3
.LDA
26
01-JUL-71
<233>
OVL4
.LDA
28
01-JUL-71
<233>
OVL5
.LDA
28
01-JUL-71
<233>
OVL6
.LDA
25
01-JUL-71
<233>
TOTL
ELKS:
123
'l'OTL
FILES:
39
If
the
user
requests
information
on
any
particular
file
or
uses
the
asterisk
feature
where
no
such
file
exists,
no
error
message
is
given.
printed.
The
directory
is
considered
blank;
and
a
blank
line
is
In
the
example
below
there
is
no
*.OVR
file
on
DT.0:
!DF:*.OVR,DT0:*.OVR/DI
DF0:
LINK11.0VR
PAL11R.OVR
DT0:
36c
40C
21-JUL-71
21-JUL-71
<233>
<233>
4.2.2
Brief
Directory
Listings
The
BRIEF
DIRECTORY
(jBR)
switch
can
be
used
to
list
only
the
device
name,
filenames,
and
extensions.
The
asterisk
and
specific
filenames
can
be
used
with
the
BRIEF DIRECTORY
switch
to
obtain
partial
brief
directories.
4-6
The
following
PIP
example
demonstrates
the
correspondence
between
/DI
and
/BR
directory
listings.
!*.OVL/DI
DK.0:
FTN.0.0.0.0VL
FTN.0.01.0VL
FTN.0.02.0VL
FTN.0.03.0VL
FTN.0.04.0VL
FTN.0.05.0VL
FTN.0.06.oVL
!*.OVL/BR
DK.0:
FTN.0.0.0.0VL
FTN.0.01.0VL
FTN.0.02.0VL
FTN.0.03.0VL
FTN.0.04.0VL
FTN.0.05.0VL
FTN.0.06.oVL
1.0.0
9C
7C
9C
l.0C
llC
8c
15-JUL-71
l5-JUL-71
15-JUL-71
15-JUL-71
15-JUL-71
15-JUL-71
15-JUL-71
<233>
<233>
<233>
<233>
<233>
<233>
<233>
An
example
of
the
/BR
switch
with
the
system
device
assumed
is
shown
below:
tt/BR
DF.0:
MONLIB
LINKll.0VR
PIP
.LDA
FCL
.PAL
PALIIR.OVR
PAL
LINK
Other
examples
of
/BR
switch
usage
are
shown
below:
!FOR.E/BR
DF.0:
FOR
.E
4-7
The
asterisk
(*)
feature
for
filenames
and
extensions
works
for
directory
listings,
both
full
and
brief
form.
For
example,
the
command:
ff:...*.PAL/BR
gives
a
brief
directory
listing
for
all
files
on
the
user's
disk
area
with
an
extension
of
.PAL.
The
asterisk
can
appear
in
the
filename
field,
the
extension
field,
or
both.
In
addition,
groups
of
file
specifiers
can
be
arranged
to
provide
sequential
listings,
as
in:
ff:...
DT
.0:*.MAC,DF:FORTRN.*/DI
The
asterisk
feature
can
be
used
in
the
UIC
field
when
obtaining
directory
listings.
ff:...LP:<DK:[*,*]/DI
All
directories
on
RKll
unit
,
are
listed
on
the
line
printer.
ff:...
LP
:<DF:[*,200]/DI
A
listing
is
produced
of
all
directories
associated
with
user
number
2~',
in
every
project.
ff:...LP:<DK:*.MAC[*,*]/DI
A
directory
of
all
files
with
extension
.MAC,
on
RKII
unit
~,
is
produced.
4-8
4.3
FREE
BLOCKS
Since
a
full
directory
listing
of
a
system
disk
provides
the
user
only
with
a
summary
of
the
number
of
blocks
used
by
his
current
UIC,
the
/FR
switch
is
available
for
determining
the
number
of
free
blocks
remaining.
For
example:
!l./FR
DF0:
FREE
BLKS:
5513
This
switch
can
be
used
with
any
file-structured
device,
but
is
generally
only
necessary
with
disk,
as
the
information
is
provided
automatically
with
a
DECtape.
Further
examples
of
the
/FR
switch
follow:
tt/FR
DK0:
FREE
BLKS:
4113
tt.DF:
,
DT0
: /FR
DF0:
FREE
BLKS:
3243
DT0:
FREE
BLKS:
282
4.4
DECTAPE
AND
RKll
DISK
INITIALIZATION
(See
Chapter
5
for
magtape
initialization
and
Chapter
6
for
cassette
initialization.)
4.4.1
DECtape
In
order
to
initialize
a
new
DEC
tape
with
the
basic
file
structure
information
required
by
the
DOS/BATCH
Monitor,
the
ZERO
switch
is
provided.
4-9
The
ZERO
switch
causes
PIP
to
create
on
the
DECtape
specified
the
permanent
bit
maps,
the
file
bit
maps,
the
MFD,
and
a
UFD
for
the
UIC
currently
running
on
the
System.
The
ZERO
switch
can
be
used
either
by
itself,
as
in:
!DT0:/ZE
or
in
combination
with
other
actions,
as
in:
!DT0:0NE/ZE<DT1:A,B,C
The
latter
command
zeroes
DT~:
first,
then
creates
file
ONE
on
DT~:
by
merging
files
A,
B,
and
C
from
DECtape
unit
1.
When
used
in
combination
with
other
actions,
ZERO
is
perfor.med
before
any
other
implied
actions.
The
/ZE
switch
can
be
used
to
zero
only
one
DEC
tape
per
PIP
comma~d
string.
In
order
to
zero
two
DECtapes,
proceed
as
follows:
#DT:/ZE
!DT1:/ZE
4.4.2
RKII
Disk
Before
initializing
an
RKII
cartridge
with
the
ZERO
switch,
en-
sure
that
the
cartridge
has
been
formatted
using
either
the
RKII
diagnostic
program
(MAINDEC-ll-D5HA-PB2)
or
the
SYSLOD
System
Program.
Consult
the
system
administrator
for
local
procedures.
The
following
actions
occur
during
cartridge
initialization.
1.
The
entire
disk
cartridge
is
zeroed;
2.
The
first
and
second
MFD
blocks
are
written;
3.
The
UIC
of
the
current
user
(and
only
this
UIC)
is
entered
in
the
MFDi
then
4.
Bit
map
blocks
are
written
A
RKII
disk
is
initialized
by
typing:
!DKn:/ZE
where
n
is
the
octal
number
of
the
appropriate
cartridge
(or
omitted
4-10
if
OK~
is
meant).
PIP
responds
by
printing:
CONFIRM:
to
which
type
either
H
(for
high-density)
or
L
(for
low-density)
followed
by
the
RETURN
key.
Should
the
user
decide
not
to
initialize
the
disk,
he
types
the
SPACE
bar
before
typing
the
RETURN
key.
High-density
cartridges
are
marked
22~~
BPI,
and
low-density
cartridges
are
marked
ll~~
BPI.
When
the
disk
has
been
initialized
(there
is
a
noticeable
pause)
PIP
again
prints
the
number
sign
(#)
to
indicate
readiness
to
accept
another
command.
4.5
RECOVERING
FILES
There
are
a
number
of
infrequent
ways
in
which
a
file
can
be
left
in
a
state
which
makes
it
inaccessible
for
subsequent
processing.
For
example,
if
a
file
is
open
and
a
system
crash
(hardware
or
soft-
ware)
occurs
causing
the
Monitor
to
be
reloaded,
the
file
will
likely
be
left
in
an
inaccessible
state.
Files
which
are
declared
inaccessible
by
the
Monitor
will
likely
have
up
to
three
things
wrong
with
them:
1.
The
LOCK
bit
in
the
UFO
entry
for
this
file
will
be
set.
2.
The
USAGE
COUNT
in
the
UFO
entry
for
this
file
will
be
invalid.
3.
Some
blocks
allocated
for
this
file
may
not
have
the
proper
bits
set
in
the
permanent
bit
map.
PIP
provides
a
partial
solution
to
this
problem
with
the
UNLOCK
switch.
The
function
of
this
switch
is
to
restore
the
LOCK
and
USAGE
COUNT
fields
so
that
the
file
can
be
read.
It
does
not
make
an
attempt
to
set
bits
in
the
bit
map
for
the
blocks.
The
sequence
for
recovery
is
to
use
the
UNLOCK
switch,
such
as:
.RUN
PIP
PIP
Vxxx
!DF:FILE.OLO/UN
which
allows
the
file
to
be
accessed.
4-11
Then,
BEFORE WRITING
ANY
NEW
DATA
ON
THE
DISK,
copy
the
file
(if
you
want
it)
to
another
device
and
DELETE
IT
from
the
disk.
#DT:<FILE
!FILE/DE
Copy,
then
delete
ALL
FILES
WHICH
WERE
OPEN
WHEN
THE
CRASH
OCCURRED.
You
may
then
use
the
disk
safely.
4-12
CHAPTER 5
MAGTAPE
OPERATION
5.1
GENERAL
MAGTAPE
INFORMATION
Magnetic
tape
is
supported
by
PIP
for
following
operations:
a.
Directory
listings;
#MTl:/DI
!MT0:/BR
b.
File
transfer
operations;
(a
magtape
reel
must
be
initialized
before
any
files
are
transferred
to
the
reel
for
the
first
time.
See
Section
5.4
for
the
initializati~q
procedure).
#MTl:FILE<DT2:ABC
!MT:MERGK<ABC,DT0:
FACT
,MTl:DATA
c.'
Magtape
initialization
(see
Section
5.4);
tLMTl:/ZE
d.
Rewind,
Rewind
Suppression,
and
Rewind
and
Unload
(see
Section
5.2
and
5.3).
Transfer
and
directory
operations
include
all
asterisk
features
used
for
other
file-structured
devices.
For
example,
it
is
possible
to
type:
tLMTl:[*,*J/DI
or
tLMTl:[*,*J/BR
This
allows
the
user
to
obtain
a
complete
listing
of
all
files
on
the
specified
magtape(s).
When
this
option
is
used,
the
UIC
speci-
fication
is
printed
as
part
of
the
file
information.
For
example:
tL
MT
0:[*,*],MTl:[*,*J/DI
5-1
5.2
REWIND
The
REWIND
switch
is
applicable
to
magtape
units
(MTn)
and
cassette
drives
(CTn)
only,
and
controls
rewind
operations
for
one
or
more
specified
units.
The
specified
unit(s)
can
still
be
addressed
after
use
of
the
REWIND
switch.
The
specifications
/RW
and
/RW:YES
cause
the
specified
unit(s)
to
be
rewound;
the
specification
/RW:NO
prevents
rewinding
of
the
specified
unit(s).
EXAMPLES:
!MTI:/RW
causes
magtape
unit
1
to
be
rewound
on
its
original
reel.
!DK¢.: <MT2:
*.
* /RW:
NO
causes
all
files
under
the
current
UIC
on
magtape
unit
2
to
be
transferred
to
disk
¢
without
rewinding
magtape
unit
2
between
file
transfers.
iDK¢:<MTl:FILE.ONE/RW:YES
causes
magtape
unit
1
to
be
rewound
before
and
after
transferring
FILE.ONE
to
disk
¢.
!MT~:/RW:NO<MTI:*.*/RW:NO,MT2:*.MAC/RW:NO
causes
the
following
to
take
place,
in
order:
(1)
starting
at
the
current
position
of
mag-
tape
unit
1,
all
files
under
the
current
UIC
on
magtape
unit
I
are
transferred
to
magtape
unit
¢
without
rewinding
between
file
trans-
fers;
then
(2)
starting
at
the
current
posi-
tion
of
magtape
unit
2,
all
files
under
the
current
OIC
with
extension
.MAC
on
magtape
unit
2
are
transferred
to
magtape
unit
¢
with-
out
rewinding
between
file
transfers.
If
the
REWIND
switch
is
not
specified
for
an
operation,
a
de-
fault
value
of
/RW:YES
is
assumed.
5-2
5.3
REWIND/UNLOAD
The
REWIND/UNLOAD
switch
is
applicable
only
to
tape
units.
This
switch
causes
the
tape
to
be
wound
back
on
its
original
reel
and
the
tape
unit
to
be
switched
off-line.
Following
this
option
the
tape
unit(s)
cannot
be
addressed
for
further
processing.
For
example:
!MT:/RU
or
!MT2:,
MT
3:/
RU
5.4
ZERO
(INITIALIZATION)
It
is
mandatory
that
a
magtape
be
zeroed
bef·ore
use.
The
/ZE
switch
writes
two
end-of-file
marks
on
the
tape
so
that
it
can
be
handled
correctly
by
the
System
Monitor.
For
example:
!MT2:/ZE
5.5
MAGNETIC
TAPE
FORMAT
All
files
on
magnetic
tape
have
the
general
format,
exclusive
of
data
format,
as
shown
in
Figure
5-1.
Any
file
on
the
tape
may
be
retrieved
by
name.
5-3
LOAD
POINT
OR
EOF
__
---+
RECORD
1
RECORD
2
RECORD
3
RECORD
n-l
RECORD
n
Figure
5-1
FILE
LABEL
7
words
DATA
256
words
..
DATA
~
256
words
j
·
·
·
DATA
}
256
words
EOF
Magtape
General
Format
5-4
CHAPTER
6
CASSETTE
TAPE
OPERATION
6.1
GENERAL
CASSETTE TAPE INFORMATION
Cassette
tape
is
suppored
by
PIP
for
the
following
operations:
a.
Directory
Listings;
!CT¢:/BR
!CT:/DI
b.
File
Transfer
Operations
(a
cassette
cartridge
must
be
initialized
before
any
files
are
transferred
to
the
cartridge
for
the
first
time.
Refer
to
section
6.3
for
the
initialization
procedure);
#CT: SOURCE.HAC<DK:
MACRO.
MAC
!CT:MERGE.MAC<CTl:FILEl.MAC,DKl:FILE2.MAC
c.
Cassette
Tape
Initialization
(Refer
to
section
6.3);
!CT:/ZE
d.
Rewind
Specifications
(Refer
to
section
6.2);
#CT:/RW
ICT:/RW:NO<CTl:*.*/RW:NO
e.
Read-after-Write
Verification
(Refer
to
section
6.5).
!CT:/VW<CTl:FILE.MAC
The
transfer
and
directory
operations
include
all
asterisk
features
used
for
other
file-structured
devices.
This
allows
the
user
to
obtain
a
complete
listing
of
all
files
on
the
specified
cassette.
6.2
REWIND
The
REWIND
switch
is
applicable
only
to
cassette
(CTn)
and
mag-
tape
(HTn)
drives.
This
switch
causes
the
tape
to
be
rewound
back
onto
its
original
reel.
Following
this
operation,
the
cassette
unit(s)
still
can
be
addressed.
The
following
are
examples.
#CTl:/RW)
!CT~:
,MTl:
/Rw)
The
REWIND
switch
can
be
used
to
explicitly
enable
rewinds
during
the
specified
cassette
operation.
The
following
example
rewinds
CTI
before
seeking
the
file
specified
for
the
transfer
operation.
!DK~:<CTl:FILNAM.EXT/RW:YES)
6-1
The
REWIND
switch
also
can
be
used
to
suppress
rewinds
during
the
spec:ified
cassette
operation.
For
example,
!DK~:
<CTl:
*.
*/RW:NO)
transfers
all
files
onto
the
disk
without
rewinding
CTI.
6.3
ZERO
(INITIALIZATION)
It
is
mandatory
that
a
cassette
be
zeroed
before
use.
The
/ZE
switch
writes
a
sentinel
label
record
(i.e.,
logical
EaT)
on
the
tape
so
that
it
can
be
handled
correctly
by
the
System
Monitor.
The
following
example,
!CTl:/ZE
zeroes
(initializes)
CTI.
6.4
CASSETTE
TAPE
FORMAT
All
files
on
cassette
tape
have
the
general
format,
exclusive
of
data
format,
shown
in
Figure
6-1.
Any
file
on
the
tape
can
be
retrieved
by
name.
BOT
OR
EOF
RECORD
1
FILE
LABEL
16
words
RECORD
2
DATA
64
words
RECORD
3
DATA
64
words
.
RECORD
n-l
DATA
64
words
EOF
Figure
6-1
Cassette
General
Format
6.5
READ-AFTER-WRITE VERIFICATION
Throughout
the
transfer,
after
writing
each
record,
the
cassette
is
backspaced
and
the
record
is
read
and
verified
against
the
contents
of
the
user's
buffer.
Notification
of
verification
failures
are
printed
on
the
operator's
console
as
either
Il~~
or
F~76
error
diagnostics.
6-2
CHAPTER 7
ERROR
MESSAGES
As
a
system
program
under
the
DOS/BATCH
Operating
system,
error
messages
received
when
using
PIP
conform
to
the
standards
for
error
handling.
PIP's
error
messages
are
of
the
form:
Sxxx
n
where
Sxxx
indicates
a
system
program
error
number
and
n
is
one
octal
word
displaying
additional
information.
Error
messages
that
PIP
may
issue
are
listed
in
Table
7-1.
Consult
the
DOS/BATCH
Monitor
Programmer's
Reference
Manual
or
the
DOS/BATCH
Batch
User's
Guide
for
a
description
of
all
Monitor
error
messages.
7-1
ERROR
CODE
82,02
82,03
82,04
82,05
82,07
8231
8232
8233
8234
8235
8236
8237
824,0
8241
8242
8252
8257
826,0
Table
7-1
PIP
8ystem
Program
Error
Messages
ADDITIONAL
INFORMATION
Error
8tatus
Byte
Error
8tatus
Byte
File
Block
Error
Code
dev:file,ext.
MEANING
End
of
Data
(EOD)
or
device
error
on
.WRITE
or
. READ.
Illegal
switch,
or
too
many
switches,
or
illegal
switch
value,
switch
value
not
given
or
illegal
switch
in
output
field
Too
many
or
too
few
output
files
Too
many
or
too
few
input
files
EOD
or
device
error
on
.TRAN
Illegal
command,
file-structured
device
required
More
than
one
action
switch
(only
one
permitted)
8pecified
UIC
not
found
in
MFD
Null
filename
or
*
given
where
filename
required
No
files
found
in
UFD
Operation
applicable
to
DECtape
only
File
not
found
during
file
recovery
operation
No
space
for
file
allocate
MFD
is
full
Meaningless
command
(no
action
taken)
Filename
given
when
none
allowed
Illegal
file
operation.
For
example,
protect
code
does
not
allow
transfer
of
file;
UIC
different
from
login
UIC
thus
making
certain
"wild
card"
operations
illegal.
The
operation
in
question
is
not
performed.
8ame
device
needed
for
input
and
output
in
fast
copy
operation.
7-2
ERROR
CODE
S262
S263
S264
S265
Il~~
I354
F~76
Table
7-1
(cont'd)
ADDITIONAL
INFORMATION
File
Number
MEANING
Record
size
too
big
for
buffer.
File
record
sizes
do
not
agree
on
verify
/VE).
Conflict
in
standard
filename
extension
which
determines
mode
of
transfer.
Use
explicit
switches
to
resolve.
Operation
attempted
on
device
which
is
not
legal
for
non-privileged
user.
Hardware
Status
Single
verification
failure
on
cassette
tape.
Register
Content
Device
(RAD5~)
Illegal
response
to
CONFIRM;
when
attempting
to
zero
an
RKll
disk
cartridge.
Legal
re-
sponses
are:
H -
for
high
density
disks
(RK~3/~5)
L -
for
low
density
disk
(RK~2)
blank
-
to
cancel
the
request
Cassette
tape
encountered
enough
read-after-
write
failures
to
exhaust
the
retry
count.
7-3
Switch
Name
/AL
Allocate
/BR
Brief
Directory
/CO
Contiguous
/DE
/DI
/EN
/FA
/FB
/FC
Delete
Directory
Enter
Formatted
ASCII
Formatted
Binary
Fast
Copy
/FC/VE
Fast
Copy
and
Verify
/FR
Free
APPENDIX A
SUMMARIES
Example
!DF:FILE/AL:lfA
!DTfA:/BR
!DTfA: <ABC/CO
!DTfA:AD/CO<ABC,DEF
!MAIN/DE
!DTfA:ABC,DTl:DEF/DE
!DTfA:/DI
!DF:/EN
!LP:/FA<DTfA:ABC
!DTfA: <ABC/FB
!DTl:<DT2:/FC/VE
!DTl:/FR
A-I
Operation
640
(10
x
64)
contiguous
words
of
file
storage
is
allocated
on
disk.
List
all
filenames
and
exten-
sions
in
directory
for
DEC-
tape
fA
on
the
user's
teleprinter.
Transfer
file
ABC
as
contigu-
ous
file
from
system
disk
to
DECtape
~.
Merge
files
ABC
and
DEF
(on
system
disk)
as
one
contigu-
ous
file
on
DECtape
~.
Delete
file
MAIN
from
system
disk.
Delete
files
ABC
and
DEF
from
DECtapes
fA
and
1
respectively.
List
all
filenames,
extensions,
size,
creation
date,
and
pro-
tection
codes
in
directory
for
DECtape
fA
onto
the
user's
teleprinter
Enter
current
user's
UIC
in
MFD
on
the
specified
disk
(device)
Copy
file
ABC
from
DECtape
fA
to
line
printer
in
formatted
ASCII
mode.
Copy
file
ABC
from
system
disk
to
DECtape
fA
in
formatted
binary
mode.
Data
on
DEC
tape
#2
is
fast
copied
onto
DEC
tape
#1.
Data
on
DECtape
#2
is
fast
copied
and
verified
onto
DEC
tape
#1.
List
the
number
of
free
blocks
remaining
on
DEC
tape
unit
1.
Switch
Name
Example
!*
.*/DE/IN
/IN
Inspect
/PR
Protect
!ABC/PR:
355
/RE
Rename
!ABC/RE<DEF
!DT~:GHI/RE<DT~:JKL
/RU
/RW
/SU
/UA
/UB
fUN
/VE
/"t.lW
/ZE
Rewind
and
#MT1:/RU
Unload
Rewind
!MT1:/RW
Supersede
!dev:<dev1:A,B,C/SU
Unformatted
!LP:/UA<DT~:ABC
ASCII
Unformatted
!DT~:<ABC/UB
Binary
Unlock
!DF:FILE.OLD/UN
Verify
Verified
Write
Zero
!DT1:
<DT2:
/VE
#CT:VW<CTl:FILE.MAC
!DT~:/ZE
A-2
Operation
Used
in
conjunction
with
file
transfers
and
/SU,
JDE,
and
/RE
switches.
Allows
user
to
selectively
perform
the
primary
function.
(User
gives
y
to
per-
form
action
on
the
displayed
filt
or
types
the
RETURN
key
to
leave
file
intact.)
Change
protection
code
of
system
disk
file
ABC
to
355.
Rename
file
DEF
to
ABC.
Rename
DECtape
~
file
JKL
to
GHI.
Causes
the
tape
on
magtape
unit
#1
to
be
wound
back
on
its
reel
and
the
unit
to
be
switched
off-line.
Causes
the
tape
on
magtape
unit
#1
to
be
wound
back
on
its
reel.
The
unit
can
still
be
addressed.
Causes
files
on
the
input
side
(DEVl)
to
replace
files
of
the
same
name
which
may
already
be
on
the
output
device
(dev).
Copies
file
ABC
from
DECtape
~
to
line
printer
in
unformatted
ASCII
mode.
Copies
file
ABC
from
system
disk
to
DECtape
~
in
unformatted
bi-
nary
mode.
Unlocks
FILE.OLD
after
a
system
failure
so
that
FILE.OLD
can
be
accessed.
Data
on
DECtape
#1
and
DEC
tape
#2
are
compared
block-by-blocki
disagreements
are
shown
by
printing
block
and
word
numbers
at
the
console.
Verify
a
write
operation
by
reading
it
after
wri
ting
it.
Erases
all
files
from
directory
of
DECtape
~
by
initializing
the
file
structure.
Standard
Device
Specification
Device
CR:
CTn:
DC:
DF:
DKn.
:
DPn:
DTn:
KB:
LP:
MTn:
PP:
PR:
PT:
SY:
Card
Reader
Cassette
Tape,
n=~,l
Fixed
Head.
Disk,
RCll
Fixed
Head
Disk,
RFll
Cartridge,
RKll,
n=0-7
Cartridge,
RP11,
n=~,7
DEC
tape
,
unit
0-7
Keyboard
(teleprinter)
Line
Printer
Magnetic
tapes,
unit
=
0-7
High-speed
paper
tape
punch
High-speed
paper
tape
reader
Low-speed
(teleprinter)
paper
tape
reader/punch
System
Device
NOTE
The
device
specification,
SY,
is
used
to
designate
the
device
on
which
the
Resident
Monitor
and
system
software
are
resident.
A-3
Radix-50
Equiv.
Code
012620
01270
014570
014760
015270
015600
016040
042420
046600
052140
063200
063320
063440
n/a
(see
note
below
APPENDIX B
HELPFUL HINTS
There
are
a
few
things
which
are
obvious
to
experienced
DOS/BATCH
users,
but
the
beginner
often
has
to
learn
them
empirically.
This
section
is
meant
to
help
the
beginner
avoid
some
common
pitfalls.
1.
If
you
are
having
difficulty
running
PIP,
make
sure
that:
a.
You
are
logged
in,
b.
You
did
a KILL
command
after
running
the
last
program
prior
to
running
PIP.
c.
The
PIP
load
module
is
on
the
disk,
or,
d.
You
are
accessing
the
proper
UIC
field
on
the
DECtape,
if
attempting
to
run
from
DECtape,
i.e.,
you
should
be
logged
in
under
the
same
UIC
as
shown
on
the
directory
of
the
DECtape.
2.
If
you
are
having
difficulty
accessing
a
DECtape
file
which
you
are
positive
is
there,
you
are
probably
logged
in
under
a
different
UIC
than
appears
on
the
DECtape.
In
this
case,
either:
a.
Explicitly
specify
the
UIC
in
the
command
b.
FINISH
and
LOGIN
under
the
proper
UIC,
or,
c.
ENTER
your
UIC
on
the
DEC
tape
(see
Section
4.1).
3.
If
you
are
having
difficulty
transferring
to
the
line
printer,
make
sure
the
printer
is
on-line;
set
the
switch
to
ON
LINE.
4.
If
you
are
having
difficulty
reading
a
file
and
there
has
recently
been
a
software
or
hardware
crash,
read
Section
4.5,
Recovering
Files.
5.
If
you
continue
to
get
file
structure
errors
on
output
files,
you
are
probably
trying
to
create
a
file
which
already
exists.
The
System
does
not
allow
this,
so
delete
the
file
first
or
use
the
SUPERSEDE
(/SU)
switch.
B-1
6.
If
you
are
logged
in
for
the
very
first
time
and
cannot
create
any
files,
it
is
because
you
have
no
User
File
Directory
(UFD)
in
the
Master
File
Directory
(MFD). To
create
one,
log
in,
call
PIP
and
type:
!SY:/EN
and
you
are
all
set.
7.
If
you
cannot
write
anything
on
a
DECtape
even
though
the
WRITE
switch
is
on,
it
is
likely
that:
a.
The
DECtape
belongs
to
someone
else
and
he
does
not
want
you
to
write
on
it
accidentally,
or
b.
The
tape
has
not
been
certified.
If
the
DECtape
does
belong
to
someone
else,
you
may
still
write
on
it
by
using
the
ENTER
switch
to
put
your
UIC
in
the
directory
of
the
DECtape,
as
in:
!DT0:/EN
Uncertified
DECtapes
can
be
certified
using
a
diagnostic
program
(TCll
DEC
tape
Formatter
MAINDEC-II-YPTB-PB)
supplied
with
the
maintenance
programs.
8.
Use
of
the
/RW:NO
option
when
transferring
files
from
magtape
and
cassette
can
save
much
time
normally
lost
during
a
rewind
operation.
9.
If
experiencing
trouble
with
transfers
from
the
card
reader,
check
to
ensure
that
(1)
control
cards
are
compatible
with
the
card
reader
type,
and
(2)
end-of-
file
cards
are
compatible
with
the
current
version.
of
the
Monitor.
B-2
APPENDIX C
PROGRAMMING
CAUTIONS
C.l
ASTERISK FEATURE
Use
of
the
asterisk
feature
with
the
ICO
switch
in
a
merge
operation
only
obtains
the
first
of
the
asterisk-specified
input
files.
No
error
message
is
given.
If
the
user
attempts
to
transfer
a
series
of
files
(with
the
*)
in
which
one
has
a
protection
code
that
does
not
allow
transfer,
a
fatal
Monitor
error
will
result
when
PIP
attempts
to
transfer
that
file,
and
successive
files
designated
for
transfer
in
that
command
string
will
~
be
transferred.
If
a
file
appears
on
disk
or
DECtape
with
a
name
not
acceptable
to
the
CSI,
it
must
be
deleted
using
the
*
feature.
For
example:
ABC.
A (2
spaces
in
extension)
is
not
acceptable
and
should
be
deleted:
ABC.*/DE
The
above
works
unless
the
file
is
locked;
in
which
case
it
must
be
unlocked.
See
Section
4.5.
To
copy
files
from
one
device
to
another
using
the
*,
the
*
must
be
in
the
input
field
of
the
command
string.
For
example:
devl:<dev2:*.*
or
devl:<dev2:*.PAL
When
transferring
files,
the
*
cannot
be
specified
in
the
output
field
of
the
command
string;
it
will
create
a
file
with
the
extension
(space)
AB,
and
no
error
message
is
given.
C-l
C.2
UIC CAPACITY
ON
DISK DEVICES
The
maximum
number
of
UIC's
that
a
disk
device
directory
can
contain
is
dependent
upon
the
block
size
of
the
device
type.
The
maximum
numbers
are
shown
in
Table
C-l.
Disk
Device
Type
RCII
RFll
RKII
Table
C-l
UIC
Capacity
of
Disk
Devices
Block
Size
(in
words)
64
64
256
Maximum
Number
of
UIC's
15
15
63
(The
maximum
capacity
is
the
integer
result
of
subtracting
one
from
the
block
size
and
dividing
that
by
four.)
C.3
TRANSFER
OF
ASCII
CARDS
To
transfer
ASCII
cards
from
the
card
reader
to
disk
or
DECtape,
the
IFA
switch
must
be
used.
C.4
ALLOCATE
SWITCH
The
ALLOCATE
switch
(/AL:)
allows
the
user
to
create
a
blank
contiguous
file
and
specify
its
length.
Data
subsequently
can
be
transferred
from
a
nonfile-structured
device
to
the
blank
contigu-
ous
file.
Without
the
ALLOCATE
switch,
it
would
be
impossible
for
the
system
to
determine
the
size
of
the
file
from
a
nonfile-structured
input
device.
Data
can
also
be
transferred
from
a
file-structured
device
to
a
blank
contiguous
file.
However,
allocation
of
the
file
space
is
not
necessary
since
the
file-structured
input
device
con-
tains
the
necessary
size
information
in
its
directory.
(See
the
description
of
the
CONTIGUOUS
(/CO)
switch.)
C-2
A
error
message,
1-2
Abort
current
job,
1-3
Action
switches,
2-6, 2-7,
2-8
/AL
(Allocate)
/BR
(Brief
Directory
/DE
(Delete)
/DI
(Directory)
/EN
(Enter)
/FC
(Fast
Copy)
/FR
(Free
Blocks)
/PR
(Protect)
/RE
(Rename)
/RU
(Run)
/RW
(Rewind
and
Unload)
fUN
(Unformatted)
/VE
(Verify)
/ZE
(Zero)
Allocate,
1-1
Angle
bracket
«),
2-3,
3-8
ASCII
mode,
3-4
INDEX
command
(cont'd),
LOGIN,
2-5
string,
1-2,
2-2, 2-5,
3-6
interpreter,
2-1
Concatenating
files,
4-10
CONFIRM,
4-11
Confirmation,
2-6
Contiguous
file,
2-6,
3-5,
3-6,
3-13
creation,
3-13
CONTINUE
command,
1~2
CTRL/C
command,
1-3,
3-7
Control
function,
1-1
Controller,
2-2
Copy,
1-1,
3-1,
3-3
operation,
3-8
CSI,
2-1
Data
format,
5-4
Date,
4-3,
4-5
Asterisk,
2-3,
2-4,
3-4, 3-9,
4-4,
Default
I/O
device,
2-3
Delete,
1-1,
2-4
4-6
feature,
2-4, 2-6,
4-8,
5-1
type
command,
3-10
type
transfers,
3-11
Batcn
stream,
1-3
BEGIN
command,
1-3
Binary
mode,
3-4
Bit
maps,
4-10
Blank
contiguous
file,
3-13
Block,
3-
3,
4-2
size,
3-13
Brackets,
an
g 1
e,
2 - 3 , 3 - 8
square,
2-5
/BR
(brief
directory)
switch,
2-3,
4-6,
5-1
listing,
4-7,
4-8
C,
3-13
Carriage
return,
3-10
Cartridge,
4-10
high-density,
4-11
low-density,
4-11
$CHANGE
command,
1-4
Changing
filenames,
3-2,
3-8
/CO
(Copy)
switch,
3-5,
3-6
operation,
3-5
Code,
switch,
2-5
Colon,
2-5,
2-7
Combine,
3-3
Comma,
2-
3,
2-5
Command
format,
2-1
all
files,
3-10
switch
(/DE)
,
3-9
Device
specification,
2-2
default
input,
2-3
Directory,
1-1
listing
operations,
2-4,
4-7,
5-1
.MAC
extension
unit
~,
4-8
/OI
switch.
2-3,
4-5,
4-7,
5-1
Dollar
sign
character,
1-2,
1-3
Duplicate,
3-1
Edit,
3-10
function,
1-1
END!
3-7
END
PT
command,
3-7
End-of-file,
3-7,
5-3
/EN(ter)
switch,
4-1
Error,
1-2
X-I
messages,
7-1,
7-2
action
switch
allocate
CONFIRM
OECtape
file
record
size
file
recovery
EOD
illegal
command
illegal
file
operation
illegal
switch
input
files
MFO
mode
of
transfer
non-privileged
user
null
filename
output
files
Error
messages
(cont.),
7-1,
7-2
protect
code
record
size
standard
filename
extension
:::264
using
fast
copy
using
high-density
RK03/05
(H)
using
low-density
RK03 (L)
US1.ng
meaningless
commands
wildcard
operation
zero
Exit
from
PIP,
1-3
ext
(filename
extension),
2-1
F
error
message,
1-3
Factor,
interleave,
3-5
Fast
Copy
(/FC)
switch,
3-2
Fatal
condition,
1-3
File,
2-1
contiguous,
2-6,
3-5,
3-6
creation
date,
4-2
designator,
3-9
input,
2-1
linked,
3-5,
3-6
manipulation,
4-1
output,
2-1
protection,
2-5
protection
code,
3-12,
4-2
DELETE
READ
RUN
WRITE
~)egment,
3-13
specification,
2-2,
3-11
transfer,
3-1,
3-5,
3-10
Filename,
2-3
extension,
2-4,
3-4
specification,
2-3
specification,
2-3
File
transfer
operation,
5-1
$FINISH
command,
1-2,
1-4
FOJcmat,
5-3
cassette
tape,
6-2
data,
5-4
~Jeneral,
5-4
swi
tch,
3-4
IFA
(Formatted
ASCII)
IFB
(Formatted
Binary)
IUA
(Unformatted
ASCII)
IUB
(Unformatted
Binary)
Formatted
ASCII
mode,
2-6
Formatted
Binary
mode,
2-6
IFR
switch,
2-3,
4-9
Free
blocks,
1-1,
2-6,
4-4,
4-9
Full
directory,
4-3
(/DI)
listing,
3-13,
4-2,
4-4,
4-9
Functions
control,
1-1
E~di
ting,
1-1
$GET
command,
1-4
Helpful
hints,
B-1
High-speed
paper
tape
punch,
3-7
High-density
(H),
4-11
cartridges,
4-11
Inaccessible
state,
4-11
Input
file,
2-1,
3-1
Inspect
switch
(lIN),
3-10
Interleave
factor,
3-5
Initialize,
4-9
cassette
tape,
6-2
disk,
4-11
RKll
disk,
4-10
$JOB
command,
1-4
KB
transfer,
3-7
KILL
command,
1-1,
1-2,
1-3
sequence,
1-4
terminates
PIP,
1-3
L
(low
density),
4-11
LINE
feed
key,
3-7
Linked
file,
3-5,
3-6
List,
2-6
Listing,
1-1,
5-1
full
directory,
3-6
LOCK
bit,
4-11
LOGIN
command,
1-2,
2-5,
4-1
Low-density
cartridges,
4-11
Low-speed
paper
tape
reader,
3-7
Magnetic
(Magtape)
tape,
2-6,
5-1,
5-3
initialization,
5-1
Master
File
Directory
(MFD)
,
2-6,
4-1,
4-10
Merge,
1-1,
3-1,
3-3
operation,
3-5
single
file,
3-3
Mode
ASCII,
3-4
Binary,
3-4
formatted
ASCII,
2-6
formatted
Binary,
2-6
transfer,
3-4,
3-5
Multiple
devices,
4-3
Multiple
units,
2-2
Non-transfer
operations,
2-5
Null
extension,
2-4
fields,
2-3
Number
of
blocks,
4-5
Number
sign
characteri
1-2,
3-7,
4-11
X-2
Operation,
copy,
3-5
deletion,
2-4
directory
listing,
2-4
merge,
3-5
non-transfer,
2-5
protection,
2-4
rename,
2-4
transfer,
2-4
Options,
switch,
2-6
Output
file,
2-1
designation,
3-1
Paper
tape
reader,
3-5
Partial
list,
4-4
Peripheral,
3-1
Period,
2-3
PIP
(Peripheral
Interchange
Program),
1-1,
1-2
Programming
cautions,
C-l
Project
listing,
user
no.
200,
4-8
Protect
switch
(/PR)
,
3-11
Protection,
1-1,
2-6
change,
3-11
code,
3-11
file,
2-5
operation,
2-4
Qualifying
switches,
2-6,
2-7,
2-8
'/co
(Copy)
IFA
(Formatted
ASCII)
IFB
(Formatted
Binary)
lIN
(Inspect)
ISU
(Supersede)
IUA
(Unformatted
ASCII)
IUB
(Unformatted
Binary)
Random
accessing,
3-5
Recovery,
4-11
Rename,
1-1,
2-4
operation,
2-4
switch
(IRE),
3-2,
3-8
Replace,
1-1,
2-6,
3-10
RESTART
command,
1-3
RETURN
key,
1-2
Rewind
switch,
5-1, 5-2,
6-1,
6-2
Rewind
and
Unload
switch,
5-1,
5-3
RKl1
disk,
4-10
$RUN
command,
1-2,
1-4
RUN
PIP
command,
1-2
S
error
message,
1-3
Sequence
of
filenames,
3-9
SHIFT/K,
2-5
SHIFT/M,
2-5
Slash,
2-5
Specification,
device,
2-2
filename
extension,
2-3
Specification
(cont.)
swi
tch,
2-2
Ule
(user
identification
code),
2-- 5
Square
brackets,
2-5
Standard
filename
extension,
3-4
String,
command,
2-5
Storage,
file,
2-5
Summaries,
A-I
Supersede
SU:OFF
cOTI@and,
3-11
SU:
ON
cornmand,
3-11
mode,
3-11
switch;
(/SU)
,
3-10,
3-11
Switch,
IAL
(Allocate),
2~6,
3-13
IBR
(Brief
Directory),
2-6,
4-7
ICO
(Contiguous),
2-6
IDE
(Delete),
2-6,
3-10
IDI
(Directory),
2-6,
3-10
lEN
(Enter),
2-6
IFA
(Formatted
ASCII),
2-6,
3-5
IFB
(Formatted
Binary),
2-6,
3-5
IFC
(Fast
Copy),
2-6
IFR
(Free),
2-3,
2-6
lIN
(Inspect),
2-3
IPR
(Protect),
2-6
IRE
(Rename),
2-6,
3-10
IRU
(Rewind
and
Unload),
2-6
IRW
(Rewind),
2-6
ISU
(Supersede),
2-6
IUA
(Unformatted
ASCII),
2-7,
3-5
IUB
(Unformatted
Binary),
2-7,
3-5
IUN
(Unlock),
2-7
/VE
(Verify),
2-7
!VW
(Verified
Write),
2-7
IZE
(Zero),
initialize,2-7
Switch
code,
2-2,
2-5
Switch
name,
2-5
Switch
options,
2-6
Switch
specification,
2-2,
2-5
System,
crash,
4-11
program
error,
6-1
Transfer,
1-1
command,
3-10
file,
3-1
operation,
2-4,
3-6,
6-1
teleprinter,
3-7
UIC
(user
identification
code),
2-1,
2-4,
2-6,
3-3,
3-9,
4-1,
4-2,
4-5,
4-10,
5-1
field,
asterisk
in,
4-8
specification,
2-5
IUN
switch
(Unlock)
I
4-11
Unformatted
ASCII,
3-4
Unformatted
Binary,
3-4
Units,
2-2
Used
blocks,
4-4
User
Free
Directory
(UFD),
4-1
entry,
4-11
usage
count
in
entry,
4-11
X-3
User
group,
2-5
Verify
(/VE)
,
switch,
1-1,
3-2,
3-3
Version
number,
1-2
Word,
3-3
Y
(Yes)
reply,
3-10
Zero
(Initialize)
switch,
1-1,
3-10,
4-2, 4-9,
4-10,
5-2
DECtape,
4-10
X-4
HOW
TO
OBTAIN
SOFTHARE
INFORHATION
Announcements
for
new
and
revised
sofbvare,
as
well
as
programming
notes,
software
problems,
and
documentation
corrections,
are
published
by
Software
Information
Service
in
the
following
newsletters.
DIGITAL
Software
Ne\vs
for
the
PDP-8
and
PDP-12
DIGITAL
Software
News
for
the
PDP-II
DIGITAL
Software
News
for
l8-bit
Computers
These
newsletters
contain
information
applicable
to
software
available
from
DIGITAL'S
Software
Distribution
Center.
Articles
in
DIGITAL
Software
News
update
the
cumulative
Software
Performance
Summary
which
is
included
in
each
basic
kit
of
system
software
for
new
computers.
To
assure
that
the
monthly
DIGITAL
Software
News
is
sent
to
the
appropriate
sofbvare
contact
at
your
installation,
please
check
with
the
Software
Specialist
or
Sales
Engineer
at
your
nearest
DIGITAL
office.
Questions
or
problems
concerning
DIGITAL'S
software
should
be
reported
to
the
Software
Specialist.
If
no
Software
Specialist
is
available,
please
send
a
Software
Performance
Report
form
with
details
of
the
problems
to:
Digital
Equipment
Corporation
Software
Information
Service
Software
Engineering
and
Services
Maynard,
Massachusetts
01754
These
forms,
which
are
provided
in
the
software
kit,
should
be
fully
completed
and
accompanied
by
terminal
output
as
well
as
listings
or
tapes
of
the
user
program
to
facilitate
a
complete
investigation.
An
answer
will
be
sent
to
the
individual,
and
appropriate
topics
of
general
int~rest
will
be
printed
in
the
newsletter.
Orders
for
new
and
revised
software
manuals,
additional
Software
Performance
Report
forms,
and
software
price
lists
should
be
directed
to
the
nearest
DIGITAL
field
office
or
representative.
USA
customers
may
order
directly
from
the
Software
Distribution
Center
in
Maynard.
When
ordering,
include
the
code
number
and
a
brief
description
of
the
software
requested.
Digital
Equipment
Computer
Users
Society
(DECUS)
maintains
a
user
library
and
publishes
a
catalog
of
programs
as
well
as
the
DECUSCOPE
magazine
for
its
members
and
non-members
who
request
it.
For
further
information,
please
write
to:
Digital
Equipment
Corporation
DECUS
Software
Engineering
and
Services
Maynard,
Massachusetts
01754
READER'S
COMMENTS
DOS/BATCH
File
Util
Program
(PIP)
DEC-ll-UPPAA-A-D
NOTE:
This
form
is
for
document
corr~ents
only.
Problems
with
software
should
be
reported
on
a
Software
Problem
Repcrt
(SPR)
form
(see
the
HOW
TO
OBTAIN
SOFTWARE
INFOR}mTION
page)
.
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
~ssociated
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
o
Assembly
language
programmer
o
Higher-level
language
programmer
o
Occasional
programmer
(experienced)
o
User
with
little
programming
experience
o
Student
programmer
o
Non-programmer
interested
in
computer
concepts
and
capabiliti4
Name
Date
____________
_
Organization
________________________________________________________
_
Stre~t-----------------------------------------------------------------
City
____________________
S
ta
te
___________
Z
ip
Code
________
_
or
Country
If
you
do
not
require
a
written
reply,
please
check
here.
0
----------------,---------------------------,-------
Fold Here
------------------------------------------------------------
-,------------------------------------
Do Not
Tear
-Fold Here and Staple
-----------------------------------------------
::SS
REPLY
MAIL
TAGE
STAMP
NECESSARY
IF
MAILED
IN
THE
UNITED
STATES
Nill be paid by:
Digital Equipment Corporation
Software Information Service
Software Engineering and Services
Maynard, Massachusetts
01754
FIRST
CLASS
PERMIT
NO. 33
MAYNARD,
MASS.

Navigation menu