Re: Réf. : upgrade 4.2.0.0 to 5.1.5.0
On Thursday 27 March 2003 22:56, Steve Roder wrote: Hi Dave I just went from 4.2.1.7 to 5.1.6.3. I had to install the following versions : 5.1.5.0 from cd to get the licencing filesets 5.1.6.0 5.1.6.3 I did an upgrade form 3.1.2.42 to 5.1.6.2 using the same steps a month ago and it went smoothly. Upgrading TSM is pretty easy as long as you have a base level from a cd. I did a similar upgrade from 4.2.2.0 to 5.1.6.2, and the only issue I am seeing is this ugly output from q pr: 279 Space Reclamation Offsite Volume(s) (storage pool COPYPOOL), Moved Files: 402380, Moved Bytes: 67,865,049,850, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 512,635~Current input volume: A00480.~Current output volume: A01551.\ It should look like this: 279 Space Reclamation Offsite Volume(s) (storage pool COPYPOOL), Moved Files: 402380, Moved Bytes: 67,865,049,850, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 512,635 Current input volume: A00480. Current output volume: A01551. Anyone else seen this, and know if there is a fix? But I don't want it to be fixed :) For me it's a feature. I parse the command select status from processes in a custom web-reporting tool written in perl. If I replace ~ with a new line (br) I have a perfect output. Stef -- [EMAIL PROTECTED] Using Linux as bandwidth manager http://www.docum.org/ #lartc @ irc.oftc.net
Réf. : upgrade 4.2.0.0 to 5.1.5.0
Hi Dave I just went from 4.2.1.7 to 5.1.6.3. I had to install the following versions : 5.1.5.0 from cd to get the licencing filesets 5.1.6.0 5.1.6.3 I did an upgrade form 3.1.2.42 to 5.1.6.2 using the same steps a month ago and it went smoothly. Upgrading TSM is pretty easy as long as you have a base level from a cd. Guillaume Gilbert CGI Canada David Cornwell [EMAIL PROTECTED]@VM.MARIST.EDU on 2003-03-27 15:58:42 Veuillez répondre à ADSM: Dist Stor Manager [EMAIL PROTECTED] Envoyé par : ADSM: Dist Stor Manager [EMAIL PROTECTED] Pour : [EMAIL PROTECTED] cc : Objet : upgrade 4.2.0.0 to 5.1.5.0 Can I do this in one jump; just go straight to 5.1.5.0 or do I have to go through some intermediate patches??? Dave Cornwell Systems Engineer Matsushita Appliance Co. Danville, KY
Re: Réf. : upgrade 4.2.0.0 to 5.1.5.0
I second that. I went from 4.2.1.9 to 5.1.6.3 in exactly the same steps. Went very smoothly. Didn't take as long as I figured, either with the upgradedb stuff. Guillaume Gilbert [EMAIL PROTECTED]To: [EMAIL PROTECTED] ARDINS.COMcc: Sent by: ADSM: Dist Subject: Réf. : upgrade 4.2.0.0 to 5.1.5.0 Stor Manager [EMAIL PROTECTED] 03/27/2003 03:31 PM Please respond to ADSM: Dist Stor Manager Hi Dave I just went from 4.2.1.7 to 5.1.6.3. I had to install the following versions : 5.1.5.0 from cd to get the licencing filesets 5.1.6.0 5.1.6.3 I did an upgrade form 3.1.2.42 to 5.1.6.2 using the same steps a month ago and it went smoothly. Upgrading TSM is pretty easy as long as you have a base level from a cd. Guillaume Gilbert CGI Canada David Cornwell [EMAIL PROTECTED]@VM.MARIST.EDU on 2003-03-27 15:58:42 Veuillez répondre à ADSM: Dist Stor Manager [EMAIL PROTECTED] Envoyé par : ADSM: Dist Stor Manager [EMAIL PROTECTED] Pour : [EMAIL PROTECTED] cc : Objet : upgrade 4.2.0.0 to 5.1.5.0 Can I do this in one jump; just go straight to 5.1.5.0 or do I have to go through some intermediate patches??? Dave Cornwell Systems Engineer Matsushita Appliance Co. Danville, KY
Re: Réf. : upgrade 4.2.0.0 to 5.1.5.0
Hi Dave I just went from 4.2.1.7 to 5.1.6.3. I had to install the following versions : 5.1.5.0 from cd to get the licencing filesets 5.1.6.0 5.1.6.3 I did an upgrade form 3.1.2.42 to 5.1.6.2 using the same steps a month ago and it went smoothly. Upgrading TSM is pretty easy as long as you have a base level from a cd. I did a similar upgrade from 4.2.2.0 to 5.1.6.2, and the only issue I am seeing is this ugly output from q pr: 279 Space Reclamation Offsite Volume(s) (storage pool COPYPOOL), Moved Files: 402380, Moved Bytes: 67,865,049,850, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 512,635~Current input volume: A00480.~Current output volume: A01551.\ It should look like this: 279 Space Reclamation Offsite Volume(s) (storage pool COPYPOOL), Moved Files: 402380, Moved Bytes: 67,865,049,850, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 512,635 Current input volume: A00480. Current output volume: A01551. Anyone else seen this, and know if there is a fix? My tivoli filesets: tivoli.tsm.devices.aix5.rte 5.1.6.2 tivoli.tsm.license.aix5.rte64 5.1.5.0 tivoli.tsm.license.cert 5.1.5.0 tivoli.tsm.msg.en_US.devices 5.1.6.0 tivoli.tsm.msg.en_US.server 5.1.6.0 tivoli.tsm.msg.en_US.webhelp 5.1.6.0 tivoli.tsm.server.aix5.rte64 5.1.6.2 tivoli.tsm.server.com 5.1.6.0 tivoli.tsm.server.webadmin5.1.6.0 Thanks, Steve Roder, University at Buffalo HOD Service Coordinator VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) TSM/ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564)
