View previous topic :: View next topic
|
Author |
Message |
yogeshpawar
New User
Joined: 01 Mar 2006 Posts: 37 Location: Sussex-UK
|
|
|
|
Hi,
We have a job which sometimes can have a blank i/p. It seems DFSORT is objecting this where it worked without any problem with Syncsort.
Can DFSORT handle blank I/P file?
Also can DFSORT cope up with the case where LRECL on O/P file(say 200) is greater than LRECL on I/P file (Say 40)? Syncsort pads with hex Zero, can DFSORT do the same? Or do we need to add OUTREC card? |
|
Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
|
|
|
|
What do you mean by a "blank input"? Do you mean an empty input file (no records) or something else? Please show your JCL, control statements, and //SYSOUT messages for the DFSORT job.
Yes, DFSORT will pad with binary zeros (what you're calling hex zero) when the SORTOUT LRECL > SORTIN LRECL. You don't need an OUTREC statement unless you want to pad with something other than binary zeros. |
|
Back to top |
|
|
yogeshpawar
New User
Joined: 01 Mar 2006 Posts: 37 Location: Sussex-UK
|
|
|
|
Thanks for the explaination on LRECL.
Blank ip means I/P file with no records. |
|
Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
|
|
|
|
Did you miss the part where I said:
Quote: |
Please show your JCL, control statements, and //SYSOUT messages for the DFSORT job. |
Your statement that
Quote: |
DFSORT is objecting this |
isn't much to go on. I don't know what type of empty file you're working with, what error message you received, what options you used or didn't use, etc.
Please supply the requested information. |
|
Back to top |
|
|
yogeshpawar
New User
Joined: 01 Mar 2006 Posts: 37 Location: Sussex-UK
|
|
|
|
Hi Frank,
The messages we got are as follows
------------------------------------------------------------------------------------
ICE000I J - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R5 - 22:42 ON MON JAN
SORT FIELDS=(3,1,CH,A,10,6,CH,A,19,1,CH,A)
ICE043A K INVALID DATA SET ATTRIBUTES SPECIFIED SORTOUT LRECL
ICE043A M INVALID DATA SET ATTRIBUTES SPECIFIED SORTIN RECFM
ICE052I J END OF DFSORT
----------------------------------------------------------------------------------
Our guess was this might be due to empty i/p file.
Note that this particular job was running fine with SYNCSORT. Then Support team hardcoded DCB parameter and job started running fine.
SORTIN DD DSN=INPUT.FILE(0),DISP=SHR,
DCB=(RECFM=FB,LRECL=38,BLKSIZE=27968)
SORTOUT DCB was already there, just added BLKSIZE parameter
There are around 25 i/p files in SORTIN
Can you let me know what could have been actual reason? As I am finding it difficult to understand how hardcoding DCB solved the problem? |
|
Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
|
|
|
|
You would only need to specify the DCB information if it could not be obtained from the data set. The ICE043A for the SORTIN data set says that the RECFM is not available. This could happen if you just allocated the data set without specifying the RECFM and then tried to use it without specifying the RECFM. DFSORT would then have no way of knowing the RECFM. Hardcoding the attributes solved the problem by telling DFSORT what the attributes are.
Perhaps Syncsort took a guess at the RECFM (could be wrong - could be right). If you specified the missing attributes for SORTIN, you wouldn't need to specify any attributes for SORTOUT since DFSORT could figure them out. |
|
Back to top |
|
|
|