Why I can read a file via UDLIST but I can't via cat command
Posted: Fri Nov 06, 2015 7:19 pm
I went to ISPF Primary Option Menu, typed 3 (Utilities), 17 (UdList), the path (/WebSphere/myCell/myNode/AppServer/profiles/default/logs/ and typed ea (edit/ASCII) on left side of wsadmin.traceout. Then I can see read the file content although I got the warning:
Truncation warning. The data you are editing is variable length data with at
least one record that ends with a blank. Saving the data will result in
removal of any trailing blanks from all records. You can issue the PRESERVE
ON command if you don't want the blanks removed.
If I try read the same file by using the cat command on OMVS shell, I will see the characters messed up.
So my doubt is:
Why can I read the same file via UdList but I can't via OMVS? Should I use a different command in OMVS (e.g. oedit, oget, something like this)? What does the warning "The data you are editing is variable length data with at least one record that ends with a blank" mean? Suppose I want to edit this file safelly, should I type PRESERVE ON and it will garantee I don't corrupt the file format?
Truncation warning. The data you are editing is variable length data with at
least one record that ends with a blank. Saving the data will result in
removal of any trailing blanks from all records. You can issue the PRESERVE
ON command if you don't want the blanks removed.
If I try read the same file by using the cat command on OMVS shell, I will see the characters messed up.
So my doubt is:
Why can I read the same file via UdList but I can't via OMVS? Should I use a different command in OMVS (e.g. oedit, oget, something like this)? What does the warning "The data you are editing is variable length data with at least one record that ends with a blank" mean? Suppose I want to edit this file safelly, should I type PRESERVE ON and it will garantee I don't corrupt the file format?