Matan

About the most useful observation in your post is your suspicion that the 
Microsoft HIS "White Paper" concerning setting up Enterprise Extender (EE) - 
aka IP-DLC - between HIS and VTAM is unreliable. It is just about the most 
terrible pretence at a description of VTAM definitions I know about and its 
presentation of the part about which the authors should know something, 
namely the definition of their IP-DLC, is very distorted.

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.

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.

>  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, 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. 

>  Is there no way that HIS can connect to my LPAR and get an LU from my 
defaults LU defining in TCP/IP.

Actually I don't understand at all what you are asking here - but it may not 
matter finally.

> 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.

The VTAM and HIS definitions are simple but there may be a complication in 
configuring your OSA, assuming you will be using an OSA.

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.

> ... 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?

>  MEDIUM=CSMACD, - If I change it to HPRIP will it work TCP/IP?

Not without massive changes elsewhere.

>  CPCP=YES I overwrite the CPCP which is now "CPCP=LEASED". Can this 
produce any problems?

This seems to suggest that you have already enabled APPN. However, 
CPCP=LEASED is a rather odd VTAM start option, the thinking behind the 
default for which is rather out of date - and was out of date when it 
was "invented"! You are right that CPCP=YES is a better start option value 
since it includes logically switched resources which is the case for *all* 
logical 
links these days and has been for a long time. Only antique SDLC lines can be 
non-switched/leased (or X.25 NPSI PVCs, equally antique - and obscure!).

> ECPATH50 PATH  DIALNO=0104000000000050, ... Should this be the MAC 
address of the SNA server?

Absolutely not. In fact you should probably rely on the HIS side to make 
contact which will mean you do not need a CALL=OUT PATH statement at all.
[2]

Do you have existing SNA sessions between say CICS and HIS? 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!

Activating PU statements in a switched major node is most unlikely to be 
disruptive to a production environment.

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!

>If I will activate this members will I be able to connect to the LPAR form the 
HIS server?

No.

> Or there is anything I'm missing?

Lots!

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.

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!

[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.

On Wed, 3 Mar 2010 20:50:59 +0200, Matan Cohen 
<[email protected]> wrote:

>hi,
>i'm in the middle of configuring an HIS server 2006 and there are several
>question on my mind ( i lack of knowledge in communication).
>the reason we configure an HIS its because we trying to perform a CICS print
>to a TCP\IP printer by defining a terminal(printer).
>
>-is there no way to perform a pure ip connectivity to my lpar? why i must
>define XCA to vtam ?
>-is there no way that HIS can connect to to my lpar and get a lu from my
>defaults lu defining in tcpip.
>
>I read this document but i wonder about how much it is accurate :
>http://www.microsoft.com/downloads/details.aspx?
displaylang=en&FamilyID=86d6011a-3396-4c36-b4b1-af7f4d80a099
>
>-is there any a similar document for configuring an HIS using DLC 802.2?
>does it require an ENTERPRISE EXTENDER ?
>
>
>when doing  'D NET,EE' i got this message . :
>IST2045I ENTERPRISE EXTENDER XCA MAJOR NODE NOT ACTIVE -
>i have already have 3 XCA major node what make an XCA major node to an
> ENTERPRISE EXTENDER XCA MAJOR?
>
>so i started redefine the follow member,   accordingly to the document and
> member we used in the past for SNA server
>:
>i created the follow member in user.vtamlst with the following:
>
>
>member XCAEE: i have already have an 3 XCA major node can  defining this 
can
>cause a problem.
> 
**********************************************************
************
> ***  MEMBER: XCAEE
> 
**********************************************************
************
> ***        EXTERNAL COMMUNICATIONS ADAPTER  (3172 ETHERNET  )      
***
> ***                 (USING THE AWS3172 DRIVER)                     ***
> 
**********************************************************
************
> XCA2E    VBUILD TYPE=XCA
> *
> XCA2PTE  PORT  ADAPNO=1,               MPTS ADAPTER NUMBER             *
>                CUADDR=E23,             LAN3172 DEVICE MAP ADDRESS      *
>                *MEDIUM=CSMACD, *          if i will change it to HPRIP will
>it work tcpip
>                SAPADDR=4,              COMM. MANAGER USES SAP=4        *
>                TIMER=120
> ***********************************
> * LAN (PU2/2.1) SWITCHED RESOURCES
> ***********************************
> XCA2GP3E GROUP DIAL=YES,               GROUP POINTED BY LAN PATH DEF.  
*
>                ANSWER=ON,                                              *
>                CALL=INOUT,                                             *
>                ISTATUS=ACTIVE,                                         *
>                AUTOGEN=(55,A)
>
>member IPPRNT :
>
>IPPRNT VBUILD TYPE=SWNET,MAXGRP=1,MAXNO=99
>PUPRNT   PU    ADDR=01,                NT LAN SERVER                   *
>               DISCNT=NO,              DISCONNECT FACILITY             *
>               DYNLU=YES,              DYNAMIC ALLOCATION OF CDRSC     *
>               IDBLK=05D,              DEVICE TYPE                     *
>               IDNUM=00600,            DEVICE SERIAL NUMBER            *
>               CPNAME=CPPRNT,          CONTROL POINT NAME              *
>               MAXPATH=1,              DIAL-OUT PATHS TO PHYSICAL UNIT *
>               PUTYPE=2
>               *CPCP**=YES    *  i'm overwrite the CPCP which is now   "CPCP
>    = LEASED "   is this can preduce any problem?
>
>ECPATH50 *PATH  **DIALNO**=0104000000000050,  DIAL NUMBER (INC. 
MAC **ADDR**.)
> **  is this should be the mac address of the SNA server?
>               GRPNM=XCA2GP3E          LAN GROUP NAME (SEE XCA02)
>ECLUSYS1 LU    LOCADDR=0,              FOR INDEPENDENT LU MUST BE 0    *
>               DLOGMOD=GUIMODE,        LOGON MODE TABLE ENTRY          *
>               MODETAB=GUILU62M,       LOGON MODE TABLE NAME           *
>               ISTATUS=ACTIVE,         INITIAL STATUS                  *
>               USSTAB=SDLUSSTR         USS TABLE NAME
>CPRT0001 LU    LOCADDR=2,              LOGICAL UNIT LOCAL ADDRESS      *
>               DLOGMOD=SCS,            LOGON MODE TABLE ENTRY          *
>               MODETAB=ISTINCLM,       LOGON MODE TABLE NAME           *
>               ISTATUS=ACTIVE,         INITIAL STATUS                  *
>               USSTAB=SDLUSSTR         USS TABLE NAME
>
>
>
> i didn't do any act for this member from the fear it might cause some
>problem because of my lack of knowledge and the fact it is a production?
>if i will activate this members will i be able to connect to the lpar form
>the HIS server? or there is anything i'm missing?
>
>
>--
>best regards,
>matan cohen
>MF System Administrator.

----------------------------------------------------------------------
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

Reply via email to