That was the message I got. And I forget exactly but $DPROCLIB gave me I think something like MSTJCL00, MSTJCL01, then some dataset names.
Cancelling a started task caused it to start right up again. So my problem was that normally I can work backwards on MVS to find the source code of the STC, but here I couldn't. Some automation software was in control, and that instream message was new to me. If I was smarter I could have a) figured out where/how MSTJCLxx was allocated, b) figure out what automation software was used (probably Tivoli or one of those), or c) found somebody who knew. I honestly had to write a simple Rexx program to look at the control blocks to show what security program was being used, even though I was told and it was clear it was RACF. I just saw too many messages starting ACF9xxxx, and hardly any ICH.... so perhaps they had major message suppression going on there that I'd never seen before. Br, Lindy -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Dan D Sent: tiistaina 3. toukokuuta 2016 20.58 To: [email protected] Subject: Re: Scheduled STCs running as instream procs? 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
