Also check with the system programmers on the performance specifications for
VTAM, TCPIP and the TSM server started task. For compatibility mode check
the IPS/ICS members of parmlib and the service classificaitons in GOAL mode.
Also have them look at the BPX tasks. At this level of OS/390, TCPIP is
partially a USS task. The BPXPRMxx member for some
parameters..MAXSOCKETS()..
In the TCPIP parmlib member:
TCPCONFIG RESTRICTLOWPORTS
TCPSENDBFRSIZE 262144
TCPRCVBUFRSIZE 262144
TCPMAXRCVBUFRSIZE 524288
and the PORT line:
1500 UDP ADSM NODELAYACKS ; ADSM PRODUCTION
I found significant performance improvement with the NODELAYACKS.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Hunley, Ike
Sent: Thursday, February 14, 2002 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Export/Import process
It's OS/390 V2R9. The LPAR has GIGABIT Ethernet, so throughput should be
good. I'll check with our network folks.
Thank you VERY much.
-----Original Message-----
From: Cook, Dwight E (SAIC) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 12:05 PM
To: Hunley, Ike
Subject: RE: Export/Import process
Is that an OS/390 running MVS/ESA ?
probably your network interface... or TCP/IP configuration on MVS
lots of tuning is required under MVS to get TSM to run well...
and it still won't run as good as on a healthy IBM S70 AIX machine...
we got rid of our two MVS tsm servers and moved them onto S70's...
We run a total of 9, S70 TSM servers
just my thoughts and experiences...
-----Original Message-----
From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 10:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Export/Import process
Great,
Thanks a lot. I'm reading TSM doc as I respond to TSM issues.
We've moved a client server from a UNIX based TSM to a TSM(4.2.1.9) started
task running on OS/390 v2r9. Now backups take a LOT more time. Where do I
begin to look for the why?
I see extended IDLE waits.
1,162 BPX-- IdleW 2.0 H 76.2 M 4.4 K Node WinNT
What causes idle wait?
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Export/Import process
Neither.
Look at the help for IMPORT NODE.
If the filespaces you are importing have identical names to the ones backed
up on the new server (and they probably will, since the clients haven't
changed), IMPORT will create new filespace names for the imported ones. TSM
will NOT merge filespace data on import.
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
-----Original Message-----
From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 11:00 AM
To: [EMAIL PROTECTED]
Subject: Export/Import process
We had a TSM region setup for testing and we are moving servers from one TSM
started task to another one.
So far we've just pointed the servers to the new TSM. We'd like to export
all data for each node to import into the new TSM. If we do this, would we
overwrite data in the new environment, or would it simply store it?
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.
