On Thu, 31 Jul 2025 23:17:52 -0500, Brian Westerman <[email protected]> wrote:
>I can't assume that SDSF will be available when my task is running. > >I would just like to know what interface to JES that SDSF is using to get that >information. How do you believe the sysout DSN will be useful for your situation? This DSN can change over time because of open/close and may (or may not) be deleted. The answer depends upon your needs and how SYSOUT is being used. For example, running SUB=MSTR that enables dynamic SYSOUT that tolerates JES2 stop and restart is very different from a simple program using sysout. The following comments are not a complete list of considerations because we don't know how you will use the DSN. DSN is usually obtained through SVC99 (dynalloc) or TIOT (useful when not in your addr space). I suspect you can find it from the DCB but I've never looked. JES sysout DSN might not be available, might be incorrect or change outside of OPEN/CLOSE. I've never looked so it might be important that your program is aware of the DD state. JES can be accessed through SAPI. I'm guessing that SDSF uses SAPI but it may also include various JES commands. Someone mentioned DSN=&&MYOUT to add MYOUT in the SYSOUT DSN. This is important because CLOSE & OPEN should create a new DSN (at least in my implementation). Might be different depending on usage. Be aware that once a SYSOUT has been closed, JES may process and delete it while creating a new sysout for the same DD. This is how STC's can run for weeks without filling up spool. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
