IBM Support

IBM ObjectConnect with IBM AnyNet

Troubleshooting


Problem

This document describes a restriction of ObjectConnect over IBM AnyNet.

Resolving The Problem


=============================================================================
Important Note: Starting in i 7.1, AnyNet (a method used to run SNA communications traffic
over IP) is no longer supported. Users of AnyNet are encouraged to migrate to Enterprise
Extender as a replacement.
=============================================================================

IBM ObjectConnect does not support user-defined local location names. The value as specified in network attributes for default local location must be used (DSPNETA LCLLOCNAME). If, because of the requirements of IBM AnyNet, you have defined your own location names (not matching the Network Attributes), ObjectConnect will not function correctly. ObjectConnect is working as designed. At this time there are no plans to redesign ObjectConnect to meet the AnyNet requirements.

To configure ObjectConnect to run over AnyNet, the mode QSOCCT needs to be set up and the following
communications entry in the Communications subsystem must be defined.

The Communication Entry would be defined as follows:

                       Add Communications Entry (ADDCMNE)                      
                                                                               
Type choices, press Enter.                                                    
                                                                               
Subsystem description              QCMN         Name                          
  Library                          *LIBL        Name, *LIBL, *CURLIB          
Device                             *ALL         Name, generic*, *ALL...      
Remote location                                 Name                          
Job description                    *USRPRF      Name, *USRPRF, *SBSD          
  Library                                       Name, *LIBL, *CURLIB          
Default user profile               *QUSER       Name, *NONE, *SYS            
Mode                               QSOCCT       Name, *ANY                    
Maximum active jobs                *NOMAX       0-1000, *NOMAX

When the above entry is added and the communication entries are displayed (WRKSBSD QCMN, Option 5 to display and Option 8 for the communication entries) the mode QSOCCT would appear as below:

                         Display Communications Entries                        
                                                            System:   RCHASLQL
Subsystem description:   QCMN           Status:   ACTIVE                      
                                                                               
                             
Job                      Default         Max    
Device        Mode        
Description    Library       User          Active    
*ALL          *ANY        *USRPRF                      *SYS          *NOMAX    
*ALL          QBRM        *USRPRF                      QBRMS         *NOMAX    
*ALL          QCASERVR    *USRPRF                      *NONE         *NOMAX    
*ALL          QIJS        *USRPRF                      QIJS          *NOMAX    
*ALL          QPCSUPP     *USRPRF                      *SYS          *NOMAX    
*ALL          QSOCCT      *USRPRF                      QUSER         *NOMAX    
*APPC         QADSM       *USRPRF                      QADSM         *NOMAX    

 *APPC         QSERVER     *USRPRF                      *NONE              0    
*APPC         QSOCCT      *USRPRF                      QUSER         *NOMAX    

Once the communications entry is added, the normal process should be followed for configuring AnyNet. For AnyNet configuration, refer to DCF Technote N1017530.
To link to N1017530 immediately, cick here: IBM AnyNet Configuration (SNA over TCP/IP)

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]

Historical Number

15110408

Document Information

Modified date:
18 December 2019

UID

nas8N1019643