Skip to content

Commit b10ad50

Browse files
committed
Better sections
Signed-off-by: worksofliam <mrliamallan@live.co.uk>
1 parent a2e315d commit b10ad50

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

src/content/docs/tips/ccsid.mdx

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ import { Icon } from '@astrojs/starlight/components';
66

77
IBM i uses the EBCDIC character set in contrast to your workstation, which uses some ASCII based character set (Windows, MAC and Linux each use their own variant). This may cause some issues with the names displayed for the objects, files and members in the Object Browser. Even worse, IBM i has several EBCDIC variants, each targeting a national language, and the special US characters '#', '@' and '$' allowed in IBM i object and member names have other code values in the other variants. But IBM i still expects the same code values of the US characters to be used, and thus the national characters with these code values must be used instead.
88

9+
## User CCSID
10+
911
From version 1.4.0 of this extension the code for handling these differences has been changed, primarily when SQL is enabled and used for retrieving object and member lists. Previously there were no conversion between the US and national characters, but now Code for IBM i converts the US characters into the national characters. This is controlled by the coded character set ID (CCSID) value on the IBM i user profile used for the connection, alternatively the system value `QCCSID` (if the user profile CCSID value is `*SYSVAL`). The CCSID is probably already set on your user profile or system, but if you need to change to another language, here are some examples of how to set the CCSID:
1012

1113
| Language | Command | Variant characters |
@@ -24,11 +26,11 @@ The special CCSID value 65535 means "no conversion" - and this will disable the
2426

2527
If you still are experiencing issues after setting the CCSID value, you may want to check that the IBM i PASE environment locale is set correctly:
2628

27-
- OS 7.4 or greater:
29+
### OS 7.4 or greater:
2830

2931
[7.4 and above defaults to UTF-8](https://www.ibm.com/docs/en/i/7.4?topic=system-default-pase-ccsid-locale-changed-utf-8)<Icon name="external" color="cyan" class="icon-inline" /> and there should be no issue.
3032

31-
- OS 7.3 or earlier:
33+
### OS 7.3 or earlier:
3234

3335
The SSH daemon must start with the correct `PASE_LANG` and `QIBM_PASE_CCSID` environment variables set. You probably want to use a locale that defaults to CCSID 1208. **Locale is case sensitive**. E.g., `FR_FR` is different from `fr_FR`.
3436

@@ -39,6 +41,8 @@ The SSH daemon must start with the correct `PASE_LANG` and `QIBM_PASE_CCSID` env
3941

4042
You are also able to change the environment variables at a `*JOB` level, but it is recommend to do it once for your entire system.
4143

44+
## More information
45+
4246
Some links to pages which containing information on variant characters:
4347

4448
- [IBM definition of Variant characters](https://www.ibm.com/docs/en/db2-for-zos/11?topic=ccsids-variant-characters)<Icon name="external" color="cyan" class="icon-inline" />

0 commit comments

Comments
 (0)