×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have a program and a display file. A screen field, say CCCCCCC, is defined in the display header format as 7char. The same field is defined in the program DS as 7char, initialized to a certain value.
I am working on a project which aims to increase the length of field C from 7 to 8 so I changed and recompiled the program as well as the display file. I forgot to deploy the display file and went on to test the new changes which means I am now using the latest program(8char fieldC) over an old display file (7char fieldC). Initially, I assumed it will just drop/truncate the last character. I was wrong. The last character of field C was placed in the next field and the rest of the fields in the screen format moved a character to the right as seen below.
I know it is best practice to deploy both but given this instance, I'd like to know if this is the correct behavior. If so, are there workarounds aside from deploying the latest display file?
Before
FldA FldB FldC FldD FldE
PGMNM ENQ XXXXXXX TITLE CCYYMMDD <-- Data value
After
FldA FldB FldC FldD FldE
PGMNM ENQ XXXXXXX XTITL ECCYYMMD <-- Data value
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
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.