We run APPC/ASCH. Here's what I see in SDSF. APPC and ASCH have no JES jobid. (Excuse the spacing; I can't seem to set the font in this note.)
JOBNAME Sys StepName JobID ASIDX APPC XX APPC 0049 ASCH XX ASCH 004E ASCHINT XX ASCHINT STC00503 0061 . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Thursday, November 20, 2014 7:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: What are STC, JOB and TSU? > John, the Unix stuff is so super cool like you said, but for me in this very > particular case I am working on when I see a TSO user ID racking up CPU time > as an STC, with my inside information I now know exactly what is going on. > They are spawned client/server sessions. Not necessarily clinent/server stuff, nor necessarily TSO user. You just define a USERID with a proper OMVS segment and no TSO segment. This user will be able to login to a UNIX shell via telnet/ssh/rlogin and do interactive work. These adress spaces will also show up as STC. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
