Matan I'm working through some suitable definitions for you as samples - with explanations - and including some guidance on HIS. Apart from the DLUR part of the VTAM definitions and anything to do with HIS, what I am offering is based on what I have working at a customer where I provide consultancy from time to time.
Nevertheless I'm reasonably confident of the DLUR definitions since they correspond to class work I have done between 1994 and 1999 and nothing significant has changed since. The HIS suggestions are based on what I can glean from the HIS EE "White Paper" which probably corresponds to a working example even if the explanations are woeful in the extreme. I get the impression I understand the definitions provided better than the authors of the "White Paper". It helps to know that the so-called IP-DLC link service was written by a competent software company - constrained into using a monstrous structure in order to add the Enterprise Extender capability to the HIS product - so it's only the Microsoft documentation which is awful and not the IP-DLC part of the HIS product itself. - > Based on this IBM answer: http://www-01.ibm.com/support/docview.wss? uid=swg21380385 This IBM "answer" to a supposedly "frequently asked question" (FAQ) actually provides two solutions: 1. The first two paragraphs describe a printer which is accessed via a TN3270E client - necessarily following RFC 2355. I am unfamiliar with any hardware/software implementations which might be specifically a TN3270E printer. I would expect such a "printer" to be a print function in say a Windows PC which was running a 3270 emulator capable of supporting TN3270E for a "display" function - mapped to a "window" obviously - with some sort of "printer" capability. It should be clear how all this is done from the documentation of the 3270 emulator, for example, PCOMM. Note that the appearance of this solution to CICS is that the "printer" appears as an LU to CICS and the session uses either LU type 1 or LU type 3 protocols - as selected via the mode table entry. The TN3270E server concatenates the SNA session to a TN3270E TCP connection to the TN3270E client. It is now up to the client how it handles the actual printer "feeding" it with the data arriving on the TN3270E TCP connection. The "defining of the printer to TCP/IP" is through the definitions in the TN3270E server. The only way to understand the answer in this FAQ is to know the answer already! This is not at all a clever document! Note that "TCP/IP Telnet" is, in much better terminology, the TN3270E server. The use of the terminology "TCP/IP attached printer" is most misleading. It is a printing function somehow or other supported through the TN3270E emulator. If there is any "standard" - as implied by the silly terminology in this FAQ - to be found in the implementations of this function in TN3270E clients, it is accidental. There are no RFCs covering this - as far as I know - and I would be very surprised if there were because there is no need. It is even more stupid when implying that the use of SNA is in the past: "did". What utter nonsense!!! As I said, as far as CICS is concerned, the printer appears as an LU as it always has and this inevitably means that SNA is used. What rank stupidity to suggest otherwise!!! The "pool of TCP/IP Telnet LUs" is a number of VTAM APPL statements, the names of which are known to the TN3270E server and one of them is used in order to pretend to be a "printer" LU. Maybe the author of this part of the FAQ had just heard about TN3270 and can't contain his/her excitement! - except he/she has forgotten the appropriate names to use and has invented some confusing terminology. Is this the way you were going to be handling your printing requirement? 2. The last two paragraphs describe another technique - note the word "also" in the third paragraph. Since this might/does involve additional products you will not be interested in using it. It is actually similar to the TN3270E solution in that the SNA session between CICS and the printing software is much the same as the SNA session between CICS and the TN3279E server. In both cases the "printer" LU is simulated by software using the VTAM API with the agency of a VTAM APPL statement. - Note that there is yet another solution which avoids the SNA session between CICS and something else. However this must involve changes to CICS and - I guess - must involve another product - although it may be one of those "free" products that are floating around for courageous people to use, courageous because the systems programmer using such a "free" product is necessarily the responsible "support representative"! - > ... my network printer IP. What is this? As I mention above, the printer that you support through a TN3270E connection must be associated with a TN3270E client in some way. If this is confusing for you, perhaps you can point me at a web page which indicates how this "printer" behaves technically. I worry that it may be the sort of "IP printer" which corresponds to the second of the solutions described in the FAQ and not the first - but I could be wrong ... - > ... using the TN3270 define an LU with LUMAP to my network printer IP. Please enclose either all or a representative sample of your TN3270E PROFILE data set so that we can check how you are using the statements. I suspect another misunderstanding - but, again, I could be wrong ... - > IST663I INIT OTHER REQUEST FAILED, SENSE=08570003 As clearly indicated by the VTAM messages - and probably also the CICS messages, the problem is that the intended session partner, FTCP0200, is not active - so nothing will happen! > ... (although the LU was CONCT) ... In order to be a partner in a session, the definition entity, in this case a VTAM APPL statement, needs to have status ACTIV.[1] - > So we decided on using HIS ... I'm obviously working through your post and making comments as I go. I hope you are not about to say something that makes all my comments worthless! It appears you have some sort of "IP printer" which you can work with HIS. What you also need to do is be sure that, if you define an LU in HIS, you can associate this printer with that LU and that whatever software makes the association can use either a 3270 data stream (LU type 3) or an SNA Character String (SCS - LU type 1) and convert it to data with which the "IP printer" is happy. Note that this solution has nothing whatsoever to do with the solutions mentioned in the IBM FAQ. - > > > - Is there no way to perform a pure IP connectivity to my LPAR? > > Note that, if the TN3270E server and CICS are running on the same LPAR ... > Yes, they are. > > ... it can be said that you have an IP connection from your workstation supporting the printer function and the LPAR where the print data is created. > I didn't completely understood you ... All I am saying here is that, in the case of the first solution described in the FAQ, with CICS and the TN3270E server running on the same LPAR, all the "outside the node" data traffic is transported by IP, thus it is "pure IP connectivity to your LPAR". > ... , my question here was : if i can using emulation to connect directly to tn3270, why in the HIS server i cant connect to the mainframe in port 23 and get a default LU. i now i simplisign it more then it is. This just doesn't make sense, I'm afraid. If you are trying to connect to the TN3270E server (port 23), then you are using the computer running HIS as a TN3270E client which, I believe, has nothing to do with the functions provided by HIS. Using the computer on which you run HIS as a TN3270E client may well be a solution - although nothing to do with HIS as I know it. You will be running some TN3270E client software such as PCOMM. In order to support the "printer" function - I guess managing to process the data in the same way as when you call the print function from any regular Windows program - you will have to examine how the TN3270E client handles a TN3270E printer TCP connection and that will be found in the documentation of the TN3270E emulator. - > Even if I will use 802.2, it means I need to define a working EE? No. - > Why should i define the OSA ? is the current definition are not enough? Again, I'm not sure what you are trying to say here. I can't "parse" it into English. There might be a "typo" where "is" is supposed to be "if" which would be consistent with not starting a new sentence or the double use of the verb "to be" in the sentence could be a mistake. The proper use of capital letters can help disentangle other mistakes - a bit like a parity bit added to a data octet! What are your current definitions? Are they for SNA connectivity to, for example, the HIS node or are they for IP connectivity - or both. If you don't use an OSA, what do you use? When an OSA is used with a QDIO INTERFACE statement (or DEVICE/LINK/HOME entry and possible BSDROUTINGPARMS entry if you are back-level), you do not need to customise the OSA resources with OSA/SF - although it is recommended for management. When an OSA is used for VTAM/SNA use emulating a 3172, you need to do some customisation using OSA/SF - not difficult but tedious. Some "hardware" definition is always required, of course. - > Already my VTAM is with APPN=YES. The key indication in VTAM that it has - one hopes - gone through the process of being completely enabled for APPN is that the NODETYPE start option has been specified as NN or EN. - > > How did you connect to HIS in the past and can you still use that type of connection? > It was an 802.2 connection to CICS including printer, ... Going on the evidence that you had an XCA major node VTAM definition with a PORT statement with MEDIUM=CSMACD, the 802.2 connection was not to CICS, it was to VTAM. I assume your reference to a printer is to an LU which is defined to CICS as a "printer" - as well as other LUs defined to CICS as "displays" perhaps. It may help to post that VTAM definitions you used, the XCA major node and the relevant PU statement from the switched major node. > but it was done on a different machine (HIS server and the z/OS was on an old machine) I'm going to guess that maybe you had some hardware on the old machine which was or emulated a 3172 but you do not have any equivalent hardware on the new machine. Anyhow, you may like to explain any differences. - > > Not without massive changes elsewhere. > Can you explain me more about the changes I need to make? Yes, and I was in the process of putting together the necessary bits and pieces when this post appeared. It will help if I have the old definitions associated with "MEDIUM=CSMACD". - > > Do you have existing SNA sessions between say CICS and HIS? > No. Now you misunderstand me! By "existing SNA sessions" I meant those you have been using until now supported by the 802.2 connections defined with the XCA major node with MEDIUM=CSMACD and some switched PU and following LU statements. In fact, you did provide some definitions in your first post but it will be best to have the originals before you made any changes. - > There isn't any VTAM specialist :( - and this is the first time I'm > configuring VTAM :). Or HIS - or the Communications Server IP component and TN3270E server? Please be aware that these lists are not a free consultancy. Your management needs to consider that, if a product is needed in order to support the business, it should be properly supported and funding should be available for that. You need to "purchase" some VTAM assistance - or you need to acquire VTAM education and undertake these changes after the education sessions. How is it that you have no VTAM support? Was the only person capable "let go" without a replacement? This is not very clever management of your business. - Now I can get back to preparing the EE-based solution definitions - and finding that 802.2 link service information. - Chris Mason [1] I forget the precise details, but I think if the associated definition entity had been an LU statement in a switched major node and the associated PU had the capability to initiate the connection, "dial out", having a status of CONCT could work in this case. On Thu, 4 Mar 2010 14:06:16 +0200, Matan Cohen <[email protected]> wrote: >> >> Hi chris, > >Thank you for helping me (as you did in the past) > > >> >> I am no longer - for decades now - a CICS specialist but I have seen in a >> recent thread in this list I think which allows CICS to pass print data to >> JES2 >> from where there is a product which uses IP-based protocols to an IP native >> - >> as it were - printer. You may like to research this possibility. >> >We are need to perform this without purchasing any product. > >> >> On the other hand, you can still treat your printer as an SNA device but >> have >> the Communications Server (CS) IP component TN3270E server concatenate >> the SNA session with a TN3270E connection to a TN3270E client 3270 >> emulator which can drive a printer attached to the workstation. >> >base on this IBM answer : >http://www-01.ibm.com/support/docview.wss?uid=swg21380385 , I perform the >following: >I tried to define a terminal(printer) in CICS and then using the TN3270 >define an LU with LUMAP to my network printer IP. > When sending a print to this terminal in the CICS. we got the following >messages in the CICS (although the LU was CONCT): >DFHZC2405 E TVABSAD3 PR01 CSNE Node FTCP0200 not activated. VTAM RETURN > CODE 1000 ((6) Module name: DFHZSYX) > >DFHZC3437 TVABSAD3 PR01 CSNE Node FTCP0200 action taken: NOCREATE CLS DST >ABTASK ABSEND ABRECV ((1) Module name: DFHZNAC) > >DFHZC3462 TVABSAD3 PR01 CSNE Node FTCP0200 session terminated. >((2) Module name: DFHZCLS) >sFHAC2236 TVABSAD3 Transaction PC02 abend PC3D in program IXOPC0 3D term >????. Updates to local recoverable resources will be backed out. >and this message on SYSLOG: >IST663I INIT OTHER REQUEST FAILED, SENSE=08570003 212 >IST664I REAL OLU=ADCD.TVABSAD3 REAL DLU=ADCD.FTCP0200 >IST889I SID = D2DF5F7A1B250B38 >IST264I REQUIRED RESOURCE FTCP0200 NOT ACTIVE > >It seems we must have the LU in activate mode,it means we must perform a >sort of connection to this LU before CICS can send any >print to it. so we decided on using HIS (it is already include in our >enterprise licence). > > > >> >> > Is there no way to perform a pure IP connectivity to my LPAR?[1] >> >> Note that, if the TN3270E server and CICS are running on the same LPAR. >> yes,they are. > >, it >> can be said that you have an IP connection from your workstation supporting >> the printer function and the LPAR where the print data is created. >> >I did'nt completly understood you perhaps i wasn't clear , my question here >was : if i can using emulation to connect directly to tn3270, why in the >HIS server i cant connect to the mainframe in port 23 and get a default LU. >i now i simplisign it more then it is. > >> >> >> >> Does it require ENTERPRISE EXTENDER? >> >> If you need SNA connectivity - in the shape of actual SNA sessions - >> between >> VTAM and HIS, you should plan to use EE since I have seen recently on the >> Microsoft HIS list/group that the only so-called DLC service that Microsoft >> will >> support in the future is their so-called IP-DLC. That means the DLC which >> supports LAN protocols such as Ethernet is going to be dropped: >> >> https://connect.microsoft.com/site66/content/content.aspx? ContentID=10997 >> >> I assume you have worked out that, if you run an SNA session from CICS via >> VTAM to HIS - using an EE logical link, you know how your printing task >> will >> work in that environment. In other words there's some point in my helping >> you >> set up EE. >> >> On the other hand, if this configuration is only to be used for a limited >> time, >> you will always just be using HIS 2006 and it is an option simply to >> connect >> VTAM to HIS over Ethernet with an 802.2 logical link, I believe it may be >> easiest to support your SNA session this way. I believe I have seen some >> samples of a HIS 802.2 connection when I was researching all the problems >> with the Microsoft EE "White Paper". I'll see if I can find it again. It is >> very >> simple on the VTAM side and should be very simple on the HIS side - >> certainly >> compared to EE definitions in both cases. >> >Even if I will use 802.2 It means i need to define a working EE? as you >explained it to me I think I will chose IP-DLC because i need >to implement this for an unlimited time. > >> >> The VTAM and HIS definitions are simple but there may be a complication in >> configuring your OSA, assuming you will be using an OSA. >> >Why should i define the OSA ? is the current definition are not enough? > >> >> Another point that must never be forgotten if you plan to use EE is to >> ensure >> that your VTAM is enabled for APPN. This is not necessarily a trivial task >> and >> could have repercussions for your existing VTAM production environment. >> Adding an 802.2 logical link is almost certainly going to have no >> repercussions. >> >Already my VTAM is with APPN=YES. > >> >> > ... accordingly to the document and member we used in the past for SNA >> server: ... >> >> How did you connect to HIS in the past and can you still use that type of >> connection? >> >is was an 802.2 connection to CICS including printer, but it was done on a >different machine (HIS server and the Z/os was on an old machine) > >> >> > MEDIUM=CSMACD, - If I change it to HPRIP will it work TCP/IP? >> >> Not without massive changes elsewhere. >> >Can you explain me more about the changes I need to make? > >> >> > CPCP=YES I overwrite the CPCP which is now "CPCP=LEASED". Can this >> produce any problems? >> >> Do you have existing SNA sessions between say CICS and HIS? > >No . > >> Does this >> explain the SSCP-independent LU - which should be defined with a CDRSC >> rather than an LU with LOCADDR=0? - and cannot possibly use an USS table!!! >> >In fact the printer - LOCADDR=2 with DLOGMOD=SCS is assumed to identify an >> SSCP-dependent printer LU - cannot possibly use an USS table either - think >> about it! >> >I'm sorry but as I said I'm lack of knowledge in this area. > >> >> The question I ask myself time and again reading this is where is your VTAM >> specialist who should be helping you with this and even perhaps the person >> writing the posts. Such a person would be well aware of my last point! >> >there is'nt any VTAM specialist :( . and this is the first time I'm >configuring VTAM :). > >> >> >> >> Please post again with answers to the above. Meantime, since it is clear >> you >> need sensible samples with sensible explanations, I'll get some sample EE >> definitions ready and a few notes on what the HIS definitions in the "White >> Paper" really mean - to be ready sometime tomorrow. >> >thanks*10 > >> >> Incidentally, as a HIS problem, you should be posting in the HIS list/group >> and/or as an EE problem, you should be posting in the IBMTCP-L list. >> >> Chris Mason >> >> [1] In order to concentrate on the problem posed and not be >> distracted/irritated by the text I am reading, I am obliged to go through >> your >> posts inserting capital letters where they are normally to be found - with >> a >> few other corrections! This explains when I quote you is not precisely what >> you wrote! >> I'm sorry sometimes i don't notice to my writing. > > > >> >> [2] You could set up a CALL=IN PATH statement for security reasons - but >> this is an obscure use of the PATH statement not generally considered all >> that >> useful. >> >I think this wouldn't be necessary ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
