Find the SDSFAUX sample JCL and copy it to your system PROCLIB. Create a user id and started task profile for it in your security product.
SDSF will automatically start the new address space when it starts. Everything should be happy. That's all I remember I had to do when I started playing with z/OS V2R3. On Tue, 9 Oct 2018 18:02:39 +0000, Dunlap, Curtis L <cvd5...@psu.edu> wrote: >Thanks, but I've checked with our ACF2 admin and he says SDSF class is not >activated. > >Curt > > >________________________________ >From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of >Matt Hogstrom <m...@hogstrom.org> >Sent: Tuesday, October 9, 2018 12:41:33 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: ISF452E on SDSF using MACRO ISFPARMS only on z/OS V2.3. > >If its the same problem I had you have to make the SDSF class Raclistable. > > >Matt Hogstrom >m...@hogstrom.org >+1-919-656-0564 >PGP Key: 0x90ECB270 > >> On Oct 9, 2018, at 5:01 PM, Dunlap, Curtis L <cvd5...@psu.edu> wrote: >> >> Hi IBM-MAIN Mainframers! Long time listener, first time caller. :-) >> >> I'm upgrading from z/OS V2.1 to V2.3 and I'm receiving this message opening >> SDSF: >> ISF452E SDSFAUX communications failed, return code 0x00000008, >> reason code 0x00370801, function "connect". SDSFAUX not available >> or function not supported >> I tried to implement SDSF with the ISFPARMS USERMOD table w/o SDSF* servers >> to expedite the OS upgrade and am now receiving this message when SDSF is >> executed from TSO, ISPF or batch. I've struck out doing searches on the >> webernets (and IBM as well) for this particular scenario, but from what I've >> read, I should still be able to use SDSF w/o the servers running. Anybody >> out there have any good ideas short of converting? >> >> Thanks in advance. >> Curt. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
