Re: Query on OSA-ICC consoles
Thank you everyone ...I understand it now ...Thanks a lot ! Linda On Tue, Jun 14, 2016 at 5:39 AM, Alan Altmark wrote: > On Fri, 10 Jun 2016 16:53:42 +0530, linda golding < > lindagolding...@gmail.com> wrote: > >Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? > > > >I did a search in our systems and see that OSA-ICC devices are > concurrently > >active on all LPARS of the sysplex . I also see that PCHID is same across > >all the systems . I am just trying to find out how multiple systems can > >write on to the same physical OSA-ICC device ?..Basically i would like to > >know how this happens at hardware level . Any pointers /documentation > would > >be a great help . > > It works because of the magic of the Multiple Image Facility, MIF. Device > numbers are for the wetware. The host OS doesn't use them, but instead > uses a subchannel number, for which there is a 1-1 binding with a device > number in the LPAR. (The STORE SUBCHANNEL instruction provides the binding > information.) > > For every device (UA) in the I/O config, IOCP creates a subchannel for > each LPAR in the access list for the device. The metadata for the > subchannel includes the owning LPAR's CSS and MIF ID. When the LPAR uses > one of its subchannels to communicate with a device, the channel subsystem > grabs the UA, CSS and MIF ID, and sends them with the I/O request to the > CU. That means that two LPARs can use the same UA on the same CU, and the > CU can tell them apart. (Yay!) Recognizing the CSS and MIF ID is what > makes a device MIF-capable. > > Now, the extent to which a CU surfaces this knowledge to the management > interfaces varies. OSA-ICC makes it very visible. You associate a > TN3270E LUNAME with a particular CSS, MIF, and, optionally, a particular > device number. The OSA has the distinct advantage of having access to the > I/O configuration data, so it can see the device number associations and > show them to you in the configuration panels, not requiring you to do the > device number <-> UA translations yourself. > > Alan Altmark > z/VM Consultant > IBM Lab Services > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Query on OSA-ICC consoles
On Fri, 10 Jun 2016 16:53:42 +0530, linda golding wrote: >Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? > >I did a search in our systems and see that OSA-ICC devices are concurrently >active on all LPARS of the sysplex . I also see that PCHID is same across >all the systems . I am just trying to find out how multiple systems can >write on to the same physical OSA-ICC device ?..Basically i would like to >know how this happens at hardware level . Any pointers /documentation would >be a great help . It works because of the magic of the Multiple Image Facility, MIF. Device numbers are for the wetware. The host OS doesn't use them, but instead uses a subchannel number, for which there is a 1-1 binding with a device number in the LPAR. (The STORE SUBCHANNEL instruction provides the binding information.) For every device (UA) in the I/O config, IOCP creates a subchannel for each LPAR in the access list for the device. The metadata for the subchannel includes the owning LPAR's CSS and MIF ID. When the LPAR uses one of its subchannels to communicate with a device, the channel subsystem grabs the UA, CSS and MIF ID, and sends them with the I/O request to the CU. That means that two LPARs can use the same UA on the same CU, and the CU can tell them apart. (Yay!) Recognizing the CSS and MIF ID is what makes a device MIF-capable. Now, the extent to which a CU surfaces this knowledge to the management interfaces varies. OSA-ICC makes it very visible. You associate a TN3270E LUNAME with a particular CSS, MIF, and, optionally, a particular device number. The OSA has the distinct advantage of having access to the I/O configuration data, so it can see the device number associations and show them to you in the configuration panels, not requiring you to do the device number <-> UA translations yourself. Alan Altmark z/VM Consultant IBM Lab Services -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Speaking of 3270-X devices (Was: Query on OSA-ICC consoles)
Thank you Tom!
On 06/12/2016 02:20 PM, Tom Brennan wrote:
Any program talking to the terminal (i.e. VTAM, Session manager, ISPF,
whatever) can ask the terminal for its capabilities and the terminal
responsds with a Query-Reply block, maybe a couple of hundred bytes
long, describing all the things the terminal can do. That includes
things like the alternate screen size (mod-3, mod4, etc.), whether it
can handle extended colors, underlining, graphics, etc.
I ran a real mod-4 green screen for many years, and it probably
returned the same block every time. And the guy nearby with the color
3279 probably returned the same block for that machine - every time.
But terminal emulators aren't stuck with the same hardware emulation,
so you can click options that will alter the Query-Reply. A typical
change is the terminal model, but an emulator could (although I don't
know why anyone would want this), simulate a terminal that say, can do
extended colors but no underlining. Who knows what that might do to
an application program that isn't ready for the odd combination though.
This book (chapter 6) has a list of all the replies if you want the
gritty details.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7P4000/CCONTENTS
Here's an example of the returned data from a randomly chosen terminal
emulator:
88001781 8101 50001801 00D30320 "h..aa...&L.."
"P+. "
0010 009E0258 070C0780 001181A6 0B01 ".¦.8...+..aw"
"...X...ª"
0020 5000 18005000 18001681 86000800 "..&...&af..."
"..P...P."
0030 F4F1F1F2 F2F3F3F4 F4F5F5F6 F6F7F700 "411223344556677."
"(±±(())÷÷˜˜."
0040 0D818704 00F0F1F1 F2F2F4F4 00078188 ".ag..0112244..ah"
".=±±==(("
0050 00010200 06819900 1B81 85820007 ".araeb.."
""
0060 0C00 0007 0002B904 170100F1 "..+1"
"..¦±"
0070 03C30136 003F818F E3C3 D7F3F2F7 ".Ca¦..TCP327"
".+.6.?p++==˜"
0080 F040E5C9 E2E3C140 40400401 25FF "0 VISTA .."
"=@s+Gp-@@@% "
0090 FF020600 00C0D59D 5000 0028 ".{N+&..." "
++.P..("
00A0 4E6F7420 79657420 6C6F6767 65642069 "+?+.`-+.%?++-+.-" "Not yet
logged i"
00B0 6E212900 000D8180 80818586 878899A6 ">.a++aefghrw"
"n!)ª"
00C0 A8FFEF "y.+ " "¿ n "
Another thing in there is the code page and character set used by the
terminal emulator, which can be picked up by the application program
and checked. For example, folks using code page 1047 might see SPUFI
give a warning that it likes code page 37 better. The 1047 SPUFI is
complaining about came from this pile of bytes - at location +6B.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Speaking of 3270-X devices (Was: Query on OSA-ICC consoles)
Thank you. On 06/12/2016 07:31 AM, esst...@juno.com wrote: If you can locate these manuals IBM 3270 Information Display SYSTEM GA23-0060 IBM 3270 Information Display SyStem Data Sream Programmers Reference GA23-0059 These Are Old Publication numbers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Speaking of 3270-X devices (Was: Query on OSA-ICC consoles)
Any program talking to the terminal (i.e. VTAM, Session manager, ISPF,
whatever) can ask the terminal for its capabilities and the terminal
responsds with a Query-Reply block, maybe a couple of hundred bytes
long, describing all the things the terminal can do. That includes
things like the alternate screen size (mod-3, mod4, etc.), whether it
can handle extended colors, underlining, graphics, etc.
I ran a real mod-4 green screen for many years, and it probably returned
the same block every time. And the guy nearby with the color 3279
probably returned the same block for that machine - every time. But
terminal emulators aren't stuck with the same hardware emulation, so you
can click options that will alter the Query-Reply. A typical change is
the terminal model, but an emulator could (although I don't know why
anyone would want this), simulate a terminal that say, can do extended
colors but no underlining. Who knows what that might do to an
application program that isn't ready for the odd combination though.
This book (chapter 6) has a list of all the replies if you want the
gritty details.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7P4000/CCONTENTS
Here's an example of the returned data from a randomly chosen terminal
emulator:
88001781 8101 50001801 00D30320 "h..aa...&L.."
"P+. "
0010 009E0258 070C0780 001181A6 0B01 ".¦.8...+..aw"
"...X...ª"
0020 5000 18005000 18001681 86000800 "..&...&af..."
"..P...P."
0030 F4F1F1F2 F2F3F3F4 F4F5F5F6 F6F7F700 "411223344556677."
"(±±(())÷÷˜˜."
0040 0D818704 00F0F1F1 F2F2F4F4 00078188 ".ag..0112244..ah"
".=±±==(("
0050 00010200 06819900 1B81 85820007 ".araeb.."
""
0060 0C00 0007 0002B904 170100F1 "..+1"
"..¦±"
0070 03C30136 003F818F E3C3 D7F3F2F7 ".Ca¦..TCP327"
".+.6.?p++==˜"
0080 F040E5C9 E2E3C140 40400401 25FF "0 VISTA .."
"=@s+Gp-@@@% "
0090 FF020600 00C0D59D 5000 0028 ".{N+&..."
" ++.P..("
00A0 4E6F7420 79657420 6C6F6767 65642069 "+?+.`-+.%?++-+.-" "Not yet
logged i"
00B0 6E212900 000D8180 80818586 878899A6 ">.a++aefghrw"
"n!)ª"
00C0 A8FFEF "y.+ " "¿ n
"
Another thing in there is the code page and character set used by the
terminal emulator, which can be picked up by the application program and
checked. For example, folks using code page 1047 might see SPUFI give a
warning that it likes code page 37 better. The 1047 SPUFI is
complaining about came from this pile of bytes - at location +6B.
esst...@juno.com wrote:
If you can locate these manuals
IBM 3270 Information Display SYSTEM GA23-0060
IBM 3270 Information Display SyStem Data Sream Programmers Reference GA23-0059
These Are Old Publication numbers
-- Original Message --
From: scott
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Speaking of 3270-X devices (Was: Query on OSA-ICC consoles)
Date: Sun, 12 Jun 2016 00:11:30 -0400
Where can I find more detailed information on 3270-X defined devices?
Are they queried to find out what their capabilities are dynamically?
Scott
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Speaking of 3270-X devices (Was: Query on OSA-ICC consoles)
If you can locate these manuals IBM 3270 Information Display SYSTEM GA23-0060 IBM 3270 Information Display SyStem Data Sream Programmers Reference GA23-0059 These Are Old Publication numbers -- Original Message -- From: scott To: IBM-MAIN@LISTSERV.UA.EDU Subject: Speaking of 3270-X devices (Was: Query on OSA-ICC consoles) Date: Sun, 12 Jun 2016 00:11:30 -0400 Where can I find more detailed information on 3270-X defined devices? Are they queried to find out what their capabilities are dynamically? Scott -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Speaking of 3270-X devices (Was: Query on OSA-ICC consoles)
Where can I find more detailed information on 3270-X defined devices? Are they queried to find out what their capabilities are dynamically? Scott -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Query on OSA-ICC consoles
While every system can use the same UCB from an OS point of view, there are cases where that may not be a good idea or even not work. As for the wisdom using the same device address, a sysplex can (in my view ought to) display messages from all members. Having the same console address might cause confusion for Ops. As for functionality, we use the product VCC to manage consoles for all z/OS LPARs in the enterprise. VCC uses defined console addresses to keep track of them. AFAIK VCC would not work if all consoles had the same UCB address. What we can do is use the same 'control unit' definition in our single enterprise IODF. We just make different device addresses accessible to different LPARs. So all LPARs see a console control unit at 0700, but the devices (00 - the max) are attached in the IODF uniquely to each LPAR for VCC management. While all the devices are visible via D U, trying to vary online someone else's console fails: 13.16.27 X0 v 0710,online 13.16.27 X0 IEE103I UNIT 0710 NOT BROUGHT ONLINE IEE763I NAME= IECVIOPM CODE= 0004 IOS551I NO PATHS PHYSICALLY AVAILABLE IEE764I END OF IEE103IRELATED MESSAGES I refer above to 'the max' because there seems to be a limitation of twenty-something (less than 32) that I don't understand. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Neubert, Kevin Sent: Friday, June 10, 2016 5:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Query on OSA-ICC consoles Not seeing a newer guide, but this one will walk you through it: OSA-Express Integrated Console Controller Implementation Guide (SG24-6364-01). Believe the gist you are looking for lies between the IODF RESOURCE macro statement and OSA-ICC CONFIG_SESSION source file. Let's say two systems (SYSA and SYSB) share the same UCB (C00). The pertinent part of the RESOURCE statement is (name, MIF image ID) and the equivalent piece in the CONFIG_SESSION file is IID=nn (MIF image ID). Abbreviated example below. IODF: RESOURCE PARTITION=((CSS(0),(SYSA,1),(SYSB,2)… CHPID PATH… CNTLUNIT CUNUMBR… IODEVICE ADDRESS=(C00,001)… OSA-ICC: CSS= 00 IID= 01 DEVICE= C00 … CSS= 00 IID= 02 DEVICE= C00 … Regards, Kevin -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of linda golding Sent: Friday, June 10, 2016 4:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Query on OSA-ICC consoles Thought to post this question as i couldn't find this information in any of the IBM documentation . Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? I did a search in our systems and see that OSA-ICC devices are concurrently active on all LPARS of the sysplex . I also see that PCHID is same across all the systems . I am just trying to find out how multiple systems can write on to the same physical OSA-ICC device ?..Basically i would like to know how this happens at hardware level . Any pointers /documentation would be a great help . Linda -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Query on OSA-ICC consoles
Not seeing a newer guide, but this one will walk you through it: OSA-Express Integrated Console Controller Implementation Guide (SG24-6364-01). Believe the gist you are looking for lies between the IODF RESOURCE macro statement and OSA-ICC CONFIG_SESSION source file. Let's say two systems (SYSA and SYSB) share the same UCB (C00). The pertinent part of the RESOURCE statement is (name, MIF image ID) and the equivalent piece in the CONFIG_SESSION file is IID=nn (MIF image ID). Abbreviated example below. IODF: RESOURCE PARTITION=((CSS(0),(SYSA,1),(SYSB,2)… CHPID PATH… CNTLUNIT CUNUMBR… IODEVICE ADDRESS=(C00,001)… OSA-ICC: CSS= 00 IID= 01 DEVICE= C00 … CSS= 00 IID= 02 DEVICE= C00 … Regards, Kevin -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of linda golding Sent: Friday, June 10, 2016 4:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Query on OSA-ICC consoles Thought to post this question as i couldn't find this information in any of the IBM documentation . Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? I did a search in our systems and see that OSA-ICC devices are concurrently active on all LPARS of the sysplex . I also see that PCHID is same across all the systems . I am just trying to find out how multiple systems can write on to the same physical OSA-ICC device ?..Basically i would like to know how this happens at hardware level . Any pointers /documentation would be a great help . Linda -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Query on OSA-ICC consoles
Think of the OSA-ICC as an analog to TN3270 (with an enhancement for MCS support). It speaks TCP/IP on one side and (MCS or LOCAL SNA) on the other. As to how the data gets from "here to there, I cannot speak to the internals. HTH, Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? I did a search in our systems and see that OSA-ICC devices are concurrently active on all LPARS of the sysplex . I also see that PCHID is same across all the systems . I am just trying to find out how multiple systems can write on to the same physical OSA-ICC device ?..Basically i would like to know how this happens at hardware level . Any pointers /documentation would be a great help . This email � including attachments � may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Query on OSA-ICC consoles
W dniu 2016-06-10 o 13:23, linda golding pisze: Thought to post this question as i couldn't find this information in any of the IBM documentation . Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? I did a search in our systems and see that OSA-ICC devices are concurrently active on all LPARS of the sysplex . I also see that PCHID is same across all the systems . I am just trying to find out how multiple systems can write on to the same physical OSA-ICC device ?..Basically i would like to know how this happens at hardware level . Any pointers /documentation would be a great help . It's "black magic" of emulated devices. Indeed, multiple LPARs can use same device number (in same CU, on same CHPID) concurrently and each has exclusive access to the device. HTH -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Query on OSA-ICC consoles
Thought to post this question as i couldn't find this information in any of the IBM documentation . Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? I did a search in our systems and see that OSA-ICC devices are concurrently active on all LPARS of the sysplex . I also see that PCHID is same across all the systems . I am just trying to find out how multiple systems can write on to the same physical OSA-ICC device ?..Basically i would like to know how this happens at hardware level . Any pointers /documentation would be a great help . Linda -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
