Exactly...multiple TSO sessions. I hadn't thought of the "first on" explanation. I'm fixin' to look at EXIT 42 to see if it has the "source" member and, if so, I may try to route SEND commands that way. Not sure though. Hoping someone has an easy solution. ;-) Leland
________________________________ From: IBM Mainframe Discussion List on behalf of Brian Peterson Sent: Thu 8/18/2005 4:27 PM To: [email protected] Subject: Re: JES2 MAS and notify Are you using support to permit one TSO userid to logon to multiple LPARs? If so, my experience is that NOTIFY messages go to the TSO session which logged on "first". I have a 5-way MAS, and logon with one TSO userid to each of the 5 LPARs. No matter which TSO I use to submit or which LPAR the job runs on, all NOTIFY messages go to the TSO userid which logged on first in the MAS. Brian On Thu, 18 Aug 2005 15:33:09 -0500, Leland Lucius <[EMAIL PROTECTED]> wrote: >I'm setting up a MAS (z/OS 1.6) and have found the job notifies go to the >wrong member. I've looked around some and can't find a way to force it to >go to the member from which the job was submitted. > >Am I missing something? > >Thanks, > >Leland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
