× 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: RE: Allowing users to do RCVNETF without granting authority to CMD RCVNETF
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Wed, 14 Jan 1998 17:50:32 -0600

You should only need to enrol in the system directory the user the file
is being sent to (which is why we had a dummy user/directory entry for a
user called FILERCVR SYSTEMxx in our directory - we always sent to that
so it didn't matter if someone changes jobs), and the user that is
running the job to receive the file.  This user would need *ALLOBJ
authority, and could be this same FILERCVR id but doesn't have to be.
As mentioned in other posts, this FILERCVR id could have *ALLOBJ
authority, but password *NONE.  You would submit the job to receive the
file to run under this user profile.

... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com


        -----Original Message-----
        From:   Chuck Lewis [SMTP:clewis@iquest.net]
        Sent:   Wednesday, January 14, 1998 6:25 PM
        To:     MIDRANGE-L@midrange.com
        Subject:        Re: Allowing users to do RCVNETF without
granting authority to     CMD RCVNETF

        Pete Hall wrote:

        <That sure sounds like the old office security where you could
specify
        the users that were allowed to process mail for you. I'd start
looking
        in the office enrollment stuff.>

        I was TRYING to avoid having the user(s) enrolled in the
Directory (thus
        the CLP being owned by QSECOFR) so that we don't have to worry
about
        whoever has authorization to this menu option being enrolled.
That might
        be obvious when we set this up the first time, but when those
people
        quit and someone else replaces them and needs to do the same
functions,
        we have to be concerned with the Directory (we don't as a
general rule,
        enroll users in the Directory since we do not use office and
MOST users
        are not using file download/upload programs...)

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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.