Actually, yes it can be "pinned" - If you go through the ADSM-L archives, you will see my same question/discussion about this, from 2011, including assistance from Dave Canan of IBM.
The original post is here: http://adsm.org/lists/html/ADSM-L/2011-04/msg00188.html But if you simply go to the search page (http://adsm.org/lists/html/ADSM-L/) and put in "logpinned", you will see the rest of the discussion/answers. On Mon, Aug 26, 2013 at 2:59 PM, Shawn DREW <[email protected]>wrote: > 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: [email protected] [mailto:[email protected]] > > Sent: Monday, August 26, 2013 2:45 PM > > To: [email protected] > > 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. > -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
