QUSER in QCMN

[Rob Berendt <rob@xxxxxxxxx>]

We are in the process of tightening up our library security.  
Basically we are changing *PUBLIC from *CHANGE to *EXCLUDE.  
We have some cross application code that we realize will have 
to adopt authority.  That's no big deal.  The problem we are 
having is with remote 400's.  When they use DDM the user doesn't 
appear as the name of the person on the remote system, it 
appears as QUSER.  And I don't want to open the objects up to 
QUSER.  I called IBM support on this and they gave a suggestion 
and I want to bounce it off of y'all.

IBM is suggesting the following:
I.  For DDM using SNA do the following:
  A.  WRKCFGL
  B.  CRTCFGL TYPE(*APPNRMT) APPNRMTE((REMOT400 *NETATR *NETATR *NONE *NETATR 
*NONE *YES))
    1.  The main item in question is:
        Secure location  . . . . . . . > *YES          *YES, *NO, *VFYENCPWD
We have 13 AS/400's.  All of our production machines list the 
development machine as a secure location.  And, yes, when I do 
DDM from the development machine to the production machines the 
job's show up under my name.  Password doesn't even have to 
match.  My question is this.  Since we have tight control over 
userid's, therefore RALPH on both machines is always the same 
RALPH, then do you consider this a problem?

II.  For DDM using TCP/IP do the following:
  A,  CHGDDMTCPA PWDRQD(*NO)
  B.  ADDSVRAUTE USRPRF(*CURRENT) SERVER(QDDMSERVER)
  C.  CHGSYSVAL SYSVAL(QRETSVRSEC) VALUE('1')
Do you see a problem with this?
+---
| 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
+---