APAR for failure to follow doc. Gotta be careful though. Could turn into a doc APAR. ;-(
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Steve Smith Sent: Wednesday, March 11, 2020 3:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Two related alias entry address questions CAUTION EXTERNAL EMAIL Seems to me that should be reported as a bug. It's not technically an enhancement to make the program conform to its documentation. sas On Wed, Mar 11, 2020 at 4:18 PM Charles Mills <charl...@mcn.org> wrote: > If anyone else would like to see IEBCOPY return RC 4 for warning > conditions you may so vote here: > > https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID= > 140952 > > > I think you need a DeveloperWorks ID. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Charles Mills > Sent: Monday, March 9, 2020 6:24 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Two related alias entry address questions > > <snip> > > My point below is relative only to IEBCOPY. IGG0nnnW messages are > documented as resulting in a return code 4. IEBCOPY is failing to do > that. > > The documentation matches what you said. The behavior does not match > the documentation. > > Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
