Volume became mountablenotinlib after label and checkin

UltraScalable Tape Library 3584-L52, SCSI Sequential device with driver version 6.0.4.2 Thanks, Regards, Zareyna Salim No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.10.10/908 - Release Date: 7/19/2007 6:10 PM

Re: Cannot write to Tape (ANR8302E)

Hi, what is the platform of your client os? Thx zareyna - original message - Subject:Re: [ADSM-L] Cannot write to Tape (ANR8302E) From: hshahizul [EMAIL PROTECTED] Date: 13/07/2007 2:07 am Thanks. Tapes were label during checkin. Few scratch tape also available

Upgrading TSM server 5.2 to 5.3

Hi all, Just a quick one.. Is there going to be a problem if the TSM server will be upgrading to 5.3.5 but the clients and Storage Agent remain to version 5.2.9? Do I need to restart the server after installing TSM for BAC and TSM for SAN? Thanks, Regards, Zareyna Salim

Volume with status mountablenotinlib

Storage Agent 5.2.9 Tape library IBM UltraScalable Tape Library 3584-L52, SCSI Sequential device with driver version 6.0.4.2 Thanks, Regards, Zareyna Salim No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.1/857

ANR8355E-I/O error has brought the tape from Read Write to Unavailable

help. Thanks, Regards, Zareyna Salim No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.15/847 - Release Date: 6/12/2007 9:42 PM

Re: ANR8355E-I/O error has brought the tape from Read Write to Unavailable

as there was no problem with the backup only after 25 May. Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Boyer Sent: Wednesday, June 13, 2007 8:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANR8355E-I/O

ANS2600S ANS151

this issue. Thanks, Regards, Zareyna Salim Technical Consultant ADR Malaysia Level 40, Tower 2, PETRONAS Twin Tower Kuala Lumpur City Centre 50088 Kuala Lumpur Malaysia Tel: +603 2168 4282 Fax: +603 2168 4201 Mobile: +6012 3200 258 website : www.adr-group.net

Re: ANR2716E Schedule prompter was not able to contact client

/dsmerror.log errorlogretention 30 D commrestartduration 60 commrestartinterval 15 compression yes Thanks, Regards, Zareyna Salim Technical Consultant ADR Malaysia Level 40, Tower 2, PETRONAS Twin Tower Kuala Lumpur City Centre 50088 Kuala Lumpur Malaysia Tel

ANR2716E Schedule prompter was not able to contact client

10.200.209.11 lanfreetcpport 1502 Anyone has any ideas of what could be wrong? Thanks, Regards, Zareyna Salim Technical Consultant ADR Malaysia Level 40, Tower 2, PETRONAS Twin Tower Kuala Lumpur City Centre 50088 Kuala Lumpur Malaysia Tel: +603 2168

Compiling db2uext2 on AIX5.3 using gcc

What went wrong actually? Did i miss anything out? Thanks, Regards, Zareyna Salim Technical Consultant

Storage Agent communication fail and could not unload tape

of this problem? My tape drive driver is 6.0.82 and I have disable the CPF. The server run on Windows 2003 Svr and the client is on AIX5.3L and have tape drives defined. Really appreciate if anybody could suggest solutions on the problem above Many Thanks Zareyna Salim

Backup DB2 with TSM

that these servers can run under the same schedule for filesystems backup? Thanks, Regards, Zareyna Salim Technical Consultant

Re: SQL2062N An error occurred while accessing media, Reason Code: 137

Hi, I have encountered this error before. What I did was to key in a new password (same password) on the client and server communication in the ISC. (under Security) and the dsmapipw works. Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto

Re: SQL2062N: Reason code =406,137, 106, Segmentation Fault

, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, July 11, 2006 7:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SQL2062N: Reason code =406 On Jul 11, 2006, at 3:09 AM, zareyna wrote: I

Re: SQL2062N: Reason code =406

the correct dsmapipw? There 2 folders, adsm and adsm64 and I execute the dsmapipw in adsm64. Appreciate if anyone could give me any suggestions to troubleshoot this 2 errors. Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED

SQL2062N: Reason code =406

, LOGRETAIN= YES 4. Backup database : Offline = SUCCESS 5. Backup database : Online= FAILED (receive the above error prompt: SQL2062N) Our database is DB 8.2.4 running on AIX 5.1 Is there any step that I have missed out? Thanks, Regards, Zareyna Salim

Re: ANR8779E: Unable to open drive mt6.0.0.1 error no=170

Hi Ian, The problem above resolved. I managed to get the problem tape drive MT6.0.0.1 working. Just need to restart the tape library and define back all the drives. Thanks all, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED

Re: ANR8779E: Unable to open drive mt6.0.0.1 error no=170

Hi Ian, Regarding the CPF, is it a must to disable the functions? What's the different of having it disable or enable? Where can I get the script to disable the CPF? Do I need to do the rollback on the library clients too? Thanks, Regards, Zareyna Salim Technical Consultant

Re: ANR8779E: Unable to open drive mt6.0.0.1 error no=170

Thanks Ian. Anyway how to disable this function from the AIX server? Is it by issuing this command: chdev -l smc0 -aalt_pathing=no ? Thanks, Regards, Zareyna Salim Technical Consultant -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith

Re: ANR8779E: Unable to open drive mt6.0.0.1 error no=170

should done first or miss? Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, I (Ian) Sent: Thursday, July 06, 2006 4:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANR8779E: Unable to open drive

Backup DB2 using TSM

. Thanks, Regards, Zareyna Salim

Re: Backup DB2 using TSM

Hi Iban, The platform is AIX. Thanks, Regards, Zareyna Salim Technical Consultant -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bernaldo de Quiros, Iban 1 Sent: Tuesday, July 04, 2006 8:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM

Re: ANR8779E: Unable to open drive mt6.0.0.1 error no=170

Ian, The Clients are library client running on AIX5L ver 5.3 and using the LTO2. There 28 AIX clients and 10 Windows clients. Thanks, Regards, Zareyna Salim Technical Consultant -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, I (Ian

ANR8779E: Unable to open drive mt6.0.0.1 error no=170

. Initially the backup run successfully and the error occur after I backup the 3 clients. I have tried to dismount the volume on the mt6.0.0.1 drive but the drive is NOT in idle state. Really hope if anybody knows the solution of this problem Thanks, Regards, Zareyna Salim

Re: ANR8779E: Unable to open drive mt6.0.0.1 error no=170

Hi Ian, I'm using 6.1.2.7. Will try on the solution below. Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, I (Ian) Sent: Wednesday, June 28, 2006 6:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L