Mark A. Stevens wrote:
Fish wrote:
Mark A. Stevens wrote:
I can't seem to build an AWS tape file,
but I can build an HET tape file.
Eh? Why not?
Fish,
It is a case of using DEVINIT in the console, versus using
hetinit in a terminal session.
Ah! Okay. The default for AUTOINIT is ON:
If I 'create' a tape in the console in the following
manner, I get a HET format tape which I can read/write
to my hearts content.
HHC01603I DEVINIT 580 tapes/2022-01-13.86WTTL.FILE132.het
HHC00221I 0:0580 Tape file tapes/2022-01-13.86WTTL.FILE132.het, type HET:
format type Hercules Emulated Tape file
HHC00235I 0:0580 Tape file tapes/2022-01-13.86WTTL.FILE132.het, type het:
tape created
HHC02245I 0:0580 device initialized
[...]
I am NOT using the hetinit command to create a blank tape, for
either HET or AWS. Therein lies the difference.
So if you entered the command:
devinit 580 tapes/2022-01-13.86WTTL.FILE132.aws
instead (note ".aws" file extension instead of .het), then you SHOULD end up with an uncompressed .aws format tape file being created instead.
So once again, the user, me, is the problem ;-)
It would appear so, yes. :)
Thanks for the help.
You're very welcome.
I was just concerned by your original claim of being able to create an AWS tape, that's all. But apparently you CAN -- if you use the correct devinit command. ;-)
Mystery solved. :)
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
