Re: Scheduled STCs running as instream procs?

My test system is z/OS 2.2 but the message I indicated has been there for a long time (before 1.13 ;-) ) I was thinking that your started job's JCL was ... //WTOTEST JOB ...etc. ... //STEPNAME EXEC WTOPROC If that was your JCL then you'd have a message in JESYSMSG indicating where WTOPROC was

Re: Scheduled STCs running as instream procs?

Hm, interesting. My started job starts with this: //WTOTEST JOB (1),'WTOTEST', // CLASS=A,REGION=32M //* . . . etc etc SDSF shows the following files: JESMSGLG JESJCL JESYSMSG SYSTSPRT TB No SYSMSGS. The JESMSGS

Re: Scheduled STCs running as instream procs?

suppression going on there that I'd never seen before. Br, Lindy -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dan D Sent: tiistaina 3. toukokuuta 2016 20.58 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Scheduled STCs running as instream

Re: Scheduled STCs running as instream procs?

"Willy Jensen" wrote ... > A started job will not tell you from where it came. On the other hand, it will also not say instream. > > Willy > Willy, If you look at the SYSMSGS of a started job you will still see ... 3 IEFC001I PROCEDURE procname WAS EXPANDED USING INSTREAM PROCEDURE DEFINITION

Re: Scheduled STCs running as instream procs?

A started job will not tell you from where it came. On the other hand, it will also not say instream. Willy -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: Scheduled STCs running as instream procs?

On Wed, 27 Apr 2016 22:16:49 +, Lindy Mayfield wrote: > > Today I saw something I've never seen before. I wanted to know where a > started task was running from and normally the SDSF jes2 log shows which > > proclib it was loaded from. But it said it was

Re: Scheduled STCs running as instream procs?

Yeah maybe Racf profiles for STARTED might give a clue. In a message dated 4/27/2016 6:29:01 P.M. Central Daylight Time, stars...@mindspring.com writes: Show us the SJ output? Anything else relevant? -- For IBM-MAIN

Re: Scheduled STCs running as instream procs?

Subject: Re: Scheduled STCs running as instream procs? Lindy, These details are a little sketchy. Could you add some more details? What STC (Is it a vendor product or something else)? Can you show us your display details that you were looking at? Show us the SJ output? Anything else relevant

Re: Scheduled STCs running as instream procs?

On 4/27/2016 6:16 PM, Lindy Mayfield wrote: No machines are as customizable as mainframes, especially ones that have been running for decades. Sometimes things are hard to figure out, especially if the machine goes from the owner to outsourced or whatever, and all that, then people are "let

Re: Scheduled STCs running as instream procs?

age- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lindy Mayfield > Sent: Wednesday, April 27, 2016 3:17 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Scheduled STCs running as instream procs? > > No machines are as customizable as mai

Re: Scheduled STCs running as instream procs?

Curiosity piqued! I would be interested in seeing what you're seeing. On Wed, Apr 27, 2016 at 5:16 PM, Lindy Mayfield wrote: > No machines are as customizable as mainframes, especially ones that have > been running for decades. Sometimes things are hard to figure out, >

Scheduled STCs running as instream procs?

No machines are as customizable as mainframes, especially ones that have been running for decades. Sometimes things are hard to figure out, especially if the machine goes from the owner to outsourced or whatever, and all that, then people are "let go" and new people have to take over and try