Hello Listers. Need to solicit some 'best practices' regarding general operating procedures for hfs/zfs files on z/OS. Specifically, how do you handle migrating webservice updates to production? More specifically, if you have several CICS regions spread across a sysplex which service the same set of webservices, what procedures do you use to migrate webservice maintenance across the lpars in the sysplex?
Ken Moore Discussion follows. Every webservice CICS region needs to be running the same code. It would seem the way to do this is to keep a read-only pick-up directory mounted everywhere. You would need to unmount the read-only everywhere and update it on one LPAR during some maintenance window. Another way might be to have a separate updateable directory on all systems, but then you need to rely on a batch job to FTP maintenance to all systems, and find a window for this when all LPARs are available and the regions are not active. And how to implement emergency changes into one or more webservice regions across a sysplex outside of a normal maintenance window? For our CICS Transaction Gateways, it's slightly different and a lot more manageable because it's almost all system code, so we have two read-only zfs mounts on every LPAR, one is current production, the other is a backout zfs (the last successfully-run pile of maintenance and config changes). Then we have an updateable zfs on just one lpar which is the entry point for new maintenance and config changes when necessary. During the maintenance window, we simply roll the mount points. This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
