It's curious that you're getting this message if you do not have the issuing product installed. Search on IBM ServiceLink shows this:
OUTPUT MANAGER FOR Z/OS 210 or TIVOLI OUTPUT MANAGER Associated with FMID HAAX210 , HAAX230 , or HAAX310 . It would seem that this product is or once was installed in your system. I don't recognize the product, but the message indicates a fingerprint. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Tony Harminc > Sent: Thursday, January 28, 2016 09:42 PM > To: [email protected] > Subject: [Bulk] Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid > > On 29 January 2016 at 00:02, Skip Robinson <[email protected]> > wrote: > > I have forgotten why this behavior is deemed a problem. It's how JES(2) has > always worked AFAIK. You can specify DEST=HAROLD with no adverse effect. > The associated output will sit demurely in spool forever until HAROLD is > defined to some device or other existing destination. A lot of normal day-to- > day procedures depend on this function. > > So what is message > IKJ56875I type NOT operation, DESTINATION UNDEFINED TO SUBSYSTEM for? I > can remember getting it; remembering part of the text is how I managed to > Google for it. And that same search found 2012 APAR PM55876 against some > product I've never heard of, but it includes: > > Under certain circumstances, Bundle print program BJTBBDYS fails to print. > Symptoms include: > IKJ56875I SYSOUT DATA SET NOT ALLOCATED, DESTINATION UNDEFINED TO > SUBSYSTEM > > Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
