39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: calculating data set size - compression concern
Caution! This message was sent from outside your organization.
Listcat output changes when fields need more digits. DCollect doesn't change.
On Tue, Nov 5, 2019 at 11:20 PM Mike Hochee wrote:
>
9 11:20 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: calculating data set size - compression concern
>
> Caution! This message was sent from outside your organization.
>
> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idai200/recstr.htm
> IDCA
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mike Schwab
Sent: Tuesday, November 5, 2019 11:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: calculating data set size - compression concern
Caution! This message was sent from outside your organization.
https://www.ibm.com/support
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idai200/recstr.htm
IDCAMS DCOLLECT
RECORD TYPE D
264(X'108') CHARACTER 8 DCDUDSIZ USER DATA SIZE (64 BIT UNSIGNED
BINARY NUMBER) 272(X'110') CHARACTER 8 DCDCUDSZ COMPRESSED DATA SET
SIZE (64 BIT UNSIGNED BINARY NUMBER)
280
A couple months ago I was in the process of retrieving the size of a data set
on disk until I came across a flag in one or more DSCBs that indicate whether
or not the data set is compressed. This was the point at which I stopped
coding, concluding that it was probably not possible to come up wi