> Yes, I am modifying (actually, repeatedly building on the fly) the member > itself in the PDS referenced by JCLLIB, not changing the member name in > the INCLUDE statement. > > This is not some "I think I'll improve the user's job" sort of thing. This > is a test process for a batch product. I've got 20 or so jobs that > exercise > the product in various ways, and then I have been using two INCLUDE files > to > parametize certain aspects of those jobs, so by commenting out or > "un-commenting" certain defined statements in the INCLUDE files, the total > number of variations in the whole suite is quite high: Does feature X > work? > Does feature X work if you also turn on option A? Etc.
This might be an out-of-left-field idea, but have you considered using ISPF file tailoring services? They are intended for pretty much exactly what you're describing. You can drive it from rexx or clist and you get complete programmatic control over what (in your case) gets submitted. CC ---------------------------------------------------------------------- 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
