History Trace contains strange characters

Document ID : KB000100628
Last Modified Date : 22/06/2018
Show Technical Document Details
Under specific circumstances the History Trace of a job may contain a strange character:
- The job contains a File Resource
- The File Resource has a file or path name definition that contains:  !SOC!, !ESP!, !COMP! or  !AREA!
- The job that is using the File Resource is in Event Wait status
- The Task that launches the Uproc has the option "Job Run History" unticked

This is an example of an History Trace, the strange character appears before or after the predefined variables:

Session: <SES> Uproc: <UPR> M.U.: <UPR> 
<YYYYMMDDhhmmss> Start Condition Check 
Modified directly in the Engine by 
Processing Date <YYYYMMDD> 
Waiting for resource code: <RESOURCE>, Expected 
Name:  /main/directory/<SOC>�<AREA>/sub/directory/filename 
Processing date: <YYYYMMDD> 
Elements were not correctly initialized

Update to a fix version listed below or a newer version if available.


Fix version:

Component(s):Application Server 

Dollar Universe 6.9.21 - Available