View previous topic :: View next topic |
Author |
Message |
kanitha-mvs Beginner
Joined: 17 May 2006 Posts: 26 Topics: 17
|
Posted: Wed May 28, 2008 2:38 am Post subject: To calculate bytes occupied by dataset |
|
|
Hi,
Is there any way to calculate the space occupied by the dataset using the LRECL and BLOCKsize information.
Thanks. |
|
Back to top |
|
|
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Wed May 28, 2008 6:02 am Post subject: |
|
|
LRECL and BLKSIZE alone will not give you the space. You need to know how many records are in the file. Maybe you do not undesrtand LRECL and BLKSIZE and the relationship between the two? One place to check this would be the JCL manual. Also look at the SPACE parameter whilst you are doing that. _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
|
Terry_Heinze Supermod
Joined: 31 May 2004 Posts: 391 Topics: 4 Location: Richfield, MN, USA
|
Posted: Wed May 28, 2008 8:24 am Post subject: |
|
|
In addition to what Nic said, you didn't indicate the DSORG. Is it F, FB, V, VB, Spanned, VSAM, PO? _________________ ....Terry |
|
Back to top |
|
|
kanitha-mvs Beginner
Joined: 17 May 2006 Posts: 26 Topics: 17
|
Posted: Fri May 30, 2008 12:39 am Post subject: |
|
|
Hi,
I want to know the space occupied by the dataset that is in migrated status in DASD. The HLIST command provides details about the tracks usage for a migrated dataset without recalling them..
Like this command, is there any command available that will provide the dataset information (Management class, storage class info..) and actual space occupied by migrated dataset without recalling it?
Thanks, |
|
Back to top |
|
|
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Fri May 30, 2008 5:14 am Post subject: |
|
|
Why not just HRECALL it, get the info you want ant then HMIG it again? You would have the info by now.
The info ISPF returns is based on current usage. If it is a GDG then looking at a non-migrated version will give you most of the info you want. The space would depend on how well the JCL was coded and the data. _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
|
expat Intermediate
Joined: 01 Mar 2007 Posts: 475 Topics: 9 Location: Welsh Wales
|
Posted: Sat May 31, 2008 4:12 am Post subject: |
|
|
You can download the MCDS and use SAS or REXX to analyse the data, or maybe look at DCOLLECTdata. _________________ If it's true that we are here to help others,
then what exactly are the others here for ? |
|
Back to top |
|
|
tcurrier Intermediate
Joined: 10 Feb 2006 Posts: 188 Topics: 68
|
Posted: Mon Jun 09, 2008 5:23 pm Post subject: |
|
|
IDCAMS with the LISTCAT function will give you everything you're looking for, EXCEPT for the space used. |
|
Back to top |
|
|
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Tue Jun 10, 2008 3:21 am Post subject: |
|
|
Hmmm, a LISTVTOC would give the space - on that volume. You could rig a rexx program to do the listcat, extract the volumes, do the LISTVTOCs and extract the data and calulate the space used. But will it work for migrated datasets? Are they compressed? Other things. _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
|
expat Intermediate
Joined: 01 Mar 2007 Posts: 475 Topics: 9 Location: Welsh Wales
|
Posted: Sat Jun 21, 2008 5:12 am Post subject: |
|
|
Actually, the HLIST command will tell you what the space allocation would be for when the dataset os recalled / recovered. _________________ If it's true that we are here to help others,
then what exactly are the others here for ? |
|
Back to top |
|
|
|
|