You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,3 +26,13 @@ These steps should help you to build the documentation
26
26
-`npm run doc:install`
27
27
5. Build and open the documentation:
28
28
-`npm run doc:dev`
29
+
30
+
## Best practices
31
+
32
+
When using paramiko to interact with z/OS UNIX System Services (USS), it's important to consider encoding and special character handling.
33
+
Since z/OS uses EBCDIC-based encodings (e.g., IBM-1047, IBM-037, etc.), some commands may return unexpected results when processed in a UTF-8 environment. This is because by default, paramiko reads responses in UTF-8, but z/OS USS may return data in an EBCDIC codepage.
34
+
Certain special characters, such as ööö, 👍, or 🔟, may not be correctly interpreted if the encoding is mismatched.
35
+
If you experience unexpected characters in output, check the terminal's encoding settings (local command on Linux).
36
+
Some commands may alter the terminal's codepage, affecting subsequent outputs.
37
+
For example, switching between ASCII and EBCDIC on mainframes can impact character interpretation.
38
+
If a command affects encoding, reset it after execution.
0 commit comments