On Mon, 20 Mar 2017 15:27:25 -0500, Paul Gilmartin <[email protected]> wrote:
>On Mon, 20 Mar 2017 13:51:43 -0500, Mark Zelden wrote: >> >>Thanks for the explanation. Normally I have no reason to run REJECT PURGE >>since I do purge at accept time. For my z/OS zones I do have to do that >>because >>the 2 companies each have their own dlib zone to go along with the 2 target >>zones, so I can't purge on accept. >> >An obvious enhancement would be a command to "purge when accepted in >all zones." > >Do you process the output of a cross-zone query or an API quiery to >generate the REJECT commands? > No, it's simply reject in purge mode after accept is done to both sets of zones. The zones to consider are part of the reject command: SET BOUNDARY (GLOBAL). REJECT PURGE (AAAD101,BBBD101) COMPRESS(ALL). (aaa and bbb are not the real prefixes of those zones, the name is related to the company and not shown). Best regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
