|
Because they changed the tape library device description(s) when they
changed the VTL.
They had to delete and recreate all of the device descriptions.
We are using BRMS. It was done when we went to the cloud.
We never changed the way that we were doing backups.
Did it 2 years ago.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rob Berendt
Sent: Tuesday, March 11, 2025 10:10 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: InzTap failing
Caution: This is an external email. Please take care when clicking
links or opening attachments. When in doubt, contact your IT
Department
Troy,
What kind of VTL you have has zero effect on what the options are on
F4 or ? to prompt for the DENSITY parameter. Try leaving the device
blank on INZTAP and hitting F4 on the DENSITY parameter.
On Tue, Mar 11, 2025 at 11:04?AM Troy Foster via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
That happened to our system.our system.
We have our system in the cloud and the company that is hosting our
system moved the VTL to new VTL and didn't check the actual setting
on
They set it to *ultrium7.recipient(s) and should "only"
They did a read not a INZTAP, you can read back 2 levels but can not
write
2 levels. They also did not notify us of the change.
I would check with whoever set up the VTL.
Ok, this makes NO sense.
Yesterday the system went down hard.
An outside company was going to do a fire alarm testing and threw
the wrong breaker and brought down the data center!!!
WTH?!?!?!
Networks, IBMi, phones, UPS. Everything.
We use a VTL for out nightly backups.
Part of the backup does a INZTAP and has *ULTRIUM5 in Density as
that is what we had and still have as needed for a physical tape.
The INZTAP failed last night saying it is an invalid density.
NOTHING has changed.
Why in the H....eck would this fail now?
When I do an INZTAP and put ? in the Density, *ULTRIUM5 is not listed.
We are at 7.4 and IPL the box every 4 weeks. Last IPL was 2 weeks
ago, except for yesterday's debacle.
Subject to Change Notice:
WalzCraft reserves the right to improve designs, and to change
specifications without notice.
Confidentiality Notice:
This message and any attachments may contain confidential and
privileged information that is protected by law. The information
contained herein is transmitted for the sole use of the intended
pertain to "WalzCraft" company matters. If you are not the intended--
recipient or designated agent of the recipient of such information,
you are hereby notified that any use, dissemination, copying or
retention of this email or the information contained herein is
strictly prohibited and may subject you to penalties under federal
and/or state law. If you received this email in error, please notify
the sender immediately and permanently delete this email. Thank You
WalzCraft PO Box 1748 La Crosse, WI, 54602-1748 http://www/
.walzcraft.com%2F&data=05%7C02%7Cmichael.mayer%40ermco-eci.com%7Cd30
4d2b0cff84d79ec4108dd60be2e60%7Cd2deeaf270e4425c91d7d99d784e89d6%7C0
%7C0%7C638773092175458440%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn
RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ
%3D%3D%7C0%7C%7C%7C&sdata=aP6%2B71ZoZqjX6TJa3CGMCBrzhn8tG7ew1pBbE0E9
%2BUI%3D&reserved=0<
http://www/
.walzcraft.com%2F&data=05%7C02%7Cmichael.mayer%40ermco-eci.com%7Cd30
4d2b0cff84d79ec4108dd60be2e60%7Cd2deeaf270e4425c91d7d99d784e89d6%7C0
%7C0%7C638773092175471855%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn
RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ
%3D%3D%7C0%7C%7C%7C&sdata=e5d0C4wLmFnuA3%2BQqUVFyWf0tJMB6UDPMWiNBBm7
hQ0%3D&reserved=0> Phone: 1-800-237-1326
--
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://li/
sts.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Cmi
chael.mayer%40ermco-eci.com%7Cd304d2b0cff84d79ec4108dd60be2e60%7Cd2d
eeaf270e4425c91d7d99d784e89d6%7C0%7C0%7C638773092175482013%7CUnknown
%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa
W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=h62wKB%2F
vvNipfngCIjGaYIBWBHSFh6QCTuIJzADW9VA%3D&reserved=0
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://li/
sts.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Cmi
chael.mayer%40ermco-eci.com%7Cd304d2b0cff84d79ec4108dd60be2e60%7Cd2d
eeaf270e4425c91d7d99d784e89d6%7C0%7C0%7C638773092175511592%7CUnknown
%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa
W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BW9m7%2
BYmeUyvuKmIxSodxv9SqcJq0fIJX97SujKjj80%3D&reserved=0
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://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Cmichae
l.mayer%40ermco-eci.com%7Cd304d2b0cff84d79ec4108dd60be2e60%7Cd2deeaf27
0e4425c91d7d99d784e89d6%7C0%7C0%7C638773092175530731%7CUnknown%7CTWFpb
GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkF
OIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=37JRd1LuJR2dhcJQ3SKRM
0Am2JB4Nuf%2FTNNU1rPk1%2BQ%3D&reserved=0
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://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Cmichae
l.mayer%40ermco-eci.com%7Cd304d2b0cff84d79ec4108dd60be2e60%7Cd2deeaf27
0e4425c91d7d99d784e89d6%7C0%7C0%7C638773092175549746%7CUnknown%7CTWFpb
GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkF
OIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SPJGLleAIdbUA56hKvY4x
Fh52g5JIhpL03iZ18NBSNI%3D&reserved=0
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.
Where can one find the valid combinations?
I don't think that's an option. I've never seen anything where it
caches the connection so the handshake isn't repeated with "familiar"
clients, but then again... I haven't really dug into it that much.
The only way I could see that happening is if the connection is left
open and the other end allows it (some do, some don't. GETURI allows
you to keep it open, but in most cases it won't work unless you're
communicating with something like an FTP, SMTP, etc server.. not just HTTP requests).
Sorry, I shouldn't have even called it a "fight". :) Just using it
as reference to bottlenecking that we'd all understand.
Now, as for a REAL fight, you should see what I look like after having
retinal detachment surgery on Friday. They beat me up good! haha..
but I'm on the mend.
On Tue, Mar 11, 2025 at 12:42?PM Jay Vaughn
<jeffersonvaughn@xxxxxxxxx>
wrote:
please don't remind me of that fight Brad. :)and
So, what about ssl handshake retention?
Ever noticed anything in that area?
thanks
Jay
On Tue, Mar 11, 2025 at 1:28?PM Brad Stone <bvstone@xxxxxxxxx> wrote:
Even if your system CPU and network is up to snuff, you willhuge
notice a
difference in speed vs native i/o. But, in most cases I've foundthe
it's
other side that is the bottleneck, not the IBM i with sufficient
CPU
customersnetworking.
It's still "fast enough" in most cases. But I have worked with
itwhere when the other end gets hit by more than 100 requests at a
time
requestsjust chokes... most of the time they are server farms, Amazonpaid
shared services, etc... never in house systems.
Think of the Tyson fight on Netflix. They were VERY underpowered
and underestimated the bandwidth and CPU that would be required.
And they
the price. It wasn't the fault of the viewers, it was the
foresight of Netflix and how many resources they thought they'd need.
On Tue, Mar 11, 2025 at 12:06?PM Jay Vaughn
<jeffersonvaughn@xxxxxxxxx
wrote:
Let me start with just a pretty generic question and scenario.
If you had a need to send a large volume of http API consumer
thatfrom your native applications (and db2)... is it correct to
think
tohttp_post may not exactly be the best choice as it is real timethat
synchronous...
If so, what are some other good options?
Or am I wrong? Could you expect http_post to hold up.
Pretty speculative scenario I realize - but imagine a level of
volume
you may consider moderate to high even for your native
applications
gooff
beafter db2 data locally - but instead, those "i/o"s are
considering to
replaced with http_post to another system.
As a change occurs in the application, that change is pushed
over
mailingplatform via http via the http_post...
can it work?
what are the considerations?
Also this would be with https (ssl authentication in play)
tia
jay
--
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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%25
2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7
C02%7Cmichael.mayer%40ermco-eci.com%7C701a5ebd9b4942f02dcf08dd60
c6126b%7Cd2deeaf270e4425c91d7d99d784e89d6%7C0%7C0%7C638773126675
911781%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
jAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C80
000%7C%7C%7C&sdata=JaZmMuXoJM20tmSauq3MVLmQopCmsompJKFjkprjqC4%3
D&reserved=0 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2F
lists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%
7Cmichael.mayer%40ermco-eci.com%7C701a5ebd9b4942f02dcf08dd60c6126b
%7Cd2deeaf270e4425c91d7d99d784e89d6%7C0%7C0%7C638773126675946378%7
CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCI
sIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C80000%7C%7C%7C
&sdata=WO1v%2Bj5Z7UVONw7CYhVkW10msipCmZWCZuMQxa2CMiU%3D&reserved=0
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://li/
sts.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Cmi
chael.mayer%40ermco-eci.com%7C701a5ebd9b4942f02dcf08dd60c6126b%7Cd2d
eeaf270e4425c91d7d99d784e89d6%7C0%7C0%7C638773126675972873%7CUnknown
%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa
W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C80000%7C%7C%7C&sdata=xkb%2
FNb00GJXTglFQ2H1FHs4WzNnUApRbuIl8idcytJY%3D&reserved=0
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://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C02%7Cmichae
l.mayer%40ermco-eci.com%7C701a5ebd9b4942f02dcf08dd60c6126b%7Cd2deeaf27
0e4425c91d7d99d784e89d6%7C0%7C0%7C638773126675998756%7CUnknown%7CTWFpb
GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkF
OIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C80000%7C%7C%7C&sdata=vj0Lpha4ms2j2Gkbs
ui7zuyw9XVE9zLlYE2SDYmKx%2Bo%3D&reserved=0
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-2025 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.
midrange.com
