Thema: encoding
-
Line endings, encodings and paths: what breaks when a file moves between operating systems
CRLF versus LF, the inconsistent encoding defaults of Windows PowerShell 5.1 versus BOM-less UTF-8 in PowerShell 7, EBCDIC on IBM mainframe-family systems, and filesystems that disagree about case sensitivity and maximum path length: a checklist of what to verify before assuming a text file or a path behaves the same way on a different OS.
-
Reaching z/OS datasets from the UNIX shell: the //'HLQ.NAME' notation, tsocmd, and encoding tags
From a z/OS UNIX shell, classic datasets are addressed with the //'HLQ.DATA.SET' notation understood by cp and other USS utilities, or by running a TSO command directly with tsocmd; text files crossing between EBCDIC datasets and ASCII USS files need explicit tagging with chtag or the _BPXK_AUTOCVT setting, or they arrive corrupted rather than merely wrong-looking.
Maschinenlesbar: JSON