Rather than rolling out 2 different versions of sdsf to the world, why
not have the output from the secondary(backleveled JES) all routed via
NJE to the primary jes?  Then you would only need to logon via special
proc to debug problems(hopefully not too often). 


________________________________________________________
Dave Jousma
Mainframe Services
[EMAIL PROTECTED]
616.653.8429


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Elardus Engelbrecht
Sent: Wednesday, October 17, 2007 12:10 PM
To: [email protected]
Subject: Re: embarressing SDSF question.

McKown, John  wrote:
>The question I have is how to get SDSF to access the JESA system. I 
>think
that I'll need to use the 1.6 version of SDSF due to the JES2
dependancies in the SDSF code. True? I am just not figuring out how to
do this. The closest that I've come up with is a second TSO proc which
is STEPLIB'ed to the old SDSF code.


Create a second SDSF server and have your users with correct STEPLIB
connect to the correct SDSF server which will use/point to the correct
JES2.

Look in SDSF book for the word SERVERGROUP where you can use the correct
name of the SDSF server against whatever JES2 and whatever JES2 HASP
member.

Start a new server with something like S SDSF.SDSFT

Use TSO command to access correct SDSF server: SDSF SERVER(SDSFT).

PS: I never tried that, but once done this something like this for JESA
and JES328X when on OS/390.

HTH!


This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

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

Reply via email to