If anyone is after a real solution for Securing there BPCS environments from
BPCS 4.05 to BPCS 6.1, then I would suggest contacting ADSS International in the
Netherlands. (Phone Colin McNaught +31 20 441 76 92) E-mail(ADSSint@ibm.net)
They have developed a solution that will prevent unauthorized access to your
BPCS Database. This includes access via ODBC, FTP, Remote SQL, Window Explorer
and file transfer just to mention a few.
Their solution will allow multiple environments and versions per system.

____________________Reply Separator____________________
Subject:    Re: Command Line Access
Author: Ata510@aol.com
Date:       7/20/99 10:44 PM

In a message dated 7/20/99 3:18:31 PM Central Daylight Time, 
jonleroi@napanet.net writes:

> Command Line Access via BPCS is not something I would want to give to
>  Users. When you have command line access through BPCS you are executing at
>  the SSA group level; the adopted authority. On our machine that is almost
>  as powerful as QSECOFR. The AS/400 is such a friendly machine that a user
>  can prompt to their hearts desire and locate all sorts of interesting
>  commands such as DLTF, PWRDWNSYS, CHGSYSVAL .... 
>  
Whoops!! Forget my previous posting on this topic. Wrong focus of 
information!! If you follow SSA's suggested install model and have all users 
on AS/400 with Group Profile SSA, you are right - no matter how you set up 
SSA user profile, if users have Group Profile SSA and SSA owns the objects, 
there is no keeping them out of BPCS files if they have command line access. 
Beware - command line is not the only worry  -- ODBC is also a problem 
regardless of command line access on OS/400. 

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---
Received: from Kitten.mcs.com ([192.160.127.90]) by ccgate.bausch.com with SMTP
  (IMA Internet Exchange 3.11) id 00038E26; Wed, 21 Jul 1999 00:04:00 -0400
Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by
Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA20733; Tue, 20 Jul 1999 23:02:27
-0500 (CDT)
Received: (from uucp@localhost)
    by uucphost.mcs.net (8.8.8/8.8.8) id XAA10580;
    Tue, 20 Jul 1999 23:02:26 -0500 (CDT)
Received: (from majordom@localhost)
    by midrange.com (8.9.3/8.9.3) id WAA12786
    for bpcs-l-outgoing; Tue, 20 Jul 1999 22:30:04 -0500
Received: (from uucp@localhost)
    by midrange.com (8.9.3/8.9.3) with UUCP id WAA12780
    for BPCS-L@midrange.com; Tue, 20 Jul 1999 22:17:44 -0500
From: Ata510@aol.com
Received: from imo13.mx.aol.com (imo13.mx.aol.com [198.81.17.3])
    by uucphost.mcs.net (8.8.8/8.8.8) with ESMTP id WAA09297
    for <BPCS-L@midrange.com>; Tue, 20 Jul 1999 22:17:20 -0500 (CDT)
Received: from Ata510@aol.com
    by imo13.mx.aol.com (IMOv20.25) id iUVFa27989 (538)
     for <BPCS-L@midrange.com>; Tue, 20 Jul 1999 22:44:09 -0400 (EDT)
Message-ID: <b3eef911.24c68df8@aol.com>
Date: Tue, 20 Jul 1999 22:44:08 EDT
Subject: Re: Command Line Access
To: BPCS-L@midrange.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 4.0 for Windows 95 sub 13
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


This thread ...


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

This mailing list archive is Copyright 1997-2019 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].