IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Need PDS statistics


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
pullaiah.cts

New User


Joined: 02 Sep 2010
Posts: 50
Location: Pune

PostPosted: Sun Sep 23, 2012 10:31 am
Reply with quote

There is a requirement in my project that we need to know get the statistics of all jcl,cobol and db2 libraries like no.of members in each library,member list,no.of lines in each member,total no.of lines in each pds and also size of each member and pds. Can we get all this info using fileaid/ispd/tso or any jcl utilities? Please suggest.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2454
Location: Hampshire, UK

PostPosted: Sun Sep 23, 2012 2:51 pm
Reply with quote

Well, that is only 3 PDSes per person - it won't take long for each person to do it manually - certainly much quicker than posting here, waiting for an answer and then doing it manually anyway.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Sun Sep 23, 2012 3:18 pm
Reply with quote

I suspect the simple answer is no. You can get most of this information from different sources easy enough but would have to combine it. Someone with good rexx skills may be able to provide something.

The only way I know of is if you have FDR (therefore FDREPORT), this will give you what you need. Although the PDS size info etc is repeated for every member, the relevent individual member information is reported for each one. (note: the XDSN field allows for dataset name masking much the same as DFDSS or 3.4)

Code:
//FDR#PDS EXEC PGM=FDREPORT,REGION=512M                         
//SYSPRINT DD  SYSOUT=*                                         
//ABRMAP   DD  SYSOUT=*                                         
//ABRSUM   DD  SYSOUT=*                                         
//SYSIN    DD  *                                               
 REPORT FIELD=(NAME,CAPBYTES,SIZE,DIRBLOCK,MEMBERS,MEMBCURR,   
               MEMBVER,MEMBSSI,MEMBSTOR,MEMNAME)               
   XS XDSN=PDS%.NAME.MASK*.**,DSORG=(PO,POE)                       
  SORT FIELD=(NAME,MEMNAME)                                     
  PRINT DATATYPE=CATVTOC,SUM=NO,SORT=CO,                       
        ENABLE=(FASTPATH),RPTYPE=TABLE                         


If you need further help just run the same JCL but with just XHELP ALL in the SYSIN and it produces a full manual.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix

PostPosted: Mon Sep 24, 2012 6:15 am
Reply with quote

Hello,

Quote:
There is a requirement in my project that we need to know get the statistics of all jcl,cobol and db2 libraries
How has this become a "requirement"? If your system uses any kind of change control / configuraton management tool, something like this is usually builtin and is managed by that group - not someone who is a developer.

What actual or percieved benefit will be realized having this? In the 70's and 80's many places implemented their own statistics generators only to realize that they provided little or no value. . .

If your organization insists on doing this, do as suggested and hire/develop the REXX skills needed to do this. Keep in mind that the ISPF statistics are not always correct. Sometimes, they are not even captured.
Back to top
View user's profile Send private message
pullaiah.cts

New User


Joined: 02 Sep 2010
Posts: 50
Location: Pune

PostPosted: Mon Sep 24, 2012 10:51 am
Reply with quote

Hi Pete,

I am using FDRREPORT to get the required data and am able to get that but I need small clarification. When I submitted the job my output is like below
Code:

CKBYTES KBYUSED  ALLOC DIRBK MEMBER  SIZE VV SSI
 849960  446329  15000  7000  35299    12  1   
 849960  446329  15000  7000  35299    12  1   
 849960  446329  15000  7000  35299     8  1   
 849960  446329  15000  7000  35299     8  1   
 849960  446329  15000  7000  35299     8  1   

In the baove screenshot, KBYUSED=446329 that means size of the PDS is 446329 kilo bytes? What parameter I need to mention in the SYSIN if I need the size in MB or GB? I used BYTESUSEM and MBYUSED but getting RC12 error, please help.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Mon Sep 24, 2012 11:13 am
Reply with quote

Yes the CKBYTES is the size of the whole PDS.

This can be changed by coding BYTEF=MEGA,SUMBYTEF=MEGA on the PRINT statement.

As I said, run the same JCL but with just XHELP ALL in the SYSIN and it produces a full manual
Back to top
View user's profile Send private message
pullaiah.cts

New User


Joined: 02 Sep 2010
Posts: 50
Location: Pune

PostPosted: Mon Sep 24, 2012 11:31 am
Reply with quote

Hi Pete,

I will use the specified options.
Please correct me if my below understanding is wrong from my screen shot.

CKBYTES -- No.of Kilo Bytes allocated for the PDS
KBYUSED -- No.of Kilo Bytes used by the PDS

And also, Please let me know how to specify multiple PDS names as Input in XS XDSN step.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Mon Sep 24, 2012 11:36 am
Reply with quote

Yes, although in my original posting I didn't specify BYTESUSE so not sure why it is being reported. Did you change the SYSIN?

NOW - LOOK CAREFULLY AT THE FOLLOWING STATEMENT:

Run the same JCL but with just XHELP ALL in the SYSIN and it produces a full manual in the SYSPRINT.

In the manual look for XDSN=. If you read my original post FULLY you would have seen this '(note: the XDSN field allows for dataset name masking much the same as DFDSS or 3.4)'

RTFM - YFW
Back to top
View user's profile Send private message
pullaiah.cts

New User


Joined: 02 Sep 2010
Posts: 50
Location: Pune

PostPosted: Mon Sep 24, 2012 11:50 am
Reply with quote

I Did 'XHELP ALL' and got the details, based onthe details I have modified my DSN to get the used space in bytes.
I have observed below thing, I have taken one COBOL library which has 4 memebers in it. I got below statistics when I run the FDRREPORT
Code:
CKBYTES KBYUSED
  21249     782
  21249     782
  21249     782
  21249     782

I mentioned CAPBYTES,BYTESUSE in the SYSIN.
That means the space consumed by COBOL library is 782 Kilo bytes.

Now, I have downloaded 4 members to my PC and checked the total size,it's showing 170 KB.

I am getting confused with these SPACE parameters in FDRREPORT. What should I mention in the SYSIN if I should get 170 KB in FDRREPORT as well.

Code'd
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Mon Sep 24, 2012 12:04 pm
Reply with quote

pullaiah.cts,

Please use the Code tags every time that they are appropriate.

Did you read Dick's post? Not just written for fun, you know.

When you "download to your PC" don't you think that dropping trailing blanks may be an effect on the program size? The more short and meaningless the data-names, the more trailing space there is. However, the amount of space physically occupied by Cobol source means, to you, what? Back to Dick's points.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Mon Sep 24, 2012 12:09 pm
Reply with quote

If you rip the lungs out of a human being (something I occasionally would like to do) they are no longer the same as they were being part of a whole human being.

That is what it is like comparing the member contents stored on the PC with the whole PDS structure and member content on ZOS.

If you look at the report value under the SIZE heading for each of the 4 members, what does that add up to?
Back to top
View user's profile Send private message
pullaiah.cts

New User


Joined: 02 Sep 2010
Posts: 50
Location: Pune

PostPosted: Mon Sep 24, 2012 12:39 pm
Reply with quote

Sorry Bill, I didn't realize that there wil be a difference between Z/os and PC statistics.

I will do some manual work at PC side to get the actual size.

Thank you all for your help and suggestions.
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Mon Sep 24, 2012 1:59 pm
Reply with quote

I still don't get how the size of a Cobol source is going to be related to anything.

With dumb data-names and shoddy layout, I guess you might get a program with 40 characters or fewer per line. Mine would be above 70, likely.

Measure away, but what are you trying to measure? And why?
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix

PostPosted: Mon Sep 24, 2012 6:53 pm
Reply with quote

Hi Bill,

Quote:
but what are you trying to measure?
How much "stuff" we have - as often demonstrated, not a valueable "thing to have".

Quote:
And why?
Because someone who doesn't know any better has made this "a requirement". . .

d
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts DB2 Statistics - Using EXPLAIN and qu... DB2 1
No new posts Extracting Compression Statistics fro... PL/I & Assembler 2
No new posts Program level statistics CICS 6
No new posts CICS Performance statistics CICS 3
No new posts Program usage statistics? CICS 6
Search our Forums:

Back to Top