home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!spool.mu.edu!darwin.sura.net!paladin.american.edu!auvm!USCMVSA.BITNET!LDW
- Message-ID: <IBM-MAIN%93010703393123@RICEVM1.RICE.EDU>
- Newsgroups: bit.listserv.ibm-main
- Date: Thu, 7 Jan 1993 01:37:00 PST
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- From: Leonard D Woren <LDW@USCMVSA.BITNET>
- Subject: Re: IOCP and Channel 0
- Lines: 34
-
- On Tue, 5 Jan 1993 12:34:47 MST,
- Keith Risinger <SYSKMR@NMSUVM1.BITNET> said:
- > (...) in the IOCP users
- > guide it states 'MVS system generation requires TYPE=BY for channel
- > number 0'. Even before I read that statement, I remembered something
- > about channel 0 having to be defined as TYPE=BY, but I don't know
- > why.
-
- A couple of people followed up with answers to other questions than
- what was asked. The correct answer to the question is "historical",
- at least for most processors and for current MVS releases. I suppose
- that some older and/or smaller processors might require CHPID 0 to be
- BYte.
-
- A pre-XA MVS requires that channel 0 be a byte channel. Since you're
- running MVS/ESA, remove the channel specification from the CHPID
- macros -- they're irrelevant. I'm guessing this is the cause of your
- trouble.
-
- > All this came about when we could not attach the new tape drives to
- > any VM id, so I thought maybe the TYPE operand may have something to
- > do with it.
-
- I don't know enough about VM RIO, but it _may_ insist that channel 0
- be a byte channel. Again, if you're running VM/XA or later, this is
- probably irrelevant. Channel numbers don't actually exist in the XA
- (MVS,VM) I/O architecture.
-
- > Our environment is VM/ESA with MVS/ESA running under it.
-
- I'd fix that too... (Just last week we had that argument on this list,
- so let's not have it again now, even if I am throwing out flame bait.)
-
- /Leonard
-