| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2644.1 | | IOSG::MAURICE | Night rolls in, my dark companion | Fri Apr 30 1993 11:57 | 14 |
| Hi,
The SYS1 through SYS5 fields are new field names with V3.0. Please do
not use them, since we are likely to use them ourselves in Vnext.
The use of CUSTOMER & V1TYPE has not changed. CUSTOMER is available
for customer use, but has been used in the past by layered products
(DecText?). V1TYPE we have marked as obsolete, but in my unofficial
opinion we are very unlikely to use it ourselves, or ever get rid of
it. So IMHO the CoV can use CUSTOMER & V1TYPE.
HTH
Stuart
|
| 2644.2 | Are 6 bytes enough? | IOSG::CARLIN | Dick Carlin IOSG, Reading, England | Fri Apr 30 1993 11:59 | 19 |
| Charly
Out of all those fields the only one that is for customer use is
CUSTOMER.
SYS1 to SYS5 are placeholders but reserved for future system use (SYS5
is already partly used in a pfr).
SYS1 and SYS2 are gaps left when I removed CREDAT and MODDAT from the
DOCDB, my database upbringing would not let me store the same
information twice. CREDAT and MODDAT are now created on the fly from
CREATED_NBS and MODIFIED_NBS when required by data set references.
I don't know the history of V1TYPE, can anyone else help out here?
I have a feeling that this is not the answer you, or CoV, wanted. Will
this cause problems with their customisations?
Dick_from_Reading
|
| 2644.3 | Fine, that's what I need | VNABRW::EHRLICH_K | The Pit and the Pendulum! | Fri Apr 30 1993 12:23 | 18 |
| Stuart and Dick
yes, that's what I've thought during reading the DOCDB record layout
in Tonys book. SYS3-SYS5 defined as a placeholder, this can only mean
you're working with them in a PFR.
Therefore I've posted this note in A1INFO Conference because we're
talking about futures.
CUSTOMER+V1TYPE can be used by customer, ok. I will talk with CoV now
(hopefully he's in the office, because it's friday)
However, I'll let you know if this answer is suitable for them.
Many thanks to both and
Best regards
Charly_from_CSC_Vienna
|
| 2644.4 | Here's a new thought from CoV... | VNABRW::EHRLICH_K | The Pit and the Pendulum! | Fri Apr 30 1993 13:46 | 25 |
| Hi,
hhhmmmm, ok, the COV is happy with your replies, but there's a
little problem behind the scene.
The fields CUSTOMER+V1TYPE are not usable for what the CoV will need,
because by sending a mailmessage this two fields are 'lost'. It seems
that this two fields are not considered for all filecabinetfunctions.
What CoV 'only' needs, is one or more fields that will consider
in all filecabinetfunctions.
They have to add a DVR number which must be defined in every document
and of course in every mail.
Is there a possibility to use a field or to define a new field that
ALL-IN-1 doesn't check and it can be used by all filecabinetfunctions.
Any Ideas ??? Yes, I know,that this not an easy question, but I'm sure
the COV pays for a good solution.
Best regards
Charly
|
| 2644.5 | | SIOG::T_REDMOND | Thoughts of an Idle Mind | Fri Apr 30 1993 15:47 | 4 |
| Why don't they use the old trick of sticking the DVR number onto the
end of an attribute (part that the user doesn't see), like DSUBJECT?
T
|
| 2644.6 | Sorry, I don't know this trick! | VNABRW::EHRLICH_K | The Pit and the Pendulum! | Fri Apr 30 1993 16:01 | 7 |
| Tony,
many thanks for your quick reply. But I must honestly apologize
that I don't know this trick. Can you explain me how this will work?
Best regards
Charly
|
| 2644.7 | Briefly.... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue May 11 1993 14:08 | 10 |
| You'll find several notes in this and previous versions of the
conference describing this trick. Basically, you use the last few
characters of the document title whch doesn't normally get displayed,
to hold your extra data. The title field is carried around the mail
system and in all the FC functions.
Note that in V3.0, SMU uses this trick to hold the real sender of the
message, so don't trample on that....
Graham
|