Configure ObjectConnect and AnyNet

Tim Shafar

August 31 2005

Table of Contents:

Set the Network Attributes to Allow AnyNet Support

Configure the Host Table Entries

Add the following host entry to the IP.

Create the APPC Controller

For the HOST system

For the TARGET system

Create the remote configuration list entry on the source system

Test with:

Items to check if Testing fails:

Objects to double check if having issues:

Diagram A:

Set the Network Attributes to Allow AnyNet Support

DSPNETA Allow AnyNet support . . . . . . . . . . . . . . : *NO

If *YES, then go to “Configure the Host Table Entries”.

If *No, issue this command: CHGNETA ALWANYNET(*YES)

Configure the Host Table Entries

Add the following host entry to the IP.

CHGTCP <<ENTER>>

10 <<ENTER>>

If there is already a host entry do the following:

Take option 2 on the IP address you need to modify.

If there NOT a host entry then add one with option 1 and then continue.

Add the following entry to the IP address: (SYSTEM NAME).APPN.SNA.IBM.COM

Repeat this step for each system you need to communicate with.

Create the APPC Controller

For the HOST system

CRTCTLAPPC CTLD(TOSYS_1) LINKTYPE(*ANYNW) RMTCPNAME(ANYNETA1) TEXT('Anynet link to ‘system name')

 The CTLD Value is the name I used to identify the controller. You can make this any value that works for you.

 RMTCPNAME is the value I used to identify the Control Point Name. You can make this any value that works for you.

 RMTCPNAME MUST BE THE SAME FOR THE TARGET AND THE HOST SYSTEM.

 If configuring for communications to multiple system the RMTCPNAME must also be unique between host and each target system. See Diagram “A”.

For the TARGET system

CRTCTLAPPC CTLD(TOSYS_A) LINKTYPE(*ANYNW) RMTCPNAME(ANYNETA1) TEXT('Anynet link to ‘system name')

 The CTLD Value is the name I used to identify the controller

 RMTCPNAME is the value I used to identify the Control Point Name.

 RMTCPNAME MUST BE THE SAME FOR THE TARGET AND THE HOST SYSTEM.

 If configuring for communications to multiple system the RMTCPNAME must also be unique between host and each target system. See Diagram “A”.

Create the remote configuration list entry on the source system

WRKCFGL <<ENTER>>

If there is already a list named “QAPPNRMT then go to “On the host system add the following entries for each target system”

If the list QAPPNRMT does not exist then create the list QAPPNRMT

 CRTCFGL TYPE(*APPNRMT) TEXT('Anynet TCP Connection list') <<ENTER>>

On the host system add the following entries for the target system.

On the target system add the following entries for the host system.

If the list ‘QAPPNRMT’ already exists, make these modifications:

 Remote Location: On the target system issue the command DSPNETA. This is value on your host system for this parameter.

 Remote Network ID: Is always APPN.

 Local Location: On the host system issue the command DSPNETA and use this value.

 Remote Control Point: Is the value that was used when creating the controller in step “Create APPC Controller.”

 Control Point Net ID: Is always APPN

 For multiple system: See diagram “A”

 Secure Loc: *NO will require a Signon to the new system. *YES will allow an automatic Signon.

Test with:

STRPASTHR (Remote System Name) <<ENTER>>

 If successful you will get a Sign on Screen.

Items to check if Testing fails:

Error stating it can’t find a route

 HOST Table should have a route to target system. (SYSTEM NAME).APPN.SNA.IBM.COM. You can test this by issuing a ping to “(SYSTEM NAME).APPN.SNA.IBM.COM.”

 Double check the configuration list for errors and that a route exists.

 Double check the configuration list to ensure the RMTCPNAME matches the name in the controller and that they are all unique between the host and the target system.

 Check the controller to ensure it’s status is ‘Varied On”

Error the ‘Controller XXX Vary Configuration failed

 The remote control point name may be duplicated or miss typed.

Objects to double check if having issues:

The unique controller should be:

 Created and varied on.

 The RMTCPNAME must match what is in the Configuration List. When testing, if you get a routing error, check the configurations list and the host table entry.

WRKTCPSTS Option(*CNN)

There should be two jobs named APPCove one with a status of *UDP and the other with a status of *LISTEN.

The subsystem QSYSWORK must have the job QAPPCTCP running and active.

Diagram A:

Use for example of configuring 1 Host to 2 Target System

Configuration List for 1 Host system 2 Target Systems
Host System System: A	Target System: System 1
QAPPNRMT List Remote Location System1 Remote Net ID APPN Local Location SystemA Remote Ctl Name ANYNETA1 Control Pnt Net ID APPN Secure Loc *NO	QAPPNRMT List Remote location SystemA Remote Net ID APPN Local Location System 1 Remote Ctl Name ANYNETA1 Control Pnt Net ID APPN Secure Loc *NO
APPC Controller	APPC Controller
APPC Controller TOSYS_1 RMTCPNAME ANYNETA1	APPC Controller TOSYS_A RMTCPNAME ANYNETA1

Host System: System A	Target System: System 2
System A Remote Location System2 Remote Net ID APPN Local Location SystemA Remote Ctl Name ANYNETA2 Control Pnt Net ID APPN Secure Loc *NO	System 2 Remote location SystemA Remote Net ID APPN Local Location System 1 Remote Ctl Name ANYNETA2 Control Pnt Net ID APPN Secure Loc *NO
APPC Controller	APPC Controller
APPC Controller TOSYS_2 RMTCPNAME ANYNETA2	APPC Controller TOSYS_A RMTCPNAME ANYNETA2