command line access security ~ (Response #2 of 2)

Dear Vincent, here's our response to your second issue: 

       Security breach concerns raised by giving 
       command line access to a BPCS user

"By Invitation Only" software grants user access to OS/400 
commands while closing the door on headaches associated 
with command line access. A specific user can be granted 
authority to execute selected OS/400 commands without 
giving that user command line authority. 

Here's how a security officer would set it up for a given 
BPCS user ... let's call her Michelle:

   Step A - Turn off command line access for Michelle
                  at the OS/400 user security level. 

   Step B - Navigate "By Invitation Only" menus to the 
                  'Work with Individual Commands' option.

   Step C - The security officer can then select which 
                  specific OS/400 commands should be 
                  authorized for access by Michelle. 
                      Note: any subset of the 1,800+ iSeries 
                                 commands can be selected. Even 
                                 custom commands developed for
                                 Michelle's job function can be 
                                 selected using this approach.
                              
   Step D - Visit Michelle and tell here she's set to go. She 
                  can now launch her authorized OS/400 commands
                  from By Invitation Only's 'User Commands' menu. 

A parallel "By Invitation Only" process is available to 
grant user authority to execute selected BPCS programs. 
   
"By Invitation Only" software replaces BPCS' clunky user 
profile maintenance process. It provides a due diligence 
process that enables prompt and comprehensive responses
to audit challenges. That's a huge improvement relative to the 
                     ' SECURITY BY OBSCURITY ' 
approach packaged with versions 4.x - 8.x of vanilla BPCS.
    http://www.unbeatenpathintl.com/BIOnly-start/source/1.html  


Here's some other clever/affordable "Bells & Whistles" for 
BPCS software products: 
   http://www.unbeatenpathintl.com/bells/source/1.html    

Warm regards and peace to you,  

Milt Habeck
Unbeaten Path International

Toll free North America:  (888) 874-8008
International voice: (262) 681-3151
mhabeck@xxxxxxxxxx   
www.unbeatenpathintl.com    



+++++++  +++++++  +++++++  +++++++  +++++++  +++++++
From: Vincent Dsouza
To: bpcs-l@xxxxxxxxxxxx
Sent: Wednesday, April 28, 2004 12:10 AM
Subject: Print reports > 132 chr

Hi,

We are running  BPCS ver 6.02 on 820 machine, The max report 
width setup in 'system control data area'  (SYS041D) is 132 chrs
We have developed many in-house queries where the report width
exceeds 132 columns. All queries are run from CL programs. When
these queries are run from the menu, the report width setup in 
SYS041D overrides the report width of these queries and the output
gets truncated to 132 character. When the CL(query) program is 
executed from command line the report width in SYS041D is 
ignored and we are able to produce reports greater than 132
columns.

By giving the user access to command line we give rise to an 
security breach, by granting the user rights to run any program 
from command line like (ACR100D1, INV100 et etc).

How can we print reports > 132 chrs from the menu without having to
compromise on the width of these reports and access to command line.
Does anyone have a solution to this problem ?.

Rgds
Vincent D'souza
Jotun UAE LTD LLC
P.O. Box 3671
Dubai, UAE.