Munif, A quick internet search on your messages produced
OA39308: DEVELOPMENT FIXES EA78051B EA3A0233 USS Latch contention (from 2013) OA11768: STOP ZFS MODIFICATION (from 2013) OA24962: ZFS PLANNED SHUTDOWN OMVS IPL SYNCHRONIZE FILE SYSTEM CORRUPTION (from 2008) So without more information, I would ask was level of maintenance is your z/OS V1.13 system at? Have you had a successful IPL? If so, was there maintenance installed and then you had problems? Any changes (parmlib, ptfs, new files, etc) since the last good IPL? What is the first set of message you get and can you post them from the IPL when there is an issue? Thanks Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Munif Sadek Sent: Sunday, June 16, 2013 7:20 PM To: [email protected] Subject: ZFS MountCall / Osi Wait Dear Listers I am trying to IPL one of the PLEX system in MONOPLEX (also tried XCFLOCAL) after creating IMAGECOPY of the disk subsystem. This single system image is taking hours to come up due to OMVS delay - ZFS MountCall / Osi Wait and multiple IOEZ00807I, IOEZ00397I. Our Plex is 6 systems parallel sysplex running on EC12, Z/OS 1.13. and ZFS is defined as SYSPLEX=FILESYS with sysplex shared root. Most of the ZFS files are READ only and as such we do not have any business / user data in ZFS , just the configuration files and hence do not care about recovery of ZFS as long as static data (configuration data) in the zfs file is intact . Is there a way we can expedite our unix system services startup in a monoplex system.. Best regards, Munif. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
