|
On 17/10/2005, at 9:28 PM, Njål Fisketjøn wrote:
The MI reference specifies that the Data Definitional Attribute Template is 112-N bytes long, but if I add the lengths of all fields I get 100 bytes as a minimum length.
The 100 byte length does not include the end calendar element. I get 116 bytes as the minimum length of a DDAT structure.
midrange.com
Fixed portion 32
Era table 50 presuming the SAA era table--different for China or
Japan.
Calendar table
start 18
end 16
---
116
===
I can't get any valid combination to equal 112 bytes. However the DDAT
length is ignored by the instructions so it doesn't matter what value
is specified. The parts of the DDAT are found via the offset fields.
If I specify 100 bytes for dat 1 _CDD fails because the format of dat 2 is wrong.
Makes sense. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.
