Re: [U2] Reporting Tools

Jeff:

I've written a little BASIC utility that takes a file, selects what I 
want, then outputs via the ITYPE function as a CSV file to the spooler.  
I wonder if that gets around the 150 field limit, since it's in BASIC?  
I know UniData is weird regarding this kind of thing.  For instance, 
they also have something like a 256 "item" limit in a query statement...

:SELECT MYFILE WITH CUST# = "1""2""3"..."256""257"

...will abort.  This too is "hardwired".  However, a neat little utility 
provided by U2 called "LSELECT" selects items whose field definition 
value is in a list, so if you're on the web you'd first allow the user 
to select stuff, put it into a list, then use LSELECT to select the 
items from the file...kind of like:

:SELECT CUSTOMERS WITH LAST_ACTIVE > "01/01/13"
500 records selected to list 0.
 >SAVE.LIST MY.LIST
Overwriting existing saved list.
500 key(s) saved to 1 record(s).
 >LSELECT SALESORDERS WITH CUSTNO IN MY.LIST VERBOSE
(Parsed Command)
LSELECT SALESORDERS WITH CUSTNO IN MY.LIST TO 0

(Selected List)
List Source MY.LIST found 500 items.

(Create Temp File)
LSELECT0031 file created with MOD = 3

(Loaded List to Temp File) - 500 items.

1436 key(s) saved to 1 record(s).
(Selected Result List)
UDT.COMMAND = select SALESORDERS WITH EVAL 
"TRANS('LSELECT0031',CUSTNO,'@ID','X')" GT "" TO 0
UDT.RESPONSE = ■1436 records selected to list 0.■■
Destination 0
Named List 0

(Delete Temp File)
LSELECT0031 file deleted...
 >

Makes one wonder...hmmmm.

Bill
Untitled Page


------------------------------------------------------------------------
----- Original Message -----
*From:* [email protected]
*To:* U2 Users List <[email protected]>
*Date:* 3/3/2014 12:57 PM
*Subject:* Re: [U2] Reporting Tools
> As a work around, would this work:
> * produce file1 with record key and then 100+ data fields
> * produce file2 with remaining data fields
> * execute Linux command:
>     paste file1 file2 >myrealdata.csv
>
>
>
>
> David Rotman, Ph.D.
> Associate Vice President for Technology
> Chief Information Officer
> Cedarville University
> 251 N. Main Street
> Cedarville, OH 45314
> [email protected]
> voice 937-766-7905
> fax 937-766-8819
>
>
>
> On Mon, Mar 3, 2014 at 3:34 PM, jeffrey Butera <[email protected]>wrote:
>
>> On 3/3/14, 3:21 PM, Jeff Schasny wrote:
>>
>>> Jeff,
>>>
>>> What I think many of us are suggesting is essentially "if it hurts when
>>> you do that, don't do that" i.e. if the query language won't accomplish
>>> what you want to do, use something else.
>>>
>> Jeff
>>
>> Believe me - I hear you (and others).  But my administration isn't
>> listening because they all think this is a reasonable request ("excel can
>> handle 200+ columns").   So if I can't make this work in Unidata I'll have
>> to move to MSSQL which I really, really, really don't want to do.
>>
>> At this point I'm just trying to understand the limit on the number of
>> fields in a LIST statement.  I know in my case that it's not a sentence
>> length issue as I might've thought earlier so I'd like to know what is
>> causing this (with the understanding that I very well may not be able to
>> solve this).
>>
>> Jeff
>>
>>
>>> jeffrey Butera wrote:
>>>
>>>> On 3/3/14, 2:58 PM, Brian Leach wrote:
>>>>
>>>>> Jeff
>>>>>
>>>>> Try mvQuery, that should not have any problems with those volumes.
>>>>>
>>>> Hi Brian
>>>>
>>>> We've isolated the problem to Unidata itself, not the reporting tool.
>>>>   In short, when we do a LIST with about 150 fields, it throws:
>>>>
>>>> "too many items in LIST"
>>>>
>>>> As soon as we erase a field (any field), the LIST statement runs
>>>> properly.  Unfortunately, I cannot locate any parameter that might control
>>>> this.  I thought we were hitting U_SENTLEN - but we're nowhere near that
>>>> value.
>>>>
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users