That's what we were assuming, but we found this article from IBM:
http://www-01.ibm.com/support/docview.wss?uid=swg21389352
It clearly states (v6.1, 6.2, 6.3) that you can pin the log and crash the
server.
Rick
From: Shawn DREW <shawn.drew AT US.BNPPARIBAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 08/26/2013 03:00 PM
Subject: Re: tsm v6 - show logpin
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
I can't find my reference anymore but I remember reading somewhere that
due to the fundamental change in the database, pinning the log in tsm6 is
not an issue anymore. Consider that a possibility in your search
Regards,
Shawn
________________________________
Shawn Drew
> From: ADSM-L AT VM.MARIST DOT EDU [mailto:ADSM-L AT VM.MARIST DOT EDU]
> Sent: Monday, August 26, 2013 2:45 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] tsm v6 - show logpin
>
> q) Is there a "show logpin" in TSM v6?
>
> In our adventure to TSM v6 I found that issuing a "show logpin" returns
that it
> is a unknown command. If I look in the Problem Determination Guide
(v6.2
> and v6.3) it list "show logpin" as one of the show cmds.
>
> q) How to identify sessions that are pinning the log in v6.
>
> We have a script we run against our TSM v5 servers that checks for the
log
> being 75% full and issues a "show logpin cancel". Is there a way to
identify
> pinning sessions in v6 so I can implement a check like this?
>
> Thanks
>
> Rick
>
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or
partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas
RCC, Inc.
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
|
