× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Be careful here.  Unless you have a very small or very new system, odds
are good that your Network Attributes are referenced in other places and
some things may not work after the change.

That said . . . On the remote system, you reference your 'local control
point name' on the APPC controller description.  This is the RMTCPNAME
parameter of the CRTCTLAPPC or CHGCTLAPPC commands.

Also on the remote system, you reference your 'default local location'
on the APPC device description.  This is the RMTLOCNAME parameter on the
CRTDEVAPPC or CHGDEVAPPC commands.

Under normal circumstances, you specify the 'remote location name' when
you issue the STRPASTHR command.  I don't believe that there is a
requirement that your location names match the Network Attributes.
There is a requirement that the remote and local location names match on
the respective device descriptions.  As a first cut, I would leave your
Network Attributes alone and recreate your APPC device descriptions,
substituting CUSTNAME for S123456 in the location name parameters.  This
would allow you to specify CUSTNAME as a target for your session without
encountering the potentially nasty side-effects of a global change in
your Network Attributes.  You will not be able to change the parameters
on the device descriptions, you will need to delete and recreate them.
Perhaps use the RTVCFGSRC command, and then change the relevant
parameter on both systems.

Regards,
Andy Nolen-Parkhouse


> On Behalf Of tomh@simas.com
> Subject: STRPASTHR question
>
> Here's a screen-shot from a customer's DSPNETA:
>
>                            Display Network Attributes
>                                                              System:
> S123456
>  Current system name  . . . . . . . . . . . . . . :   S123456
>    Pending system name  . . . . . . . . . . . . . :
>  Local network ID . . . . . . . . . . . . . . . . :   APPN
>  Local control point name . . . . . . . . . . . . :   S123456
>  Default local location . . . . . . . . . . . . . :   S123456
>  Default mode . . . . . . . . . . . . . . . . . . :   BLANK
>  APPN node type . . . . . . . . . . . . . . . . . :   *NETNODE
>  Data compression . . . . . . . . . . . . . . . . :   *NONE
>  Intermediate data compression  . . . . . . . . . :   *NONE
>  Maximum number of intermediate sessions  . . . . :   200
>  Route addition resistance  . . . . . . . . . . . :   128
>  Server network ID/control point name . . . . . . :   *LCLNETID   *ANY
>
>
> I've set up the line, controller, and device descriptions to allow
> pass-thru using the command STRPASTHR S123456.  I'd like to be use
> STRPASTHR CUSTNAME instead.  How do I change my configuration to allow
me
> to do that?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.