| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1801.1 | IPMID_HASH | AIMTEC::BUTLER_T | | Wed Nov 18 1992 15:52 | 15 |
|
ookubo,
I believe the field you want is IPMID_HASH, see vol 1 page 8-10, or
possibly OBJECT_ID.
You could use the CAB$ dsab for IPMID_HASH, and the CAB$ATTRIBUTES
dsab for OBJECT_ID.
Hopefully, one of the people familiar with this area will reply.
Thank You for asking,
Tim
|
| 1801.2 | | SIOG::T_REDMOND | Thoughts of an Idle Mind | Thu Nov 19 1992 09:01 | 5 |
| Yes, there is an IPMID_HASH field in DOCDB now, but it's only waiting
for the introduction of X.400 support. I believe that the field is
pretty well ignored for now...
Tony
|
| 1801.3 | Accessing the IP-message ID | IOSG::CHRISTIE | Chris Christie | Thu Nov 19 1992 09:11 | 12 |
|
Ookubo,
The IP-message ID is stored in the ALL-IN-1 File Cabinet SDAF
attribute "JOB_NUMBER" which is accessible from the ALL-IN-1 API via the CAB$
dsab e.g.
GET CAB$.JOB_NUMBER[OA$CURMES]
Hope this helps,
Chris
|
| 1801.4 | Two different attributes | SIOG::T_REDMOND | Thoughts of an Idle Mind | Thu Nov 19 1992 09:19 | 13 |
| Isn't JOB_NUMBER the Message Router ID rather than the IPM_ID? There
were lots of struggles to get this attribute stored correctly (for
incoming and outgoing messages) in early versions of V2.*...
Looking at a message that has come in from TeamLinks, JOB_NUMBER is
shown as ......./A08011/DUBSWS, which is the Message Router ID. The
full IPM_ID for the same message has another set of numbers after
DUBSWS -- something like 1167A373000!!!
IPM_ID is an X.400 attribute. JOB_NUMBER has been around (in fits and
starts) for ages.
Tony
|
| 1801.5 | Don't use object-id | FORTY2::ASH | Grahame Ash @REO | Thu Nov 19 1992 10:13 | 10 |
| <<< Note 1801.1 by AIMTEC::BUTLER_T >>>
-< IPMID_HASH >-
> I believe the field you want is IPMID_HASH, see vol 1 page 8-10, or
> possibly OBJECT_ID.
If you do decide to store it yourself, don't use OBJECT-ID - that should only
be used for object-ids!
grahame
|
| 1801.6 | access SDAF data | JIT981::OOKUBO | | Fri Nov 20 1992 09:16 | 20 |
|
Thank you for your help.
I found IPMID_HASH field in DOCDB. But no message has this data.
I think it'll be supported in future.
>> shown as ......./A08011/DUBSWS, which is the Message Router ID. The
>> full IPM_ID for the same message has another set of numbers after
>> DUBSWS -- something like 1167A373000!!!
^^^^^^^^^^^^
Exactly. I expect IP message ID like this.
I tried to search this number about SDAF file.
$ SEARCH sdaf-file number
I found the record has the same number. I don't know if is has
another meaning. But it must be IP message ID.
I want to know how to access SDAF data.
Can I get this data from SDAF ?
ookubo
|
| 1801.7 | | SIOG::T_REDMOND | Thoughts of an Idle Mind | Fri Nov 20 1992 11:26 | 6 |
| FOR CAB$ATTRIBUTES....
Don't use utilities like EDIT/TPU or SEARCH on the SDAF. Use the data
sets written for this purpose...
Tony
|
| 1801.8 | My mistake ! | IOSG::CHRISTIE | Chris Christie | Mon Nov 23 1992 16:57 | 12 |
| Re .4
Tony,
My mistake - you are indeed correct, the Message Router ID is stored
in the JOB_NUMBER SDAF attribute.
The IP-message ID is *NOT* currently stored in the ALL-IN-1 FC data
structures. However this may chnage in a PFR. Sorry no more details in this
public notesfile.
/Chris
|