Have you searched IBM website for IOS000I and CMD and E7? Did any of the entries help?
What was the customer doing at the time of the IOS000I messages? Sorting, cobol pgm, etc? Did you capture LOGREC to see what the full entries for the device said? Did you engage EMC hardware on this? Note: When cross posting to multiple groups, it is helpful to start your posting off with CROSS POSTING TO x,y,z Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Veryl Ellis > Sent: Friday, October 31, 2014 6:00 AM > To: [email protected] > Subject: IOS000I CMD REJ E7 > > *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? > > > > I know this is a long distance shot in the dark, but I figure it can't > > hurt to ask. > > > > Thanks, > > > > S. Veryl Ellis > > Sungard Availability Services > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
