Misplaced statement error

Nithya Usha Mohanan · New User Joined: 16 Oct 2007 Posts: 7 Location: pune

Hi,

I am executing a jcl calling a proc and getting a strange error while doing JCK in changeman.

After the proc getting called in the first step of the proc viz

//PROCNAME PROC CNTL = 'abc.xyz.deg',

// UNIT = 'sysda'

it is giving error " Misplaced statement" . the next statement is

//EXEC PGM = IEFBR14
the calling JCl looks fine and the proc is getting called too...

Could you please suggest me the reasons of this error?

superk · Posted: Thu May 05, 2011 7:59 pm

My best guess is, since UNIT is a reserved word, that it appears to be misplaced. You should probably try something else, like UNT.

Bill Woodger · Posted: Thu May 05, 2011 7:59 pm

Whoops, I replied whilst superk was moving it. Content no longer relevant.

Nithya Usha Mohanan · New User Joined: 16 Oct 2007 Posts: 7 Location: pune

thanks superk,

but i ran it commenting unit out , still not working....

regards,
nithya

ridgewalker58 · New User Joined: 26 Sep 2008 Posts: 51 Location: New York

Without any more information than what you provided, I can only make ASSUMPTIONS:

I have to ASSUME that the line //EXEC PGM = IEFBR14
is EXACTLY as you coded it:

Therefore, I would ALSO give you JCL error.

The format of an EXECUTE statement is:

'//' followed by a STEPNAME or atleast one SPACE
followed by EITHER
"EXEC PGM=your program name"
or
"EXEC PROCNAME"

for example:

//STEP001 EXEC PGM=IEFBR14

****** WITH NO SPACES IN THE PGM=IEFBR14

ridgewalker58 · New User Joined: 26 Sep 2008 Posts: 51 Location: New York

I had assumed that UNIT had been a Symbolic parameter which was defined WITHIN the PROC

UNIT=&UNIT
&UNIT to be replaced in the Execution JCL with
something like UNIT=SYSDA

superk · Posted: Thu May 05, 2011 8:13 pm

Nevermind, I just tested that PROC, and it works fine with UNIT as a symbolic parameter.

I don't have JCK or Changeman available, so I can't comment further.

Phrzby Phil · Posted: Thu May 05, 2011 8:19 pm

Unless we see code cut&pasted between code tags, we are wasting our time.

ridgewalker58 · New User Joined: 26 Sep 2008 Posts: 51 Location: New York

Superk, Bill and Phil -- I have noticed that you "all" spend time answering questions and giving solutions ---- BUT I have noticed
that RARELY the person who is asking the question -- has the
time to give you the response " yes it worked"

I believe the problem is that he coded it as

//EXEC PGM = IEFBR14

instead of

//STEP001 EXEC PGM=IEFBR14

Phrzby Phil · Posted: Thu May 05, 2011 8:33 pm

I absolutely agree - and cut&pasted code would have shown that right away.

Anuj Dhawan · Posted: Thu May 05, 2011 8:34 pm

There are a lot of loose ends in your question, Nithya.

Nithya Usha Mohanan · New User Joined: 16 Oct 2007 Posts: 7 Location: pune

Hi everyone,

Thanks for all ur suggestion.This issue is now resolved,
but the real culprit was a set of comments given before the

(procname) PROC statement in the proc . Since it was not my proc and JCl and i was helping in resolving the error, it didnt cross my mind at all abt the comments given at the starting of the proc ...

Now i have given it after the PROC statement and things are working fine...

but the confusion was bcoz the error was flagged at the PROC statement.

I should really say thank you to everyone in this site coz whenever i am really facing an issue i really depend on the many comments and help available here...

Anuj Dhawan · Posted: Thu May 05, 2011 9:02 pm

Glad to hear that!

Bill Woodger · Posted: Thu May 05, 2011 9:17 pm

enrico-sorichetti · Posted: Tue Jun 07, 2011 9:38 pm

Anuj Dhawan · Posted: Wed Jun 08, 2011 1:31 pm

Have fun, enrico!