View previous topic :: View next topic
|
Author |
Message |
Brad Polhemus
New User
Joined: 15 Aug 2008 Posts: 3 Location: Jacksonville
|
|
|
|
Does something like this exist?
I have the need to convert many execution jcls (and their procs) to straight jcl.
Thanks!! |
|
Back to top |
|
|
Brad Polhemus
New User
Joined: 15 Aug 2008 Posts: 3 Location: Jacksonville
|
|
|
|
Would it be possible to run jclcheck or something... and output a datset... then extract info from there... that seems relatively easy. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
It will probably help if you define "straight jcl".
Many (most?) PROCs use symbolic parameters. If you take away the proc, this may become more than just a little inconvenient. . . |
|
Back to top |
|
|
DB2 Guy
New User
Joined: 28 Oct 2008 Posts: 98 Location: Cubicle
|
|
|
|
May be some trick would do it(JSCAN & save the outcome to in some DSN. . . ), but what's the final use of that? By the way, if those jobs are existing and had been run at least once, XDC the "JESJCL" DDname from SYSOUT . . . |
|
Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008 Posts: 400 Location: Mumbai
|
|
|
|
You can run the job with Typrun=scan and then use an edit macro to convert the substitutions back to jcl. It is a little complicated to do, a little more than 100 lines of rexx, but it gets you most of the way there. I have one that is invoked from the SE subcommand in SDSF and recreates the JCL after substitution but I can't post it (property of my employer and also might not work completely and no comments so I don't know how it works anymore). The the only thing I remember that it doesn't know about is inline data but there are probably other limitations to this approach. |
|
Back to top |
|
|
mtaylor
Active User
Joined: 20 Feb 2009 Posts: 108 Location: Kansas City
|
|
|
|
There are a lot of problems with this; what happens to JES2/JES3 statements? Are they dropped? Comments? When text is substituted, lines my be longer than 72 characters causing errors if the JCL is submitted without further editing.
I used to do A LOT of hand editing of JCL like this. When you get in a rythm you can knock these out pretty fast (>100 a day?). It's basically glorified data entry, but it's the only choice I had. |
|
Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008 Posts: 400 Location: Mumbai
|
|
|
|
mtaylor wrote: |
There are a lot of problems with this; what happens to JES2/JES3 statements? Are they dropped? Comments? When text is substituted, lines my be longer than 72 characters causing errors if the JCL is submitted without further editing. |
On my system. comments and JES2 statements are preserved. The job card has to have the right MSGLEVEL, of course, and the macro has to split lines that would go past 71 including correctly quoting parameters. But as I said, there are limitations to this approach so you need to do a manual verification anyway but this does get you 90% of the way. |
|
Back to top |
|
|
|