Re: STAE/ESTAE
Glad you enjoyed them mate. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Rob Scott Sent: Tuesday, July 19, 2005 5:31 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: STAE/ESTAE Chris, Carbon-based recovery analysis routine And ..that offer a point and shoot shortcut to your next unplanned IPL Two good chortles in two days ! -- 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: STAE/ESTAE
OK, I'll bite. In what way would having an MNOTE issued from STAE help someone? STAE is fully supported (and will be forever); it is just that there are better things out there, especially considering that STAE does not even support AMODE 31. If you're currently happy with your use of STAE, what benefit is there to your changing your (presumably working) program from its current use? If the MNOTE was a warning (CC=4), current users would be very unhappy. If it was CC=0 then you'd have to know to search for the MNOTE (unless you stumbled over it), and if you did know to search for it, you'd know enough just to scan for STAE. And if you're new and looking at documentation, you will see that the first line of the documentation for STAE contains Note: IBM recommends that you use the ESTAEX macro or ESTAE macro rather than STAE. Peter Relson z/OS Technology Design -- 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: STAE/ESTAE
thanks to all who answered my query. Bill Fairchild [EMAIL PROTECTED] wrote: In a message dated 7/19/2005 7:29:34 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: When will a STAE retry routine issue an abend? You have to write your own STAE, ESTAE, or ESTAEX routine. If you choose to put an ABEND macro inside that routine, then your STAE routine will issue the ABEND wherever you put it. If you don't put an ABEND macro in the routine, it will not issue the ABEND, in which case normal IBM code will sooner or later ABEND the program. But you asked about a STAE retry routine. The purpose of a retry routine is to keep executing even though the program has done something illegal which would ultimately result in an ABEND and termination of your program, in which case your STAE retry routine would not be issuing an ABEND. When your program has finished doing whatever is necessary to do in the retry situation, then you can choose to issue an ABEND macro or you can return to the normal return point in the Initiator/Terminator's code and tell MVS that everything ended normally (as in loading R15 with 0). It's your retry routine. You write it to do whatever you want. One thing you could do in the retry routine is continue executing normally just as if nothing bad had ever happened. Bill Fairchild -- 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 - Start your day with Yahoo! - make it your home page -- 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: STAE/ESTAE
David Alcock wrote: In the Java world, there is a term called deprecated for older API calls that still work but newer replacement ones are available. Here's one explanation: http://www.mindprod.com/jgloss/deprecated.html This term has been used for quite some time in the mainframe world (possibly for an even longer time than Java has been a language). Search the z/OS collection for the word deprecated. I found hits in 40 books. It'd be nice if IBM added a comment or MNOTE when an older macro like STAE is expanded. The comment would have a standard format which could be searched on in listings. The code generated would not be changed, just an additional comment printed. Or they could do something like what's being done in MCSOPER for z/OS V1R7 when certain obsolete keywords are used. The macro generates a severity one MNOTE, but provides a mechanism to suppress it for those cases in which you know its OK to use them (e.g., code that is guaranteed to execute on a back release only). Problem is, nobody wants to touch the old stuff. Doing so requires (albeit minimal) development time, testing time, and documentation effort -- all of which take away from resources allocated for new functionality. If it ain't broke, don't fix it -- *especially* if nobody's paying for it to be fixed! -- .-. | Edward E. Jaffe|| | Mgr, Research Development| [EMAIL PROTECTED]| | Phoenix Software International | Tel: (310) 338-0400 x318 | | 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801| | Los Angeles, CA 90045 | http://www.phoenixsoftware.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: STAE/ESTAE
The best reference for this is in the Authorized Assembler Programming Guide, pub number SA22-7608-07 Which can be viewed online at http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A850/CCONTENT S?SHELF=IEA2BK51DN=SA22-7608-07DT=20040714145712 But in short, ESTAE is used to trap ABEND conditions and allow the program to recover from errors, release resources or attempt to retry processing. Wayne Driscoll Product Developer Western Metal Supply NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of mary george Sent: Tuesday, July 19, 2005 6:57 AM To: IBM-MAIN@BAMA.UA.EDU Subject: STAE/ESTAE Hi, Can anyone throw light on the significance of STAE and ESTAE macro on error processing. Thanks in advance, Cheers, Mary __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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: STAE/ESTAE
Thanks Wayne. I have a further doubt on STAE, When will a STAE retry routine issue an abend? Wayne Driscoll [EMAIL PROTECTED] wrote: The best reference for this is in the Authorized Assembler Programming Guide, pub number SA22-7608-07 Which can be viewed online at http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A850/CCONTENT S?SHELF=IEA2BK51DN=SA22-7608-07DT=20040714145712 But in short, ESTAE is used to trap ABEND conditions and allow the program to recover from errors, release resources or attempt to retry processing. Wayne Driscoll Product Developer Western Metal Supply NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of mary george Sent: Tuesday, July 19, 2005 6:57 AM To: IBM-MAIN@BAMA.UA.EDU Subject: STAE/ESTAE Hi, Can anyone throw light on the significance of STAE and ESTAE macro on error processing. Thanks in advance, Cheers, Mary __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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: STAE/ESTAE
...
I have a further doubt on STAE,
When will a STAE retry routine issue an abend?
...
When will a COBOL programme write a record?
When you tell it to.
(8-{]}
-teD
In God we Trust!
All others bring data!
-- W. Edwards Deming
--
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: STAE/ESTAE
On Tue, 19 Jul 2005 05:29:19 -0700 mary george [EMAIL PROTECTED] wrote: :Thanks Wayne. :I have a further doubt on STAE, :When will a STAE retry routine issue an abend? What are you trying to do? What do you expect the (E)STAE(X) routine to do? :Wayne Driscoll [EMAIL PROTECTED] wrote: :The best reference for this is in the Authorized Assembler Programming :Guide, pub number SA22-7608-07 :Which can be viewed online at :http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A850/CCONTENT :S?SHELF=IEA2BK51DN=SA22-7608-07DT=20040714145712 :But in short, ESTAE is used to trap ABEND conditions and allow the program :to recover from errors, release resources or attempt to retry processing. :Wayne Driscoll :Product Developer :Western Metal Supply :NOTE: All opinions are strictly my own. :-Original Message- :From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf :Of mary george :Sent: Tuesday, July 19, 2005 6:57 AM :To: IBM-MAIN@BAMA.UA.EDU :Subject: STAE/ESTAE :Hi, :Can anyone throw light on the significance of STAE and ESTAE macro on error :processing. -- 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: STAE/ESTAE
On Tue, 19 Jul 2005 04:56:49 -0700, mary george [EMAIL PROTECTED] wrote: Hi, Can anyone throw light on the significance of STAE and ESTAE macro on error processing. Thanks in advance, Cheers, Mary Hmmm. Sounds suspiciously like a homework question. I can usually tell (I get them on search390.com all the time). -- Mark Zelden Sr. Software and Systems Architect Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ 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: STAE/ESTAE
I have a further doubt on STAE, STAE is obsolete, but still functional. You would never voluntarily choose to use STAE. IBM recommends ESTAEX. When will a STAE retry routine issue an abend? How long is a piece of string? There's no answer because its not a rational question. CC -- 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: STAE/ESTAE
How long is a piece of string? The purpose of a recovery routine is to recover from a situations that you have otherwise not programmatically not catered to. If no such recovery is possible, i.e. a request cannot be retried, you cannot figure out what is going on in the first place or manual intervention is required, you abend. In essence if you cannot recover or plain ignore what happened, you abend. And indeed - you always use ESTAEX for any number of reasons. /re -- 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: STAE/ESTAE
The purpose of a recovery routine is to recover from a situations that you have otherwise not programmatically not catered to. That's only one of the things a recovery routine is for. The primary purpose is to collect diagnostic information so that a carbon-based recovery analysis routine can figure out what went wrong and fix the application so it won't happen again. If its possible to safely retry to somewhere (without step 1 above) then that's a bonus. If no such recovery is possible, i.e. a request cannot be retried, you cannot figure out what is going on in the first place or manual intervention is required, you abend. In essence if you cannot recover or plain ignore what happened, you abend. NO! You collect diagnostic information and then you percolate control back to RTM with RC=0 which means I give up. There is no point in abending in a recovery routine. You're already under the control of RTM's tender mercies. That said, there's no great harm in it either. RTM is quite prepared to deal with recovery routines that abend. That happens all the time and often enough without the recovery routine even issuing SVC D :o) CC -- 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: STAE/ESTAE
In a message dated 7/19/2005 7:29:34 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: When will a STAE retry routine issue an abend? You have to write your own STAE, ESTAE, or ESTAEX routine. If you choose to put an ABEND macro inside that routine, then your STAE routine will issue the ABEND wherever you put it. If you don't put an ABEND macro in the routine, it will not issue the ABEND, in which case normal IBM code will sooner or later ABEND the program. But you asked about a STAE retry routine. The purpose of a retry routine is to keep executing even though the program has done something illegal which would ultimately result in an ABEND and termination of your program, in which case your STAE retry routine would not be issuing an ABEND. When your program has finished doing whatever is necessary to do in the retry situation, then you can choose to issue an ABEND macro or you can return to the normal return point in the Initiator/Terminator's code and tell MVS that everything ended normally (as in loading R15 with 0). It's your retry routine. You write it to do whatever you want. One thing you could do in the retry routine is continue executing normally just as if nothing bad had ever happened. Bill Fairchild -- 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: STAE/ESTAE
Chris, Carbon-based recovery analysis routine And ..that offer a point and shoot shortcut to your next unplanned IPL Two good chortles in two days ! -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Craddock, Chris Sent: 19 July 2005 11:53 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: STAE/ESTAE The purpose of a recovery routine is to recover from a situations that you have otherwise not programmatically not catered to. That's only one of the things a recovery routine is for. The primary purpose is to collect diagnostic information so that a carbon-based recovery analysis routine can figure out what went wrong and fix the application so it won't happen again. If its possible to safely retry to somewhere (without step 1 above) then that's a bonus. If no such recovery is possible, i.e. a request cannot be retried, you cannot figure out what is going on in the first place or manual intervention is required, you abend. In essence if you cannot recover or plain ignore what happened, you abend. NO! You collect diagnostic information and then you percolate control back to RTM with RC=0 which means I give up. There is no point in abending in a recovery routine. You're already under the control of RTM's tender mercies. That said, there's no great harm in it either. RTM is quite prepared to deal with recovery routines that abend. That happens all the time and often enough without the recovery routine even issuing SVC D :o) CC -- 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: STAE/ESTAE
In the Java world, there is a term called deprecated for older API calls that still work but newer replacement ones are available. Here's one explanation: http://www.mindprod.com/jgloss/deprecated.html It'd be nice if IBM added a comment or MNOTE when an older macro like STAE is expanded. The comment would have a standard format which could be searched on in listings. The code generated would not be changed, just an additional comment printed. -- 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
