Mapping enumerated slots to msg slot

Symptom

Consider the following example.

Set up a situation which monitors Channel Status (from the Channel Statistics attribute group).
The "native" Channel Status is numeric (e.g. 101 for inactive) and needs to be mapped to its human-readable value.
In the mapping file kmq.map (that is in <ITMHOME>/tables/<temsname>/TECLIB), the corresponding entry looks like this:
<slot slotName="channel_status_enum">
<mappedAttributeEnum name="Channel_Statistics.Channel_Status"/>
</slot>
So it seems that there is no native "Channel_Status_Enum" attribute.

You can also try to map the value "Channel_Statistics.Channel_Status" to the slot "channel_status_enum" by checking the "Process Enumerations" checkbox from the EIF Slot Customization TEP panel, but any attempt to also include the human readable "channel status" in the "msg" slot fails with one the two cases below.

First case below is related to the following literal substitution in the msg slot in the EIF Slot Customization panel:
The MQ channel $Channel_Statistics.Channel_Name$ is not inactive or not running (actual status: $Channel_Statistics.channel_status_enum$).

Second case below is related to the following literal substitution in the msg slot in the EIF Slot Customization panel:
The MQ channel $Channel_Statistics.Channel_Name$ is not inactive or not running (actual status:
$Channel_Statistics.channel_status$).

As you can see, the channel_status_enum slot itself is being filled in correctly, but this slot cannot be translated in the Literal Value of the msg slot.

1~8888115~19~1310563974(Jul 13 15:32:54 2011)
### EVENT ###
ITM_Channel_Statistics; ...
channel_status_enum='Inactive';
mq_manager_name='QMECT';msg='The MQ channel SYSTEM.DEF.SVRCONN is not inactive or not running (actual status: ).';situation_eventdata='~';END

### END EVENT ###
PROCESSED

[...]

1~8888074~3~1310563365(Jul 13 15:22:45 2011)
### EVENT ###
ITM_Channel_Statistics; ...
channel_status_enum='Inactive';
mq_manager_name='QMECT';msg='The MQ channel SYSTEM.DEF.SVRCONN is not inactive or not running (actual status: 101).';situation_eventdata='~';END

### END EVENT ###
PROCESSED