SandyM,
Where I worked previously we used Harvest (change management tool) along with some additional scripting to automatically promote and process the zip files. It was quite a while ago but I'll see if I can remember enough to at least summarize the process.
The developer would create his/her zip file and check it in to Harvest. Then a home-grown script, called from within Harvest, would run at a predetermined time (or times) and would;
Copy the zip file(s) to the target machine cm/load directory.
Execute the IBI script that loads zip files.
Check the cmevent.log file for errors.
Report back with the results (I don't remember how this was incorporated into Harvest).
I believe that there was a way in Harvest to see the contents of the zip file although I don't recall how that was accomplished but there were approval processes/procedures set up within Harvest. After an approval from "whomever", the zip file was again automatically promoted up to the next logical environment and automatically processed there.
As I'm writing, I'm realizing there were other aspects to this that are foggy that I just don't remember too much about how the versioning control worked, the setup within Harvest to demote a zip file, we had a script that would purge old zip files, etc.).
I know I haven't given you much but I hope that at least some of this helps.
Craig
8.8.09 - z/Linux (WF, Report Caster, Report Library).
Iway FFS on MVS (HFS)