Re: ACS Write Statement Limitations
Ted, Agreed. And if it's conditional then it doesn't even get executed for datasets with the right naming standards. Ron The cost for doing this is a lot less than people believe. Stupid coding is still a problem; normal coding doesn't cost that much. -- 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: ACS Write Statement Limitations
On Tue, 2 Sep 2008 13:58:01 -0500, Mark Zelden [EMAIL PROTECTED] wrote: I empathize that you would like to write a novella to explain why it did not work, but then they won't need to call for help so that line could be removed. When faced with a limitation on what you can write out, use the IBM example - write your brief it failed call us mesage, followed by your own internal message id and fields you need to decipher why it failed and explain it when they call. Just look at an IOS* message for an example. And remember it takes time to process all that lengthy code your acs routines will be running through, slowing down your processor from doing real work. On Tue, 2 Sep 2008 14:51:09 -0400, Lizette Koehler [EMAIL PROTECTED] wrote: According to the DFSMS manual I am only allowed 110 characters. If it hurts, don't do it. :-) What's wrong with something like this: WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS.' + '** CONTACT STORAGE MGMT IF NEEDED' They should already know the allocation failed by the IGD* messages. Mark -- -- 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: ACS Write Statement Limitations
And remember it takes time to process all that lengthy code your acs routines will be running through, slowing down your processor from doing real work. The cost for doing this is a lot less than people believe. Stupid coding is still a problem; normal coding doesn't cost that much. Also, remember productivity (the reason we have computers) is a lot more important than worrying about one (or two) extra lines of messages. - Too busy driving to stop for gas! -- 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: ACS Write Statement Limitations
The text in your messages does not match the text in your WRITE statements. Are you sure you have the correct ACS routine? -Original Message- From: Lizette Koehler [mailto:snip] Sent: Tuesday, September 02, 2008 11:51 AM To: IBM-MAIN@BAMA.UA.EDU Subject: ACS Write Statement Limitations I am trying to figure out how to correct this issue. I am at z/OS V1.9. IGD01008I *** IGD01008I ** A L L O C A T I O NF A I L E D ! ! ** IGD01008I *** IGD01008I ** DATA SET DOES NOT CONFORM TO PROD NAMING STANDARDS** IGD01008I ** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS ** IGD01008I MESSAGES ISSUED BY STORCLAS ROUTINE HAVE EXCEEDED BUFFER AREA. NOT ALL MESSAGES WERE WRITTEN. According to the DFSMS manual I am only allowed 110 characters. However, I have the following coded +1+2+3+4+5+6+7-- +1+2+3+4+5+6+- WRITE '***' WRITE '** A L L O C A T I O NF A I L E D ! ! **' WRITE '***' WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS***' WRITE '** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS **' WRITE '***' EXIT CODE(22) END Which is 299 characters (spaces counted). Is there a way around this so I can produce more lines? Or do I have to reduce my content until it is at or below 110 characters? -- 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
ACS Write Statement Limitations
I am trying to figure out how to correct this issue. I am at z/OS V1.9. IGD01008I *** IGD01008I ** A L L O C A T I O NF A I L E D ! ! ** IGD01008I *** IGD01008I ** DATA SET DOES NOT CONFORM TO PROD NAMING STANDARDS** IGD01008I ** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS ** IGD01008I MESSAGES ISSUED BY STORCLAS ROUTINE HAVE EXCEEDED BUFFER AREA. NOT ALL MESSAGES WERE WRITTEN. According to the DFSMS manual I am only allowed 110 characters. However, I have the following coded +1+2+3+4+5+6+7--- WRITE '***' WRITE '** A L L O C A T I O NF A I L E D ! ! **' WRITE '***' WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS***' WRITE '** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS **' WRITE '***' EXIT CODE(22) END Which is 299 characters (spaces counted). Is there a way around this so I can produce more lines? Or do I have to reduce my content until it is at or below 110 characters? Lizette -- 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: ACS Write Statement Limitations
On Tue, 2 Sep 2008 14:51:09 -0400, Lizette Koehler [EMAIL PROTECTED] wrote: I am trying to figure out how to correct this issue. I am at z/OS V1.9. IGD01008I *** IGD01008I ** A L L O C A T I O NF A I L E D ! ! ** IGD01008I *** IGD01008I ** DATA SET DOES NOT CONFORM TO PROD NAMING STANDARDS** IGD01008I ** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS ** IGD01008I MESSAGES ISSUED BY STORCLAS ROUTINE HAVE EXCEEDED BUFFER AREA. NOT ALL MESSAGES WERE WRITTEN. According to the DFSMS manual I am only allowed 110 characters. However, I have the following coded +1+2+3+4+5+6+7--- WRITE '***' WRITE '** A L L O C A T I O NF A I L E D ! ! **' WRITE '***' WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS***' WRITE '** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS **' WRITE '***' EXIT CODE(22) END Which is 299 characters (spaces counted). Is there a way around this so I can produce more lines? Or do I have to reduce my content until it is at or below 110 characters? If it hurts, don't do it. :-) What's wrong with something like this: WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS.' + '** CONTACT STORAGE MGMT IF NEEDED' They should already know the allocation failed by the IGD* messages. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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: ACS Write Statement Limitations
EXIT CODE(22) END Which is 299 characters (spaces counted). Is there a way around this so I can produce more lines? Or do I have to reduce my content until it is at or below 110 characters? If it hurts, don't do it. :-) What's wrong with something like this: WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS.' + '** CONTACT STORAGE MGMT IF NEEDED' They should already know the allocation failed by the IGD* messages. Mark -- FWIW, in our environment (CA-Allocate AND SMS), we also make use of the JOBNAME/STEPNAME/DDNAME variables in our WRITE statements. Helps folks figure out what's going on a bit easier than IGD* messages. Bob Lester OppenheimerFunds -- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. == -- 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: ACS Write Statement Limitations
Lizette Koehler wrote: I am trying to figure out how to correct this issue. I am at z/OS V1.9. IGD01008I *** IGD01008I ** A L L O C A T I O NF A I L E D ! ! ** IGD01008I *** IGD01008I ** DATA SET DOES NOT CONFORM TO PROD NAMING STANDARDS** IGD01008I ** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS ** IGD01008I MESSAGES ISSUED BY STORCLAS ROUTINE HAVE EXCEEDED BUFFER AREA. NOT ALL MESSAGES WERE WRITTEN. According to the DFSMS manual I am only allowed 110 characters. However, I have the following coded +1+2+3+4+5+6+7--- WRITE '***' WRITE '** A L L O C A T I O NF A I L E D ! ! **' WRITE '***' WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS***' WRITE '** PLEASE CONTACT STORAGE MANAGEMENT FOR FURTHER DETAILS **' WRITE '***' EXIT CODE(22) END Which is 299 characters (spaces counted). Is there a way around this so I can produce more lines? Or do I have to reduce my content until it is at or below 110 characters? Lizette Lizette, I think the limitation you are running into is not number of characters, but number of lines. The 110 character limit is per line, but I think you can only write 4 or 5 lines. In a quick scan of the manual, I don't see this documented, but I remember running into this problem. -- Richard -- 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: ACS Write Statement Limitations
The z/OS V1R8.0 DFSMS Storage Administration Reference has this for the Write Statement At execution and allocation time, an end user can receive a maximum of five messages. If any more messages are generated, a sixth and final message indicates that additional messages have been generated, but the additional messages are not displayed. Thanks...Guy M. Gates Jr. TTI Z/OS Systems Programmer II -- 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: ACS Write Statement Limitations
Gates, Guy wrote: The z/OS V1R8.0 DFSMS Storage Administration Reference has this for the Write Statement At execution and allocation time, an end user can receive a maximum of five messages. If any more messages are generated, a sixth and final message indicates that additional messages have been generated, but the additional messages are not displayed. Thanks...Guy M. Gates Jr. TTI Z/OS Systems Programmer II Thanks for finding it, I figured it was in there somewhere, but didn't see it in my quick scan. -- Richard -- 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: ACS Write Statement Limitations
WRITE '** DATA SET DOES NOT CONFORM TO SYSTEM STANDARDS.' + '** CONTACT STORAGE MGMT IF NEEDED' Or: WRITE 'NON-STANDARD DATASET -- REFER TO STANDARDS DOCUMENT' - Too busy driving to stop for gas! -- 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
