Rex Bontrager <REXB@PURCCVM.bitnet> (02/28/90)
In VM's DMKRIO, we defined our Hyperchannel as device type 1234. In VM/XA's HCPRIO, it's apparently not as simple. How is a Hyperchannel defined under VM/XA in HCPRIO? Rex Bontrager IBM Systems Programmer, IBM Postmaster, Bitnet TechRep Purdue University Computing Center Bitnet: rexb@purccvm Internet: rexb@vm.cc.purdue.edu Phone: (317) 494-1787 ext. 256
Mike Friedman <SPGMNF@UCBCMSA.bitnet> (02/28/90)
We define our Hyperchannel as DEVTYPE=0220,CLASS=DISPLAY on our VM/XA SP 2 system, for use with FAL. Basically, it's an 'unsupported' device type, so '0220' is really equivalent to '1234' (non-existent device types). It appears to work fine.
"Philip G. Pishioneri 814 865 0824" <PGP@PSUVM.bitnet> (02/28/90)
Our HCPRIO:
RDEVICE DEVTYPE=A220,DEVNO=(E00,64),CLASS=DASD
(A220 is of course "unknown")
and our IOCP for same:
CNTLUNIT CUNUMBR=E00,PATH=(5E),SHARED=N,UNIT=A220, X
UNITADD=((00,64))
IODEVICE ADDRESS=(E00,64),CUNUMBR=E00,UNIT=A220
We went with the DASD class because the original DMKRIO example used a 3830
CUTYPE (which is a disk control unit). Later recommendations may now be
different; anyone have the definitive word? I already saw that UCBCMSA uses
class=DISPLAY.
-Phil