INVALID BLOCK SIZE



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

INVALID BLOCK SIZE

Postby chetan_007 » Thu Mar 05, 2009 5:01 pm

Hello Friends,

Why does the load datasets will have block size as zero and if we try to open it will display message as INVALID BLOCK SIZE.
Any idea why we get invalid block size when opening some of the datasets.

Thanks
chetan_007
 
Posts: 24
Joined: Sun Mar 02, 2008 3:22 am
Has thanked: 0 time
Been thanked: 0 time

Re: INVALID BLOCK SIZE

 

Re: INVALID BLOCK SIZE

Postby swd » Thu Mar 05, 2009 6:52 pm

Hi - it might be useful if you tell us how these datasets were created, perhaps show us the JCL that created them. From what you say it sounds like some DCB information was missing when these datasets were created and perhaps they are empty? It sounds like z/os doesn't know what blocksize to allocate because it doesn't know the record length, or the DSORG information.
User avatar
swd
 
Posts: 109
Joined: Wed Feb 18, 2009 9:18 pm
Location: UK
Has thanked: 0 time
Been thanked: 0 time

Re: INVALID BLOCK SIZE

Postby dick scherrer » Fri Mar 06, 2009 12:44 am

Hello,

Why does the load datasets will have block size as zero
Load library datasets are not like other datasets. I suspect it is the record length is zero rather than the block size. . . :?:

If you look at the Data Set Information in tso/ispf 3.4 it should look something like:
Organization  . . . : PO     
Record format . . . : U       
Record length . . . : 0       
Block size  . . . . : 32760   

If this is not your issue, please post the requested info.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post