On Sun, Jul 20, 2014 at 1:22 PM, R.S. <[email protected]> wrote: > In the old times of 3174 (not so old for me), the console was able to > reconnect automatically after POR. So the console could work as a NIP or > later as MCS console. > I observed that OSA-ICC console (actually emulator session) do not reconnect > automatcially after POR. The session has enabled "automatically connect" > option, but it didn't help. > In fact it's not big problem to manually reconnect the session to the ICC, > but I would like to have the consoles as in good old days of 3174. > > Any clue? > > -- > Radoslaw Skorupka > Lodz, Poland
I am not a hardware guru. Just to consolidate things in my head. Back in those days (and even today) certain "local non-SNA" 3270 devices were generated in the SYSGEN (now the HCD and CONSOLxx member) as being CONSOLES. With z/OS, there are two classes of consoles NIPCONS and normal consoles. The NIPCONS are in the HCD. The normal consoles are in the CONSOLxx member of PARMLIB. At IPL, NIP reads in the HCD and finds the NIPCONS. NIP uses these local non-SNA 3270 device addresses, if active, as consoles until the CONSOLE address space starts up. Then the local non-SNA 3270 address in the CONSOLxx member are activated. The above worked well in the real 3174 time frame because the 3270 terminals were "always connected" directly to the z machine, via a 3174 on a channel. In the OSA-ICC world, the OSA is emulating a local non-SNA controller. And is always telling whomever asks "Yes, the device at address .... is working fine, feel free to send data!". In reality, the OSA is keeping a virtual 3270 buffer in its memory and mainly not doing much with it. Eventually, somebody on a PC will use a TN3270 emulator to connect to the OSA-ICC. The OSA-ICC will then associate that TN3270 session with one of its 3270 virtual devices and the user sees the 3270 screen. The problem now can be restated as "how can I have the TN3270 emulators on specific PCs detect that the z/OS system has disconnected due to being IPL'd and have it, the emulator, periodically attempt to reconnect to the OSA-ICC". This stops being a z/OS question and becomes a PC Emulator question. Have you considered the x3270 emulator? It is not "top of the line" by any means. But by proper use of the ~/.x3270pro file, the keyboard can be configured along with other configuration options. And, at least on Linux, it could be started at Linux BOOT time. The magic is the "-reconnect" switch. The command might look something like: x3270 -reconnect luname@hostname So, what emulator are you using? Do you know if it has an automatic poll to reconnect on disconnect option? Note that I have a vague idea that it might be possible, somehow, to have a z/OS STC run at IPL time which can "send a message" (SNMP trap?) to "some server" (or to the PCs running the TN3270 emulator) which could then "somehow" (script?) cause the TN3270 emulator to be started or to reconnect to the OSA-ICC. Long ago, we had a PC which ran Rumba. This Rumba had a "workbook" which had 3270 printers defined in it. These were CICS printers which used to exist. The Rumba printers emulated 3287s and each virtual 3287 was associated with a Windows printer. I don't remember how, but we had this set up to automatically reconnect the 3287 printer sessions when they disconnected. IIRC, when disconnected, they would attempt to reconnect every 2? minutes until they succeeded. This is a little fuzzy. But "fuzzy logic" is all the rage now, right? -- P.S. Despite your fine attempts, I am just not able to learn Polish. <GRIN/> -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
