PCOM attached printer and TN3270E
I am trying to define a PCOM session as a printer to TN3270E. At PCOM I clicked Session Parameters and Taged PRINTER instead of DIsplay. I then clicked OK and again, on Link Parameters. I specified an IUP ADDR, LUNAME and PORET. When I try to connect, I get a gray screen whth the word QUIT on it and after some minutes, a dialog box saying PCSTLNET009 - The spoecified LU name is not known to the server. The LU NAME is defined in the same member in VTAMLST as all other LU names defined to TN3270. If I switch fdrom PRINTER to DISPLAY in Session parameters, everything works fine. What am I missing in VTAM or TN3270 definitions? ITschak -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: PCOM attached printer and TN3270E
What is the session trying to connect to? And OSA or an OSC adapter? Or something else? It would seem it is not defined there. If you are using an OSC adapter, the session must be defined there as well. Doug Fuerst Itschak Mugzach wrote: I am trying to define a PCOM session as a printer to TN3270E. At PCOM I clicked Session Parameters and Taged PRINTER instead of DIsplay. I then clicked OK and again, on Link Parameters. I specified an IUP ADDR, LUNAME and PORET. When I try to connect, I get a gray screen whth the word QUIT on it and after some minutes, a dialog box saying PCSTLNET009 - The spoecified LU name is not known to the server. The LU NAME is defined in the same member in VTAMLST as all other LU names defined to TN3270. If I switch fdrom PRINTER to DISPLAY in Session parameters, everything works fine. What am I missing in VTAM or TN3270 definitions? ITschak -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: PCOM attached printer and TN3270E
No sure I understand your questiion. It is an OSA adapter, but the address is resolved by TN3270E for sure, as we configured PCOM to terminal and then the LU was found. ITschak On Mon, Mar 8, 2010 at 4:17 PM, Doug Fuerst d...@bkassociates.net wrote: What is the session trying to connect to? And OSA or an OSC adapter? Or something else? It would seem it is not defined there. If you are using an OSC adapter, the session must be defined there as well. Doug Fuerst Itschak Mugzach wrote: I am trying to define a PCOM session as a printer to TN3270E. At PCOM I clicked Session Parameters and Taged PRINTER instead of DIsplay. I then clicked OK and again, on Link Parameters. I specified an IUP ADDR, LUNAME and PORET. When I try to connect, I get a gray screen whth the word QUIT on it and after some minutes, a dialog box saying PCSTLNET009 - The spoecified LU name is not known to the server. The LU NAME is defined in the same member in VTAMLST as all other LU names defined to TN3270. If I switch fdrom PRINTER to DISPLAY in Session parameters, everything works fine. What am I missing in VTAM or TN3270 definitions? ITschak -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: PCOM attached printer and TN3270E
Itschak This is an interesting problem. I haven't done this but I have - tried to - read up on how it is done - and it's not easy! Incidentally: 1. You should really be asking in the IBMTCP-L list since that's where this sort of expertise mainly resides: post tail For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L /post tail 2. You (and also Phil Kingston) are interrupting my efforts getting a rather long response ready for your friend/colleague Matan regarding connecting EE and HIS - just so he can detect that I am still working on it! PCSTLNET009 - The specified LU name is not known to the server This indicates a failure in the sort of exchange described by the following example near the end of RFC 2355: quote The following example shows a TN3270E-capable server and a TN3270E- capable client establishing a printer session where the client requests a specific device-name, and where some amount of 3270 function negotiation is required before an agreement is reached: Server: IAC DO TN3270E Client: IAC WILL TN3270E Server: IAC SB TN3270E SEND DEVICE-TYPE IAC SE Client: IAC SB TN3270E DEVICE-TYPE REQUEST IBM-3287-1 CONNECT myprt IAC SE Server: IAC SB TN3270E DEVICE-TYPE IS IBM-3287-1 CONNECT myprt IAC SE Client: IAC SB TN3270E FUNCTIONS REQUEST DATA-STREAM-CTL IAC Server: IAC SB TN3270E FUNCTIONS REQUEST DATA-STREAM-CTL RESPONSES IAC SE Client: IAC SB TN3270E FUNCTIONS REQUEST DATA-STREAM-CTL IAC Server: IAC SB TN3270E FUNCTIONS IS DATA-STREAM-CTL IAC SE (3270 data stream is exchanged) /quote The following is what works when you try using a display - note confusingly called terminal in the RFC and also Communications Server manuals: quote The following example shows a TN3270E-capable server and a TN3270E- capable client establishing a generic pool (non-specific) terminal session: Server: IAC DO TN3270E Client: IAC WILL TN3270E Server: IAC SB TN3270E SEND DEVICE-TYPE IAC SE Client: IAC SB TN3270E DEVICE-TYPE REQUEST IBM-3278-2 IAC SE Server: IAC SB TN3270E DEVICE-TYPE IS IBM-3278-2 CONNECT anyterm IAC SE Client: IAC SB TN3270E FUNCTIONS REQUEST RESPONSES IAC SE Server: IAC SB TN3270E FUNCTIONS IS RESPONSES IAC SE (3270 data stream is exchanged) /quote You haven't given any details of your TN3270E server PROFILE statements. I expect that your display connection is allocated an LU name - corresponding to a VTAM APPL statement - from the old DEFAULTLUS pool as the easiest way of doing it. Although the manual descriptions are tortuous in the extreme, I believe your printer connection, because you have specified a so-called LU name, will be regarded as specific rather than generic - as well as because it's a printer connection - cannot be allocated an LU name from the DEFAULTLUS pool. I believe, in the absence of those fancy mapping statements, that you need ultimately to have the LU name for the printer connection allocated from the DEFAULTPRTSPEC pool: quote Use the optional DEFAULTPRTSPEC or SDEFAULTPRTSPEC object and mapping statements to define a list or range of printer LUs with a default mapping to the NULL client identifier. This LU pool is be used by a printer emulator requesting a specific connection if no other printer LU group maps specifically or generically to the client. /quote Try DEFAULTPRTSPEC prtlu ENDDEFAULTPRTSPEC where prtlu is the APPL name you hope to use for your printer. I think an alternative could be not to specify a so-called LU name in PCOMM and use the following statement: DEFAULTPRT prtlu ENDDEFAULTPRT quote Use the optional DEFAULTPRT or SDEFAULTPRT object and mapping statements to define a list or range of printer LUs that have a default mapping to the NULL client identifier. This LU pool is used by a printer emulator that is requesting a generic connection if no other printer LU group maps to the client. /quote I guess I need to go through the text in the CS IP Configuration Guide and the CS IP Configuration Reference yet again to be sure but I suspect that the so- called LU name as specified in PCOMM is misleading. I suspect the following: The so-called LU name is merely a name which is used in TN3270E negotiation between the client and the server as shown in RFC 2355. The CS TN3270E server statements will determine whether there is really any relationship between the so-called LU name and the VTAM LU names. It's significant that the LU name can be treated within the CS TN3270E server as the name of a group of LUs. Do let us know how you get on so that there is an archive entry which explains how a TN3270E printer is set up, at least in the case of PCOMM. Thank you. Chris Mason On Mon, 8 Mar 2010 15:47:12 +0200, Itschak Mugzach imugz...@gmail.com wrote: I am trying to define a PCOM session as a printer to TN3270E. At PCOM I clicked Session Parameters and Taged PRINTER instead of DIsplay. I then clicked OK
Re: PCOM attached printer and TN3270E
Thanks Chris, I'll try to ask the question in TCP-L and respond here with some answers. Few years ago I did this to config a Mackinney product that used to send SMS messages, but I don;t recall how I did it... ITschak On Mon, Mar 8, 2010 at 5:11 PM, Chris Mason chrisma...@belgacom.net wrote: Itschak This is an interesting problem. I haven't done this but I have - tried to - read up on how it is done - and it's not easy! Incidentally: 1. You should really be asking in the IBMTCP-L list since that's where this sort of expertise mainly resides: post tail For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L /post tail 2. You (and also Phil Kingston) are interrupting my efforts getting a rather long response ready for your friend/colleague Matan regarding connecting EE and HIS - just so he can detect that I am still working on it! PCSTLNET009 - The specified LU name is not known to the server This indicates a failure in the sort of exchange described by the following example near the end of RFC 2355: quote The following example shows a TN3270E-capable server and a TN3270E- capable client establishing a printer session where the client requests a specific device-name, and where some amount of 3270 function negotiation is required before an agreement is reached: Server: IAC DO TN3270E Client: IAC WILL TN3270E Server: IAC SB TN3270E SEND DEVICE-TYPE IAC SE Client: IAC SB TN3270E DEVICE-TYPE REQUEST IBM-3287-1 CONNECT myprt IAC SE Server: IAC SB TN3270E DEVICE-TYPE IS IBM-3287-1 CONNECT myprt IAC SE Client: IAC SB TN3270E FUNCTIONS REQUEST DATA-STREAM-CTL IAC Server: IAC SB TN3270E FUNCTIONS REQUEST DATA-STREAM-CTL RESPONSES IAC SE Client: IAC SB TN3270E FUNCTIONS REQUEST DATA-STREAM-CTL IAC Server: IAC SB TN3270E FUNCTIONS IS DATA-STREAM-CTL IAC SE (3270 data stream is exchanged) /quote The following is what works when you try using a display - note confusingly called terminal in the RFC and also Communications Server manuals: quote The following example shows a TN3270E-capable server and a TN3270E- capable client establishing a generic pool (non-specific) terminal session: Server: IAC DO TN3270E Client: IAC WILL TN3270E Server: IAC SB TN3270E SEND DEVICE-TYPE IAC SE Client: IAC SB TN3270E DEVICE-TYPE REQUEST IBM-3278-2 IAC SE Server: IAC SB TN3270E DEVICE-TYPE IS IBM-3278-2 CONNECT anyterm IAC SE Client: IAC SB TN3270E FUNCTIONS REQUEST RESPONSES IAC SE Server: IAC SB TN3270E FUNCTIONS IS RESPONSES IAC SE (3270 data stream is exchanged) /quote You haven't given any details of your TN3270E server PROFILE statements. I expect that your display connection is allocated an LU name - corresponding to a VTAM APPL statement - from the old DEFAULTLUS pool as the easiest way of doing it. Although the manual descriptions are tortuous in the extreme, I believe your printer connection, because you have specified a so-called LU name, will be regarded as specific rather than generic - as well as because it's a printer connection - cannot be allocated an LU name from the DEFAULTLUS pool. I believe, in the absence of those fancy mapping statements, that you need ultimately to have the LU name for the printer connection allocated from the DEFAULTPRTSPEC pool: quote Use the optional DEFAULTPRTSPEC or SDEFAULTPRTSPEC object and mapping statements to define a list or range of printer LUs with a default mapping to the NULL client identifier. This LU pool is be used by a printer emulator requesting a specific connection if no other printer LU group maps specifically or generically to the client. /quote Try DEFAULTPRTSPEC prtlu ENDDEFAULTPRTSPEC where prtlu is the APPL name you hope to use for your printer. I think an alternative could be not to specify a so-called LU name in PCOMM and use the following statement: DEFAULTPRT prtlu ENDDEFAULTPRT quote Use the optional DEFAULTPRT or SDEFAULTPRT object and mapping statements to define a list or range of printer LUs that have a default mapping to the NULL client identifier. This LU pool is used by a printer emulator that is requesting a generic connection if no other printer LU group maps to the client. /quote I guess I need to go through the text in the CS IP Configuration Guide and the CS IP Configuration Reference yet again to be sure but I suspect that the so- called LU name as specified in PCOMM is misleading. I suspect the following: The so-called LU name is merely a name which is used in TN3270E negotiation between the client and the server as shown in RFC 2355. The CS TN3270E server statements will determine whether there is really any relationship between the so-called LU name and the VTAM LU names. It's significant that the LU name can be treated within the CS TN3270E server as the name of a group of LUs. Do let us know how you get on so that
Re: PCOM attached printer and TN3270E
Doug Not sure I understand your question. Ditto! This is a logical problem involving RFC 2355 negotiation and Communications Server TN3270E server PROFILE statements - until I have a more convincing description of what it is all about! Incidentally Itschak's display connection works so the IP substructure is just fine. But perhaps I see the source of your confusion. Talk of session makes one assume SNA. You have managed to overlook two references to TN3270. And so I heartily agree if you want to curse the stupid misuse of terminology which has TN3270E TCP ***connections*** described libellously as - it sticks in my throat - sessions. This is an invitation to confusion and you appear to have wholeheartedly accepted that very invitation! Chris Mason On Mon, 8 Mar 2010 17:06:43 +0200, Itschak Mugzach imugz...@gmail.com wrote: No sure I understand your questiion. It is an OSA adapter, but the address is resolved by TN3270E for sure, as we configured PCOM to terminal and then the LU was found. ITschak On Mon, Mar 8, 2010 at 4:17 PM, Doug Fuerst d...@bkassociates.net wrote: What is the session trying to connect to? And OSA or an OSC adapter? Or something else? It would seem it is not defined there. If you are using an OSC adapter, the session must be defined there as well. Doug Fuerst Itschak Mugzach wrote: I am trying to define a PCOM session as a printer to TN3270E. At PCOM I clicked Session Parameters and Taged PRINTER instead of DIsplay. I then clicked OK and again, on Link Parameters. I specified an IUP ADDR, LUNAME and PORET. When I try to connect, I get a gray screen whth the word QUIT on it and after some minutes, a dialog box saying PCSTLNET009 - The spoecified LU name is not known to the server. The LU NAME is defined in the same member in VTAMLST as all other LU names defined to TN3270. If I switch fdrom PRINTER to DISPLAY in Session parameters, everything works fine. What am I missing in VTAM or TN3270 definitions? ITschak -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: PCOM attached printer and TN3270E
It sounds like you are using an OSA adapter as an OSC adapter for terminal (TN3270 or Console) access. I have my printer configured to the address of the IP stack in the MF, the LU is the printer LU I defined in VTAM, and I am using port 23. I connect immediately. Status screen indicates connected immediately. Doug Itschak Mugzach wrote: No sure I understand your questiion. It is an OSA adapter, but the address is resolved by TN3270E for sure, as we configured PCOM to terminal and then the LU was found. ITschak On Mon, Mar 8, 2010 at 4:17 PM, Doug Fuerst d...@bkassociates.net wrote: What is the session trying to connect to? And OSA or an OSC adapter? Or something else? It would seem it is not defined there. If you are using an OSC adapter, the session must be defined there as well. Doug Fuerst Itschak Mugzach wrote: I am trying to define a PCOM session as a printer to TN3270E. At PCOM I clicked Session Parameters and Taged PRINTER instead of DIsplay. I then clicked OK and again, on Link Parameters. I specified an IUP ADDR, LUNAME and PORET. When I try to connect, I get a gray screen whth the word QUIT on it and after some minutes, a dialog box saying PCSTLNET009 - The spoecified LU name is not known to the server. The LU NAME is defined in the same member in VTAMLST as all other LU names defined to TN3270. If I switch fdrom PRINTER to DISPLAY in Session parameters, everything works fine. What am I missing in VTAM or TN3270 definitions? ITschak -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
