I don't know why, but I have had similar problems printing columns that have
type VARCHAR and length 256 or larger.  Sometimes I have been able to get
around it by using the LEFT function like this:

select node_name,hl_name,left(ll_name,50) from backups where etc.

That prints only the first (leftmost) 50 characters from the ll_name field.

OF course, if there really was an item with more than 50 characters in the
name, you would see only the first part of the name in your report.

Hope you can use this,
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************




> -----Original Message-----
> From: Mira Jung [SMTP:mira AT SEAS.UCLA DOT EDU]
> Sent: Wednesday, June 16, 1999 5:42 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      trouble printing certain LL_NAME values
>
> Hi,
>
> I'm having problem with certain values stored in LL_NAME field
> in the backups table.
>
> If I do "select * from backups" within the dsmadmc command,
> the troublesome LL_NAME value will print as show here:
>
>         HL_NAME: \BACKUP\
>         LL_NAME:
>
>                   $PROPOSAL.DOC
>       OBJECT_ID: 123923
>
> Notice that the LL_NAME value doesn't print on the same line
> but it prints after extra blank line so I assume that the value
> contains a new line character.
>
> If I try to use -COMMA option with dsmadmc to output the results
> with comma separated, then the report will abort when it runs
> into this field containing this troublesome LL_NAME value.
>
> Could someone explain why the LL_NAME field has this kind of value?
> And how I can get around the problem?
>
> Thanks so much for any help,
>
> Mira Jung
> mira AT seas.ucla DOT edu