Re: The hardest JCL ERROR I have met

On Thu, 1 Apr 2010 18:37:05 -0500, Larry Stout wrote: >A quick way to determine the error is to submit the JCL as a batch >job. If the job fails during syntax checking, it will not matter >whether the data sets are cataloged or whether JES2 is already >running. > >//JES2PROC M=JES2PARM >//IE

Re: The hardest JCL ERROR I have met

.com > >-Original Message- >From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ron Wells >Sent: 29 March 2010 14:01 >To: IBM-MAIN@bama.ua.edu >Subject: Re: The hardest JCL ERROR I have met > >(2) HASPLIST ?? >STEPLIB s/b after EXEC

Re: The hardest JCL ERROR I have met

On Thu, 1 Apr 2010 12:44:56 -0400, Shmuel Metz (Seymour J.) wrote: > >>The STEPLIB can be anywhere within the step boundries. It is only by >>convention that we place it directly after the EXEC. In fact this can >>cause a problem. The external writer, at least back a couple of decades >>ago, would

Re: The hardest JCL ERROR I have met

>This was back around 1984 or so. I don't even know if ETRs existed back then. Their equivalent did. I opened my first ticket with IBM in 1981. It was all telephone and courier, but the system still worked, sort of. The ISC wasn't that far from where I worked at the time. - Too busy driving to s

Re: The hardest JCL ERROR I have met

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.) > Sent: Thursday, April 01, 2010 11:45 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: The hardest JCL ERROR I have met > > In > , on

Re: The hardest JCL ERROR I have met

In , on 03/29/2010 at 07:56 AM, "McKown, John" said: >The above just looks wrong to me for some reason. Because of the undoubled apostrophes? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don't ha

Re: The hardest JCL ERROR I have met

In <222817403-1269867357-cardhu_decombobulator_blackberry.rim.net-19525017...@bda026.bisx.prod.on.blackberry>, on 03/29/2010 at 12:55 PM, Ted MacNEIL said: >Usually, if there is a parm specified on the START command, and it's not >specified in the PROC statement, this generates a JCL error. N

Re: The hardest JCL ERROR I have met

In , on 03/29/2010 at 08:09 AM, "McKown, John" said: >The STEPLIB can be anywhere within the step boundries. It is only by >convention that we place it directly after the EXEC. In fact this can >cause a problem. The external writer, at least back a couple of decades >ago, would scan the TIOT a

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

On Tue, 30 Mar 2010 13:48:39 -0500, McKown, John wrote: >> 2) Put JES2 parm member HASJES2 in logical parmlib concatenation >> ... this is the default name that will be looked for >> if > >Where is HASJES2 documented? I can't seem to find it. I tested it on my z/OS 1.10 sandbox and it does

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Brian Peterson > Sent: Tuesday, March 30, 2010 1:57 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Safeguarding your JES2 Proc (was Re: The hardest > JCL ERROR I hav

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

>From z/OS JES2 Commands: 4. default MEMBER=HASjesx member of the default PARMLIB concatination In this case "jesx" is JES2. Brian On Tue, 30 Mar 2010 13:48:39 -0500, McKown, John wrote: >> >> 2) Put JES2 parm member HASJES2 in logical parmlib concatenation >>

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden > Sent: Tuesday, March 30, 2010 1:28 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Safeguarding your JES2 Proc (was Re: The hardest > JCL ERROR I hav

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

On Tue, 30 Mar 2010 12:54:56 -0500, Ward, Mike S wrote: >I guess you can't see the presentation if you are not a share user. It >asked me for an ID and Password. > Reader's Digest version: 1) Remove all data set references from JCL. only use EXEC PGM=HASJES20 - optional parm= and //

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

Have you tried the Contact Us button on the web site? I had thought I understood that if you ask, SHARE will give you an ID for the site. Brian On Tue, 30 Mar 2010 12:54:56 -0500, Ward, Mike S wrote: >I guess you can't see the presentation if you are not a share user. It >asked me for an ID and

Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

bject: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met) I suggest that you consider removing all those statements from your JES2 proc. My production JES2 proc looks like this: BROWSESYS1.PROCLIB(JES2) - 01.02 Command ===> * Top

Re: The hardest JCL ERROR I have met

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Lizette Koehler > Sent: Monday, March 29, 2010 6:44 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: The hardest JCL ERROR I have met > > I was wondering if starti

答复: The hardest JCL ERROR I have met

It is shame to say the JCL error was caused by duplicate DD HASPLIST. Thanks again. Thanks Mark! -邮件原件- 发件人: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] 代表 Mark Zelden 发送时间: Tuesday, March 30, 2010 8:03 AM 收件人: IBM-MAIN@bama.ua.edu 主题: Re: The hardest JCL ERROR I have

Re: The hardest JCL ERROR I have met

On Mon, 29 Mar 2010 17:32:22 -0600, Rick Fochtman wrote: >-- > >> >>Nothing jumps out at me. But I would suggest one change to the COMMND00 member: >> >>COM='S JES2,PARM=(WARM,NOREQ)' >> >>instead of >> >>COM='S JES2,PARM='WARM,NOREQ

Re: The hardest JCL ERROR I have met

I was wondering if starting JES2 with SUB=MSTR be of any more help on this issue? Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO S

Re: The hardest JCL ERROR I have met

-- Nothing jumps out at me. But I would suggest one change to the COMMND00 member: COM='S JES2,PARM=(WARM,NOREQ)' instead of COM='S JES2,PARM='WARM,NOREQ'' The above just looks wrong to me for some reason. -

答复: The hardest JCL ERROR I have met

- 发件人: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] 代表 Mark Zelden 发送时间: Monday, March 29, 2010 11:47 PM 收件人: IBM-MAIN@bama.ua.edu 主题: Re: The hardest JCL ERROR I have met On Mon, 29 Mar 2010 11:18:46 -0400, Lizette Koehler wrote: >Have you check out your MSTRJCL setu

Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)

I suggest that you consider removing all those statements from your JES2 proc. My production JES2 proc looks like this: BROWSESYS1.PROCLIB(JES2) - 01.02 Command ===> * Top of Data * //JES2PROC //JES2EXEC PGM=HASJES20,REGION=0M,TIME=NOLIMIT

Re: The hardest JCL ERROR I have met

>All EXEC values are valid on a START statement. You're right. I (re-)learned something. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu w

Re: The hardest JCL ERROR I have met

Correct. And in this case since it is pointing to IEFRDER, I think that is what the problem is. Ted, regarding your "ignored" statement: This has been discussed at various times on this list. That "trick" is often used with SYSUDUMP. For example: //*NOTE THAT THE FOLLOWING, SEEM

Re: The hardest JCL ERROR I have met

Actually, IIRC, they are not really ignored - they simply don't cause an error. They wind up in the TIOT, with all the proper resources allocated - but they are very difficult to use. >>> Ted MacNEIL 3/29/2010 12:19 PM >>> >But why do you have 2 HASPLIST DDs? Except for confusion, I thought t

Re: The hardest JCL ERROR I have met

>But why do you have 2 HASPLIST DDs? Except for confusion, I thought the second, and subsequent (if any), DD's with duplicate names were ignored. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive

Re: The hardest JCL ERROR I have met

>You also have a symbolic '&M' to represent a membername. Where is that being >provided? It's right there on the OP's original post: >>//JES2PROC M=JES2PARM - Too busy driving to stop for gas! -- For IBM-MAIN subscribe /

Re: The hardest JCL ERROR I have met

>(2) HASPLIST ?? STEPLIB s/b after EXEC Not necessarily. I learned years ago, by accident, that STEPLIB can be anywhere withing the step. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access i

Re: The hardest JCL ERROR I have met

On Mon, 29 Mar 2010 11:18:46 -0400, Lizette Koehler wrote: >Have you check out your MSTRJCL setup? Is the proclib that JES2 is in, in that concatenation? > Good thought. I didn't mention it because I would that that would be obvious. Again, I'll ask about MSGIEF16I. Wouldn't you see seomthin

Re: The hardest JCL ERROR I have met

bama.ua.edu] On Behalf Of Hu Lei Sent: Monday, March 29, 2010 07:36 To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image

Re: The hardest JCL ERROR I have met

On Mon, 29 Mar 2010 20:35:38 +0800, Hu Lei wrote: >Hello world! > > > >I am trying to setup a mini system, and during IPL, I have met JES2 start >error. I am suffer from this error for days, I have do all I can image to >correct the error, but still no result. > >It would be great appreciated if

Re: The hardest JCL ERROR I have met

Have you check out your MSTRJCL setup? Is the proclib that JES2 is in, in that concatenation? Lizette Hu Lei Wrote: > >Hello world! > > > >I am trying to setup a mini system, and during IPL, I have met JES2 start >error. I am suffer from this error for days, I have do all I can image to >co

Re: The hardest JCL ERROR I have met

Out JES2 proc also contains: //IEFRDER DD DUMMY Kevin. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hu Lei Sent: 29 March 2010 13:36 To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to

Re: The hardest JCL ERROR I have met

Wasn't there a description of the JCL error (IEF196I?)? The COMMNDxx entry looks fine. But why do you have 2 HASPLIST DDs? Lose the second one. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Ma

Re: The hardest JCL ERROR I have met

On Mon, 29 Mar 2010 12:55:48 + Ted MacNEIL wrote: :>>//JES2PROC M=JES2PARM :> :>>//IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) :>. :>. :>. :>>COM='S JES2,PARM='COLD,NOREQ'' > :>Where is your PARM= on the PROC statement? Don't think that would work. :>U

Re: The hardest JCL ERROR I have met

logy Services Iowa State University 515-294-3088 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Elardus Engelbrecht Sent: Monday, March 29, 2010 8:15 AM To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met Hu Lei wrote:

Re: The hardest JCL ERROR I have met

Hu Lei wrote: >The joblog during IPL looks: >IEF403I IEESYSAS - STARTED - TIME=03.47.40 >IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED >IEF452I JES2 - JOB NOT RUN - JCL ERROR There should be more errors shown on SYSLOG. >And the JES2 proc: >//JES2PROC M=JES2PARM >//IEFPROC EXEC PGM

Re: The hardest JCL ERROR I have met

...@bama.ua.edu] On Behalf Of Ron Wells Sent: 29 March 2010 14:01 To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met (2) HASPLIST ?? STEPLIB s/b after EXEC From: Hu Lei To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe

Re: The hardest JCL ERROR I have met

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ron Wells > Sent: Monday, March 29, 2010 8:01 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: The hardest JCL ERROR I have met > > (2) HASPLIST ?? > STEPLIB s

Re: The hardest JCL ERROR I have met

IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO)>> YES COMM >> do not need it is above set From: Hu Lei To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe Discussion List Hello world! I

Re: The hardest JCL ERROR I have met

>COM='S JES2,PARM='WARM,NOREQ'' >The above just looks wrong to me for some reason. If you are allowed to pass it, without specifying PARM= in the PROC statement, then the problem looks like quoting to me. The above should be: COM='S JES2,PARM=''WARM,NOREQ''' Or even: COM='S JES2,PARM=WAR

Re: The hardest JCL ERROR I have met

(2) HASPLIST ?? STEPLIB s/b after EXEC From: Hu Lei To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe Discussion List Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am

Re: The hardest JCL ERROR I have met

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hu Lei > Sent: Monday, March 29, 2010 7:36 AM > To: IBM-MAIN@bama.ua.edu > Subject: The hardest JCL ERROR I have met > > Hello world! > > I am tryi

Re: The hardest JCL ERROR I have met

>//JES2PROC M=JES2PARM >//IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) . . . >COM='S JES2,PARM='COLD,NOREQ'' Where is your PARM= on the PROC statement? Usually, if there is a parm specified on the START command, and it's not specified in the PROC statement,

Re: The hardest JCL ERROR I have met

edu] On Behalf Of Hu Lei Sent: Monday, March 29, 2010 8:36 AM To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to c

The hardest JCL ERROR I have met

Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IP