CA Disk

[Anon Anon]

We have a report that originally gave space information in Tracks. Starting a couple months ago, the same report began showing the space information in Cylinders. We did not make any changes to the job, so we assume there must have been an upgrade or maintenance applied to CA Disk to cause our report to change. Is there a way to tell CA Disk to report in tracks instead of cylinders?

Here are the commands issued to DMS:
[font=Courier New]
//DMS.SYSIN DD *
SCAN REALVOLS
SELECT DSN=(/),VOL=(NMDP/,NMO0/,NMDT/)
REPORT SVDICT,COMPONENTS
SELECT DSN=(/), X
VOL=(NMDP/,NMO0/,NMDT/), X
CRITERIA=(USEDT,LE,TODAY-180)
EXCLUDE DSN=(UWDDB/)
EXCLUDE DSN=(VWDDB/)
REPORT DSUTIL,COMPONENTS
VREPORT ALLOCS [font]

Original report headings:

[font=Courier New] DEVICE UNIT SMS ----DATA SET CONTROL BLOCKS (DSCB) COUNTS----- ------------TRACKS---------- ---------FREE SPACE----------
VOLUME TYPE ADDR STAT FREE F1 F2 F3 F4 F5 F6 DEVICE ALLOC AVAIL IDLE EXTENTS THREE LARGEST
[font]
Headings now...

[font=Courier New] DEVICE UNIT SMS ----DATA SET CONTROL BLOCKS (DSCB) COUNTS----- -----------CYLINDERS----------- ---------FREE SPACE----------
VOLUME TYPE ADDR STAT FREE F1 F2 F3 F4 F5 F6 DEVICE ALLOC AVAIL IDLE EXTENTS THREE LARGEST
[font]
Thank you,
Arnold Brody
[e-mail]

[Dirk Reffke]

Hi Arnold,

The VREPORT generating modules were changed to support EAV devices.
For EAV devices the 54 GB limitation is gone and these devices can
now support up to 262,668 cylinders (223GB) per volume.
A report line with 132 characters could not accomodate all fields if
they are represented by tracks so we switched to cylinders.

Please let me know if this answers your question or if you would like
to pursue this further as a problem issue.

Regards,
Dirk Reffke
Sr Support Engineer
CA Technologies

[Anon Anon]

[font=Verdana][size=5]Hi, Dirk. Thank you for your feedback.

We have a complicated sequence of jobs used to generate space reports. All of these jobs feed off of the report produced in the first step of the first job, which used to give us space information in tracks.

I would like the option of asking for tracks. If I could get the report to look like it did before, our problem would be solved. Otherwise, it becomes a large task to rewrite all of the jobs based on cylinders.

Kindly advise what our options are. For example, would it be possible to return to some of the old modules that report on Tracks? I'm thinking in terms of loading the old modules into a separate library that the first job would point to. Are there other ways to resolve our problem?

Thank you for your advice.

Regards,
Arnold Brody[size][font]

[Dirk Reffke]

Hi Arnold,

I suggest we treat this as a problem. Please open a ticket and let me know the issue number,
or let me open it for you. In this case I would need your Company ID.

Regards,
Dirk

[Anon Anon]

[font=Verdana][size=4][size]Hi, Dirk.

I have engaged my IBM support team to open an internal change request. That will probably result in someone from the hosting MVS team (HP, not IBM) contacting Computer Associates to discuss possible solutions.

Since HP hosts the processing center and are likely the customer for your CA products, they would be able to provide the required Company ID.

Thank you for your assistance, and I hope a simple solution will be found!

Regards,
Arnold[font]

[System]

Hi Arnold,

Thank you for keeping everyone posted on this issue. Please post your resolution here when you have it.

Thanks!
Chris

[Marjory Montgomery]

While the VREPORT fields have been modified to display cylinders for the allocation, the ISPF Reporting is still using tracks. A very simliar report could be constucted using the ISPF Online Reports to replace the VREPORTS ALLOC currently being used.
My test job today
2011.223 AUG 11, 2011 TEST
THURSDAY 1.38 PM

FMT 1 FMT 2 FMT 3 FMT 4 FMT 5 FMT 6 SECOND THIRD
DEVICE UNIT DSCB DSCB DSCB DSCB DSCB DSCB FREE LARGEST LARGEST LARGEST
VOLSER TYPE ADDR COUNT COUNT COUNT COUNT COUNT COUNT DSCBS EXTENT EXTENT EXTENT EXT
------ ------ ---- ----- ----- ----- ----- ----- ----- ----- ------- ------- ------- ---
SMD001 3390 256C 2669 0 12 1 0 0 0 4269 4267 990 1
SMD002 3390 256E 2709 0 9 1 0 0 0 8534 4267 4267 1
SMD003 3390 20D7 2902 0 14 1 0 0 0 4267 3752 1708 1
SMD004 3390 20DB 6788 0 45 1 0 0 0 697 423 229 1
SMD005 3390 20AE 5676 0 29 1 0 0 0 6843 3000 2056 1
SMD006 3390 2030 3583 0 25 1 0 0 0 7755 405 90 1
SMD007 3390 2070 4314 0 15 1 0 0 0 2475 1140 1097 1
SMD008 3390 2050 4038 0 11 1 0 0 0 1545 1305 859 1
SMD009 3390 2035 3185 0 11 1 0 0 0 4267 4267 754 1


There are many other fields that could be included, I was trying to pick ones from ALLOC report.