![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: Hello, Here are some more hints to your answer of 1285 "DLT III re-initialize in a TZ85..." I don't know how to contact you on different way. Hope you don't bother. Kind Regards Andreas -------------------------------------------------------------------------- DLT III re-initialize for different DLT types The Answer is : DLT Matrix DLT COMPACT Media IV TK90 40/80GB => TK90 / TK89 / TK88 / TK87 / TK86 .ditto. TK89 35/70GB => TK89 / TK88 / TK87 / TK86 / TK85 .ditto. TK88 20/40GB => TK88 / TK87 / TK86 / TK85 DLT COMPACT Media III TK87 10/20GB => TK87 / TK86 / TK85 / TK70 read only / TK50 read only .ditto. TK86 6GB => TK86 / TK85 / TK70 read only / TK50 read only .ditto. TK85 2.6GB => TK85 / TK70 read only / TK50 read only DLT COMPACT Media II TK70 296MB => TK70 / TK50 read only DLT COMPACT Media I TK50 95MB => TK50 Media: http://www.compaq.com/products/storageworks/mediafamily/DLT.html Via OpenVMS... The mentioned 'problem' appears at all 'older' DLT's. For instance a TZ89 can't read a TZ90 initialized media by default, or TZ88 can't read TZ89 media and so forth... But... Since OpenVMS 7.2 following qualifiers are supported during tape initialize that provides a different density. Please read the extract from OpenVMS help below. That means it can be re-initialize a DLT media via following command. Assuming we have a DLT media initialised on a TZ89 and should be accessible on a TZ88 and the tape device name is MKA600: TAMDHU_SYSDAVO> sho dev mk Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt TAMDHU$MKA600: Online 0 TAMDHU_SYSDAVO> sho dev/full mka600: Magtape TAMDHU$MKA600:, device type TZ89, is online, record-oriented device, file-oriented device, error logging is enabled, controller supports compaction (compaction enabled), device supports fastskip. Error count 0 Operations completed 4109263 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 0 Default buffer size 512 Density TK89 Format Normal-11 Volume status: no-unload on dismount, beginning-of-tape, odd parity. TAMDHU_SYSDAVO> mount/for mka600: %MOUNT-I-MOUNTED, TH0418 mounted on _TAMDHU$MKA600: TAMDHU_SYSDAVO> dismount/nounload mka600: TAMDHU_SYSDAVO> INITIALIZE /DENSITY=TK88 /MEDIA=COMPACTION MKA600: TEST TAMDHU::SYSDAVO 13:37:57 INIT CPU=00:00:01.00 PF=1720 IO=4074 MEM=122 TAMDHU_SYSDAVO> TAMDHU::SYSDAVO 13:40:37 (DCL) CPU=00:00:01.01 PF=1725 IO=4086 MEM=67 TAMDHU_SYSDAVO> mount/for mka600: %MOUNT-I-MOUNTED, TEST mounted on _TAMDHU$MKA600: TAMDHU_SYSDAVO> sho dev/full mka600: Magtape TAMDHU$MKA600:, device type TZ89, is online, allocated, deallocate on dismount, mounted foreign, record-oriented device, file-oriented device, error logging is enabled, controller supports compaction (compaction disabled), device supports fastskip. Error count 0 Operations completed 4109314 Owner process "SYSDAVO" Owner UIC [SYSMGT,SYSDAVO] Owner process ID 00002500 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 2 Default buffer size 512 Volume label "TEST " Relative volume no. 0 Record size 0 Transaction count 1 Mount status Process Mount count 1 ACP process name "" Density default Format Normal-11 Volume status: beginning-of-tape, odd parity. TAMDHU_SYSDAVO> dismount/nounload mka600: TAMDHU_SYSDAVO> -------------------------------------------------------------- INITIALIZE /DENSITY /DENSITY=density-value The /DENSITY qualifier is not applicable to any TF tape device. Valid density values are as follows: Keyword Meaning DEFAULT Default density 800 NRZI 800 bits per inch (BPI) 1600 PE 1600 BPI 6250 GRC 6250 BPI 3480 IBM 3480 HPC 39872 BPI 3490E IBM 3480 compressed 833 DLT TK50: 833 BPI TK50 DLT TK50: 833 BPI TK70 DLT TK70: 1250 BPI 6250 RV80 6250 BPI EQUIVALENT NOTE: Only the keywords above are understood by TMSCP/TUDRIVER code prior to OpenVMS Version 7.2. TK85 DLT Tx85: 10625 BPI - Cmpt III TK86 DLT Tx86: 10626 BPI - Cmpt III TK87 DLT Tx87: 62500 BPI - Cmpt III TK88 DLT Tx88: (Quantum 4000) - Cmpt IV TK89 DLT Tx89: (Quantum 7000) - Cmpt IV QIC All QIC drives are drive-settable only 8200 Exa-Byte 8200 8500 Exa-Byte 8500 DDS1 Digital Data Storage 1 - 2G DDS2 Digital Data Storage 2 - 4G DDS3 Digital Data Storage 3 - 8-10G DDS4 Digital Data Storage 4 AIT1 Sony Advanced Intelligent Tapes To format a diskette on RXnn diskette drives, use the INITIALIZE/DENSITY command. Specify the density at which the diskette is to be formatted as follows: Keyword Meaning single RX01 - 8 inch double RX02 - 8 inch dd double density: 720K - 3 1/2 inch hd high density: 1.44MB - 3 1/2 inch ed extended density: 2.88MB - 3 1/2 inch If you do not specify a density value for a diskette being initialized on a drive, the system leaves the volume at the density to which the volume was last formatted. NOTE Diskettes formatted in double density cannot be read or written by the console block storage device (an RX01 drive) of a VAX-11/780 until they have been reformatted in single density. RX33 diskettes cannot be read from or written to by RX50 disk drives. RX50 diskettes can be read from and written to by RX33 disk drives; they cannot be formatted by RX33 disk drives. For magnetic tape volumes, specifies the density in bits per inch (bpi) at which the magnetic tape is to be written. For magnetic tape volumes, the density value specified can be 800 bpi, 1600 bpi, or 6250 bpi, as long as the density is supported by the magnetic tape drive. If you do not specify a density value for a blank magnetic tape, the system uses a default density of the highest value allowed by the tape drive. If the drive allows 6250-, 1600-, and 800-bpi operation, the default density is 6250 bpi. If you do not specify a density value for a magnetic tape that has been previously written, the system uses the density of the first record on the volume. If the record is unusually short, the density value will not default. INITIALIZE Subtopic? <<< buthed::SYS$SYSDEVICE:[NOTES$LIBRARY]WIZARD.NOTE;1 >>> -< Ask the Wizards >-
|