Joined: 13 Jul 2007 Posts: 34 Topics: 10 Location: Los Angeles
Posted: Fri May 01, 2009 7:53 pm Post subject: NDM Through JCL - Passing Parameters to NDM PROC?
Hi,
I need to NDM files (some hundreds) from a batch job (not from the Panel). To reduce the effort, I decided to pass parameters from JCL to NDM Proc each time I run the batch job.
But I found out that I can not pass the parameters to Proc dynamically (or I am not doing it right).
When I do the JCL PREP, it says REG, ID & NUID are never used and he file names are not being recognized either as the parameters are not being resolved in the Proc.
Please let me know how can I handle this, else I have to have so many JCLs for each file.
Thanks a lot,
Cheers,
BK _________________ Regards,
BK
***** " If You Have To Do It, You Might As Well Do It Right.....If It Is Worth Doing At All, It's Worth Doing It Right !!! " *****
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
Posted: Sat May 02, 2009 8:34 am Post subject:
You are confusing your data with JCL. Symbolic parameters (the &... stuff) is JCL. The JCL converter only converts JCL not your data.
You can have a symbolic parmeter to a program (PARM=&MYPARM) which could generate your NDM control data. _________________ Utility and Program control cards are NOT, repeat NOT, JCL.
I'm not doing anything in the Proc. Still it is not resolving the parameters. Is it due to they are being given in single quotes or something like that?
Please advise. _________________ Regards,
BK
***** " If You Have To Do It, You Might As Well Do It Right.....If It Is Worth Doing At All, It's Worth Doing It Right !!! " *****
As long as both of the datasets for DS1 and DS2 are cataloged when the DMBATCH step runs, everything should work OK. Of course, if both datasets were cataloged and existed on the same system, then it wouldn't make much sense to be using Connect:Direct in the first place.
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
Posted: Sun May 03, 2009 9:18 am Post subject:
BK
SET still only affects JCL statements - not the data within a jobstream. (JCL statements are those beginning //, /* and //*. Even then it will not affect JCL statements that are data i.e. come after a //... DD * and before the matching /*, or otherwise defined, delimiter.) _________________ Utility and Program control cards are NOT, repeat NOT, JCL.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
