Curiosity piqued! I would be interested in seeing what you're seeing. On Wed, Apr 27, 2016 at 5:16 PM, Lindy Mayfield <[email protected]> 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 go" and new people have to take over and > try to understand. Lots of times my job is to help with such transitions. > > 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 instream, and looking at > the SJ jcl it didn't look "normal." > > $DPROCS showed something weird, I forget, but it was some proclib DD's, > two or 3 of them, then the system proclibs by name (SYS1.PROCLIB, etc....). > > When I stopped the STC, it started right back up again, which meant > automation software was there. It also meant that any proc of the same > name in any of the SYS1. or similar proclibs wouldn't start before the ones > that seems to be dynamically allocated in some way. > > Anyone have any idea what software I'm dealing with? I'll get around this > by simply creating a new STC name with STDATA and new USER and putting it > in one of the proclibs like SYS1.VDR.PROCLIB, but I'd like to understand if > I can what I wasted a few hours trying to figure out and never did. :) > > Thanks and kind regards! > Lindy > > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
