Was the failure on the floor system, or the customer system? (according to the below, the z/OS customer system) Who "owns" the device in question. z/VM, z/OS (floor), z/OS (customer)? (according to the below, the z/OS customer system)
As I see it there are three possibilities. 1) Customer is running downlevel software that can't handle the "modern" equipment. 2) Bug in floor system (z/OS, z/VM). (I consider this unlikely.) 3) hardware issue (either microcode or physical). (I consider this the most likely) There were several hits in the IBM database, the most recent being July, 2011, Most seemed to be related to z/OS 1.10. HTH, <snip> *Problem description * I'm not sure if this should be directed to z/OS or z/VM. Unfortunately, I cannot recreate this issue with my environment. This happened in a customer's environment while they were conducting a Disaster Recovery (DR) test in this facility. Scenario: z/OS running as guest under my z/VM 6.2. Customer is using EMC VMAX DASD and zHPF in their z/OS. Customer received following message many times which caused several jobs to ABEND. IOS000I 1E25,5A,CMD,E7,0E00,,00600001,PRD40A,KMBDSS90 Again, this happened during a DR test and I can't recreate in my environment as I have no idea what they were doing in their system. I am asking has this type of failure scenario been reported or experienced? Is it possible PTFs need to be applied to z/OS or z/VM? It is my z/VM 6.2, but the customer's z/OS (which I assume is 1.13). Is it possible the EMC VMAX DASD needs some sort of microcode update? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
