Author: prino
Subject: Re: Reply to: Replace repeated JCL with looping REXX
Posted: Fri Oct 14, 2016 1:55 am (GMT 5.5)
Rhetorical question, I presume?![icon_cool.gif]()
I'm interested, but I will probably use a somewhat easier route and add a
and parse the DSN obtained via LISTDSI() and with REXX it's obviously far easier to allocate different SYSIN members for ISRSUPC for those n+1 versus n compares where I need to mask "irrelevant" changes.
I find thatI'm using "that" system a lot less than the same 1.10 system you also seem to be using.![icon_lol.gif]()
_________________
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
No programming here (yet)![icon_smile.gif]()
Subject: Re: Reply to: Replace repeated JCL with looping REXX
Posted: Fri Oct 14, 2016 1:55 am (GMT 5.5)
| enrico-sorichetti wrote: |
| You know the logic better than anybody else, so I' ll just stick to the SET stuff. what liberty do You have in installing free software on the system. |
Rhetorical question, I presume?
| enrico-sorichetti wrote: | ||
I have tested both on MVS 3.8 an on zOS 10 the Control Card subsystem in file 364 of the cbt tape that would solve in a simple and elegant fashion the problem of reading as a dataset the SET stuff if You are interested It should take just couple of hours to test it again for a proc the jcl would look like
the only bother would to write the ddname with the SET vars You could always test it on that  systemif You want it I will send You my streamlined version |
I'm interested, but I will probably use a somewhat easier route and add a
| Code: |
| //PARMDD DD DSN=&SYSUID.$SET1..&SET2..&SETn, // DISP=(MOD,DELETE), // SPACE=(TRK,0) |
and parse the DSN obtained via LISTDSI() and with REXX it's obviously far easier to allocate different SYSIN members for ISRSUPC for those n+1 versus n compares where I need to mask "irrelevant" changes.
I find thatI'm using "that" system a lot less than the same 1.10 system you also seem to be using.
_________________
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
No programming here (yet)
