Joined: 07 Jan 2003 Posts: 1056 Topics: 91 Location: The Blue Planet
Posted: Mon Sep 26, 2005 9:12 am Post subject:
Thanks for the info Kolusu,
Never realized that there was such a difference.
Question:
In your previous post, you said you can divide the 15000 bytes into chunks of 1500 bytes each. Is the same thing possible with SORT command ? I think I have posted a question on this longgg back where SORT FIELDS exceeds the limits. That time I tried splitting the data into chunks but - no use.
I know SORT & SELECT are two different statements having separate functions, but just curious.
Joined: 02 Dec 2002 Posts: 415 Topics: 6 Location: Hove, England
Posted: Mon Sep 26, 2005 10:23 am Post subject:
Well, I ran it again with the split ON statement, but failed. Quickref gave me the reason:
Code:
Item ==> * MVS/QuickRef 6.3 *
Command ==>
ICE189A 0 BLOCKSET REQUIRED BUT COULD NOT BE USED - REASON CODE IS 63
----------------------------------------- V=IBM P=DFSORT MSGS & CODES R=V1R14 I=ICE189A
| 63 Too many control fields were specified or control fields were too
| large.
I reasoned that I could live with just checking the first part of each record, so I cut it down to the first 3000 bytes. This time, I had resourcing issues with SORTWK. I'll try again tomorrow, when there should be more resources available.
Cheers,
Merv _________________ The day you stop learning the dinosaur becomes extinct
Joined: 02 Dec 2002 Posts: 1618 Topics: 31 Location: San Jose
Posted: Mon Sep 26, 2005 11:34 am Post subject:
Quote:
Frank didn't comment anything over the length. So, I believe 4092 is the limit with DFSORT too.
I couldn't comment earlier since I just got into work. I'm on the West Coast of the U.S. so I don't see the questions as early as other people. (This usually means that Kolusu or somebody else has answered the question by the time I see it which tends to limit my participation on this board.)
With SELECT, you can use up to 1500 bytes for a BI ON field. You can use multiple ON fields. But you can't use more than about 4K bytes total for the ON fields because that's the limit for the sort control statement (SELECT does a sort). So you can't SELECT on 14K+ bytes.
Looks like Merv was able to cut if down to 3000 bytes which is allowed with multiple ON fields. _________________ Frank Yaeger - DFSORT Development Team (IBM)
Specialties: JOINKEYS, FINDREP, WHEN=GROUP, ICETOOL, Symbols, Migration
DFSORT is on the Web at:
www.ibm.com/storage/dfsort
Joined: 07 Jan 2003 Posts: 1056 Topics: 91 Location: The Blue Planet
Posted: Tue Sep 27, 2005 12:08 am Post subject:
Frank,
Quote:
I couldn't comment earlier since I just got into work. I'm on the West Coast of the U.S. so I don't see the questions as early as other people.
I was not referring to Mervyn's post. I was mentioning about your response in the link that I gave to Mervyn. Here you highlighted the possible issues with mixed Signs when we use CH/BI for the entire record. But never said anything about the 4092 limit with SORT statement.
I apologize if my statement was not clear. Since I posted two messages in succession, it was a continuous flow for me, but for an external reader it looks otherwise. I didn't realise that.
Joined: 02 Dec 2002 Posts: 1618 Topics: 31 Location: San Jose
Posted: Tue Sep 27, 2005 9:57 am Post subject:
Phantom,
In that thread, we were talking about a length of 4043 (at least I think we were). Since the 4K limit was not relevent for that thread, I didn't mention it. _________________ Frank Yaeger - DFSORT Development Team (IBM)
Specialties: JOINKEYS, FINDREP, WHEN=GROUP, ICETOOL, Symbols, Migration
DFSORT is on the Web at:
www.ibm.com/storage/dfsort
All times are GMT - 5 Hours Goto page Previous1, 2
Page 2 of 2
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
