Easy way to acquire VSAM Space in REXX

[Chip Grantham]

Good morning gentle listers,

Any thoughts on a simple way to find out the number of tracks allocated to
a VSAM component or sphere from REXX. I'm hoping for something like the
LISTDSI command. I understand I could use CSI and parse for the used /
allocated RBA and calculate tracks. It's a lot of code with multi-volume,
multi-extents etc.

Chip Grantham | Ameritas | Sr. IT Consultant | cgra...@ameritas.com
5900 O Street, Lincoln NE 68510 | p: 402-467-7382 | c: 402-429-3579 | f:
402-325-4030


*******
This message may contain confidential information intended only
for the use of the addressee(s) named above and may contain
information that is legally privileged. If you are not the
addressee, or the person responsible for delivering it to the
addressee, you are hereby notified that reading, disseminating,
distributing or copying this message is strictly prohibited. If you
have received this message by mistake, please immediately notify
us by replying to the message and delete the original message
immediately thereafter. Thank you.
*******


----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

[Lizette Koehler]

I think there is a caveat here. Unless the VSAM dataset is closed, the
space may not be accurately described.

And other than LISTC or CSI I do not think the LISTDSI is sufficient. I
think (depending on z/OS level) it will only return volume, unit, primary
allocation. But not what is actually used (HI-RBA vs. USED-RBA)



Lizette

[Lizette Koehler]

Sorry, according to the manual

If you use LISTDSI to retrieve information about a VSAM data set, LISTDSI
stores only the volume serial
ID (in variable SYSVOLUME), the device unit (in variable SYSUNIT), and the
data set organization (in
variable SYSDSORG).

I thought maybe space would be included.

Lizette

> Subject: RE: [TSO-REXX] Easy way to acquire VSAM Space in REXX

>
> I think there is a caveat here. Unless the VSAM dataset is closed, the
space may not
> be accurately described.
>
> And other than LISTC or CSI I do not think the LISTDSI is sufficient. I
think (depending
> on z/OS level) it will only return volume, unit, primary allocation. But
not what is
> actually used (HI-RBA vs. USED-RBA)
>
>
>
> Lizette
>
>
> > -----Original Message-----
> > From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On
> > Behalf Of Chip Grantham
> > Sent: Tuesday, May 01, 2012 8:03 AM
> > To: TSO-...@VM.MARIST.EDU
> > Subject: [TSO-REXX] Easy way to acquire VSAM Space in REXX
> >

> > Good morning gentle listers,
> >
> > Any thoughts on a simple way to find out the number of tracks
> > allocated to a VSAM component or sphere from REXX. I'm hoping for
> > something like the LISTDSI command. I understand I could use CSI and
> > parse for the used / allocated RBA and calculate tracks. It's a lot of
code with multi-
> volume, multi-extents etc.
> >
> > Chip Grantham | Ameritas | Sr. IT Consultant |
> > cgra...@ameritas.com
> > 5900 O Street, Lincoln NE 68510 | p: 402-467-7382 | c: 402-429-3579 | f:
> > 402-325-4030

[John P Kalinich]

I use something from CBT file 137 called VSAM Information. It traps
LISTCAT output and then displays an ISPF screen. I am sure you could adapt
it to your needs.

Regards,
John K

--------------------------- VSAM Dataset Information
--------------------------
COMMAND ===>
Data Set Name: MVSSMPS.ACF2.R15.CSI
General Data: Current Allocation:
Volume serials: LTSMPS Allocated trks:
120
Type: INDEXED Allocated extents:
1
Ave record length: 24
Max record length: 143 Current Utilization:
Key length: 24 Used trks:
45
Relative key position: 0 Used percent:
38
CI size: 4096
CI freespace: 10 Usage Data:
CA freespace: 5 Total records:
65430
1st extent cylinders: 8 Records deleted:
659
Secondary cylinders: 1 Records inserted:
1587
Creation date: 2012/02/18 Records updated:
0
Expiration date: Records retrieved:
860134
CI splits:
16
CA splits:
0
SHROPTNS(2,3) RECOVERY UNIQUE NOERASE INDEXED
NOWRITECHK UNORDERED NOREUSE NONSPANNED

From: Chip Grantham <CGra...@AMERITAS.COM>
To: TSO-...@vm.marist.edu
Date: 05/01/2012 10:06 AM
Subject: [TSO-REXX] Easy way to acquire VSAM Space in REXX

[Chip Grantham]

Thanks for the replies.

I use LISTDSI a lot. Really handy little command. I know the RBA
values are only updated at close, but at least it is the size at
sometime?? which is a little better than no size. I like the idea of
using CSI and building a stem variable with all the components and their
attributes, but didn't want to take the time right now. Maybe start with
a quick and dirty and expand it later.

*******
This message may contain confidential information intended only
for the use of the addressee(s) named above and may contain
information that is legally privileged. If you are not the
addressee, or the person responsible for delivering it to the
addressee, you are hereby notified that reading, disseminating,
distributing or copying this message is strictly prohibited. If you
have received this message by mistake, please immediately notify
us by replying to the message and delete the original message
immediately thereafter. Thank you.
*******

[Chip Grantham]

Nice idea. Thanks.

Chip Grantham | Ameritas | Sr. IT Consultant | cgra...@ameritas.com
5900 O Street, Lincoln NE 68510 | p: 402-467-7382 | c: 402-429-3579 | f:
402-325-4030

From: John P Kalinich <jkal...@CSC.COM>
To: TSO-...@VM.MARIST.EDU

[Fabio Fioravanti]

Hi,

follow some of the variable-name and content output of the LISTDSI command:

+-----------------+------------------------------------------------------|
| SYSDSNAME | Data set name |
+-----------------+------------------------------------------------------|
| SYSVOLUME | Volume serial ID |
+-----------------+------------------------------------------------------|
| SYSUNIT | Generic device type on which volume resides, for |
| | example 3390. |
+-----------------+------------------------------------------------------|
| SYSALLOC | Allocation, in space units |
+-----------------+------------------------------------------------------|
| SYSUSED | Allocation used, in space units. For a partitioned |
| | data set extended (PDSE), 'N/A' will be returned; |
| | see the description of the variable SYSUSEDPAGES for |
| | used space of a PDSE. |
+-----------------+------------------------------------------------------|
| SYSUSEDPAGES | The used space of a partitioned data set extended |
| | (PDSE) in 4K pages. |
+-----------------+------------------------------------------------------|
| SYSPRIMARY | Primary allocation in space units |
+-----------------+------------------------------------------------------|
| SYSSECONDS | Secondary allocation in space units |
+-----------------+------------------------------------------------------|
| SYSUNITS | Space units: |
| | |
| | CYLINDER - Space units in cylinders |
| | TRACK - Space units in tracks |
| | BLOCK - Space units in blocks |
| | ???????? - Space units are unknown |
+-----------------+------------------------------------------------------|
| SYSEXTENTS | Number of extents allocated |
+-----------------+------------------------------------------------------|


Hope to help you

By
fabio

-----Messaggio originale-----
Da: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] Per conto di Lizette Koehler
Inviato: martedì 1 maggio 2012 17.19
A: TSO-...@VM.MARIST.EDU
Oggetto: Re: Easy way to acquire VSAM Space in REXX

BNL Gruppo BNPP notice

This e-mail, including any attachments, may contain private or confidential information.

If you think you may not be the intended recipient, or if you have received this e-mail in error,
please contact the sender immediately and delete all copies of this e-mail.

If you are not the intended recipient, you must not reproduce any part of this e-mail or disclose
its contents to any other party.

This message represents the opinion of the sender and not necessarily the opinion of the company.