Input/Output Configuration Program: Difference between revisions

Content deleted Content added
m Typo fixing, typos fixed: of of → of using AWB
m clean up of articles listed as "needing cleanup" using AWB (8759)
Line 41:
}}</ref> mode, IBM changed the I/O architecture to allow the [[Channel Subsystem]] to handle the channel scheduling that the operating system had to handle in S/370 mode. The new I/O architecture used a 16-bit '''Channel Path Id''' ('''CHPID'''); the [[Channel Subsystem]] was responsible for mapping the '''CHPID''' to the channel and device numbers, for queuing I/O requests and for selecting from the available paths. The installation was responsible for defining the [[Input/Output Configuration Data Set]]s ('''IOCDS''''s), and the operator could select a specific '''IOCDS''' as part of a [[power on reset]] (POR). Input/Output Configuration Program (IOCP)<ref name=GC38-0097/><ref name=GC38-0401/><ref name=GC38-0456/> is a program for IBM mainframes that compiles a description of the [[Channel Subsystem]] and [[LPAR]]<ref name=GA22-7123/> configuration, optionally loading it into an [[Input/Output Configuration Data Set]] (IOCDS); it recognizes the syntax of [[MVS Configuration Program]] (MVSCP)<ref name=GC28-1615/> input, and there is no need to maintain separate input files.
 
The direct use of IOCP and [[MVS Configuration Program | MVSCP]] has been mostly supplanted by [[Hardware Configuration Definition | Hardware Configuration Definition (HCD)]]<ref name=GA22-7525/>
 
<!-- Note - standard section headins are as below. We do not have External References: -->
Line 113:
}}
 
{{operating-system-stub}}
[[Category:IBM mainframe operating systems]]
[[Category:IBM mainframe technology]]
 
 
{{operating-system-stub}}