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.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile jo.skip.robin...@att.net > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of SUBSCRIBE IBM-MAIN Harold Gray > Sent: Thursday, January 28, 2016 02:57 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid > > Another update after many breaks in my research. I have not been able to find > any fault with the IBM code. In doing some research on JES2 initialization, I > haven't seen anything that tells JES to ignore invalid DESTs or require valid > DESTs. I can change any report in the output queue with SDSF to any DEST > value I want (using my names from my earlier posts: XYZ, HCGPNTR etc.) and > these names are not defined to JES. This tells me that my JES is setup to > accept any DEST name (that doesn't conform to the standard explicit naming > conventions). Does anyone know of an initialization parameter that would > allow this? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
