>>>substring=${bigstring:0,2}
I wrote:
>>What shell are you using? This does not work in Bourne, C, Korn or Bourne
>>Again shell as far as I can tell.
"Doyle, Patrick" <[EMAIL PROTECTED]> wrote:
>BASH
Aha. I checked again and it does work in bash - but the correct syntax
is ${bigstring:0:2}
"Doyle, Patrick" <[EMAIL PROTECTED]> wrote:
>Have you tried this with your shell?
>
>substring=${bigstring:0,2}
>
>
>${parameter:offset}
>${parameter:offset:length}
>Expands to up to length characters of parameter starting at the character
>specified by offset. If length is omitted, expands to the
Christian Demnitz <[EMAIL PROTECTED]> wrote:
>is there any way, to get data from tsmdatabase directly into a mysql db?
>like via odbc to ms access?
>
>i want to generat a report with a mysql db!
I do this regularly, using the same technique you would use to load
data directly from TSM into an Exc
>>I need to inspect a variable (the node name) for the first 2 characters
>>= LT or the first 5 characters = CLELT to do the script line otherwise
>>don't do the sscript line.
>It's stupid that UNIX doesn't have a simple way of doing this! Try:
>
>substring = `echo $variable | cut -c 1-2`
>if [[
>My understanding of Mike´s sentences per se is:
>The schedules did not run untill 02:41.
>The schedules may have run later,
>but Mike is either not sure about or not exact at this point.
>
>Your understanding is: the schedules did run at 02:41.
>Is this fully clear from Mike´s sentences?
Normal
Steve Harris <[EMAIL PROTECTED]> wrote:
>To upgrade a Solaris package you have to delete it and then install
>the new one. If those files were left in the usual place, they would
>be deleted with the uninstall and you'd lose your customisations.
>By linking to /usr/bin they are left alone.
Fine,
>Just checked my client install. Solaris client v5.2.0.
>
>Same thing, dsm.opt and dsm.sys link to /usr/bin/ respective names.
>
>Don't know why that choice was made.
We never even understood why the choice was made to store
configuration text files in a bin directory to begin with.
(As part of
"Gable, Josh" <[EMAIL PROTECTED]> wrote:
>> Has anyone seen the following error? I am getting it while trying to run
>> an incremental backup on an SGI client node. We are not using an
>> include/exclude file, and there are no exclude statements in dsm.sys. Any
>> assistance would be greatly ap
Bernd Schemmer <[EMAIL PROTECTED]> wrote:
>I'm writing some scripts using dsmadmc with the select command to
>retrieve data from the TSM database. At this time I've to use various
>grep commands to remove the headers and footers from the dsmadmc output.
>
>Is it possible to suppress those headers
Thomas Denier <[EMAIL PROTECTED]> wrote:
>We have been having problems with a Solaris client since we 'upgraded' its
>client code from 4.1.2.0 to 5.1.6.0. The 'query node' command reports the
>Solaris level as 5.8. The server is at 5.1.6.2 and runs under OS/390.
>
>The client error log is showing
Justin Bleistein <[EMAIL PROTECTED]> wrote:
>any alternatives to running: "dsmserv" via batch mode with the:
>
>dsmadmc -id=login -pass=password syntax...
>
>I mean it's passwords in clear text so all someone has to do is cat that
>file and your exposed... Any ideas on how to automate the client-s
>Anyone here has any experience with TSM on Red Hat Linux!?
Yes, we run it on many Linux machines here with no problem.
Note that TSM clients prior to 5.1.5 do not have native support
for "ext3" filesystems. However, you can get around that by
using a VIRTUALMOUNTPOINT statement in your dsm.sys
Mark Stapleton <[EMAIL PROTECTED]> wrote:
>> For example: my*file.txt
>
>Well, there's part of the problem there. '*' is an invalid character for
>a filename in any UNIX system I've ever heard of. Such filenames appear
>from time to time when using misconfigured moves and copies.
'*' is a perfect
>Is anyone using some sort of script to verify their backups by a byte total?
>I've got scripts to monitor events and the dsmerror and act logs but still
>miss files.
Some time ago we designed a Bourne shell script to do backup/restore
verification for Unix systems, using a verification machine wi
"Chetan H. Ravnikar" <[EMAIL PROTECTED]> wrote:
>anyone seen this error, when I am trying to backup an NFS directory on a
>client I get this error. Is there a limitation within TSM w.r.t
>length of file-names
>
>I am on 4.2.20 client (solaris-2.8) talking to a 4.2.20 server (sol-2.8)
>Any info is
Bob Booth - UIUC <[EMAIL PROTECTED]> wrote:
>Has anyone heard when an ITSM client will be available for Solaris 9?
>
>We tried to install the latest patch level, and it failed.
Do you mean the install failed? The Solaris install package, as built
by IBM/Tivoli, will reject a Solaris 9 system.
16 matches
Mail list logo
