UCX.MSL file showing unexpected characters

Document ID : KB000115612
Last Modified Date : 05/10/2018
Show Technical Document Details
Issue:
Referencing Version 12.2 documentation:

https://docs.automic.com/documentation/webhelp/english/AWA/12.2/DOCU/12.2/AWA%20Guides/help.htm#Installation_Manual/InstallAgents/InstallAgentzOS.htm?

The instructions have been followed, but the .MSL file presents differently in some instances. Example:

Version 10:

0000001DENO DATA (end of file, invalid key, no message...) 
0000001EENO DATA (end of file, invalid key, no message...) 
0000001FEDONNEES ABSENTES (fin de fichier, cle non valable, pas de message, ...) 
0000002DEEXISTS 
0000002EEEXISTS 
0000002FEEXISTE 
0000003DETRUNCATED 
0000003EETRUNCATED 

Version 12.2:

........àä@.........áä.@.........ãä.@.........àá+|.à è ..à/ÈÁÑÁ>ÀÁ..Í>ÅÍÁ%ÈÑÅÁÊ. 
...áïàá à<|ä..........ãïâ<|ä åá.........àáàÑÁËÁ.ãÍ>,ÈÑ?>.ÑËÈ.>?ÄÇ.>ÑÄÇÈ.Ñ_ø%Á_Á> 
Environment:
z/OS
Cause:
The file may have been transferred incorrectly, resulting in a file that is unintelligible on the mainframe. This may cause issues such as not being able to recognize where one record ends and the next begins, and instead treat the file as one long string of data. 
Resolution:
To work around this issue, we have seen success by opening the .MSL file with a text editor, then saving the file as .TXT.  Afterwards, transfer the file as specified in the above documentation.