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- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Yury Us Sent: Friday, August 06, 2004 5:36 AM To: [EMAIL PROTECTED] Subject: 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 have on that filesystem 136Gb free space. The computer is F50, AIX5.2 ADSMserver 5.2.0. No clients yet. I created filesystem as follows: File system name/vol1 NEW mount point[/vol1] SIZE of file system Unit Size 512bytes + * Number of units[286261248] # Mount GROUP[] Mount AUTOMATICALLY at system restart? yes + PERMISSIONS read/write + Mount OPTIONS [] + Start Disk Accounting? no + Fragment Size (bytes) 4096 Number of bytes per inode 131072 Compression algorithm no Large File Enabled true Allocation Group Size (MBytes) 64 Any idea would be greatly appreciated. Yuriy Us.
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.
===
class Tsm
=begin
=Tsm
A ruby class to interface with the dsmadmc command
based on the perl Adsm package by Owen Crow
==Methods
Tsm.new("username","password")
The new method creates a TSM object. Username and password are optional, and
are the TSM username and password to be usd for this session. If these are
not supplied, the user's HOME environment variable is used to locate a file named
.dsmrc. See the Files section below.
Dsmadmc("c1","c2","c3"...)
When the Dsmadmc method is invoked on the Tsm object the string parameters passed are
joined with a space and the resulting string is passed as a command to the dsmadmc
command. The output of the command is stripped of TSM header and footer information,
continuation lines and blank lines, and returned as a single string to the caller.
The TSM return code is placed into the rc instance variable
rc
This method returns the TSM return code from the last executed command
Dsmconsole {|line| ...}
This method opens a TSM console session and passes returned lines to the block.
No processing is done on the returned lines. Interrupt is trapped.
==Files
tsm.rb - source
.dsmrc optionally contains lines of the form
ID username
PA password
The first line of each type found is used to supply the TSM Id and Password
that is used when invoking the dsmadmc command.
== Examples
require "tsm"
x = Tsm.new("someadmin","somepassword")
puts "#{x.Dsmadmc("-commad","q sess")} rc=#{x.rc}"
puts "#{x.Dsmadmc("q mount")} rc=#{x.rc}"
x.Dsmconsole { |l| puts l}
=end
attr_accessor(:rc)
def initialize(*args)
@id=args.shift
@pa=args.shift
@rc=0
if (@id.nil? or @pa.nil?) and not(ENV['HOME'].nil?)
dsmrcfile=ENV['HOME'] + "/.dsmrc"
begin
mode = File.stat(dsmrcfile).mode%32678
uid = File.stat(dsmrcfile).uid
#mode must be 600 or 400
raise "Permissions of #{dsmrcfile} are #{sprintf("%o",mode)} and should be
octal 600 or 400" unless ("477".oct & mode) != "400".oct
raise "#{dsmrcfile} must be owned by you" unless uid == Process.uid
File.open(ENV['HOME'] + "/.dsmrc").each_line do |l|
if @id.nil? && l =~ /^ID\s+(.*)$/
@id = $1
end
if @pa.nil? && l =~ /^PA\s+(.*)$/
@pa = $1
end
end
rescue Errno::ENOENT # ./dsmrc file does not exist
prompt_user
end
if @id.nil? || @pa.nil?
prompt_user
end
end
end
def prompt_user
if $stdin.isatty
# an interactive terminal
stty = `stty`
if @id.nil?
print "Enter your user id: "
@id = $stdin.gets.chomp
end
if @pa.nil?
# Turn off echoing of characters for the password entry (only in UNIX
`stty -echo`
print "Enter password for [EMAIL PROTECTED]: "
@pa=$stdin.gets.chomp
`stty echo` if stty =~ /[^-]echo\b/
print "\n"
end
else
# Last effort is to read the ID and password from stdin
@id=$stdin.gets.chomp
@pa=$stdin.gets.chomp
end
end
def Dsmadmc(*args)
# dsmadmc accepts a list as its argument. The list is joined with spaces
# to form the command submitted to tsm
command = args.join(" ")
output = String.new("") # output of dsmadmc command
@rc = 0
flag = false
IO.popen("dsmadmc [EMAIL PROTECTED] [EMAIL PROTECTED] #{command}
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 upgrade later? I only want to do one upgrade but can't find any information on the IBM support website. Thanks, Gordon Woodward -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
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 some discussions and math about throughput etc., but there should be some rule of thumb that can guide me to whether I have a "reasonable' configuration or not. HBA's aren't cheap so I'd hate to require 8 of them. Thanks, Rod Hroblak ADP __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail
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 want to open a call with support just in case. "Slag, Jerry B." <[EMAIL PROTECTED]> wrote: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/2003 ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>q backupset * * begindate=04/02/2003 enddate=04/04/2003 ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. My help says a wildcard is valid in the del backupset command - however, I still get a no match message. tsm: ADSM>del backupset js11 js11bkupst ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>del backupset js11 js11bkupst begindate=04/02/2003 enddate=04/04/2003 whereret=10 ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>del backupset * * begindate=04/02/2003 enddate=04/04/2003 ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: Thursday, August 05, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: 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: ADSM>q volh type=backupset > > Date/Time: 04/03/2003 16:20:36 > Volume Type: BACKUPSET > Backup Series: >Backup Operation: > Volume Seq: 1 > Device Class: MAGSTAR > Volume Name: 101334 > Volume Location: > Command: gen backupset js11 js11bkupst devclass=magstar ret=10 > >tsm: ADSM>q backupset * * >ANR2034E QUERY BACKUPSET: No match found using this criteria. >ANS8001I Return code 11. Try QUERY BACKUPSET * * TODATE=04/04/2003 >tsm: ADSM>del backupset * * >ANR2034E DELETE BACKUPSET: No match found using this criteria. >ANS8001I Return code 11. A look at HELP DELETE BACKUPSET shows that wildcards are not supported. (If they were, it would say so, as it does for the QUERY BACKUPSET command.) The proper syntax for the command would be DELETE BACKUPSET >tsm: ADSM>q vol 101334 >ANR2034E QUERY VOLUME: No match found using this criteria. >ANS8001I Return code 11. Backupset tapes don't show up in a QUERY VOLUME command; only tapes that belong to a storage pool show up with this command. -- Mark Stapleton - Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
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 05, 2004 2:08 PM >To: [EMAIL PROTECTED] >Subject: 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: 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 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? > >
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 have on that filesystem 136Gb free space. The computer is F50, AIX5.2 ADSMserver 5.2.0. No clients yet. I created filesystem as follows: File system name/vol1 NEW mount point[/vol1] SIZE of file system Unit Size 512bytes + * Number of units[286261248] # Mount GROUP[] Mount AUTOMATICALLY at system restart? yes + PERMISSIONS read/write + Mount OPTIONS [] + Start Disk Accounting? no + Fragment Size (bytes) 4096 Number of bytes per inode 131072 Compression algorithm no Large File Enabled true Allocation Group Size (MBytes) 64 Any idea would be greatly appreciated. Yuriy Us.
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/2003 ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>q backupset * * begindate=04/02/2003 enddate=04/04/2003 ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. My help says a wildcard is valid in the del backupset command - however, I still get a no match message. tsm: ADSM>del backupset js11 js11bkupst ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>del backupset js11 js11bkupst begindate=04/02/2003 enddate=04/04/2003 whereret=10 ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>del backupset * * begindate=04/02/2003 enddate=04/04/2003 ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: Thursday, August 05, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: 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: ADSM>q volh type=backupset > > Date/Time: 04/03/2003 16:20:36 > Volume Type: BACKUPSET > Backup Series: >Backup Operation: > Volume Seq: 1 >Device Class: MAGSTAR > Volume Name: 101334 > Volume Location: > Command: gen backupset js11 js11bkupst devclass=magstar ret=10 > >tsm: ADSM>q backupset * * >ANR2034E QUERY BACKUPSET: No match found using this criteria. >ANS8001I Return code 11. Try QUERY BACKUPSET * * TODATE=04/04/2003 >tsm: ADSM>del backupset * * >ANR2034E DELETE BACKUPSET: No match found using this criteria. >ANS8001I Return code 11. A look at HELP DELETE BACKUPSET shows that wildcards are not supported. (If they were, it would say so, as it does for the QUERY BACKUPSET command.) The proper syntax for the command would be DELETE BACKUPSET >tsm: ADSM>q vol 101334 >ANR2034E QUERY VOLUME: No match found using this criteria. >ANS8001I Return code 11. Backupset tapes don't show up in a QUERY VOLUME command; only tapes that belong to a storage pool show up with this command. -- Mark Stapleton
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
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: ADSM>q volh type=backupset > > Date/Time: 04/03/2003 16:20:36 > Volume Type: BACKUPSET > Backup Series: >Backup Operation: > Volume Seq: 1 >Device Class: MAGSTAR > Volume Name: 101334 > Volume Location: > Command: gen backupset js11 js11bkupst devclass=magstar ret=10 > >tsm: ADSM>q backupset * * >ANR2034E QUERY BACKUPSET: No match found using this criteria. >ANS8001I Return code 11. Try QUERY BACKUPSET * * TODATE=04/04/2003 >tsm: ADSM>del backupset * * >ANR2034E DELETE BACKUPSET: No match found using this criteria. >ANS8001I Return code 11. A look at HELP DELETE BACKUPSET shows that wildcards are not supported. (If they were, it would say so, as it does for the QUERY BACKUPSET command.) The proper syntax for the command would be DELETE BACKUPSET >tsm: ADSM>q vol 101334 >ANR2034E QUERY VOLUME: No match found using this criteria. >ANS8001I Return code 11. Backupset tapes don't show up in a QUERY VOLUME command; only tapes that belong to a storage pool show up with this command. -- Mark Stapleton
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 Backup Series: Backup Operation: Volume Seq: 1 Device Class: MAGSTAR Volume Name: 101334 Volume Location: Command: gen backupset js11 js11bkupst devclass=magstar ret=10 tsm: ADSM>q backupset * * ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>del backupset * * ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: ADSM>q vol 101334 ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. Jerry Slag Information Technology Department State of North Dakota 600 East Boulevard Avenue Dept 112 Bismarck, ND 58505-0100 phone: (701) 328-4350 fax: (701) 328-3000 [EMAIL PROTECTED]
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 [EMAIL PROTECTED] cc Subject 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 lots of data - any filesystem not over 10GB of data really isn't being counted at all. I think this is what you're looking for: select cast(sum(physical_mb)/100 as decimal(6,2)) as "Total TB" from occupancy That one sums up physical_mb from occupancy, then divides it by the 10 for TB, then casts it to the format you want. Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. Curtis Stewart <[EMAIL PROTECTED] AWSON.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Weird Select Behavior 08/05/2004 01:38 PM Please respond to "ADSM: Dist Stor Manager" 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 same select, but cast the result as decimal I get a wildly different result. I expected it to just format the output and get rid of some of the trailing decimal places. I looked at the syscat.columns occupancy stuff and it says the physical_mb field is decimal, so I don't understand the behavior. Obviously, there's something I just don't know about the select behavior. Here are the two scripts and their output. Any help is appreciated. tsm: MSPTSM01COL>select sum(physical_mb/100) from occupancy Unnamed[1] - 70.2977500 tsm: MSPTSM01COL> tsm: MSPTSM01COL>select sum(cast (physical_mb/100 as decimal(6,2))) as "Total TB" from occupancy Total TB - 66.17 tsm: MSPTSM01COL> [EMAIL PROTECTED]
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 lots of data - any filesystem not over 10GB of data really isn't being counted at all. I think this is what you're looking for: select cast(sum(physical_mb)/100 as decimal(6,2)) as "Total TB" from occupancy That one sums up physical_mb from occupancy, then divides it by the 10 for TB, then casts it to the format you want. Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. Curtis Stewart <[EMAIL PROTECTED] AWSON.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Weird Select Behavior 08/05/2004 01:38 PM Please respond to "ADSM: Dist Stor Manager" 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 same select, but cast the result as decimal I get a wildly different result. I expected it to just format the output and get rid of some of the trailing decimal places. I looked at the syscat.columns occupancy stuff and it says the physical_mb field is decimal, so I don't understand the behavior. Obviously, there's something I just don't know about the select behavior. Here are the two scripts and their output. Any help is appreciated. tsm: MSPTSM01COL>select sum(physical_mb/100) from occupancy Unnamed[1] - 70.2977500 tsm: MSPTSM01COL> tsm: MSPTSM01COL>select sum(cast (physical_mb/100 as decimal(6,2))) as "Total TB" from occupancy Total TB - 66.17 tsm: MSPTSM01COL> [EMAIL PROTECTED] <><><>
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 PROTECTED] cc Subject 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? Fred Johanson ITSM Administrator University of Chicago 773-702-8464 ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
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
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 same select, but cast the result as decimal I get a wildly different result. I expected it to just format the output and get rid of some of the trailing decimal places. I looked at the syscat.columns occupancy stuff and it says the physical_mb field is decimal, so I don't understand the behavior. Obviously, there's something I just don't know about the select behavior. Here are the two scripts and their output. Any help is appreciated. tsm: MSPTSM01COL>select sum(physical_mb/100) from occupancy Unnamed[1] - 70.2977500 tsm: MSPTSM01COL> tsm: MSPTSM01COL>select sum(cast (physical_mb/100 as decimal(6,2))) as "Total TB" from occupancy Total TB - 66.17 tsm: MSPTSM01COL> [EMAIL PROTECTED]
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 client. Also the Objects ...\SourceSafe\vss_dotnet\data\u are not files - these objects are directories. >From the dsmerror.log: - Sorry - the admin installed the client in german language :-( 03.08.2004 21:40:53 ANS4037E Datei '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\n' während der Verarbeitung geändert. Die Datei wurde übersprungen. 03.08.2004 21:40:53 ANS1228E Senden des Objekts '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\u' fehlgeschlagen 03.08.2004 21:40:53 ANS4037E Datei '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\u' während der Verarbeitung geändert. Die Datei wurde übersprungen. 03.08.2004 21:40:54 ANS1228E Senden des Objekts '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\v' fehlgeschlagen 03.08.2004 21:40:54 ANS4037E Datei '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\v' während der Verarbeitung geändert. Die Datei wurde übersprungen. 03.08.2004 21:40:54 ANS1228E Senden des Objekts '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\w' fehlgeschlagen 03.08.2004 21:40:54 ANS4037E Datei '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\w' während der Verarbeitung geändert. Die Datei wurde übersprungen. 03.08.2004 21:40:54 ANS1228E Senden des Objekts '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\y' fehlgeschlagen 03.08.2004 21:40:54 ANS4037E Datei '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\y' während der Verarbeitung geändert. Die Datei wurde übersprungen. 03.08.2004 21:40:54 ANS1228E Senden des Objekts '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\z' fehlgeschlagen 03.08.2004 21:40:54 ANS4037E Datei '\\svnue510\d$\E44\Projekte\KonfigDB.Net\SourceSafe\vss_dotnet\data\z' während der Verarbeitung geändert. Die Datei wurde übersprungen. 03.08.2004 21:43:09 WARNING: InsertSlashHack missing dirDelimter, continuing... 03.08.2004 21:43:11 WARNING: InsertSlashHack missing dirDelimter, continuing... 03.08.2004 21:43:20 WARNING: InsertSlashHack missing dirDelimter, continuing... 03.08.2004 21:43:21 ANS1228E Senden des Objekts '\\svnue510\d$\E44\Projekte\SWS\RiÌÌÌ' fehlgeschlagen 03.08.2004 21:43:21 ANS1304W Aktives Objekt nicht gefunden Kind regards Joachim Stumpf
