|
we just got a new DD, and when it auto-config'ed to the IBMi, is is a
3584-032. we set up LTO-8 drives in the DD-VTL,
so our IBMi tape drives are 3580-008.
On Mon, Apr 1, 2024 at 10:05 AM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:
<snip> If you are emulating a tape drive with a DD, does IBM even carewhat
model you use? </snip>gens
Only if for some reasons the stuff I posted on WRKHDWRSC *STG becomes an
issue.
<snip> LTO did adhere to R/W -1 and R -2, it is only in the last two
that they didn't keep to that </snip>themselves
Ok, it wasn't a myth, until it was.
On Mon, Apr 1, 2024 at 10:49 AM Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:
I haven't seen IBM i STOP supporting tape, beyond the adapters
howbeing no longer available. I mean, If you had an LTO1 SCSI HVD tape,
machineswould you connect it to a P10 nowadays? On the contrary, I've used LTOwould
drives of higher generations than IBM i even knew about (say, LTO4 on a
v5r2 machine) and other than having to initialize them with the "tape
default" keyword instead of being able to specify LTO4 I had no issues.
There's not really that much going on with the SCSI/FC protocols that
make IBM i stop supporting a tape drive, other than EoSL for the
isinvolved and you needing to involve IBM support but... If you areemulating
a tape drive with a DD, does IBM even care what model you use? Support
capacityon the DD's side isn't it?
One reason I can think for moving up from LTO7 is the presented
ifand
you don't care about duplicating to physical tapes.allow
I don't know why you call it a myth, but until the technology didn't
it, LTO did adhere to R/W -1 and R -2, it is only in the last two gensthat
they didn't keep to that and I'm pretty sure it was for technicalreasons.
On Mon, 1 Apr 2024 at 11:26, Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:
1-No, I do not have any physical tape whatsoever. If this was an
admonishment for an "air gap" we're using Safe Guarded Copy for that.
2-No I am not a member of LUG as I am only using Scale Out systems
releaseyouBeing
have to order those by the ship container load to qualify for LUG.
upcomingan IBM Champion and some other stuff I do does give me access to some
information not generally available. However, if I knew of any
(and,thing that was not generally available I couldn't even hint at it.
no, this is not to be intended as a hint itself)figure
3-I think we upgraded from LTO5 to LTO7 when we upgraded our old Data
Domains as they reached out of service.
4-As far as whether or not this matters, this is what I'm trying to
out. It would be nice if there was a chart of tape support for
ofofand
IBM i much like the IT Jungle article today had on tape compatibility
the busted myth that LTO can read/write x-1 and read x-2. This isprobably
why we only went to LTO7 on the VTL. I suppose I could start weaningover
to a higher level just to be ready for the next thing(s). We have noLTO5
left. The last were duped to LTO7 some time ago.
On Mon, Apr 1, 2024 at 10:01 AM Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx>
wrote:
In accordance with your penchant for keeping on the bleeding edge
physicalwhateverreleases LTO9 has been out since 2021. LTO7 came out in 2012.
The current model of the tape library is 3588.
That said, I always tell my customers to set up the VTL to match
physical tape you have on the system (You do have an Oh S**t
supportandtape
don't you?) that you off load the critical updates to for off site
malware,retention purposes. Physical tape can't be beset by hackers,
matter?etc.
Since IBM i supports everything at the levels you're at, does it
You are a member of the LUG, have they talked about dropping
notfortape
robertowenberendt@xxxxxxxxx>LTO6, 7 or 8?
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On Mon, Apr 1, 2024 at 8:43 AM Rob Berendt <
modelswrote:
When using a VTL is there any reason to be concerned about what
you
emulate? We haven't had a physical tape library or any physical
media
in a decade.
My question is mainly if WRKHDWRSC *STG shows this
Resource Type-model
USSG7VTL 3584-400
TAP62 3580-007
TAP55 3580-007
TAP61 3580-007
TAP58 3580-007
TAP56 3580-007
TAP57 3580-007
TAP59 3580-007
TAP60 3580-007
is there any possibility that some future release will say LTO7
tendsupported and/or 3584 is not supported? As many of you know I
mailingtomailing
mailingrush
to a new release of IBM i as soon as I can.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listrelated
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
questions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listrelated
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
questions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
relatedlistrelated
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
listquestions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
listquestions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.