In a recent note, Charles Mills said:
> Date: Mon, 16 Oct 2006 17:29:21 -0700
>
> So I'm trying to automate it. (Automate just the submission part -- I can
> scan ISPF pretty quickly for seventy 0000 return codes.) I have an exec that
>
To what extent could you run the job steps with Rexx address ATTCHMVS
rather than submitting batch jobs? Advantage:
o Rexx can readily produce summary output; even better than scanning
flowerboxen.
Disadvantages:
o Rexx can't perform DSN serialization as the batch initiator
can.
o Rexx's ability to handle multi-file tapes is limited.
> Are there other ways I could do this? Of course. Could I build the entire
> test job on the fly? I suppose so, but that is a major change from what I am
> doing today. Building test jobs that will run in a development environment
> in a constant way and give a can't-miss zero or not, go or no-go return code
> is not a trivial process, and I don't find it to be much fun. I really want
> to minimize the re-do of that part.
>
I am progressively converting my Rexx JCL tailoring to shell script.
Reasons:
o Shell scripts provide inline files ("here-documents") not available
in Rexx.
o Here-documents support symbol substitution and even command
substitution, conspicuously absent from JCL instream data sets.
When necessary, shell scripts can incorporate inline sed scripts
for more elaborate tailoring, and inline awk scripts for procedural
coding.
Yes, there are other ways.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
