The rule was that the range defined in IOCP for **control units** had to cover the range that was "plugged in" by the HW CE. The ranges of defined devices is not important. The reason is that control units can tell something to the OP sys using any address it has been defined. When such a "message" arrives and CP can not match it to a control unit range it knows, the message is thrown away. Often leading to missing interrupts.
So: - for control units: define the full range - for devices: define what you have (or plan to have in a short time) That's how I always worked, and still do. 2010/11/5 Edward M Martin <emar...@aultman.com> > Hello everyone, > > Just a question about the IOCP gen of 3592 drives. > > We are getting two IBM System Storage TS1120 Tape Drive Model E05 (3592 > E05) with encryption. > > Do I need to generate a full range of devices? Seems that I remember that > z/VM > likes to have full ranges even > > If we physically only have 2 drives. > > CHPID PCHID=161,PATH=61,TYPE=CNC,SHARED .ESCON 3590 > > CHPID PCHID=171,PATH=71,TYPE=CNC,SHARED .ESCON 3590 > > * > > ********************************************************* > > * C H A N N E L 61, 71 * > > * IBM 3592 TAPE DRIVES * > > ********************************************************* > > * > > CU280 CNTLUNIT CUNUMBR=280,PATH=(61), X > > UNITADD=((00,16)),UNIT=3590 > > CU680 CNTLUNIT CUNUMBR=680,PATH=(71), X > > UNITADD=((00,16)),UNIT=3590 > > D0680 IODEVICE ADDRESS=(680,02),CUNUMBR=(280,680),UNIT=3590, X > > UNITADD=00 > > Or should this be > > D0680 IODEVICE ADDRESS=(680,16),CUNUMBR=(280,680),UNIT=3590, X > > UNITADD=00 > > Ed Martin > > Aultman Health Foundation > > 330-363-5050 > > ext 35050 > > -- Kris Buelens, IBM Belgium, VM customer support
