HP3000-L Archives

February 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stoney Ratliff <[log in to unmask]>
Reply To:
Stoney Ratliff <[log in to unmask]>
Date:
Thu, 8 Feb 2001 16:41:42 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
=================Original question==================================
Those of you hosting AMISYS on your HP3K may be able
to relate to this question challenge.

Are you at a site which has experienced session timeouts
while the user was logged in and active?  Our users log-on
through a "Reflections" emulation.  All users are familiar with
the timing out which occurs as a result of not using their
session.  Yet a few (small percentage) are experiencing ses-
sion disconnects while working and receive the same logoff
message you would receive if logging off manually.  To date,
there are no identifiable similarties between the few experienc-
ing problems.  One or two are having to work at other terminals
when the problem is severe for them.

The connection scenario is standard:  NT4 workstation on
standard NT network using TCP/IP to connect to its IP
address.  Identical connect path for our OS390 users as well
who are not experiencing this problem.

Field technicians who have worked the issue are quite confi-
dent it is not a hardware problem.  AMISYS supervisors who
are managing dozens upon dozens of data-entry people are
quite confident it is not an AMISYS problem.  Softwares have
been installed and reinstalled.  Drives have been re-imaged, etc.

Does anything come to mind to you from a previous experience
of your own which might relate?

TIA,

Doug Hensley
Baton Rouge
(225) 381-6728
(225) 381-6551 FAX
====================================================================
+++++++++++++++++++++Items to check+++++++++++++++++++++++++++
You did not say what error codes the clients are getting
when the session is terminated. Some suggestions.

Check some of the network configuration settings on the HP3000.
   1) Execute this command when users have been logged off
      during a session.

 mpe:NETTOOL.NET.SYS;INFO="RESOURCE;DISPLAY;QUIT"

        Check your INBOUND BUF POOL, for smiley face.
        If HIGH mark is close to MAX then change the number of buffers.

        mpe: NMMGR
  OPEN CONFIG
  NS
  UNGUIDED CONFIG
  Go to NETXPORT
  Go to GLOBAL
   Modify Inbound Buffer Pool here.
   Use F7 key to check help for allowed values.
   Once modified, Save Data and validate NETXPORT.
   A full stop and restart of the network will
   will apply changes.

   2) Check vtservers = mpe:NSCONTROL STATUS=SERVERS
 If max vtservers are low and it shows you are running
 near the max change it. If command above, shows max 300
        and you are running near the max and you want to increase to 400.
        Use this command.

            mpe:NSCONTROL SERVER=VTSERVER,0,400

        VT sessions use more HP3000 System resources.
 Telnet sessions via JINETD less inpact on HP3000.
        May want to change.

   3) Check that you have the latest Telnet ARPA and NS patches on the HP3K.

Hope this helps,
Stoney Ratliff
R&R Consulting

ATOM RSS1 RSS2