AW: Re: TIME= on JOB card vs. EXEC card

>If you put TIME= on the JOB card, then this trounces the JOBCLASS TIME=, and >none of your steps, either the first step or in total, can exceed the TIME on >the JOB card. While I agree with the second part, I do not with the first. As I described earlier, the job level TIME= defines how

JCLLIB RECFM?

in: z/OS 2.1.0 z/OS MVS z/OS MVS JCL Reference JCLLIB statement Description Considerations for using the JCLLIB statement I read: ... The private library must have the same data set attributes as a system library, which are: ... Fixed length records (RECFM=F or

Re: EXTERNAL: Re: many OMVSKERN task not stop

Just so. Check the AUTOLOG statement in the TCPIP PROFILE deck. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jerry Whitteridge Sent: Wednesday, 26 October 2016 3:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: EXTERNAL: Re:

Re: Does anyone use HFS files extensively with HLASM?

On Tue, 25 Oct 2016 16:49:46 -0700, Charles Mills wrote: > >Yeah, I could test the basic issues but I am wondering if anyone is doing >this extensively and "happy with it." What are the gotchas? Those are tough >questions to answer via experimentation. > It's purportedly supported. IBM has fixed

Does anyone use HFS files extensively with HLASM?

Yeah, I know, there's an assembler listserve and this isn't it. I'm not on it and I think most of its members are also here. This IS a mainframe question ... Yeah, I could test the basic issues but I am wondering if anyone is doing this extensively and "happy with it." What are the gotchas? Those

Re: SMP/E and RFPREFIX

On Tue, 25 Oct 2016 16:08:25 -0700, Phil Smith wrote: > >2) Is there a cleaner way to specify this than just adding >RFPREFIX(whatever) when needed? I had hoped to be able to provide, say, >RFPREFIX() and then use a set symbol, but I know that won't work. > Why not? Is it because the

SMP/E and RFPREFIX

OK, I feel stupid. Not an unfamiliar feeling, especially when SMP/E is involved. But I think I mostly figured this out, and am looking for confirmation. I have a package that installs fine, but recently someone said "You should support using RFPREFIX in your provided JCL". This was prompted by

Re: Help with orphan in FIFO control block chain

Where do you set R1? On Tue, 25 Oct 2016 11:25:02 -0500 Donald Likens wrote: :>I posted before on this issue and you all were a great help because I was using CS and PLO to serialize. However I changed the code and the issue still exists. The issue looks like, I create

Re: Just when you thought it was really dead

Is this new RPG cloud and analytics enabled? :-) Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Oct 25, 2016 at 4:02 PM, Charles Mills wrote: > Can OORPG be far behind? > > Charles > > -Original Message- > From: IBM Mainframe Discussion List

Re: Just when you thought it was really dead

Can OORPG be far behind? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Gould Sent: Tuesday, October 25, 2016 1:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Just when you thought it was really dead > Who Knew You

Just when you thought it was really dead

> Who Knew You Could Do That with RPG IV? Modern RPG for the Modern Programmer > > A draft IBM Redbooks publication > > View online > > Download PDF (5.6 MB) > > Get Adobe® Reader®

Re: TIME= on JOB card vs. EXEC card

W dniu 2016-10-25 o 19:15, Jesse 1 Robinson pisze: Answer inline It's interesting to see varying opinions and interpretations. To reiterate: my question is not 'how to accomplish something' but merely how it actually works. So: -- No TIME= of any kind coded on JOB or EXEC card Then jobcard

Re: TIME= on JOB card vs. EXEC card

Yes. The TIME= from the JOBCLASS only affects any EXEC which doesn't have an explicit TIME= (all of yours). If you put TIME= on the JOB card, then this trounces the JOBCLASS TIME=, and none of your steps, either the first step or in total, can exceed the TIME on the JOB card. (you've not

Re: TIME= on JOB card vs. EXEC card

W dniu 2016-10-25 o 18:28, Lizette Koehler pisze: Correct. The JOBCLASS TIME will rule all TIME= for that class. If you do not exceed the JOBCLASS TIME= limit then either the JOBCARD or STEP will then enforce the limit. If the JOBCLASS TIME=30 is coded (30 mins) then it will not matter to code

Re: EXTERNAL: Re: many OMVSKERN task not stop

My suspicion is you are starting your Telnet Server out of your TCPIP proccess with an auto start. When your Telnet server abends it gets auto started once TCPIP notices. On Tue, 2016-10-25 at 18:42 +0100, Giovanni Bozzetti wrote: > Lizette > > Is during normal work. > > Seems to me that TCPIP

Re: many OMVSKERN task not stop

Lizette Is during normal work. Seems to me that TCPIP is restarting INETD many times, I did find a message that TCPIP is in loop Seems TCPIP is not understand the port where INETD is working and try to restart all the time We just see this task this month we have sure that last month they are

Re: HMC logs

Andy, I am one of the HMC/SE team leaders and I've been talking to another team leader and we would like to help you to get this working. There are two basic approaches to getting the HMC logs. One would be to use the Scheduled Operations task to setup a scheduled op to collect the "audit

Re: TIME= on JOB card vs. EXEC card

It's interesting to see varying opinions and interpretations. To reiterate: my question is not 'how to accomplish something' but merely how it actually works. So: -- No TIME= of any kind coded on JOB or EXEC card -- JES2 time for a particular JOBCLASS is 3 -- Five steps in the job -- No IEFUTL

Re: many OMVSKERN task not stop

I am not sure I understand. Is this during a shutdown for an IPL? A normal process where you want to shutdown OMVS? Could you provide an example or more details? Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of

Re: TIME= on JOB card vs. EXEC card

Correct. The JOBCLASS TIME will rule all TIME= for that class. If you do not exceed the JOBCLASS TIME= limit then either the JOBCARD or STEP will then enforce the limit. If the JOBCLASS TIME=30 is coded (30 mins) then it will not matter to code TIME=60 on the JOBCARD or the STEP. The 30Mins

Re: TIME= on JOB card vs. EXEC card

Or products like Trident Software z/OSEM or MVS Solutions (?) Thruput Manager. You could also look a EASYEXIT by DTS Software. So if the JOBCLASS definition does not include a TIME= parm the default for that class is 30 mins If there is a JOBCARD TIME= it controls all steps. So the total time

Help with orphan in FIFO control block chain

I posted before on this issue and you all were a great help because I was using CS and PLO to serialize. However I changed the code and the issue still exists. The issue looks like, I create a control block but it does not get added to the chain… I think the term is orphan. The control block

Re: many OMVSKERN task not stop

Elardus Thank you Did a more detailed investigation and is related with INETD1 and seems TCPIP is doing a loop and restart many times INETD1 this is the cause to have many OMVSKERN it use this task when use BPXAS start $HASP100 BPXASON STCINRDR

Re: many OMVSKERN task not stop

Giovanni Bozzetti wrote: >We have z/OS 1.13 and z/OS 2.1 running with all last APAR but now we observe >that OMVSKERN task didn't stop anymore >We can find lot of this task started we can cancel but after some time it >appears again. What OMVS tasks? Could you see what are they doing? Did

many OMVSKERN task not stop

Hi We have z/OS 1.13 and z/OS 2.1 running with all last APAR but now we observe that OMVSKERN task didn't stop anymore We can find lot of this task started we can cancel but after some time it appears again. Someone know why this is happen ? Regards Giovanni System Programmer

Re: TIME= on JOB card vs. EXEC card

Try Jes2 Exit 6 to enforce the limits. I had some fun a while back writing some code to process the internal text of the job and force the values I wanted for the time parameter. If TIME= was coded, it was forced to the expected value. May also be done (I think) in IEFUSI or IEFUJI. HTH,

Re: TIME= on JOB card vs. EXEC card

Radoslaw Skorupka wrote: >Answer: it depends. Absolutely. For once, I have TIME to agree with you. I wish I have TIME (sic!) to test your one step job examples, but... >Rule of thumb: KISS! >Keep It Simple! Indeed. >Don't code TIME in both JOB and EXEC We tell people to rather sit any

Re: TIME= on JOB card vs. EXEC card

I thought that the jobclass time limit overrides everything - so for this example wouldn't the time be 60? Examples (for one-step job): jobclass ; JOBcard ; EXEC ; effective 60 ; none ; 90 ; 90 - increased I thought that the jobclass was the maximum regardless of what you

Re: System REXX

On Mon, Oct 24, 2016 at 7:37 PM, Steve Horein wrote: > > > > > Thank you for the explanation and reasoning sir! > I supported OPS/MVS in a previous life (loved it), and I am now supporting > NetView automation (love it), so I am lucky to be able to currently work > with

Re: TIME= on JOB card vs. EXEC card

On Tue, 25 Oct 2016 11:47:34 +0200, R.S. wrote: W dniu 2016-10-25 o 04:55, Jesse 1 Robinson pisze: > OK, consider this case. All defaults, no TIME= coded anywhere. JES2 parms > have TIME=3. Five steps. How long will the job run? > >Assumed first step consumed 30s the limit for the rest of the

Re: TIME= on JOB card vs. EXEC card

On Mon, 24 Oct 2016 17:06:00 -0700, Lizette Koehler wrote: >Good write up on KB here > >http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieab500/iea3b5_JOB_and_EXEC_TIME_parameter.htm This is from the JCL User's Guide. -- Tom Marchant

Re: TIME= on JOB card vs. EXEC card

W dniu 2016-10-25 o 04:55, Jesse 1 Robinson pisze: OK, consider this case. All defaults, no TIME= coded anywhere. JES2 parms have TIME=3. Five steps. How long will the job run? Answer: it depends. First: we talk about CPU time, not "wall clock" time. Second: we know there is a limit 3 minutes

AW: Re: AW: Re: TIME= on JOB card vs. EXEC card

>I didn't know that about the EXEC of a PROC. Nor did I. Interesting. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO

Re: AW: Re: TIME= on JOB card vs. EXEC card

There's a useful description with examples here: http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieab500/iea3b5_JOB_and_EXEC_TIME_parameter.htm I didn't know that about the EXEC of a PROC. How it works must hark back to long ago. You booked your time to use on the

AW: Re: TIME= on JOB card vs. EXEC card

>So each step no more than 3 minutes. 3 mins 1 sec it fails on that step. Think of it as there being a big CPU time bucket for *the job*. There is a limited amount of CPU time in it when TIME= *is* specified on the JOB statement, or an unlimited amount, when TIME= *is not* specified on the JOB