Years ago when my then employer started using the OMVS technology the ESM was CA TOP SECRET. Processes failed because the inherited user did not have access to the STC "facility". TS allows you to control the ability to initiate a started task. Upon some head scratching analysis "holy cow, this stuff coming from the dark side uses mini STCS to do their thing." So we had to allow any user who did OMVS processes the ability to initiate a started task. I have long since forgotten which processes (oh, like I ever knew....) become started tasks. We figured all of them but never tested in order to be positive. Wish I would have learned better.....
Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone -------- Original message -------- From: Tom Marchant <[email protected]> Date: 6/17/2016 6:25 AM (GMT-08:00) To: [email protected] Subject: Re: Where is format of Job ID documented? On Thu, 16 Jun 2016 22:03:36 -0400, Robert A. Rosenberg wrote: >At 15:43 -0700 on 06/16/2016, Charles Mills wrote about Re: Where is >format of Job ID documented?: > >>Thanks. Anyone ever see an 'O'? Or a Mount? > >I think Mount is a Started Task and thus is S----. OTOH: It might run >under Master Scheduler not JES. IIRC, there three ways in MVS to create an address space: Start, Logon and Mount. So, is mount a started task? I don't know, but my guess is "no". Job ID is a JES construct, and I wouldn't expect JES to be involved in Mount. IIRC, JES3 assigns Job ID differently from JES2. -- Tom Marchant ---------------------------------------------------------------------- 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
