Well, I would say (1) it is part of IBM z/OS now. IBM charges big bucks for it, so they own the problem, no matter where it came from originally.
But (2) nowhere did I blame IBM explicitly. It is shamefully poor programming practice no matter what company hat the programmer was wearing at the time. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Schwab Sent: Friday, November 9, 2018 6:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Venting about error messages and documentation BPX* is Open System Service, or ported Unix. Not an IBM Mainframe style product at all. On Fri, Nov 9, 2018 at 4:52 PM Charles Mills <charl...@mcn.org> wrote: > > Gosh some of the error message documentation -- really the software design > leading up to the error message -- is just plain awful! > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bp > xa800/fsum7131.htm > > FSUM7131 Out of space or reached the end of the archive file. If you want > to go on, type device or file name when ready. > Explanation > There is no more room to write the archive or extract members, or the end of > the archive file has been reached. It is also possible that the archive is > corrupt. > > Was it really necessary to fold three different error conditions into one > error message? And by the way, "type device or file name" is inappropriate > in a batch job. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
