> On our z/OS 2.4 system there's still a SDSFAUX address space.
Yes, SDSFAUX remains to execute various data gatherers, XCF communications and
so on, but the allocation of HSFLOG and HSFTRACE was moved to the SDSF address
space with z/OS 2.3.
On our z/OS 2.4 system there's still a SDSFAUX address space.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> I believe it's SDSFAUX that allocates these files...
> Dan
Used to be SDSFAUX. With z/OS 2.3, the SDSF address space took over this
function.
Ant.
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
Allocate them yourself.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Gadi Ben-Avi
Sent: Wednesday, January 15, 2020 1:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: HSFLOG and HSFTRACE
Hi
> Hi,
> SDSF allocates two SYSOUT files named HSFLOG and HSFTRACE.
> How do I change the SYSOUT Class these files use?
> I am running z/OS v2.3
> Gadi
SYSOUT class for SDSF trace can be set in ISFPRMxx
OPTION TRCLASS(output class)
Defaults to class A.
I don't see an ISF
I believe it's SDSFAUX that allocates these files.
Check proclib for this member and just change the DD statements.
Dan
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
Hi,
SDSF allocates two SYSOUT files named HSFLOG and HSFTRACE.
How do I change the SYSOUT Class these files use?
I am running z/OS v2.3
Gadi
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists
