| Philippe,
Both the Iconic Map and the FCL use the same validation routines for these
datatypes and because they are primitive data types, the Iconic Map and FCL
display them in a similar fashion.
To the best of my knowledge, there is no plan to change the display of these
datatypes for V1.3.
Verna
|
| Verna,
The problem is not with validation, it's just that the PM's *won't*
print out the time in YYYY-MM-DD-HH:MM:SS.HHHH�HH:MM format, they print
out something like "%X 02 02 BE ...." or whatever which is not very
explicit for the average operator. The BNF output specifed in the SRM
leads me to think I can expect something a lot more readable.
I ILV-encoded a string in the exact format specified in the SRM and it
doesn't work, so my question is :
- Is this a documentation error?
- Is this a bug?
- Is this a feature ?
Regards,
Philippe.
|
| The latest on CharAbsTime, CharRelTime:
The Char_abs_time and Char_rel_time data types are NOT supported.
They are in the process of being removed from the SRM for V1.2. These
data types, not being supported, should not be sent across the call
interface. The conversions from character to binary, then back, are
the proper operations. Some PMs (Notification PM) use these data
types in a private way (the mcc_time_conversion routine knows how to
convert them). Others should use the DECdts library routines to
perform conversions on our binary times to generate what the
Char_abs_time and Char_rel_time data types would provide if they
were supported. We hope to introduce into some future DECmcc version
the support for the DECdts routines that do this. For now, the code
writer must reach an agreement with the DECdts group to use their
routines.
Ted Hupper
|