I think the globalv variables would be information that is the same from one invocation to the next, such as userid, jobclass, destination, account numbers, etc.
A typical skeleton jcl modifying pipeline would be something like this: 'PIPE <' skel_fn skel_ft skel_fm , '| change /&USER/'|| userid() ||'/' , '| change /&DEST/'|| destination ||'/' , '| change /JJJJJ/'|| jdate ||'/' , '> OUTPUT JCL A' Then you submit the OUTPUT JCL file to your batch system. I think the SUB MIT program I use came from the IBM DOWNLOADs website. On Thu, 18 Jan 2007 07:33:18 -0600, Rich Smrcina <[EMAIL PROTECTED]> wro te: >It's not so much a plumbing exercise as it is changing the JCL skeleton >to use REXX variables and REXX style logic. No global variables >required, unless your passing data between invocations of the EXEC. > >Ed Zell wrote: >> OK, here is an example of some file tailoring that we do for >> our programming staff using ISPF and Dialog Manager. This >> one creates a compile job stream for a COBOL CICS program. >> >> It may or may not contain SQL statements, that is determined >> by the library type (COBOL or SQLCOBOL). A REXX EXEC drives >> the process (display panel, do some basic editing to validate >> what can't be handled on the panel itself, invoke file tailoring >> to create top of JCL, punch it, punch source member, file >> tailoring for bottom of JCL, punch it). >> >> It uses ISPF shared and profile variables to initially populate >> the panel (but I would guess that CMS global variables would work >> just fine too). I could handle the XEDIT full screen stuff to >> replace the panel, but I don't know much about CMS plumbing if >> that's what would replace file tailoring. >> >> Sorry for the length of this post, but the skeletons are pretty big! >> I appreciate any thoughts on how to convert something like this. >>
