source: trunk/athena/bin/ansi/ansi.1 @ 6954

Revision 6954, 3.9 KB checked in by probe, 31 years ago (diff)
Initial revision
  • Property svn:executable set to *
Line 
1.\"
2.\"     $Source: /source/4.3/man/man1/RCS/ansi.1,v $
3.\"     $Author: wjmadden $
4.\"     $Locker:  $
5.\"     $Log:   ansi.1,v $
6.\"Revision 1.1  84/08/15  23:21:39  wjmadden
7.\"Initial revision
8.\"
9.\"Revision 1.1  84/05/10  18:46:20  root
10.\"Initial revision
11.\"
12.\"
13.TH ANSI 1I 5/21/83
14.UC 4
15.SH NAME
16ansi, unseg \- read and convert VMS ansi labeled tapes.
17.SH SYNOPSIS
18.B ansi
19[ \fB-bfisv\fP ] [ \fRdrive\fP ] [ files ] ...
20.LP
21.B unseg
22< file > newfile
23.SH DESCRIPTION
24\fIAnsi\fP is used to read and convert files from ansi labeled tapes.
25In particular, it handles gracefully the following situations:
26(1) non-standard block sizes,
27(2) variable length records, both text and binary data
28(binary data is converted to f77 style variable records),
29(3) extraction of particular files from the tape,
30(4) version numbers of files,
31(5) fortran carriage control text files,
32(6) fixed length record binary files.
33In particular, it is useful for reading labeled tapes produced by
34Vax/VMS.
35All \fIfiles\fP
36listed in the argument are extracted into the current directory.
37If no files are specified, all files on the tape are extracted.
38.PP
39The companion program \fIunseg\fP
40is useful for converting VMS fortran variable length segmented files
41(the default file type produced by VMS fortran) to a form readable directly
42by the Unix fortran compiler.
43.TP
44.B \-v
45Verbose mode.
46\fIAnsi\fP
47will give a running commentary of the files created and the types
48determined from the HDR1 and HDR2 labels.
49.TP
50.B \-s
51Superverbose mode.
52Dumps all useful contents of the HDR1 and HDR2 records on the standard output.
53This is useful for debugging purposes.
54.TP
55.B \-b
56Force binary input of all data in the file.
57No record interpretation is performed.
58.TP
59.B \-f
60Read the tape on device \fIdrive\fP rather than \fI/dev/rmt8\fP.
61.TP
62.B \-i
63Ignore version numbers.  No version numbers will be appended to the file
64names.
65.TP
66.B \-l
67List all file names and types on the tape.  This prevents any files from being
68extracted.
69.LP
70\fIUnseg\fP gives up the ghost if presented with a file in a format it can't
71understand.
72.SH WARNING
73\fIAnsi\fP will destroy any file in the current directory of the same name
74of a file extracted from tape.
75.SH DIAGNOSTICS
76.TP
77Can't open \fIfile\fP
78\fIAnsi\fP could not open the tape drive for reading.
79.TP
80Error in reading volume label.
81The label on the tape was bad.
82.TP
83Volume label found was XXXXXX.
84The volume label on the tape was XXXXXX.
85.TP
86Creating file \fIfile\fP, file type is ....
87verbose information commentary.
88.TP
89Can't Create \fIfile\fP, skipping file on tape.
90\fIAnsi\fP could not create the file in the current directory,
91probably because there was already a file of that name that was not writeable.
92.TP
93Bad HDR2 record!
94Tape is probably not an ansi tape.
95.TP
96ansi: bad forms, binary assumed in \fIfile\fP.
97The forms control character was not A, M or space.
98All \fIansi\fP can do is read in the data as binary,
99as it has no way to find out how to format the data.
100.TP
101ansi: unknown type, binary assumed in \fIfile\fP.
102Fixed format files should always have internal forms control;
103something else was detected.
104.TP
105ansi: unknown format, binary assumed in \fIfile\fP.
106The format of the tape was neither fixed or variable,
107the only forms that \fIansi\fP understands.
108.TP
109Record wrong size (count = XXXXX)
110The block size on tape does not match the block size recorded in the
111file header.
112.SH "SEE ALSO"
113Digital Equipment Corporation,
114\fIVax/VMS Magnetic Tape User's Guide\fP and \fIVax/VMS Fortran User's Guide\fP
115.SH AUTHOR
116Jim Gettys
117.SH BUGS
118Should do more sanity checking on tape files.
119.LP
120There is no way to automatically unsegment fortran files as they come in;
121VMS fortran does its own segmentation on input and output and does not tell
122RMS.
123.LP
124Should be tested with against other Ansi tapes written on other than VMS.
125.LP
126VMS is obsolete and should be abolished.
127.LP
128Fortran carriage control conversion is not perfect.  Then again,
129neither is fortran.
Note: See TracBrowser for help on using the repository browser.