ADSM-L

Re: [ADSM-L] TSM v5 SQL help

2010-11-18 12:56:05
Subject: Re: [ADSM-L] TSM v5 SQL help
From: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 18 Nov 2010 12:55:17 -0500
There is an efix available for this.  You need to get a PMR opened and
escalated.  They told me 5.5.5.1 isn't due until mid/late Q1

Regards,
Shawn
________________________________________________
Shawn Drew




Internet
deehre01 AT LOUISVILLE DOT EDU

Sent by: ADSM-L AT VM.MARIST DOT EDU
11/18/2010 10:13 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] TSM v5 SQL help






The following script worked at TSM v5.5.3.0:

Q_OFFLINE  1      select cast(drives.library_name as char(6)) as "LIB",
-
           5       cast(drives.drive_name as char(10)) as "DRIVE", -

           10      cast(source_name as char(15)) as "PATH", -

           15      cast(drives.online as char(5)) as "DRIVE ONLINE?", -

           20      cast(paths.online as char(5)) as "PATH ONLINE?" -

           25      from drives,paths where -

           30      drives.library_name=paths.library_name and -

           35      drives.drive_name=paths.destination_name -

           40      and (paths.online='NO' or drives.online='NO')


At TSM v5.5.5.0 it produces the following error:

tsm: LIBMGR>run q_offline
ANR2914E SQL identifier token 'DRIVES.LIBRARY_NAME' is too long; name
or
component exceeds 18 characters.

                     |

............V..................................................
         select cast(drives.library_name as char(6)) as "LIB",
cast(driv

ANR1463E RUN: Command script Q_OFFLINE completed in error.
ANS8001I Return code 3.

Any idea on how to fix this?

David



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

<Prev in Thread] Current Thread [Next in Thread>