Wrong output of :MODIFY_STATE with STATUS_TEXT for more then 32 characters

Document ID : KB000092611
Last Modified Date : 03/05/2018
Show Technical Document Details
Issue:
The script statement :MODIFY_STATE with the property STATUS_TEXT issues a faulty message to the Post Processing Report. This happens in case the value for STATUS_TEXT in longer than 32 characters. This is shown by two examples for use of :MODIFY_STATE STATUS_TEXT in post processing below.
 
 
Case 1:
The text you want to set is shorter than 32 characters. In this case the report is correct:
 
:MODIFY_STATE STATUS_TEXT="less than 32 characters"
 
The report shows:
2018-01-24 13:16:00 - U00020512 'Status_Text' modified from 'Job ended' to 'less than 32 characters'.
 
 
Case 2:
The text you want to set is longer than 32 characters (in the example there are 33 characters). In this case, the report is wrong:
 
:MODIFY_STATE STATUS_TEXT="abcdefghijklmnopqrstuvfxyzabcdefg"
 
The report shows:
2018-01-24 13:16:44 - U00020512 '' modified from '          abcdefghijklmnopqrstuvfxyzabcdef' to 'Status_Text'.
 
The text is truncated correctly after the 32nd character, but at the beginning 10 blanks are added. The parts of the message U00020512 are combined incorrectly.

Conclusion:
Please see message library file uc.msl where the definition of this U-number is:
 
00020512EI'&03' modified from '&01' to '&02'.
 
I.e. for more than 32 characters the placeholder &03 is left empty, &01 should be "Job ended" and &02 should be "abcdefghijklmnopqrstuvfxyzabcdef" without the blanks.
It should be:
 
2018-01-24 13:16:00 - U00020512 'Status_Text' modified from 'Job ended' to 'abcdefghijklmnopqrstuvfxyzabcdef'.
Cause:
The case is still under investigation with CA Development.
Resolution:
Workaround:
Cut the string to 32 characters before executing :MODIFY_STATE STATUS_TEXT by using script STR_CUT.

Example:

 
:SET &STRING# = STR_CUT("abcdefghijklmnopqrstuvfxyzabcdefg",1,32)
 
Solution:
Not yet planned