|
midrange.com
I know you don't want to modify the code, (being BPCS shop also, I
understand). I am just saying that the 400 actually does support true
field level security. There are two methods of doing this. The first
method, available day 1 of OS/400, is to not allow anyone to directly
access the physical. And in your logicals only select the fields you need.
If you need specifics, reply.
The other method came out around V4R5 and this allows you to set up field
level security directly on your physicals. Again, if you need specifics,
reply.
Rob Berendt
==================
Remember the Cole!
"Smith, Graham
(EBM)" To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
<Graham_SmithEBM@he cc:
inz.co.uk> Subject: Altering field
display attributes by user without touching
Sent by: DSPF s ource
owner-midrange-l@mi
drange.com
04/24/01 07:11 AM
Please respond to
MIDRANGE-L
We're running a ERP package, BPCS as it happens, and the company is after
some form of field level security by user.
They're basically looking to protect or non-display specific fields.
We've identified 50 odd programs with affected display files.
We don't want to go and modify the program code.
We've considered copying the dspf source and creating a set of Display
files in a separate library with the particular fields DDS attributes set
to
PR/ND and loading this library higher in the library list than the std DSPF
based on user.
Is there any way of grabbing the buffer or bit stream sent to the display
(5250 emulation used in all cases I believe) and altering the attribute
settings at that point? If so how and what skill set would we need to
acheive this?
Thanks in advance
Regards
Graham Smith
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
EBM Project
Hayes Park,
Telephone + 44 208 848 2585
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
**********************************************************************
This email and any attachments are confidential and solely
for the use of the intended recipient. They may contain
material protected by legal professional or other privilege.
If you are not the intended recipient or the person responsible
for delivering to the intended recipient, you are not authorised
to and must not disclose, copy, distribute or retain this email
or its attachments. Although this email and its attachments
are believed to be free of any virus or other defect, it is the
responsibility of the recipient to ensure that they are virus free
and no responsibility is accepted by the company for any
loss or damage arising from receipt or use thereof.
**********************************************************************
+---
| 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
+---
+---
| 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 mailing list archive is Copyright 1997-2025 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.
