|
I have looked, and I have looked and debugged, and I don't see any type
of data in positions 57 through 64 and then 65 through 72 that could
be date values. All I see there are spaces (x'40').
> EVAL RNF_Data:x
00000 D6D8D9D7 C7D3C5E2 D9C340C4 E2D9F2F4 - OQRPGLESRC DSR24
00010 F3404040 40000000 06000000 00000040 - 3 ..........
00020 40404040 40404040 40404040 40404040 -
00030 40404040 40404040 40404040 40404040 -
00040 40404040 40404040 40404040 40404040 -
00050 40404040 40404040 40404040 40404040 -
00060 40404040 40404040 40404040 40404040 -
00070 40404040 40404040 ........ ........ - ........
Here is how I am describing my data structure in the //copy member:
D RNF_Data DS
D NetType 1A Inz( *Loval )
D NetFile 10A Inz( *Loval )
D NetLib 10A Inz( *Loval )
D NetNumber 10U 0 Inz( 0 )
D NetFiller 95A Inz( *LoVal )
Here is how I am populating my data structure:
C CallP FNDINXEN( %Addr( RNF_Data ) : Idx :
C %Addr( Options ) :
C %Addr( RNF_Data ))
Here is how Options is defined:
D Options DS Static
D Rule 5U 0 Inz( 2 )
D Length 5U 0 Inz( 25 )
D Offset 5U 0 Inz( 0 )
D Occurrence 5U 0 Inz( 1 )
D Count 5U 0 Inz( 0 )
D 4A
Am I doing something wrong? I thought at first that the Length could be
referring to the length of the data returned, and I changed it to Inz(120)
but that didn't seem to change anything.
Any clues?
Regards,
Jim Langston
Dave McKenzie wrote:
>
> The magic numbers are hex type and sub-type codes for a library (X'0401') and
>a
> distribution index (X'0ED1' - X'0E' is the type for an index, and X'D1' the
> subtype for this particular kind of index). A list of some of the common
>types
> is in the MI Functional Reference manual, and you can see others by dumping
> objects of various types.
>
> The send and arrival dates are at position 57 and 65 in the returned data,
> respectively. They are in 8-byte "system time-stamp" format (*DTS). You can
> convert them to a more friendly form using the QWCCVTDT API, described in the
> Miscellaneous API's manual. Any time you see 8-byte data (the last 2 or 3
>bytes
> may be zero) starting with hex 7 or hex 8, you can suspect it to be a
> timestamp. (Those starting with 8 are on or after Jan 1, 2000, and those
> starting with 7 are before.)
>
> --Dave
+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.