Input/Output Configuration Program: Difference between revisions

Revision as of 19:48, 28 May 2023

Revision as of 12:22, 29 May 2023

Line 40:

| id = SA22-7085-1

| version = Second Edition

| date = January 1987}}</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 '''subchannel number''', a 16-bit device number and an 8-bit '''Channel Path Identifier''' ('''Channel Path Id''' or '''CHPID'''); the [[Channel Subsystem]] was responsible for mapping the '''subchannel number''' to the channel and device numbers, for queuing I/O requests and for selecting from the available paths.

Starting with [[SystemIBM z9]]z#IBM runningzSeries [[z/OSfamily|z990]] 1.7, IBM offeredintroduced the multiple-subchannelconcept setof facility, which allowed up to four independent sets ofa 64'''Logical KiChannel subchannels.Subsystem'''<ref>{{cite manual

| title = IBM IBM eServer zSeries 990 Technical Guide

| id = SG24-6947-01

| date = May 2004

| edition = Second

| section = 4.1 Multiple Logical Channel Subsystem (LCSS)

| section-url = https://www.redbooks.ibm.com/redbooks/pdfs/sg246947.pdf#page=122

| pages = 110-115

| url = https://www.redbooks.ibm.com/redbooks/pdfs/sg246947.pdf

| access-date = May 29, 2023

}}

</ref> (LCSS); each physical channel (of 1024) has a unique ''Physical Channel Path Identifier''' ('''PCHPID'''), each LCSS has a CHPID to PCHPID mapping and each LPAR is assigned to one LCSS.

Starting with [[System z9]] running [[z/OS]] 1.7, IBM offered the multiple-subchannel set facility, which allowed up to four independent sets of 64 Ki subchannels.<ref>{{cite manual

| title = Multiple Subchannel Sets: An Implementation View

| url = https://www.redbooks.ibm.com/redpapers/pdfs/redp4387.pdf

Line 47 ⟶ 62:

| access-date = May 28, 2023

}}

</ref>

</ref> Although some models allowed more than 256 channel paths, each LPAR is limited to 256 CHPIDs and part of the IOCP definition is mapping the CHPIDs for each LPAR to the corresponding Physical Channel Path Identifiers (PCHPIDs).

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/>(HCD).

==See also==