Does anybody have the APAR number for the PASSEXP problem so I can track it? Thanks
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Matthew McGeary Sent: Monday, June 09, 2014 10:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 7.1 upgrade aftermath I don't know if it's documented anywhere but that hit us as well. That, and our datamovers aren't purging the c:\windows\temp directory after a backup operation. Ah, the joys of being on the bleeding edge. Matthew McGeary Technical Specialist PotashCorp - Saskatoon 306.933.8921 From: "Gee, Norman" <norman....@lc.ca.gov> To: ADSM-L@VM.MARIST.EDU Date: 06/05/2014 04:53 PM Subject: [ADSM-L] TSM 7.1 upgrade aftermath Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> I am not sure if this is documented, but after I upgraded my TSM servers to 7.1 code. Somehow the passexp setting for all of my TDP nodes got change from 0 (zero, never expire) to blank, which means they now will take the server default settings. Where is this documented? Other issues are a bunch of new warning messages during migration of file device class.
