|
Graham, I think your original idea of copying source and disabling fields with PR and ND attributes is going to be the easiest and most reliable means to accomplish your goals. A couple of gotchas to look out for..... Make sure you don't reorder or remove any fields, including indicators (unless the screens already used INDARA) as that will change your buffers and make the screens incompatible with your applications. Compile the DSPFs with level check *no (though I'm not sure if the format level ids will change if all you do is change attributes). hth, Eric DeLong -----Original Message----- From: Smith, Graham (EBM) [mailto:Graham_SmithEBM@heinz.co.uk] Sent: Tuesday, April 24, 2001 7:11 AM To: 'MIDRANGE-L@midrange.com' Subject: Altering field display attributes by user without touching DSPF s ource 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-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.