InsertSlashHack missing dirDelimter - on W2K node with 5.1.5.9

Hi together, I searched adsm.org but found no useful help for "InsertSlashHack" ... Has anyone seen this error before? This happens since a few days on a W2K-Node with 5.1.5.9 (TSM-Server 5.2.2.1 on z/OS). The admin of the W2K Node told us that there is no file Ri... On that clien

Weird Select Behavior

Hi everyone. I've been struggling with this for a time now and can't seem to come up with an answer on my own. I hope one of you might be able to explain it to me. When I run a simple sum select statement from the physical_mb field of the occupancy table I get one answer. However, when I run the s

Agent for Oracle on Windows?

Are there any plans for an Oracle TDP for Windows? Fred Johanson ITSM Administrator University of Chicago 773-702-8464

Re: Agent for Oracle on Windows?

Been around awhile! David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 08/05/04 02:19PM >>> Are there any plans for an Oracle TDP for Windows?

Re: Agent for Oracle on Windows?

Try this. http://publib.boulder.ibm.com/tividd/td/DPON/SH26-4113-02/en_US/HTML/anow0005.htm [EMAIL PROTECTED] fred johanson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/05/2004 01:19 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL

Re: Weird Select Behavior

Easy! With the first statement, you're converting physical_mb to TB (roughly, 1048576 is the "right" value), then adding them up. For the 2nd one, you're converting to TB, cutting it off at the 10GB level (the cast to decimal(6,2) does that), then adding them up. So the 2nd one is dropping

Re: Weird Select Behavior

Nicholas, You the man! Works like a charm. I knew it had to be simple. Thank you. [EMAIL PROTECTED] Nicholas Cassimatis <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/05/2004 01:37 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To

volhistory error

TSM currently at 5.2.2.2 on z/OS 1.4 The volume history file shows a backupset on tape 101334 but a query or delete for backupset returns nothing. How do I get rid of the entry in the volume history? tsm: ADSM>q volh type=backupset Date/Time: 04/03/2003 16:20:36 Volume Type: BACKUPSET

Re: volhistory error

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Slag, Jerry B. >TSM currently at 5.2.2.2 on z/OS 1.4 >The volume history file shows a backupset on tape 101334 but a query or >delete for backupset returns nothing. >How do I get rid of the entry in the volume history? > >tsm: AD

Upgrade media

I'm preparing to upgrade TSM server from 5.1.3.6 to 5.2.3.1. I have a 5.2.2.0 cd, plus the 5.2.3.0 and 5.2.3.1 downloads. Is that sufficient media or do I have to have an earlier 5.2.?.0 cd?

Re: volhistory error

tsm: ADSM>q backupset * * todate=04/04/2003 ANR2020E QUERY BACKUPSET: Invalid parameter - TODATE. ANS8001I Return code 3. tsm: ADSM>q backupset * * begindate=04/03/2003 ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>q backupset * * enddate=04/04/2

MAX size for disk volume

Hi everybody. I searched over ADSM.ORG and find out that there is no limitation for volume size. But may be somebody can explain to me what am I doing wrong? The message I have got is : # ./dsmfmt -g -data /vol1/vol1.dsm 120 File size for /vol1/vol1.dsm must be less than 68,589,453,312 bytes I h

Re: Upgrade media

More information needed. What OS platform is your TSM server running under? -- Mark Stapleton >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of David E Ehresman >Sent: Thursday, August 05, 2004 2:08 PM >To: [EMAIL PROTECTED] >Subject: Upgrade med

Re: Upgrade media

AIX 5.1 64 bit >>> [EMAIL PROTECTED] 8/5/2004 3:38:37 PM >>> More information needed. What OS platform is your TSM server running under? -- Mark Stapleton >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of David E Ehresman >Sent: Thursday, August 0

Re: volhistory error

I had a few backupset volumes that had the same problem and working with TSM support I was able to delete the volhist volume. In my case something happened to allow the backupset to be deleted but all the volumes with it didn't go away. It has been a few years since I've seen this. You might

FC 3590E1A per HBA

Hi, I saw somewhere in the list that IBM recommends two 3590 FC drives per HBA. Is this published somewhere or just "word of mouth"? If there is a planning document that discusses this I would be interested in the link. I currently have 16 drives across four 6228 HBA's on an AIX box. I've seen som

TSM 5.2 Upgrade and Maintenance releases

I want to upgrade our TSM servers next week to v5.2.3 from 4.2.4.1. I was going to install TSM server 5.2 first and then the 5.2.3 maintenance release over the top. What file is it that needs to be moved/renamed to stop the database being upgraded after v5.2 is installed so I can do a manual upg

Ruby TSM dsmadmc interface

Hi all I've been switching from perl to the ruby programming language for my scripting as ruby is nicer in many ways. In order to use this with TSM I have ported Owen Crow's Adsm.pm perl module. Some of you might find it useful. Steve. ==

Re: MAX size for disk volume

Yuri, AIX JFS1 filesystems have a maximum file size limit of 64G. The filesystem output you've given looks JFS1 so I'll assume that /vol1 is JFS1. If you recreate the filesystem as JFS2 you should have better luck. Regards, Dave Smith Business Services and Resources -Original Message