....If I use a WRITE header followed by an EXFMT main screen, only the main screen is displayed and none of the file-level keywords from the header are active.
Use the OVERLAY keyword on the EXFMT screen, and watch your header record remain:
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzakc%2Frzakcmstoverla.htm
I have also seen advice to designate a header field in your display file and customize it in your program in order to allow a more standardized header, but I don't know how (or if) it can be used with file-level keywords and allowed function keys?
Probably header fields (plural). Most of mine show a file/screen name upper left, application name in the middle, date and time upper right, a subtitle on the 2nd line centered. Go by shop standards, and/or clone somebody's DDS code and customize to your specifications.
If this is not possible, how is screen standardization usually handled?
Shops vary on this one, but almost all of them are pretty definite about that. If they don't seem to, or it's a tiny shop, they might not, in which case I have usually simply tried to find what most of the screens already look like to the users and take it from there.
(Would that more shops were pushing for Web interfaces)..
Alan Cassidy
At Caledonia Financial Services
acassidy@xxxxxxxxxxxxxx
954-693-0000 ext. 3433 - Direct phone
786-380-9236 - Mobile phone
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sarah Kemp
Sent: Tuesday, January 28, 2014 5:38 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Common Display File (Header + File-level Keywords)
I learning about RPG and DDS for screens and I am trying to determine if there is some method of including or referencing one DDS screen inside of another. What I want to be able to do is create a "common" display file that has, for instance, the company name and the date, and includes some file-level keywords and allowed function keys (INDARA, CA03, etc.). Then, ideally, I would be able to create program-specific screen content in a separate file without having to redefine the common function keys, header information, and file-level keywords.
Is there a method of including DDS source with something like a /copy? Or can I use two display files in one RPG program and have their allowed keys and keywords both active at the same time? I have tried using two in one program, but I can only get them both to display by using EXFMT rather than WRITE for the header file, which means control needs to be returned before the main screen is written. If I use a WRITE header followed by an EXFMT main screen, only the main screen is displayed and none of the file-level keywords from the header are active.
I have also seen advice to designate a header field in your display file and customize it in your program in order to allow a more standardized header, but I don't know how (or if) it can be used with file-level keywords and allowed function keys?
If this is not possible, how is screen standardization usually handled?
Thank you,
Sarah
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--------------------------------------------------------------------------------
Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------------------
midrange.com
