Re: UR1 vs FIN
I prefer: BAC Broken As Coded John P. Baker -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Monday, June 23, 2008 8:06 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: UR1 vs FIN >The APAR closing codes are: You forgot: WAD Working As Designed And (humour?): BAD Broken As Designed FN Fixed Never - 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: UR1 vs FIN
>The APAR closing codes are: You forgot: WAD Working As Designed And (humour?): BAD Broken As Designed FN Fixed Never - 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: UR1 vs FIN
Roger Bolan wrote: UR1 is used for changes that are regarded as "new function" or some kind of improvement or enhancement that was not technically a "programming error" (close code PER) because the program was implementing what the programming specification had said it should do. It also means that the "fix" will be in a PTF for the current release. Pinnacle wrote: It's better than a FIN because the work's been done. I've had FIN's get "lost" before, and waited multiple releases for the fix. Based on what I learned here, I asked: |UR1 means the fix has already been coded and tested. Otherwise, it would |be FIN. Right? The response was ... | UR1 does not indicate that the fix has |already been coded and tested. It basically means that the problem will |be fixed but cannot be rolled back to earlier releases. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] 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: UR1 vs FIN
On Mon, 16 Jun 2008 14:24:08 -0400, Robert Wright wrote: > > OA25428, for example, let current IPCS developers know that a >developer 14 years ago made a data entry field on one panel two >characters too narrow to accept the widest item that can properly be >entered there. Hopefully, a lot of these irritants can go away as a >consequence of similar FIN APARs. > OTOH, over time I reported two errors in SMP/E very similar to the above: one where it got an error on a widest possible item, and later another where it got an error on the narrowest possible item (in the same field). Both were fixed in the service stream. And another that I called a SEV4 on SMP/E's issuing an unclear error message. They produced a PTF within 3 weeks that removed the error entirely. SMP/E development has pride in craftsmanship. I hope JCL development is paying attention. -- gil -- 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: UR1 vs FIN
In addition to Bob's update, I was told the same thing offline. Fixed If Next. Roger Bolan infoprint.com Boulder, Colorado, USA P Think before you print Robert Wright <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List 06/16/2008 12:24 PM Please respond to IBM Mainframe Discussion List To IBM-MAIN@BAMA.UA.EDU cc Subject Re: UR1 vs FIN Roger Bolan wrote: > > FIN means "fixed in next", but this does not absolutely guarantee that there will be a "next release". That's why you might have heard it as "fixed IF next". It's generally used for certain kinds of changes that are only allowed to happen on a release boundary (like a significant change in the packaging protocol) or some other kind of really significant change that can't be done by just a PTF. FIN really means "Fixed IF next" for good, legal reasons. In addition to the situations that you describe for FIN use, it opens the door wider for customers to report nits that neither the customer nor IBM thinks warrant shipping more PTFs in the service streams for current releases. OA25428, for example, let current IPCS developers know that a developer 14 years ago made a data entry field on one panel two characters too narrow to accept the widest item that can properly be entered there. Hopefully, a lot of these irritants can go away as a consequence of similar FIN APARs. Bob Wright - MVS Service Aids -- 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: UR1 vs FIN
Roger Bolan wrote: > > FIN means "fixed in next", but this does not absolutely guarantee that there will be a "next release". That's why you might have heard it as "fixed IF next". It's generally used for certain kinds of changes that are only allowed to happen on a release boundary (like a significant change in the packaging protocol) or some other kind of really significant change that can't be done by just a PTF. FIN really means "Fixed IF next" for good, legal reasons. In addition to the situations that you describe for FIN use, it opens the door wider for customers to report nits that neither the customer nor IBM thinks warrant shipping more PTFs in the service streams for current releases. OA25428, for example, let current IPCS developers know that a developer 14 years ago made a data entry field on one panel two characters too narrow to accept the widest item that can properly be entered there. Hopefully, a lot of these irritants can go away as a consequence of similar FIN APARs. Bob Wright - MVS Service Aids -- 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: UR1 vs FIN
In my experience, the difference is normally this: UR1 is used for changes that are regarded as "new function" or some kind of improvement or enhancement that was not technically a "programming error" (close code PER) because the program was implementing what the programming specification had said it should do. It also means that the "fix" will be in a PTF for the current release. FIN means "fixed in next", but this does not absolutely guarantee that there will be a "next release". That's why you might have heard it as "fixed IF next". It's generally used for certain kinds of changes that are only allowed to happen on a release boundary (like a significant change in the packaging protocol) or some other kind of really significant change that can't be done by just a PTF. Roger Bolan infoprint.com Boulder, Colorado, USA P Think before you print Edward Jaffe <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List 06/16/2008 09:36 AM Please respond to IBM Mainframe Discussion List To IBM-MAIN@BAMA.UA.EDU cc Subject UR1 vs FIN I'm being offered "UR1" closure for an APAR. The description sounds just like "FIN" closure. Is there a difference? -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] 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 -- 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: UR1 vs FIN
Brian Peterson wrote: FIN Fixed in next release UR1 Programming error in the reported release; the problem has been corrected in a release not yet available from distribution Sounds like "UR1" means something to the effect that the problem has actually been fixed in an announced but not yet GA release. In presentations more recent than the above document, I've heard IBM refer to FIN as "Fixed IF Next" so that the FIN code is not interpreted as being a commitment to deliver a product prior to such product's actually being announced. I specifically asked if UR1 meant it would be fixed in R10. They said "No". That means it must be R11 -- which (AFAIK) has not yet been announced. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] 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: UR1 vs FIN
- Original Message - From: "Edward Jaffe" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main Sent: Monday, June 16, 2008 11:36 AM Subject: UR1 vs FIN I'm being offered "UR1" closure for an APAR. The description sounds just like "FIN" closure. Is there a difference? Ed, It's better than a FIN because the work's been done. I've had FIN's get "lost" before, and waited multiple releases for the fix. Tom -- 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: UR1 vs FIN
>From ServiceLink User's Guide Document Number SH52-0300-10 September 1996, as found in VM IBMLink: Appendix B.1 APAR Closing Codes The APAR closing codes are: ADM A partially closed APAR; can still be added to AST list; contains administrative information only right now; technical information will be added later CAN Canceled by person who submitted APAR DOC Documentation error DUA Duplicate of a resolved APAR closed for more than ten days DUB Duplicate of a resolved APAR closed for ten days or less DUU Duplicate of an unresolved APAR FIN Fixed in next release MCH Machine or microcode error PER Programming error PRS Permanent restriction REQ Requirement for Development's consideration RET Returned for additional information STD Open Systems Standards deficiency SUG Suggestion for product enhancement UR1 Programming error in the reported release; the problem has been corrected in a release not yet available from distribution UR2 Same as UR1 but written against an unsupported release UR3 Programming error in the reported release; does not exist in the current release available from distribution UR4 Same as UR3 but written against an unsupported release UR5 Unable to reproduce on the reported release USE User error Sounds like "UR1" means something to the effect that the problem has actually been fixed in an announced but not yet GA release. In presentations more recent than the above document, I've heard IBM refer to FIN as "Fixed IF Next" so that the FIN code is not interpreted as being a commitment to deliver a product prior to such product's actually being announced. I would further say that if you believe the problem should be fixed in the current release, you should still ask for that. If you believe IBM is correct that an upcoming release is adequate, then accept IBM's offer for the UR1 closing code. Brian On Mon, 16 Jun 2008 08:36:24 -0700, Edward Jaffe wrote: >I'm being offered "UR1" closure for an APAR. The description sounds just >like "FIN" closure. Is there a difference? > >-- >Edward E Jaffe -- 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
UR1 vs FIN
I'm being offered "UR1" closure for an APAR. The description sounds just like "FIN" closure. Is there a difference? -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] 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
