My understanding was it would be different based on RECORD CONTAINS used in the program. Can anybody please explain the reason for it? We do have utilities where we have the concatenation of input files so want to ensure that all have the same BLKSIZE.
Joined: 10 May 2007 Posts: 2180 Location: Hampshire, UK
You do not need the same blocksize for concatenated datasets. You used to be required to have the dataset with the largest blocksize as the first data set in the concatenation but that is no longer the case.
When posting code and data please use the code tags (available in the "post reply" editor). I have coded your post for you.
Thank you Nic for the response. I am sorry I was not aware of the tags.
Based on your response, now concatenation of input datasets with different block sizes is not the concern. I have tested that with the combinations using SORT utility and job ran fine and the o/p blksize is determined by the system.
Question - Based on the results in my post for BLOCK CONTAINS, can we conclude that DCB change in JCL to remove BLSIZE or code BLKSIZE=0 will be enough to get the system determined blksize even though if we do not remove BLOCK CONTAINS <non zero> or add BLOCK CONTAINS 0 in the program? fyi - Our programs are compiled with NOBLOCK0 compiler option.