On Thu, Nov 13, 2008 at 11:10 PM, Wandschneider, Scott <[EMAIL PROTECTED]> wrote: > The only I/O Errors that we are seeing are on one of the paging volumes
When CP gets a paging I/O error writing to a particular record (99.9999% of the time because it isn't formatted or some z/OS system writes a VTOC in the middle of the volume), he'll remember it is bad and move on to another record. If he gets 6 in a row, the operator gets a message. If that keeps up, you could get a CP abend because CP is queueing those messages for the operator! An excellent reason to keep your critical volumes (page, spool) away from other systems. z/OS has no need to see a CP paging pack in its I/O config. Only certain errors are recorded by EREP: Channel data checks, channel control checks, interface control checks, and any unit check where the error recovery procedure contained in the SENSE data says "generate an EREP record". A normal I/O error such as is encountered when the disk isn't formatted isn't [likely to be] a hardware problem. Alan Altmark z/VM Development IBM Endicott
