HP3000-L Archives

December 2000, Week 3

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:
JIM McINTOSH <[log in to unmask]>
Reply To:
JIM McINTOSH <[log in to unmask]>
Date:
Wed, 20 Dec 2000 14:01:21 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Happy Holidays.

We use SNA to connect to a UNISYS box.  We have multiple nodes on multiple
machines.  All the nodes appear to be working for the most part as they have
for 12+ years.  We introduced a new process that calls the existing
subroutine that utilizes the SNA connection and are experiencing a strange
error.  On some nodes, the new process (running under a new account, by the
way), encounters the following error:

"Program not authorized to use this security class.  Add your program to the
PGMLIST for the security class, or use another security class that is
already configured properly for use with your program."

We have reviewed the configuration of the nodes in NM manager and can find
nothing that would cause this error.  That is to say, the nodes are all
configured to allow all programs @[log in to unmask]  Indeed, the new process works great
on some of the nodes.  Thank goodness, the condition is at least consistent.
The new process always works on the same nodes and always fails on the same
nodes.

We have used TTSSON.PUB.SYS to verify that the nodes are indeed available
and working.  This is consistent with the results of the existing programs
that are able to use all the nodes.

All things point a configuration problem, but we cannot find it.  Does
anyone have a suggestion?  Thanks in advance.

Jim McIntosh

ATOM RSS1 RSS2