Google
 

Trailing-Edge - PDP-10 Archives - scratch - 10,7/unscsp/filex/filex.hlp
There are 8 other files named filex.hlp in the archive. Click here to see a list.
Commands are of the form:
dev:file.ext[p,pn]<prot>/s=dev:file.ext[p,pn]/s

The input (right-hand) side may have more  files  in  the  same  format,
separated by commas.
dev:  defaults to DSK:
file, .ext default to *
but .TMP files are not included in .* when reading from DSK:

prot defaults to system standard, <233> on PDP11 tapes
/s is a switch letter
(ssss) is ok for multiple switches

files are transferred in binary and individually at all times, except in
some cases of /V and /F

switches are:

/A forces ascii processing of /V and /F files
/B forces binary file transfers
/C says file is compressed (PDP10 .SAV)
/D says file is PDP6 .DMP format
/E says file is PDP10 .XPN format
/F says tape is a PDP fifteen tape
/G says go on in case of I/O errors
/H says help message (no file transfers are done)
/I forces image mode on /V tapes
/L says list file directory of tape (do not say TTY:;  that's assumed)
/M says tape is project MAC format
/O says tape is old PDP6 format
/P says same as /Q but preserve the temp file
/Q says quick mode processing (copy in big gulps between dsk and tape)
/R says same as /Q but re-use temp file (don't access tape)
/S says file is a project MAC save file (SBLK)
/T says tape is a normal PDP ten tape
/V says tape is a PDP-ele-V-en tape
/Z says zero the tape;  "^tapeid" or "[p,pn]" may  appear  with  /Z  for
   tapes where this is meaningful


In /P, /Q, or /R if two devices are given in the  file  spec,  then  the
second  device  defines  the  name  of  the  temp  file  (which is given
extension .DTA).

In the event no switches direct processing, file  extensions  cause  the
right thing to happen in the following cases:
.DMP implies /D
.SAV, .LOW, .SVE, .SHR, .HGH, .EXE imply /C
.XPN implies /E
These file extensions are implied for output files with  those  switches
too, as is .BIN for /S.  When /C is explicit or implied, .SHR, .HGH, and
.EXE are assumed to be in their standard formats respectively.

When transferring from .EXE to .HGH or .SHR, the high segment  extension
is  determined  from  the  contents of he input file.  Also, a .LOW file
will be created if needed.
When transferring from .HGH or .SHR to .EXE, a .LOW file  will  also  be
read if needed.

In the case of /V, the following extensions imply /B processing:   .BIN,
.OBJ,  .SYS,  .LDA,  .LDR, .LOD, .LBO, .MFD, .UFD, .SYM otherwise, /A is
assumed

In the case of /F, .ABS implies /B (not IOPS),  and  .BIN  implies  IOPS
binary  transfers.   Otherwise,  IOPS ascii is assumed for output to /F,
and IOPS headers are checked for input from /F