ICE200I 0 IDENTIFIER FROM CALLING PROGRAM IS 0003
ICE143I 0 BLOCKSET COPY TECHNIQUE SELECTED
ICE250I 0 VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, EXAMPLES AN
ICE000I 0 - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R5 - 23:32 ON WED JUN
OUTFIL FNAMES=(OUT01,OUT02,OUT03,OUT04,
OUT05,OUT06,OUT07,OUT08,OUT09,
OUT10,OUT11,OUT12,OUT13,OUT14,
OUT15,OUT16,OUT17,OUT18,OUT19,OUT20,
OUT21),
$
ICE001A 0 TEXT BEGINS IN WRONG COLUMN
SPLIT1R=00546055
ICE146I 0 END OF STATEMENTS FROM CTL3CNTL - PARAMETER LIST STATEMENTS FOLLOW
DEBUG NOABEND,ESTAE
OPTION MSGDDN=DFSMSG,LIST,MSGPRT=ALL,RESINV=0,SORTDD=CTL3,SORTIN=IN,DYN*
ALLOC
SORT FIELDS=COPY
ICE751I 0 C5-K26318 C6-K90007 C7-K90000 C8-K23476 E7-K24705
ICE052I 3 END OF DFSORT
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
No, I need see all of the TOOLMSG messages and all of the DFSMSG messages for the entire job. You sent me a job with three COPY operators. You only show pieces of the messages above. I need to see the complete messages for ALL of the COPY operators.
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
Ok, I guessed what the problem was, but this allowed me to confirm it.
The 80:X doesn't do any good because your System Programmers chose to change DFSORT's shipped default of SOLRF=YES to SOLRF=NO. This change is NOT recommended. SOLRF=NO tells DFSORT to use the input LRECL for output rather than the reformatted length which is not a good idea. With SOLRF=NO, the 80:X in INREC is ignored and the output is set to 244 instead of 80. So your DD * control statements have an LRECL of 80, but your concatenated C1 record has an LRECL of 244 instead of 80.
With the shipped default of SOLRF=YES, this wouldn't happen. I always assume people leave the shipped default alone so it takes a while before I think of this possibility.
I don't know why your System Programmers changed the default but it will probably cause problems for your site. You might want to ask them about this.
At any rate, you should be able to fix things up by overriding their bad choice with:
Thanks for your detailed explanation on my problem. When I overrode SOLRF option, my JOB got executed successfully.
Can you please let me know what could be the other impacts due to this SOLRF change? If there is any document or link to explain about the impact, please provide me the same.
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
Quote:
just curious, why have a default if it's not recommended ?
Because some of our customers, especially those in a particular country, always require that we give them a way to run things as they used to run whether it makes sense or not.
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
Quote:
Can you please let me know what could be the other impacts due to this SOLRF change? If there is any document or link to explain about the impact, please provide me the same.
SOLRF=YES/NO is documented in "z/OS DFSORT Installation and Customization" at: