×
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.
Hello Greg,
Am 11.08.2023 um 14:42 schrieb Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>:
In my experience, I expected these fields to get updated with the system date/time when the record was created... But my experience is with RPG and SQL. And I suspect that NEITHER is used to populate the DB2 file.
I think this is what the "default" thing is about. I don't know anything about Tli, but if they use some magic to allow you to expand the file without the *PGM complaining about a failing level check, I guess you're halfways there.
From what I understand, it should work like that: If they pass a buffer to the WRITE call which is smaller than the buffer + your defined fields, those fields don't get any content from the application. As long as you didn't define a DFT() in DDS, the described behavior of the manuals should kick in and the current date/time should be placed in the buffer by the OS prior to the creation of a new record happens.
I admit this is highly theoretical, but based on some of my own experiences with PFs and timestamp fields.
:wq! PoC
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.
midrange.com
