× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: DRDA security question
  • From: David Brown <davbrown@xxxxxxxxxx>
  • Date: Fri, 12 Feb 1999 13:47:51 -0800 (PST)


Hi - I am posting this for a colleague:

I am trying to set up a connection to DB2 for a pair of LU's.  One will be
required to provide security information while the other is a "trusted" LU.
I have checked the DRDA Connectivity guide and it say I should be able to
this. My problem is that the "trusted" LU is being rejected as not having
sent the appropriate SECCHK DRDA code point.  (reason code 00D31050).  The
reason code says that DRDA Security Level 5 is designated.  Is there a way
to ensure that I'm not using Security Level 5 for the trusted LU?  A
parameter perhaps, ZPARM?

I have modified the APPLID to use SECACPT to ALREADYV and VERIFY to NONE.  I
have the following settings in my SYSLUNAMES:

LUNAME    SYSMODENAME SEC-IN  SEC-OUT ENCRYPT  MODESELECT  USERNAME
LUTRUST   IBMRDB2     A       A       N        N

I have created RACF LU pairings with security required = NONE.  The only
thing I can think of is that I still have PASSWORD = keyword in my BSDS.  If
I take that out then I can't implement the level of security for my
non-trusted LU.  Does anyone have any ideas?

----
David Brown
StarQuest, Berkeley
davbrown@netcom.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.