Steve,

... which all means that, in your CONFIGxx member, you must specify the TRL
member names before any major nodes which will need to refer to them. This
then is probably what Abdullah needs to do.

This same principle can also be applied to similar relationships such as
model definitions and switched major nodes before NCPs and XCA major nodes
are activated. I once had to sort out a problem where someone had
unfortunately been copying some samples - from a redbook - without
understanding what the operands did - always a big risk. The sample had
DYNPU=YES and the poor guy couldn't work out why connections appeared to
work but no LUs got activated - or something like that - it was some years
ago. Putting the switched major nodes in CONFIGxx in front of the NCP fixed
the problem - but then so would removing DYNPU=YES if you didn't really need
it.

The sad thing is that the offending samples got copied and copied into a
number of redbooks on similar topics - and it may still be happening.

Oh, ... and well spotted. On this occasion Abdullah has given too much
information. Before your reply appeared I was going to ask him for more
details of what was in his major nodes. I was trying to work out what role
taking the "backup" might play. Actually it's all about simply starting
VTAM.

Chris Mason

----- Original Message ----- 
From: "Steve Wolf" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Wednesday, 31 May, 2006 7:20 PM
Subject: Re: APPN connection


> Abdullah,
>
> I has a similar problem setting up a APPN connection.  I discovered that
> the VTAM Node with the TRL definition must be activated before the Node
for
> the MPC definition.
>
> I hope this helps,
>
> Regards,
> Steve

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