Re: Dynamically obtaining allocated space characteristics
Thank you for your help Charles & all. I believe I am now able to calculate/generate most of the same information for a dataset that is available in ispf which is the bulk of my current project. Dave -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Charles Mills Sent: Thursday, November 16, 2006 10:25 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics It occurs to me that the conclusion of my note should read "CSI will return the former. The DSCBs will let you compute the latter, and also return the TRK and the 2 part of the original allocation." Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Charles Mills Sent: Wednesday, November 15, 2006 4:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics Specifically, it's in DFSMS Managing Catalogs. Does the OP want to know the space requested for the dataset, or the space used by a dataset? E.g., do you want to be able to determine that the dataset was allocated SPACE=(TRK,(5,2)) or that the dataset now occupies 9 tracks? CSI will return the former. The DSCBs will let you compute the latter. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 11/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 11/13/2006 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
It occurs to me that the conclusion of my note should read "CSI will return the former. The DSCBs will let you compute the latter, and also return the TRK and the 2 part of the original allocation." Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Charles Mills Sent: Wednesday, November 15, 2006 4:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics Specifically, it's in DFSMS Managing Catalogs. Does the OP want to know the space requested for the dataset, or the space used by a dataset? E.g., do you want to be able to determine that the dataset was allocated SPACE=(TRK,(5,2)) or that the dataset now occupies 9 tracks? CSI will return the former. The DSCBs will let you compute the latter. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
RES: Dynamically obtaining allocated space characteristics
Take a look at archives and search for a program provided by Jim Moore, that does exactly what you need. Atenciosamente / Regards / Saludos Banco Bradesco S/A 4254/DPCD Alphaville Suporte Técnico - Software Básico Mainframes Ituriel do Nascimento Neto Tel: 55 11 4197-2021 Fax: 55 11 4197-2814 -Mensagem original- De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Em nome de Gerhard Postpischil Enviada em: terça-feira, 14 de novembro de 2006 20:33 Para: IBM-MAIN@BAMA.UA.EDU Assunto: Re: Dynamically obtaining allocated space characteristics Dave Quinn wrote: > Ive been digging for a couple of days now trying to find out how I > can dynamically retrieve the allocated space of a known dataset. Can > anyone give me even a whiff of where to look? It would help if you defined your environment. Easiest is the write an assembler routine to obtain and analyze the format 1 and (if any) format 3 DSCB entries for the data set. That requires knowing the volume serial, doing a catalog locate, or prompting user. In TSO you can write a small REXX function to get variables for the data set (LISTDSI). Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html AVISO LEGAL Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou legalmente privilegiada. Se você não for destinatário desta mensagem, desde já fica notificado de abster-se a divulgar, copiar, distribuir, examinar ou, de qualquer forma, utilizar a informação contida nesta mensagem, por ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu conteúdo em sua base de dados, registros ou sistema de controle. Fica desprovida de eficácia e validade a mensagem que contiver vínculos obrigacionais, expedida por quem não detenha poderes de representação. +**+ LEGAL ADVICE This message is exclusively destined for the people to whom it is directed, and it can bear private and/or legally exceptional information. If you are not addressee of this message, since now you are advised to not release, copy, distribute, check or, otherwise, use the information contained in this message, because it is illegal. If you received this message by mistake, we ask you to return this email, making possible, as soon as possible, the elimination of its contents of your database, registrations or controls system. The message that bears any mandatory links, issued by someone who has no representation powers, shall be null or void. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
Specifically, it's in DFSMS Managing Catalogs. Does the OP want to know the space requested for the dataset, or the space used by a dataset? E.g., do you want to be able to determine that the dataset was allocated SPACE=(TRK,(5,2)) or that the dataset now occupies 9 tracks? CSI will return the former. The DSCBs will let you compute the latter. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Eric Spencer Sent: Wednesday, November 15, 2006 12:13 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics Have a look at the Catalog Search Interface (CSI) in the DFSMSdfp manuals. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
Have a look at the Catalog Search Interface (CSI) in the DFSMSdfp manuals. Eric Spencer Neon Enterprise Software Inc. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Black Sent: Wednesday, November 15, 2006 11:53 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics > > I refuse to admit that this is not kept handy somewhere. ISPF's "Dataset > Information" has it, why can't I. ISPF does not display the primary allocation, it displays the "first extent size" General Data Current Allocation Management class . . : **None** Allocated cylinders : 10 Storage class . . . : PRIDATAAllocated extents . : 1 Volume serial . . . : IDPLB4 Maximum dir. blocks : 200 Device type . . . . : 3390 Data class . . . . . : **None** Organization . . . : POCurrent Utilization Record format . . . : FB Used cylinders . . : 9 Record length . . . : 80 Used extents . . . : 1 Block size . . . . : 23440 Used dir. blocks . : 200 1st extent cylinders: 10 Number of members . : 1,195 Secondary cylinders : 0 Data set name type : PDS -- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: [EMAIL PROTECTED] sales info: [EMAIL PROTECTED] tech support: [EMAIL PROTECTED] web: www.innovationdp.fdr.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
I refuse to admit that this is not kept handy somewhere. ISPF's "Dataset Information" has it, why can't I. ISPF does not display the primary allocation, it displays the "first extent size" General Data Current Allocation Management class . . : **None** Allocated cylinders : 10 Storage class . . . : PRIDATAAllocated extents . : 1 Volume serial . . . : IDPLB4 Maximum dir. blocks : 200 Device type . . . . : 3390 Data class . . . . . : **None** Organization . . . : POCurrent Utilization Record format . . . : FB Used cylinders . . : 9 Record length . . . : 80 Used extents . . . : 1 Block size . . . . : 23440 Used dir. blocks . : 200 1st extent cylinders: 10 Number of members . : 1,195 Secondary cylinders : 0 Data set name type : PDS -- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: [EMAIL PROTECTED] sales info: [EMAIL PROTECTED] tech support: [EMAIL PROTECTED] web: www.innovationdp.fdr.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
Dave, >I want to run in a batch Assembler program. Possibly provide a DSN as input and return information as close to as possible that is returned from ISPF's Dataset Information screen. I think Charles (Mills) offered some sample code that may help you (already deleted the article). >I had been looking at DSCB and came to the same conclusion about the primary space. I can total the tracks used through the extent list to get the space used and get the secondary space requested, just not the primary requested. I don't believe I could always find the SMF record. I refuse to admit that this is not kept handy somewhere. ISPF's "Dataset Information" has it, why can't I. I believe ISPF only shows the size of the first extent which may or may not be the primary allocation amount. You can use up to five extents getting your primary allocation. >I do not have any 3rd party software. I use CA-Disk (DMS) to produce a report showing this kind of information. The only place that I ever found the primary allocation amount was in the job output (or jcl) of the creating job or on the SMF 15 record written when the dataset was allocated. Regards, John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
You're right: ISPF has it, and you should be able to get it the same way, but you can't. Why not? For the answer, search the archives for FAMS. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dave Quinn Sent: Wednesday, November 15, 2006 8:00 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics Thanks so far ... I want to run in a batch Assembler program. Possibly provide a DSN as input and return information as close to as possible that is returned from ISPF's Dataset Information screen. I had been looking at DSCB and came to the same conclusion about the primary space. I can total the tracks used through the extent list to get the space used and get the secondary space requested, just not the primary requested. I don't believe I could always find the SMF record. I refuse to admit that this is not kept handy somewhere. ISPF's "Dataset Information" has it, why can't I. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
Thanks so far ... I want to run in a batch Assembler program. Possibly provide a DSN as input and return information as close to as possible that is returned from ISPF's Dataset Information screen. I had been looking at DSCB and came to the same conclusion about the primary space. I can total the tracks used through the extent list to get the space used and get the secondary space requested, just not the primary requested. I don't believe I could always find the SMF record. I refuse to admit that this is not kept handy somewhere. ISPF's "Dataset Information" has it, why can't I. I do not have any 3rd party software. Dave Quinn. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Kington Sent: Wednesday, November 15, 2006 10:26 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics You can tell the secondary allocation amount from the DSCB but the primary is not kept in the DSCB for nonvsam datasets. Only the size of the first extent is kept. If you have the SMF type 15 record, a portion of the JFCB is imbedded in the record. Somewhere around offset 220 is the primary amount in three byte binary followed by one byte binary for space type and then a three byte binary field with the secondary amount. This would not help if the dataset is never opened. In that case, the amount of space allocated would be the primary amount and you can see the secondary amount in the DSCB. I have CA-Allocate (VAM) available to me. If you have that product or a similar product, you should be able to look for the program, ddname, jobname or whatever and generate a wto message with the primary amount, secondary amount and space allocation type. This would be the easiest and surest method. Regards, John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 11/13/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 11/13/2006 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
You can tell the secondary allocation amount from the DSCB but the primary is not kept in the DSCB for nonvsam datasets. Only the size of the first extent is kept. If you have the SMF type 15 record, a portion of the JFCB is imbedded in the record. Somewhere around offset 220 is the primary amount in three byte binary followed by one byte binary for space type and then a three byte binary field with the secondary amount. This would not help if the dataset is never opened. In that case, the amount of space allocated would be the primary amount and you can see the secondary amount in the DSCB. I have CA-Allocate (VAM) available to me. If you have that product or a similar product, you should be able to look for the program, ddname, jobname or whatever and generate a wto message with the primary amount, secondary amount and space allocation type. This would be the easiest and surest method. Regards, John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
There is no one great method. I've got a routine that does this although my comments at the front say: * Several SERIOUS shortcomings to this routine: *1. No multi-volume support. *2. "Large file" (z/OS 1.7) and "extended file" support untested. *3. What to do about members, VSAM, etc. The routine gets passed two parameters: *1. The name of the dataset, 1 to 44 characters, left-justified *2. The first volume on which it resides. * The plan is to make this second parameter optional at some * point. If the parameter were omitted, the assembler code * would use LOCATE and CAMLST to find the dataset. The code uses OBTAIN and CAMLST to read the DSCB-1 for the dataset. It totals up the tracks from the DSCB-1. If the DSCB indicates that there is a DSCB-3, it reads the next DSCB-3 and totals up the tracks from the DSCB-3(s). I'd offer to share the code with you but it has several special aspects that would probably make it unsuitable for your use. I'll answer any specific questions if you come back here with them. I'll e-mail you the key "total up the tracks" loop if you e-mail me privately. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Binyamin Dissen Sent: Wednesday, November 15, 2006 12:43 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Dynamically obtaining allocated space characteristics On Tue, 14 Nov 2006 15:59:53 -0500 Dave Quinn <[EMAIL PROTECTED]> wrote: :>I've been digging for a couple of days now trying to find out how I can :>dynamically retrieve the allocated space of a known dataset. Can anyone :>give me even a whiff of where to look? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
On Tue, 14 Nov 2006 15:59:53 -0500 Dave Quinn <[EMAIL PROTECTED]> wrote: :>Ive been digging for a couple of days now trying to find out how I can :>dynamically retrieve the allocated space of a known dataset. Can anyone :>give me even a whiff of where to look? DSCB. -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamically obtaining allocated space characteristics
Dave Quinn wrote: I’ve been digging for a couple of days now trying to find out how I can dynamically retrieve the allocated space of a known dataset. Can anyone give me even a whiff of where to look? It would help if you defined your environment. Easiest is the write an assembler routine to obtain and analyze the format 1 and (if any) format 3 DSCB entries for the data set. That requires knowing the volume serial, doing a catalog locate, or prompting user. In TSO you can write a small REXX function to get variables for the data set (LISTDSI). Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Dynamically obtaining allocated space characteristics
I’ve been digging for a couple of days now trying to find out how I can dynamically retrieve the allocated space of a known dataset. Can anyone give me even a whiff of where to look? Dave Q -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 11/13/2006 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html