Like most UNIX stuff, there's a setting in the RACF OMVS segment used to limit CPU time. See CPUTIMEMAX.
In article <caajsdjhmwujebqm2gs+ecbdsb49owg1vxvaqucat1h2p9ql...@mail.gmail.com> you wrote: > On Fri, Sep 19, 2014 at 9:55 AM, Terry Sambrooks > <[email protected]> wrote: > > Hi > > > > I might be wrong but the idle-time limit (Job Wait Time(JWT)) is surely a > > system wide limit set within SMFPRMnn and as such applies to both Batch and > > STCs, hence many installations code TIME=1440 on the EXEC within the STC > > procedure. > I think you are right. I know that I always code TIME=NOLIMIT or 1440 > in all STCs. Even ones that I know are short lived. I am unsure if it > applies to a UNIX address space which comes about via a fork(). I > think that fork() forces the equivalent of TIME=1440 on every address > space which it creates. But I could be wrong. > > > > Similarly the doesn't the PPT entry applu equally to a program whether it is > > started via an STC or Batch. CICS (DFHSIP) has PPT entries but can be > > started either as an STC or a Batch job are we saying that if CICS is > > started via Batch, as some installations do, that the PPT entry is not > > relevant. > Sorry about the PPT stuff. I was remembering the SYST entry in the > PPT. That one parameter only applies when the program is running in a > "single step STC". > > > > Kind Regards - Terry > > > > Director > > KMS-IT Limited > -- > There is nothing more pleasant than traveling and meeting new people! > Genghis Khan > Maranatha! <>< > John McKown -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive [email protected] (919) 531-5637 Cary, NC 27513 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
