Re: SNA Connection Problem

From: aelmanso (member46506_at_dbforums.com)
Date: 10/31/03

Date: Fri, 31 Oct 2003 04:47:42 -0500

Hi,

We face the same problem. Have you manage to solve it? Thanks

Originally posted by Pjg

> Our application is run on a Risc 6000(43p/140) server, with AIX 4.2.1,

> SNA 3.1.2 and C as the programming language. The application receives

> data and passes the data to a Gateway Host. We have problems when the

> application looks fine but it is not sending data. There are no

> errors on the Risc box. We have issued the SNA failure trace and

> checked the IBM error report (errpt -a | pg) and nothing shows up.

> The customer has to stop and start the application to get the data to

> start sending to the Gateway Host. According to the customer site,

> they are not getting any failure messages on their network either.

> There are 3 sites that are attached to the Risc 6000 via a WAN. The

> application worked fine at all 3 sites until they switched to Data

> Link Switching(DLSW). We don't know if it is a timing issue with the

> WAN or our application on the Risc. If it is a timing problem we need

> to know what parameters need to be changed in the SNA profile. The

> application is running on 72 sites without any problems. All sites are

> running DLSW.

> What does the limited_resource_timeout parameter do? Would this be

> something to consider changing? Here is how it is set now on all of

> our Risc's:

> sna:

> prof_name = "sna"

> max_sessions = 200

> max_conversations = 200

> restart_action = once

> dynamic_inbound_partner_lu_definitions_allowed = yes

> standard_output_device = "/dev/console"

> standard_error_device = "/var/sna/sna.stderr"

> nmvt_action_when_no_nmvt_process = reject

> trusted_group_ids = {system}

> sense_detail_level = specific

> start_snmp_subagent = no

> limited_resource_timeout = no

> limited_resource_timeout_value = 15

> comments = ""

> Any suggestions would be much appreciated.

> Thanks,

PJG

--
Posted via http://dbforums.com