Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

Skip, Thanks for the explanation (I had to look up what AFAIK meant LOL) which makes sense to me. I verified my test code will return with RC=04 for an invalid DEST name (ANY!@#$%) which is what you would expect. I don't know if you saw the previous discussion (in December) as to what lead

Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

I think the IKJ message is from send/receive. -teD   Original Message   From: Tony Harminc Sent: Friday, January 29, 2016 00:42 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid On 29 January 2016 at 00:02, Skip

Re: [Bulk] Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

On 29 January 2016 at 01:09, Skip Robinson wrote: > 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 I guess I was

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

On 1/29/2016 9:13 AM, Skip Robinson wrote: I would be very interested to see a case where JES(2) rejects a DESTID, but in the meantime I'm inclined to believe that there is no restriction other the one(s) I mentioned above. Not a rejection per se, but I detect a significant difference in

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

Quoting Skip, "I would be very interested to see a case where JES(2) rejects a DESTID' Try the TSO command ALLOC SYSOUT(A) DEST(NOSUCH.ANY) where NOSUCH is a node not defined to your JES and ANY is anything. -- For

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: [Bulk] Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 > Destid > > On 29 January 2016 at 01:09, Skip Robinson <jo.skip.robin...@att.net> > wrote: > > It's curious that you're getting this message if you d

Re: [Bulk] Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

; From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Tony Harminc > Sent: Thursday, January 28, 2016 09:42 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid > > On 29 January 2016

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

Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

M-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

Re: [Bulk] Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

On 29 January 2016 at 00:02, Skip Robinson 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

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

@LISTSERV.UA.EDU] On Behalf Of SUBSCRIBE IBM-MAIN Harold Gray Sent: 04 December 2015 04:59 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFSSREQ SSOBUSER Validate A JES2 Destid A quick update. My test program is working (I get the same results as my subsystem R15=0 and SSOBRETN=0) for any printer name I

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

A quick update. My test program is working (I get the same results as my subsystem R15=0 and SSOBRETN=0) for any printer name I give it. I even changed the parmlist to create a version 0 SSUS and received the same results: SSOB @ C21C SSUS extension @ C238 SSIB @ C258 R1 pointer at

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

Yes, it did at one point but I'm not sure when it stopped. I only have access to z/OS 1.13 and 2.1 and JES2 in both accepts any destination name. CODE: LAR1,#JESSSIB LOAD AND DECLARE USING SSIB,R1 SSIB BASE

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

On 2 December 2015 at 09:54, SUBSCRIBE IBM-MAIN Harold Gray < harold.g...@mantissa.com> wrote: > Yes, it did at one point but I'm not sure when it stopped. I only have > access to z/OS 1.13 and 2.1 and JES2 in both accepts any destination name. What is the actual invalid name that it's

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

Tony, Thanks for the ideas especially looking at the source routine. I just assumed that JES was mostly OCO now! Anything I put in SSUSUSER is accepted. (ex HCGPRTR, XYZ, TRANSTT1 etc.). There are about 20 different id's that we use that do not correspond to JES. They are our own printers

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

On Tue, 1 Dec 2015 18:26:07 -0600 SUBSCRIBE IBM-MAIN Harold Gray wrote: :>Yes, that is the one I replied to. I guess it started a new number since it was so old. I was searching on the IEFSSREQ requests and saw the function code 11 which is exactly what I am doing.

AW: Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

> Anything I put in SSUSUSER is accepted. (ex HCGPRTR, XYZ, TRANSTT1 etc.). > There are about 20 different id's that we use that do not correspond to JES. > They are our own printers (desktops, LAN printers etc) that are only defined > to our subsystem. What do you mean with "do not

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

Any more ideas on this issue? I have the same problem under z/OS 2.1 (not sure how far back it quit working - unable to bring up anything older than 1.13). -- For IBM-MAIN subscribe / signoff / archive access instructions, send

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

AIN Harold Gray <harold.g...@mantissa.com> >Sent: Dec 1, 2015 2:48 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: IEFSSREQ SSOBUSER Validate A JES2 Destid > >Any more ideas on this issue? I have the same problem under z/OS 2.1 (not >sure how far back it quit working - unable

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

: IEFSSREQ SSOBUSER Validate A JES2 Destid Any more ideas on this issue? I have the same problem under z/OS 2.1 (not sure how far back it quit working - unable to bring up anything older than 1.13). -- For IBM-MAIN subscribe

Re: IEFSSREQ SSOBUSER Validate A JES2 Destid

Yes, that is the one I replied to. I guess it started a new number since it was so old. I was searching on the IEFSSREQ requests and saw the function code 11 which is exactly what I am doing. The R15 rc is 0 and the SSOBRETN value is 0 on any destination I submit to the function. I was