|
View previous topic :: View next topic
|
| Author |
Message |
Deepthi Budhiwant
New User
Joined: 15 Dec 2008
Posts: 6
Location: Pune
|
|
|
|
Hi All,
I m trying to execute a procedure with parameters as,
| Code: |
//STEP1 EXEC PROC=PROCABC,
// CONDN=ONLY,
// INFILE=XYZ.ABC.DEF |
In the proc I have used CONDN and INFILE as symbolic parameters.
When I execute the job, it gives JCL error that there are excessive number of positional parameters on EXEC step.
Can anyone throw light on the same.
Thanks,
Deepthi
Edited: Please use BBcode when You post some code/error, that's rather readable, Thanks... Anuj |
|
| Back to top |
|
 |
abhishek dadhichi
New User
Joined: 19 Apr 2007
Posts: 37
Location: Bangalore
|
|
|
|
Hi Deepthi,
Can you please post the error you got.
Also,you can try below code:
| Code: |
//STEP1 EXEC PROCABC,
// CONDN=ONLY,
// INFILE=XYZ.ABC.DEF |
Thanks,
Abhishek
Edited: Please use BBcode when You post some code/error, that's rather readable, Thanks... Anuj |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Post the output that shows the error |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| When I execute the job, it gives JCL error that there are excessive number of positional parameters on EXEC step. |
Use BBCode to post the JCL expansion that you're getting -- it's hard to diagnose a problem without seeing what the system thinks you're doing. |
|
| Back to top |
|
|
Deepthi Budhiwant
New User
Joined: 15 Dec 2008
Posts: 6
Location: Pune
|
|
|
|
Hi Abhishek,
As I mentioned the error msg is
EXCESSIVE NUMBER OF POSITIONAL PARAMETERS ON THE EXEC STATEMENT
I had already tried with the code you suggested, but it still threw the same error.
Thanks,
Deepthi |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
1, 2, three....
post the output, until somebody sees Your output, there will only be useless network noise
the previous suggestion does not work because the two exec formats are equivalent
see the exec syntax in the jcl manual |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
As previously requested, post the output / expanded JCL showing exactly what we need to help you.
We do request this information for a good reason. Being able to help you !!! |
|
| Back to top |
|
|
abhishek dadhichi
New User
Joined: 19 Apr 2007
Posts: 37
Location: Bangalore
|
|
|
|
Hi Deepthi,
What I feel is, you might be specifying a parameter in the exec step
which you may not be using in the Proc PROCABC.
Please check it out and please do post the exact JCL and the Exact error to get a feasible solution.
Thanks,
Abhishek |
|
| Back to top |
|
|
Mukesh Pandey
Active User
Joined: 11 Nov 2008
Posts: 143
Location: India
|
|
|
|
hi Deepthi,
Use the below code in your job while calling the proc... hope it works.. let me know the details after execution.
//STEP1 EXEC PROCABC,
// CONDN=ONLY,
// INFILE=XYZ.ABC.DEF |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Mukesh Pandey
We have asked for the OP to post his JCL and error messages so that we can help him. Without this information all that you are doing is confusing matters.
Besides, how does your suggestion differ from the one originally posted ?
It does NOT so how do you think that this will suddenly start to work ? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
Mukesh Pandey
Active User
Joined: 11 Nov 2008
Posts: 143
Location: India
|
|
|
|
| Well ..., deepthi post the jcl error u are getting... use jj before submiting the job... |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Mukesh Pandey wrote: |
| Well ..., deepthi post the jcl error u are getting... use jj before submiting the job... |
JJ is probably site specific, used by some JCL scan / pre processor that is installed at your site, and possibly not at the OP site.
It certainly is not installed where I am working so all I recieved was
IKJ56500I COMMAND JJ NOT FOUND |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| hope still lies if u r willing to learn. |
If you are willing to learn, you will be willing to follow directions. . . Is there some reason you have not yet posted the requested information?
People here can tell what is causing the problem once you provide the info (the expanded jcl). You should not attempt to determine what needs to be posted and what does not because if you knew this correctly, you would also know why the problem.
The job should be submitted with MSGLEVEL=(1,1) to make sure the diagnostic info is shown. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi,
With this
| Quote: |
| IEF640I EXCESSIVE NUMBER OF POSITIONAL PARAMETERS xxxx |
at the most one can tell you..
| Quote: |
| Commonly caused by a misplaced comma, duplication of a keyword, or an empty operand field. (xxxx indicates the approximate location or field in which the error occurred.) |
|
|
| Back to top |
|
|
umakanth.ravirala
New User
Joined: 04 Sep 2007
Posts: 15
Location: Halifax, United Kingdom
|
|
|
|
Deepti,
Hope you are not using the parameters mentioned in JCL anywhere in PROC, Probably no one can answer exactly unless and untill your complete JCL & PROC is posted here. |
|
| Back to top |
|
|
Deepthi Budhiwant
New User
Joined: 15 Dec 2008
Posts: 6
Location: Pune
|
|
|
|
Hi All,
My apologies for late response.
Here is the code snippet i've been using:
| Code: |
//PROC01 PROC
//STEP1 EXEC PGM=SORT, COND=&CONDN
//SORTIN DD DSN=&INPUT,
// DISP=SHR,
//SORTOUT DD DSN=&OUTPUT,
// DISP=SHR,
//SYSIN DD DSN=<LIBRARY_NAME>(<PARAMETER_NAME>)
//* The parameter contains a simple sort control statement i.e
//*SORT FIELDS=COPY
//*since procs can't have instream data so I've used parameter.
// PEND
//* PROC CALLED HERE
//STEP01 EXEC PROC=PROC01,
// CONDN=ONLY,
// INPUT=ABC.DEF,
// OUTPUT=PQR.STU, |
//* there are 5 more job steps identical to the STEP01 just calling PROC with different conditions and file names.
I've posted the error message in the earlier post.
Thanks,
Deepthi
Edited: Please use BBcode when You post some code/error, that's rather readable, Thanks... Anuj |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Okay, first we asked you to post the JCL expansion from the job, not your interpretation of the JCL. If you can't post a copy of the job output (not what you want us to see) you're not likely to get the help you say you want.
Second, your original post was
| Code: |
//STEP1 EXEC PROC=PROCABC,
// CONDN=ONLY,
// INFILE=XYZ.ABC.DEF |
and now your JCL looks like
| Code: |
//STEP01 EXEC PROC=PROC01,
// CONDN=ONLY,
// INPUT=ABC.DEF,
// OUTPUT=PQR.STU, |
so it is no longer clear if you're talking about one problem, two problems, or what.
Third, without posting the job output we don't know if your error message is on the first execution, the second, or the sixth -- so what you posted may be perfectly correct (it isn't, by the way since there's a trailing comma on the OUTPUT= parameter that will guarantee a JCL error if the JCL is as presented) but the error could be on a different step. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Well Robert, you handled that rather more diplomatically than I would have. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| Here is the code snippet i've been using: |
people trying to help you
do not care about what You say You have been using,
care about the output of Your run
the interpreter/converter will print the jcl statements,
before the substitution
after the substitution pointing the changes
giving a strong hint on Your mistake
until You post what You are asked its' just useless blabbering and a loss of time
if You want to be out of the s**t do what You are asked not what You think is right
if Your thoughts were right You would be on the other side of the fence
( replying, not asking )
| Quote: |
| no matter u fail,hope still lies if u r willing to learn. |
no... there is hope if You do what You are told/asked ( nicely until now ) |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
...And please use BB code tags when you post some code as used by Robert. Notice your post is been edited to add BBcode and I was not sure that should I add this line
| Quote: |
| //* there are 5 more job steps identical to the STEP01 just calling PROC with different conditions and file names. |
in BBcode or not so left outside.. |
|
| Back to top |
|
|
Mukesh Pandey
Active User
Joined: 11 Nov 2008
Posts: 143
Location: India
|
|
|
|
| Expat... use typerun=scan ................... in your job card...... |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| It's TYPRUN not TYPERUN and expat is not the one with the JCL error. |
|
| Back to top |
|
|
Mukesh Pandey
Active User
Joined: 11 Nov 2008
Posts: 143
Location: India
|
|
|
|
| Terry..... the reply is based on the discussion.... if jj does not work.. a simple way is use typrun=scan.... |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hello,
The bottom line is "JJ" etc. are site specifc commnads - I use "JEM" and "JSCAN" to check JCL-syntax which have no meaning outside my shop & if they have it's just a coincidence..
-Ad |
|
| Back to top |
|
|
|
|
