The APAR actually applies to all TSM server platforms. For the MVS server
a ZAP
is available. Although the problem is in common code, the symptom does not
occur on the Windows platform. The MVS and the Solaris servers will hang.
The
AIX server will crash. I am not sure what the HP server will
This should be fully documented in the README file.
The 4.1 server has a different licensing scheme than the 3.7 version of the
server.
The 3.7 licenses are not recognized by 4.1. You need to do the REGISTER LICENSE
commands on the 4.1 server.
The current architecture of the license manager is a
>As it says in the README
>>This is a smit/installp installable PTF that will install as
>>level 4.1.1.0. You must have the base level (4.1.0.0) installed
>>otherwise this PTF will fail to install.
>
>I wouldn't be surprised if you need to pay for the baselevel CD.
This is a good point. I did
>Hi *SM-ers!
>My TSM 3.7.3.0 server is crashing at least once a day for the last 5 days.
>There no addition information in the Activity log. The only output is a core
>dump and some unclear messages in the dsmserv.err:
>
>09/21/2000 10:14:28 ANR7834S Thread 49 (tid 3196) terminating on signal 11
If the filesystem is full and the nodelock file can not get written to then
you should get an ANR9627E message stating "Cannot access node license lock
file".
If this is not happening then let me know.
David Bohm
TSM server development
(520) 799-5082 T/L 321-5082
email - [EMAIL PROTECTED]
Richa
There are a few possibilities that I can think of.
First check in your license file for the line that look like this
ProductVersion=3.7
Make sure it shows 3.7, you can not use license files for a different
version.
Another thing to check is I notice in your output
Server date/time: 01/01/70
T
The answer is yes and no. I won't go into all of the details, but if this
change is made you will get messages not only for the licenses you
are attempting to register but you will also get them for any invalid
license in the nodelock file. The only way then to get rid of those
messages would be
My best guess without additional details being given is you have different
reclamation
thresholds for each of these storage pools. The difference is probably
expired or
deleted files in an aggregate on the copy storage pool that are not in the
primary
pool because reclamation and aggregate recons
Just use
REGISTER LIC MANAGEDSYSLAN 45
The syntax was changed after the manuals were published and
documented in the readme file.
David Bohm
TSM server development
(520) 799-5082 T/L 321-5082
email - [EMAIL PROTECTED]
Tim Brown <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/15/2001 11:02:56 AM
Each of these threads will have at least one other thread associated with
it.
You should find an admin command thread that has a ptid= the thread number
of the session thread. What this session thread is waiting for is more
output
from that command thread. You should probably open a problem reco
This sounds like APAR IC27402, or IC27929 for the V4 AIX server.
David Bohm
TSM server development
email - [EMAIL PROTECTED]
Hernando Ramirez <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/27/2001 07:50:37
AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor
I tried posting this a few days ago, but because of a change in my email address
I was not authorized. Trying again..
>Is there a maximum recovery log size of 4 gig in the version of ADSM we
>are running?
There is a limitation of 5.3G. You can use the undocumented command SHOW LVMFA
to
>> This thread reminds me of a question I've been meaning to ask. I have
>> several SQL queries that run as cron jobs to keep me current on system
>> status. About two months ago the server started crashing every Sunday at the
>> same exact time. The problem was traced to an automated query that r
13 matches
Mail list logo
