Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

How to find KSDS Block Size and No. of records.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
abdul.faras

New User


Joined: 29 Feb 2008
Posts: 49
Location: Pune

PostPosted: Thu Mar 13, 2008 2:57 pm    Post subject: How to find KSDS Block Size and No. of records.
Reply with quote

How to find KSDS Block Size and No. of records.

I need to find Block Size and No. of records in a VSAM KSDS File.

While creating the file, in JCL the BLKSIZE is =0, so system will decide the BLKSIZE for that. I need to find what exact BLKSIZE system assigned for the file.
I have tried searching it in FILEAID, it doesn't give any information regarding Blocksize or number of records the file contains.
Back to top
View user's profile Send private message

murmohk1

Senior Member


Joined: 29 Jun 2006
Posts: 1439
Location: Bangalore,India

PostPosted: Thu Mar 13, 2008 4:14 pm    Post subject:
Reply with quote

Abdul,

Quote:
While creating the file, in JCL the BLKSIZE is =0, so system will decide the BLKSIZE for that. I need to find what exact BLKSIZE system assigned for the file.

Just wanted to see your vsam creation step. If you dont mind, post the job.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Mar 13, 2008 4:14 pm    Post subject:
Reply with quote

A KSDS does not have a BLKSIZE and LISTCAT will tell you the number of records.
Back to top
View user's profile Send private message
abdul.faras

New User


Joined: 29 Feb 2008
Posts: 49
Location: Pune

PostPosted: Thu Mar 13, 2008 4:22 pm    Post subject:
Reply with quote

murmohk1 wrote:
Abdul,

Quote:
While creating the file, in JCL the BLKSIZE is =0, so system will decide the BLKSIZE for that. I need to find what exact BLKSIZE system assigned for the file.

Just wanted to see your vsam creation step. If you dont mind, post the job.


Code:

//KMC13C   EXEC PGM=XXXXX,COND=(00,NE)
//KZZZZZ  DD  DSN=VMEDPAC.KUPRFMD,DISP=SHR
//KDDDDD  DD  DSN=BMEDPAC.IDCAMS.KMMRMWD,DISP=SHR,DCB=BUFNO=14
//KRRRRR  DD  DSN=BMEDPAC.KMC13CBC.KMMRMWD,
//         DISP=(NEW,CATLG,DELETE),
//         VOL=SER=&VOLSER,
//         UNIT=&SYSDA,SPACE=(CYL,(2,1),RLSE),
//         DCB=(RECFM=VB,LRECL=30284,BLKSIZE=0)
//CNTLRPT  DD  SYSOUT=&SYSRPT
//SYSOUT   DD  SYSOUT=&SYSMSG
//SYSDBOUT DD  SYSOUT=&SYSMSG
//SYSUDUMP DD  SYSOUT=&SYSMSG
Back to top
View user's profile Send private message
murmohk1

Senior Member


Joined: 29 Jun 2006
Posts: 1439
Location: Bangalore,India

PostPosted: Thu Mar 13, 2008 4:24 pm    Post subject:
Reply with quote

Abdul,

Quote:
//KRRRRR DD DSN=BMEDPAC.KMC13CBC.KMMRMWD,
// DISP=(NEW,CATLG,DELETE),
// VOL=SER=&VOLSER,
// UNIT=&SYSDA,SPACE=(CYL,(2,1),RLSE),
// DCB=(RECFM=VB,LRECL=30284,BLKSIZE=0)

And what made you think that your o/p file is a vsam?
Back to top
View user's profile Send private message
abdul.faras

New User


Joined: 29 Feb 2008
Posts: 49
Location: Pune

PostPosted: Thu Mar 13, 2008 4:52 pm    Post subject:
Reply with quote

murmohk1 wrote:
Abdul,

Quote:
//KRRRRR DD DSN=BMEDPAC.KMC13CBC.KMMRMWD,
// DISP=(NEW,CATLG,DELETE),
// VOL=SER=&VOLSER,
// UNIT=&SYSDA,SPACE=(CYL,(2,1),RLSE),
// DCB=(RECFM=VB,LRECL=30284,BLKSIZE=0)

And what made you think that your o/p file is a vsam?


Actually this step creates the flat file and then this flat file is reproed in to a KSDS.

For documentation perpose I need the BLKSIZE.
But I guess its given wrong in my old documents, as expat has mentioned KSDS does not have a BLKSIZE is right.
Correct me if I am wrong.
Back to top
View user's profile Send private message
murmohk1

Senior Member


Joined: 29 Jun 2006
Posts: 1439
Location: Bangalore,India

PostPosted: Thu Mar 13, 2008 8:28 pm    Post subject:
Reply with quote

Abdul,

Quote:
But I guess its given wrong in my old documents,

Refer IBM documentation.

Quote:
Correct me if I am wrong.

Not required. You got it properly.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Mar 13, 2008 8:51 pm    Post subject:
Reply with quote

Quote:
For documentation perpose I need the BLKSIZE.

Why do you need to know the BLKSIZE ?

It may vary depending on the architecture of the DASD that you may use, for 3380 the BLKSIZE will be different from 3390.

Let the system determine the optimum BLKSIZE for you, it is so much easier and efficient.
Back to top
View user's profile Send private message
abdul.faras

New User


Joined: 29 Feb 2008
Posts: 49
Location: Pune

PostPosted: Fri Mar 14, 2008 11:00 am    Post subject:
Reply with quote

Quote:
Why do you need to know the BLKSIZE ?



In the old documentation related to my project the BLKSIZE has been mentioned, due to which I got confused.

Thank you murmohk1 and expat for your replies.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts find particular member name in PDS us... ravi243 CLIST & REXX 10 Mon Dec 19, 2016 6:44 pm
No new posts Removing Duplicates based on certain ... chandracdac DFSORT/ICETOOL 8 Fri Dec 09, 2016 4:40 am
No new posts How to find the first monday of the w... abdulrafi COBOL Programming 10 Fri Nov 25, 2016 3:24 pm
No new posts Limit duplicate records in the SORT pshongal SYNCSORT 6 Mon Nov 21, 2016 12:54 pm
No new posts How to split the records using the am... vnktrrd DFSORT/ICETOOL 24 Fri Oct 28, 2016 7:33 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us