Is that true regardless of the emmory size of the controller?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Attila Fogarasi [[email protected]] Sent: Sunday, December 12, 2021 5:57 AM To: [email protected] Subject: Re: VTAM LU coding for 3192G display I just remembered that unrelated devices on the same controller can affect what are valid values for the bind for 3192g. For example if there is a 3287 (printer) defined on the same controller, then the max RU size is reduced even for the 3192g (so what would have been a valid bind with no 3287 configured becomes invalid). This is the reason the otherwise very capable 3270 architecture became abandoned :) All of this varies with specific device types, of course, once you get out of mainstream devices. Good luck getting GDDM working. On Sun, Dec 12, 2021 at 9:42 PM Attila Fogarasi <[email protected]> wrote: > Logmode is invalid for the physical device, sense 0821 means that the bind > was rejected due to having invalid parameters (which come from the logmode > entry). You might want to check the PSERVIC value. > > On Sun, Dec 12, 2021 at 8:35 PM Alexander Huemer <[email protected]> > wrote: > >> Hi >> >> This has probably not been done by anybody in 20 years, I'll try my luck >> anyways. >> I have several physical 3270 displays hooked up to a 3174 that talks >> APPN to VTAM. 3179, 3290 and an IRMA board work without any issues. >> There is a 3192G (DFT, like the 3290) as well, that doesn't. >> The display does show the VTAM logon screen, though upon logon attempt >> it errors out. >> >> The display shows: >> > T005 UNABLE TO ESTABLISH SESSION - BIND FAILED WITH SENSE 08210000 >> >> In the OIA it says: >> > X PROG722 >> >> VTAM says: >> > 00 19.01.51 STC00160 IST663I BIND FAIL REQUEST RECEIVED, >> SENSE=08210000 >> > IST664I REAL OLU=MYNETID.T005 REAL DLU=MYNETID.A06TSO01 >> > IST889I SID = F4EF78629E2CE0DD >> > IST891I MYNETID.P390SSCP.VN3174PU GENERATED FAILURE NOTIFICATION >> > IST893I ORIGINAL FAILING REQUEST IS BIND >> > IST314I END >> > - 19.01.51 STC00161 IKT030I TCAS LOGON PROCESS FAILURE PLU=A06TSO01 >> > - SLU=MYNETID.A06TSO01 SENSE= 08210000 >> > 19.01.51 IKT117I TSO/VTAM INITIALIZATION FAILED FOR >> > APPLNAME=TSO0001 , LUNAME=MYNETID.T005 >> > 19.01.51 IKT111I APPLNAME=TSO0001 FAILED DUE TO: TCAS >> CLSDST >> > PASS FAILURE >> > 19.01.51 IKJ608I LOGON TERMINATED, IKTXINIT, TSO/VTAM >> > INITIALIZATION ERROR >> > 19.01.51 STC00160 IST804I CLOSE IN PROGRESS FOR TSO0001 OPENED BY >> > ***NA*** >> > 19.01.51 STC00160 IST400I TERMINATION IN PROGRESS FOR APPLID >> TSO0001 >> > 19.01.51 STC00160 IST805I VTAM CLOSE COMPLETE FOR TSO0001 >> > IEE612I CN=01 DEVNUM=0700 SYS=P390 >> >> The LU coding for T005 in VTAM looks like this: >> > T005 LU LOCADDR=5,ISTATUS=ACTIVE,DLOGMOD=DYNAMICB,USSTAB=USSS >> >> I had this previously, to the same effect: >> > T005 LU LOCADDR=5,ISTATUS=ACTIVE,DLOGMOD=D4C32XX3,USSTAB=USSS >> >> I suspect the LU coding is the culprit, maybe DLOGMOD. >> Any suggestions appreciated. >> >> -Alex >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
