View previous topic :: View next topic
|
Author |
Message |
Captain Paralytic Warnings : 1 New User
Joined: 21 Apr 2010 Posts: 40 Location: UK
|
|
|
|
I've just tried a sort include with a long SS comparison field. I got an error:
ICE113A E COMPARISON FIELD ERROR
with the character at position 256 highlighted and the product shown as V1R5.
When I checked QuickRef (for V1R5), the documentation told me that it was possible that my field exceeded 32753 whilst the PTF document:
service.boulder.ibm.com/storage/dfsort/mvs/sortsoc.pdf
tells me that the the Release 14 PTF of February increased the size to 32752.
The Messages and Codes manual for Release 14 from 2007 tells me that the message refers to a maximum length of 4093.
So we have 255, 32753, 32752 and 4093.
CONFUSED!?!?!?!?!? |
|
Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
|
|
|
|
Please post the complete set of //SYSOUT messages you received. |
|
Back to top |
|
|
Captain Paralytic Warnings : 1 New User
Joined: 21 Apr 2010 Posts: 40 Location: UK
|
|
|
|
Frank Yaeger wrote: |
Please post the complete set of //SYSOUT messages you received. |
As requested:
Code: |
ICE000I J - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R5 - 11:05 ON WED SEP 15, 2010 -
INCLUDE COND=(1,5,SS,EQ,C'001BI,001CD',
AND,(6,3,SS,EQ,
C'-
QQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ -
QQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ -
QQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ -
QQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ -
£
ICE113A E COMPARISON FIELD ERROR |
|
|
Back to top |
|
|
Captain Paralytic Warnings : 1 New User
Joined: 21 Apr 2010 Posts: 40 Location: UK
|
|
Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
|
|
|
|
The only confusion here is that you're mixing up the position, length and constant limits.
The error you're getting is for the length of the constant, not the position or length of the field.
The maximum length of the constant for SS, as documented, is 256.
The position of the field in this case is 6. The length of the field in this case is 3. The current maximum for the field position is 32752. The current maximum for the field length is 32752.
DFSORT has two current releases, z/OS DFSORT V1R5 for z/OS 1.5-1.9 and z/OS DFSORT V1R10 for z/OS 1.10-1.11. At the end of September, z/OS DFSORT V1R12 will be available for z/OS 1.12 and z/OS DFSORT V1R5 for z/OS 1.5-1.9 will be out of service.
The most current DFSORT books at this point are the z/OS 1.11 books for z/OS DFSORT V1R10 and PTFs. In September, the most current DFSORT books will be the z/OS 1.12 books for z/OS DFSORT V1R12. We update the next level of the z/OS books with the new PTF functions. If you look at the Summary of Changes in each level of the book, it tells you what is included in that book. (We do not update older levels of the books for PTFs.) |
|
Back to top |
|
|
Captain Paralytic Warnings : 1 New User
Joined: 21 Apr 2010 Posts: 40 Location: UK
|
|
|
|
Hi Frank,
thanks for that. However that really only addresses one of the confusions.
Could you possibly address these:
- The error message ICE113A actually says "Make sure that the position plus the length of each field does not exceed 32753". Does this mean that if the field starts at position 10, the maximum length of it is actually 32743?
- If the current 2 releases of DFSORT are V1R5 and V1R10, why does the messages manual that the page www-01.ibm.com/support/docview.wss?rs=114&uid=isg3T7000080 states is for V1R5, say that it is for V1R8?
TIA
Regards
Paul |
|
Back to top |
|
|
Captain Paralytic Warnings : 1 New User
Joined: 21 Apr 2010 Posts: 40 Location: UK
|
|
|
|
oops |
|
Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
|
|
|
|
1. Yes, that's correct. A field must not go past position 32752.
2. The April, 2006 PTF was for V1R5, so the DFSORT 1.8 book was updated for that PTF (that was the next z/OS release after that PTF was available).
The July, 2008 PTF was for V1R5 and V1R10, so the DFSORT 1.11 book was updated for that PTF (that was the next z/OS release after that PTF was available).
The Nov, 2009 PTF was for V1R5 and V1R10, so the DFSORT 1.12 book has been updated for that PTF (that was the next z/OS release after that PTF was available). I will put up the 1.12 book links when z/OS DFSORT V1R12 GAs.
3. What was the "oops" for? |
|
Back to top |
|
|
|