Below are sample instructions to to download ICU, configure it not to use multi-threading, and compile it for various platforms. Note that download sites, versions of compilers, and milli and micro releases of ICU may well change subsequent to the writing of these instructions, and make these instructions obsolete. Therefore, these procedures must be considered examples, not gospel.

Compiling ICU version 3.6 on x86 Linux

As of this writing (January, 2007), ICU version 3.6 can be compiled on x86 Linux with the following configuration:

Operating System	バージョン	Compilers
Linux	Red Hat Enterprise Linux 4 Update 2	gcc 3.4.4, GNU make (3.77+), ANSI C compiler

手順

1. ［参考］ Ensure that system environment variable <s0>$PATH</s0> includes the location of all the compilers mentioned above.

2. Download the source code of ICU version 3.6 for C from http://icu.sourceforge.net/download/3.6.html#ICU4C

3. At the shell prompt, execute the following commands:

   gunzip -d < icu4c-3_6-src.tgz | tar -xf - 
   cd icu/source/
   chmod +x runConfigureICU configure install-sh       
   runConfigureICU Linux --disable-64bit-libs --disable-threads 
   gmake
   gmake check
   gmake install>

4. ［参考］ ICUの位置をポイントするために、環境変数LD_LIBRARY_PATHを使用します（AIXではLIBPATH）。GT.M uses the environment variable LD_LIBRARY_PATH to search for dynamically linked libraries to be loaded.

［参考］ ICU is now installed in <s0>/usr/local</s0>.

	By default, ICU is installed on /usr/local directory. If you need to install ICU on a different directory type: runConfigureICU Linux --prefix=<install_path> --disable-64bit-libs --disable-threads Then execute the gmake commands, and set the environment variable LD_LIBRARY_PATH to point to the appropriate location.

Compiling ICU version 3.6 on HP PA-RISC HP-UX

As of this writing (January, 2007), ICU version 3.6 can be compiled on PA-RISC HP-UX with the following configuration:

Operating System	バージョン	Compilers
HP-UX	HP-UX 11.11	aCC A.03.50, cc B.11.11.08, GNU make (3.77+)

手順：

1. ［参考］ Ensure that system environment variable <s0>$PATH</s0> includes the location of all the compilers mentioned above.

2. Download the source code of ICU version 3.6 for C from http://icu.sourceforge.net/download/3.6.html#ICU4C

3. Add the following line in the configuration file source/config/mh-hpux-acc to include the appropriate C++ runtime libraries:

   DEFAULT_LIBS = -lstd_v2 -lCsup_v2 -lcl

4. At the shell prompt, execute the following commands:

   gunzip -d < icu4c-3_6-src.tgz | tar -xf - 
   cd icu/source/
   chmod +x runConfigureICU configure install-sh       
   runConfigureICU HP-UX/ACC --disable-64bit-libs --disable-threads
   gmake
   gmake check
   gmake install

5. ［参考］ ICUの位置をポイントするために、環境変数LD_LIBRARY_PATHを使用します（AIXではLIBPATH）。［参考］ Set the environment variable <s0>$LD_LIBRARY_PATH</s0> to point to the location of ICU.  HP-UX uses the environment variable <s1>$LD_LIBRARY_PATH</s1> to search for dynamically linked libraries to be loaded.

［参考］ ICU is now installed in <s0>/usr/local</s0>.

	By default, ICU is installed in the /usr/local directory. If you need to install ICU on a different directory type: runConfigureICU HP-UX/ACC --prefix=<install_path> --disable-64bit-libs -disable-threads Then execute the gmake commands, and set the environment variable LD_LIBRARY_PATH to point to the appropriate location.

Compiling ICU version 3.6 on Solaris

As of this writing (January, 2007), ICU version 3.6 can be compiled on Solaris with the following configuration:

Operating System	バージョン	Compiler
Solaris	Solaris 9 (SunOS 5.9)	Sun Studio 8 (Sun C++ 5.5), GNU make (3.77+), ANSI C compiler

手順：

1. ［参考］ Ensure that system environment variable <s0>$PATH</s0> includes the location of all the compilers mentioned above.

2. Download the source code of ICU version 3.6 for C from http://icu.sourceforge.net/download/3.6.html#ICU4C

3. Add the following line in the configuration file source/config/mh-solaris to include the appropriate C++ runtime libraries:

   DEFAULT_LIBS = -lCstd -lCrun -lm -lc

4. At the shell prompt, execute the following commands:

   gunzip -d < icu4c-3_6-src.tgz | tar -xf -
   cd icu/source/
   chmod +x runConfigureICU configure install-sh       
   runConfigureICU Solaris --disable-64bit-libs --disable-threads
   gmake
   gmake check
   gmake install

5. ［参考］ ICUの位置をポイントするために、環境変数LD_LIBRARY_PATHを使用します（AIXではLIBPATH）。Solaris uses the environment variable LD_LIBRARY_PATH to search for dynamically linked libraries to be loaded.

ICU is now installed in the/usr/local directory.

	By default, ICU is installed in the /usr/local directory. If you need to install ICU on a different directory type: runConfigureICU Solaris --prefix=<install_path> --disable-64bit-libs -disable-threads Then execute the gmake commands, and set the environment variable LD_LIBRARY_PATH to point to the appropriate location.

Compiling ICU version 3.6 on AIX

As of this writing (January, 2007), ICU version 3.6 can be compiled on AIX with the following configuration:

Operating System	バージョン	Compilers
AIX	AIX 5.2 (PowerPC 64-bit)	VisualAge 6, GNU make (3.77+), ANSI C compiler

手順：

1. ［参考］ Ensure that system environment variable <s0>$PATH</s0> includes the location of all the compilers mentioned above.

2. Download the source code of ICU version 3.6 for C from http://icu.sourceforge.net/download/3.6.html#ICU4C

3. At the shell prompt, execute the following commands:

   gunzip -d < icu4c-3_6-src.tgz | tar -xf - 
   cd icu/source/
   chmod +x runConfigureICU configure install-sh       
   runConfigureICU AIX --disable-64bit-libs --disable-threads
   gmake
   gmake check
   gmake install

4. Set the environment variable LIBPATH to point to the location of ICU. AIX uses the environment variable LIBPATH to search for dynamically linked libraries to be loaded.

［参考］ ICU is now installed in <s0>/usr/local</s0>.

	By default, ICU is installed on /usr/local directory. If you need to install ICU on a different directory type: runConfigureICU AIX --prefix=<install_path> --disable-64bit-libs -disable-threads Then, execute the gmake commands, and set the environment variable LIBPATH to point to the appropriate location.

	AIX includes the release (or minor version) number in the name of the ICU library which can change based on updates from IBM. Users must set the environment variable gtm_icu_minorver to the release number so that GT.M uses that number to activate and access the ICU. If gtm_icu_minorver is not defined, GT.M assumes the release number to be 0.

Jobコマンドは、MのプロセスがDOで生成されるように同じ環境でバックグラウンドプロセスを生成します。そのため、もし親プロセスがUTF-8モードで動作している場合、JobプロセスもUTF-8モードで動作します。In the event that a background process must have a different mode from the parent, create a shell script to alter the environment as needed, and spawn it with a ZSYstem command, e.g., ZSYstem "/path/to/shell/script &".

In pre-Unicode™ releases, and in M mode, the concept of an illegal character does not exist - all 256 combinations of the 8 bits in a byte are legal characters. In UTF-8 mode, there are certain sequences of bytes that are illegal characters. For example, $ZCHAR(192) is an illegal character because it is a sequence of 2-bytes whose second byte is missing (U+0000).

The [NO]BADCHAR keyword argument for the VIEW command enables or disables the triggering of an error when character-oriented functions encounter malformed byte sequences (illegal characters).

At process startup, GT.M initializes BADCHAR from the environment variable gtm_badchar. Set the environment variable gtm_badchar to a non-zero number or "YES" (or “Y”) to enable VIEW "BADCHAR". Set the environment variable gtm_badchar to 0 or "NO" or "FALSE" (or ”N” or “F”) to enable VIEW "NOBADCHAR". By default, GT.M enables VIEW "BADCHAR".

If VIEW "BADCHAR" is enabled, functions generate the BADCHAR error when they encounter malformed byte sequences. With this setting, GT.M detects and clearly reports potential application program logic errors as soon as they appear. As the an illegal UTF-8 character in the argument of a character-oriented function likely indicates a logic issue, FIS recommends the use of VIEW “BADCHAR” in production environments.

When all strings consist of well-formed characters, the value of VIEW [NO]BADCHAR has no effect whatsoever. If VIEW "NOBADCHAR" is enabled, the same functions treat malformed byte sequences as valid characters. During the migration of an application to add support for Unicode™, illegal character errors are likely to be frequent and indicative of application code that is yet to be modified. VIEW "NOBADCHAR" は、それら存在が開発を妨げる時間に、これらのエラーを抑制します。

ZSHOWコマンドは、現在のGT.MM環境に関する情報を表示します。Refer to the GT.M Programmer's Guide for a complete description and M-mode examples.

UTF-8モードで、ZSHOWのコマンドは、次のようにバイト指向とディスプレイ指向の挙動を示します。

O[PEN][:tvexpr] expr[:[(keyword[=expr][:...])] [:numexpr]][,...]

OPENコマンドは、GT.Mプロセスとデバイス間の接続を作成します。Refer to the GT.M Programmer's Guide for a complete description and M-mode examples.

In UTF-8 mode, the OPEN command recognizes ICHSET, OCHSET, and CHSET as three additional deviceparameters to determine the encoding of the the input / output devices. 次のセクションでは、これらのデバイスパラメータを説明します。

In M mode, the OPEN command ignores ICHSET, OCHSET, CHSET, and PAD device parameters.

If an I/O device uses a multi-byte character encoding, every READ and WRITE operation of that device checks for the well-formed characters according to the specified character encoding with ICHSET or OCHSET. If the I/O commands encounter an illegal sequence of bytes, they always trigger a run-time error; a VIEW “NOBADCHAR” does not prevent such errors. Strings created by $ZCHAR() and other Z equivalent functions may contain illegal sequences. The only way to input or output such illegal sequences is to specify character set “M” with one of these deviceparameters.

R[EAD][:tvexpr] (glvn|*glvn|glvn#intexpr)[:numexpr]|strlit|fcc[,...]

READコマンドは、READの引数として指定されたグローバルまたはローカル変数へ、現在のデバイスからの入力を転送します。利便性のために、READもまた、制限された出力を現デバイスに実行する引数を受け入れます。Refer to the GT.M Programmer's Guide for a complete description and M-mode examples.

UTF-8モードで、READコマンドは、入力デバイスの文字エンコーディングとしてOPENデバイスで指定された文字セットの値を使用しています。もし文字セットが "M"または"UTF-8"に指定されている場合、データは変換なしで読み込まれます。もし文字セットが"UTF-16"、"UTF-16LE"、"UTF-16BE"の場合、データは指定されたエンコーディングで読み込み、UTF-8に変換されます。もしREADコマンドが、不正な文字または選択された表現以外の文字を検出した場合、それは実行時エラーがトリガされます。The READ command recognizes all Unicode™ line terminators for non-FIXED devices. See “Line Terminators” section for more details.

	In M mode, characters and bytes have a one-to-one relationship and therefore READ can be used to read bit-streams of non-character data.

番号記号(#) と非ゼロの整数式が変数名の直後に続く時は、整数式はREADコマンドの入力として受け入れられる文字の最大数を特定します。In UTF-8 mode, this can occur in the middle of a sequence of combining code-points (some of which are typically non-spacing). 入力デバイス上の任意の表示が発生する時、固定長のREAD ( READ #) で返される文字を表すものではありません。

In UTF-8 mode, the READ * command accepts one character in Unicode™ of input and puts the numeric code-point value for that character into the variable.

In M mode, the READ * command reads a single byte and returns the numeric byte value. If character set UTF-8 is specified, the READ * command reads one to four bytes, depending on the encoding and returns the numeric code-point value of the character. If ICHSET specifies "UTF-16", "UTF-16LE" or "UTF-16BE", the READ * command reads a byte pair or two byte pairs (if it is a surrogate pair) and returns the numeric code-point value.

GTM>Set filename="mydata.out"; assume that mydata.out contains "新年好"
GTM>Open filename:(readonly:ichset="UTF-16LE")
GTM>Use filename
GTM>Read *x
GTM>Close filename
GTM>Write $char(x)
新

W[RITE][:tvexpr] expr|*intexpr|fcc[,...]

WRITEコマンドは、現デバイスへその引数で指定された文字ストリームを転送します。Refer to the GT.M Programmer's Guide for a complete description and M-mode examples.

UTF-8モードで、WRITEコマンドは、出力デバイスの文字エンコーディングとしてOPENデバイスで指定された文字セットを使用します。もし文字セットが"M"または"UTF-8"を指定している場合、GT.Mは変換なしでデータを書き込みます。もし文字セットが "UTF-16"、"UTF-16LE"、"UTF-16BE" を指定している場合、データはUTF-8でエンコードされていると仮定し、WRITEは文字セットのデバイスパラメータで指定された文字エンコーディングに変換します。

例：

GTM>Set filename="mydata.out"
GTM>Set T16LE="准备庆祝新年在上海"
GTM>Open filename:(chset="UTF-16LE")
GTM>Use filename
GTM>Write T16LE
GTM>Close filename

The above example creates a file mydata.out in UTF-16LE character set.

	If a WRITE command encounters an illegal character, it triggers a run-time error irrespective of the setting of VIEW "BADCHAR". In M mode, the WRITE command ignores the OCHSET deviceparameter .

WRITEコマンドの引数が整数式に続いて先頭にアスタリスク(*) で構成するとき、WRITEコマンドは、その整数式のコードポイント値によって表される文字を出力します。

With character set M specified at device OPEN, the WRITE * command transfers the character (byte) associated with the numeric value of the integer expression. With character UTF-8 specified at device OPEN, the WRITE command outputs the character associated with the numeric code-point value. If character set "UTF-16", "UTF-16LE" or "UTF-16BE" is specified, WRITE * transforms the character code to the mapping specified by that character set.

For non FIXED format sequential files and terminal devices for which character set is not M, all the standard Unicode™ line terminators terminate the logical record. These are U+000A (LF), U+0000D (CR), U+000D followed by U+000A (CRLF), U+0085 (NEL), U+000C (FF), U+2028 (LS) and U+2029 (PS). For these devices, LF is used to terminate a record on output though if FILTER=CHARACTER is enabled, all of the terminators are recognized to maintain the values of $X and $Y.

When the ICHSET for a device is not "M", if BOM (U+FEFF) is at the beginning of the initial input for a file or data stream, GT.M uses it to determine the endian if the ICHSET is UTF-16 and checks for agreement with ICHSET UTF-16BE or UTF-16LE.

If character set for a device is UTF-16, GT.M uses BOM (U+FEFF) to determine the endians. . For this to happen, the BOM must be at at the beginning of the initial input for a file or data stream. If there is no BOM present, GT.M assumes big endianess.

If the character set of a device is UTF-8, GT.M checks for and ignores a BOM on input.

If the BOM does not match the character set specified at device OPEN, GT.M triggers an error. READ does not return BOM to the application and the BOM is not counted as part of the first record.

If the output character set for a device is UTF-16 (but not UTF-16BE or UTF-16LE,) GT.M writes a BOM before the initial output. The application code does not need to explicitly write the BOM.

The measurement characteristics of some deviceparameters change when they are applied to certain devices. For example, terminal WIDTH is measured in display-columns whereas socket WIDTH is measured in code-points. The following tables lists the units of measurement (byte, code-point, or display-column) for $X and deviceparameters for TRM, SD, SOC, and FIFO. All deviceparameters that are not described in this section remain unchanged from preceding releases. "-" denotes that the deviceparameter has no effect for that device.

	In M mode, display-columns, characters and bytes are all equivalent In all UTF-16 I/O modes, RECORDSIZE must be even and PAD characters are two bytes GT.M implements SD output in a fashion that supports copying files to display devices such as printers and terminals.

The $ASCII() function returns the integer code for a character in a string. Refer to the GT.M Programmer's Guide for a complete description and M-mode examples.

With character set UTF-8 specified, the $ASCII() function returns a decimal representation of the integer Unicode™ code-point value of a character in the given string.

In the Unicode™ Standard, the code-point is the hexadecimal integer that appears after the “U+” in the definition of each character) and may be as large as 1114109, corresponding to U+10FFFD.

	Although it seems counter-intuitive for a function called $ASCII() to return Unicode™-point values, the M standard has retained the name of $ASCII() for all character sets, which minimizes the application code changes needed to add the support for Unicode™.

GTM>W $ZCHSET
UTF-8
GTM>W $ASCII("新") 
26032 
GTM> W $$FUNC^%DH("26032")
000065B0

The $CHAR() function returns a string of one or more characters corresponding to integer codes specified in its argument(s). Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the $CHAR() function returns a string composed of characters represented by the integer equivalents of the Unicode™ code-points specified in its argument(s).

With VIEW NOBADCHAR enabled, the $CHAR() function ignores all expressions that do not correspond to valid Unicode™ code-points,the $CHAR() function never returns a string with illegal or invalid characters .

With VIEW BADCHAR enabled, the $CHAR() function triggers a run-time error if any expression evaluates to a code-point value that is not a character in Unicode™ According to the Unicode™ Standard version 5.0, invalid code-points include the following sets:

Example of $CHAR() in UTF-8 mode

GTM>W $ZCHSET 
UTF-8
GTM> W $CHAR(26032)
新
GTM> W $CHAR(65)
A

In the above example, the integer value 26032 is the Unicode™ character "新" in the CJK Ideograph block of Unicode™.

	The output of the $CHAR() function for values of integer expression(s) from 0 through 127 does not vary with choice of the character encoding scheme. これは、7ビットASCII は UTF-8 文字エンコーディング方式の適切なサブセットであるためです。値が128〜255となる$CHAR() 関数によって返される文字の表現は、それぞれの文字のエンコーディング方式によって異なります。

When compiling a program with VIEW "BADCHAR" and a literal argument for the $CHAR() function specifies an illegal character, the GT.M compiler triggers a BADCHAR error and embeds that error in the object in case the object is every used. When compiling a program with VIEW "NOBADCHAR" and a literal argument for $CHAR() specifies an illegal character, the GT.M compiler does not trigger the BADCHAR error nor can the GT.M run-time system detect the error. Therefore, application developers must ensure a routine is compiled and executed with appropriately chosen (usually matching) settings of VIEW "BADCHAR".

$EXTRACT() 関数は、与えられた文字列の部分文字列を返します。Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the $EXTRACT() function interprets the string arguments as UTF-8 encoded. With VIEW "BADCHAR" enabled, the $EXTRACT() function triggers a run-time error when it encounters a character in the reserved range of the Unicode™ Standard, but it does not process the characters that fall after the span specified by the arguments.

	For byte-oriented operations, use $ZEXTRACT(), as $EXTRACT() in NOBADCHAR mode interprets its string arguments as character, rather than byte-oriented and only returns byte-oriented results when all characters in its arguments are encoded in a single byte.

GTM>FOR i=0:1:4 WRITE !,$EXTRACT("新年好",i),"<" 
<
新<
年<
好<
<
GTM>

GTM>FOR i=0:1:4 WRITE !,$E("新年好",1,i),"<" 
<
新<
新年<
新年好<
新年好<
GTM>

TRIM(x) 
	NEW i,j
	FOR j=$L(x):-1:0 S nx=$E(x,1,j) Q:$EXTRACT(x,j)'=" " 
	FOR i=1:1:j S fx=$E(nx,i,$L(x)) Q:$EXTRACT(x,i)'=" " 
	QUIT fx 
GTM>SET str=" 新年好 "
GTM>WRITE $LENGTH(str)
5 
GTM>WRITE $LENGTH($$TRIM^trim(str))
3

$FIND() 関数は、その位置の文字列内の部分文字列の出現を整数文字位置を返します。Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the $FIND() function interprets the string arguments as UTF-8 encoded. With VIEW "BADCHAR" enabled, the $FIND() function triggers a run-time error when it encounters a malformed character, but it does not process the characters that fall after the span specified by the arguments.

	The $FIND() function must never be used for byte-oriented operations.

GTM> WRITE $FIND("新年好","年") 
3 
GTM> 

GTM> WRITE $FIND("准备庆祝新年在上海:准备庆祝新年在上海","上",9) 
19 
GTM> 

GTM> SET t=1 FOR  SET t=$FIND("准备庆祝新年在上海:准备庆祝新年在上海","祝新",t) Q:'t  W !,t 
6 
16 
GTM> 

$JUSTIFY 関数はフォーマットされた文字列を返します。Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the $JUSTIFY() function interprets the string argument as UTF-8 encoded. With VIEW "BADCHAR" enabled, the $JUSTIFY() function triggers a run-time error when it encounters a malformed character.

GTM> WRITE $JUSTIFY("新年好",10),!,$JUSTIFY("准备庆祝新年在上海",5) 
       新年好
准备庆祝新年在上海
GTM>

GTM> WRITE "1234567890",!,$JUSTIFY(10.545,10,2) 
1234567890 
     10.55 
GTM>

GTM> WRITE "1234567890",!,$JUSTIFY(10.544,10,2) 
1234567890 
     10.54 
GTM> 

GTM> WRITE "1234567890",!,$JUSTIFY(10.5,10,2) 
1234567890 
     10.50 
GTM> 

GTM> WRITE $JUSTIFY(.34,0,2)     
0.34 
GTM> 

The $LENGTH() function returns the length of a string measured in characters, or in "pieces" separated by a delimiter specified by one of its arguments. Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the $LENGTH() function interprets the string argument(s) as UTF-8 encoded. With VIEW "BADCHAR" enabled, the $LENGTH() function triggers a run-time error when it encounters a malformed character.

GTM> WRITE $LENGTH("新年好") 
3 
GTM> 

GTM> SET x="新年好/准备庆祝新年在上海/准备庆" 
GTM> WRITE $LENGTH(x,"/") 
3 
GTM> 

GTM> WRITE $LENGTH("/新/年好/","/") 
4 
GTM> 

$PIECE() 関数は、区切り文字は、1つまたは複数の文字で構成された、指定した文字列が部分文字列の区切りを返します。Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the $LENGTH() function interprets the string arguments as UTF-8 encoded. With VIEW "BADCHAR" enabled, the $PIECE() function triggers a run-time error when it encounters a malformed character, but it does not process the characters that fall after the span specified by the arguments.

GTM< FOR i=0:1:4 WRITE !,$PIECE("新 年 好"," ",i),"<" 

<
新<
年<
好<
<
GTM>

GTM< FOR i=-1:1:4 WRITE !,$PIECE("新 年 好"," ",i,i+1),"<" 
<
新<
新 年<
年 好<
好<
<
GTM>

F p=1:1:$L(x,"/") W ?p-1*10,$piece(x,"/",p) 

GTM> s $P(x,".",25)="" W x 

$TRANSLATE()関数は、引数の最初の文字を置換または削除の結果は、そのほかの引数のパターンで指定された文字列を返します。Refer to the GT.M Programmer's Guide for a complete description and M mode examples.

With character set UTF-8 specified, the algorithm of the $TRANSLATE() function interprets the string arguments as UTF-8 encoded. With VIEW "BADCHAR" enabled, the $TRANSLATE() function triggers a run-time error when it encounters a malformed character.

GTM> WRITE $TR("新年好","年好","1") 
新1 
GTM> 

GTM>WRITE $TR("新","X新","年好") 
好

GTM> WRITE $TR("新年好","好新") 
年
GTM>

The $ZASCII() function returns the numeric byte value (0 through 255) of a given sequence of octets (8-bit bytes) .

$ZASCII 関数のフォーマットは次のとおりです：

$ZA[SCII](expr[,intexpr])

$ZASCII() は、バイトのシーケンスの中にバイトを調べる手段を提供します。Used with $ZCHAR(), $ZASCII() also provides a means to perform arithmetic operations on the byte values associated with a sequence of octets.

GTM>FOR i=0:1:4 WRITE !,$ZA("新",i) 

-1
230
150
176
-1

$ZCHAR() 関数は、その引数で指定された数値バイト値（0〜255）に対応する1つ以上のバイトのバイトシーケンスを返します。

$ZCHR()関数のフォーマット：

$ZC[HAR](intexpr[,...])

GT.Mは引数の数を最大254に制限します。$CHAR() provides a means of producing byte sequences. Used with $ZASCII(), $ZCHAR() can also perform arithmetic operations on the byte values of the bytes associated with a sequence of octets (8-bit bytes).

GTM> $ZCHAR(230,150,176,7) 
新
GTM>

The $ZEXTRACT() function returns a byte sequence of a given sequence of octets (8-bit bytes) .

$EXTRACT関数のフォーマット：

$ZE[XTRACT](expr[,intexpr1[,intexpr2]])

GTM>FOR i=0:1:9 WRITE !,$ASCII($ZEXTRACT("新年好",i)),"<"
-1<
230<
150<
176<
229<
185<
180<
229<
165<
189<

$ZFIND ()関数は、オクテット（8ビットバイト）のシーケンス内のバイトのシーケンスの発生位置の整数のバイト位置を返します。

The format of the $ZFIND() function is:

$ZF[IND](expr1,expr2[,intexpr])

$ZFIND() は、バイトシーケンスを検索するツールを提供しています。包含演算子( [ ) と2つの引数の$ZLENGTH() は、関連する関数を提供する他のツールです。

GTM> WRITE $ZFIND("新年好",$ZCHAR(150)) 
3 
GTM> 

GTM> WRITE $ZFIND("新年好",$ZCHAR(229),5) 
8 
GTM> 

[参考]GTM>Set t=1 For  Set t=$ZFind("新年好",$ZChar(230,150,176),t) Quit:'t  Write !,t

4
GTM> 

$JUSTIFY() 関数は、フォーマットされた固定長のバイトシーケンスを返します。

$ZJUSTIFY()関数のフォーマット：

$ZJ[USTIFY](expr,intexpr1[,intexpr2])

$ZJUSTIFY()は、固定長のバイトシーケンスを作成するには、オクテットのシーケンスを埋め尽くします。しかし、もし指定された式の長さ指定されたバイトサイズを超える場合、$ZJUSTIFY() は、結果を切り捨てません（3番目の引数に基づいてまだ丸めるかもしれないが）。必要なときに、$ZEXTRACT() で切り捨てを実行します。

$ZJUSTIFY() は、オプションで小数点の後の結果の一部を丸めます。3番目の引数がない場合には、$ZJUSTIFY() は、式の評価を制限しません。3番目（丸め）引数の存在することで、$JUSTIFY() は、数値として式を評価します。丸めのアルゴリズムは、以下のように理解することができます：

GTM> WRITE "123456789012345",! WRITE $ZJUSTIFY("新年好",15),!,$ZJUSTIFY("新年好",5) 
123456789012345
      新年好
新年好
GTM>

The $ZLENGTH() function returns the length of a sequence of octets measured in bytes, or in "pieces" separated by a delimiter specified by one of its arguments.

$ZLENGTH()関数のフォーマット：

$ZL[ENGTH](expr1[,expr2])

$ZLENGTH() provides a tool for determining the lengths of a sequence of octets in two ways--bytes and pieces. 1つの引数がバイト数を返すにもかかわらず、$ZLENGTH() の2つの引数は、既存の部分文字の数を返します。

GTM> WRITE $LENGTH("新年好") 
9 
GTM> 

GTM> SET x="新"_$ZCHAR(63)_"年"_$ZCHAR(63)_"好" 
GTM> WRITE $ZLENGTH(x,$ZCHAR(63))
2 
GTM>

GTM>SET x=$ZCHAR(63)_"新"_$ZCHAR(63)_"年"_$ZCHAR(63)_"好_$ZCHAR(63)" 
GTM>WRITE $ZLENGTH(x,$ZCHAR(63)
4
GTM>

$ZPIECE()関数は、1つ以上のバイトで構成される、指定されたバイトシーケンスによって、バイトの区切りのシーケンスを返します。In M, $ZPIECE() returns a logical field from a logical record.

$ZPIECE() 関数のフォーマット：

$ZP[IECE](expr1,expr2[,intexpr1[,intexpr2]])

$ZPIECE() は、長さが可変であるそれぞれが複数のエレメントまたはフィールドが含まれている値を効果的に使用するツールを提供します。

アプリケーションは、通常、ストレージのオーバーヘッドを最小限に抑えるために、$ZPIECE() 区切り文字（2番目の引数）に単一のバイトを使用し、そして、実行時の効率を向上させます。データ値は区切り文字を決して含まないので、区切り文字を選択する必要があります。編集のチェックでこの習慣を強制することの障害は、データ値内の部分文字列の位置に予期しない変更が発生する可能性があります。キャレット記号（^）、バックスラッシュ（\）、アスタリスク（*）文字は、良く利用する目に見える区切り文字の例です。複数バイトのデリミタは、フィールドの内容とのコンフリクトの可能性を減らすことができます。しかし、それらはストレージの効率性を低下させ、単一バイトの区切り文字よりも効率性は少なく処理されます。一部のアプリケーションでは、データに現れる区切り文字の可能性は減らせ、目に見える区切り文字で提供される読みやすさが犠牲になりますが、制御文字が使用できます。

SETコマンドの引数は、その等号（=）の左辺の$ZPIECE() のフォーマットを持っている何かを持つことができます。この構文は、オクテットのシーケンス内のそれぞれの部分を容易にメンテナンスが可能です。また、区切り文字のバイトシーケンスを生成するために使用することもできます。SET $ZPIECEの詳細については、コマンドの章の <a0>“Set”</a0> を参照してください。

GTM>FOR i=0:1:3 WRITE !,$ZPIECE("新"_$ZCHAR(64)_"年",$ZCHAR(64),i),"<" 

<
新<
年<
<
GTM>

GTM>FOR i=-1:1:3 WRITE !,$ZPIECE("新_$ZCHAR(64)_"年",$ZCHAR(64),i,i+1),"<" 
<
新<
新 年<
年<
<
GTM>

F p=1:1:$ZL(x,"/") W ?p-1*10,$zpiece(x,"/",p) 

GTM> s $P(x,$ZCHAR(64),25)="" W x 
新年好@@@@@@@@@@@@@@@@@@@@@@@@

$ZTRANSLATE()関数は、その他の引数のパターンによって指定された、その引数の最初のバイトを、置換したり省略したりする結果として、バイトシーケンスを返します。

$ZTRANSLATE()関数のフォーマット：

$ZTR[ANSLATE](expr1[,expr2[,expr3]])

$ZTRANSLATE() は、暗号化などタスクのためのツールを提供しています。

$ZTRANSLATEのアルゴリズムは、以下のように理解することができます：

GTM>set hiraganaA="あ" ; # $ZCHAR(227,129,130)
GTM>set temp1=$ZCHAR(130)
GTM>set temp2=$ZCHAR(140)
GTM>W hiraganaA
あ
GTM>W $ZTRANSLATE(hiraganaA,temp1,temp2)
が
GTM>

$ZCONVERT() 関数は、異なったエンコーディングに変換された文字列として、第1引数を返します。2つの引数の形式は、文字セット内の大文字小文字のエンコーディングを変更します。3つの引数の形式は、符号化方式を変更します。

The format for the $ZCONVERT() function is:

$ZCO[NVERT](expr1, expr2,[expr3])

The valid (case insensitive) character codes for expr2 in the two-argument form are:

The valid (case insensitive) codes for character set encoding for expr2 and expr3 in the three-argument form are:

When UTF-8 mode is enabled, GT.M uses the ICU Library to perform case conversion. As mentioned in the Theory of Operation section, the case conversion of the strings occurs according to Unicode™ code-point values. This may not be the linguistically or culturally correct case conversion, for example, of the names in the telephone directories. Therefore, application developers must ensure that the actual case conversion is linguistically and culturally correct for their specific needs. The two-argument form of the $ZCONVERT() function in M mode does not use the ICU Library to perform operation related to the case conversion of the strings.

GTM>W $ZCONVERT("Happy New Year","U")
HAPPY NEW YEAR

GTM>W $ZCHSET 
M
GTM> W $ZCONVERT("HAPPY NEW YEAR","T")
%GTM-E-BADCASECODE, T is not a valid case conversion code

GTM>S T8="准备庆祝新年在上海"
GTM>W $L(T8)
9
GTM>S T16=$ZCONVERT(T8,"UTF-8","UTF-16LE")
GTM>W $L(T16) 
%GTM-E-BADCHAR, $ZCHAR(198) is not a valid character in the UTF-8 encoding form
GTM>S T16=$ZCONVERT(T16,"UTF-16LE","UTF-8")
GTM>W $L(T16)
9

$ZSUBSTR() 関数は、バイトのシーケンスから適切にエンコードされた文字列を返します。

$ZSUB[STR] (expr ,intexpr1 [,intexpr2])

The $ZSUBSTR() function is a new function introduced in conjunction with Unicode™ support. Like the $ZCONVERT() function and the $ZWIDTH() function, it does not have a traditional M equivalent.

GTM>W $ZCHSET
M
GTM>set char1="a" ; one byte character 
GTM>set char2="ç"; two-byte character
GTM>set char3="新"; three-byte character
GTM>set y=char1_char2_char3
GTM>W $ZSUBSTR(y,1,3)=$ZSUBSTR(y,1,5)
0

GTM>W $ZCHSET
UTF-8
GTM>set char1="a" ; one byte character 
GTM>set char2="ç"; two-byte character
GTM>set char3="新"; three-byte character
GTM>set y=char1_char2_char3
GTM>W $ZSUBSTR(y,1,3)=$ZSUBSTR(y,1,5)
1

$ZW[IDTH] (expr)

$ZWIDTH() 関数は、画面やプリンタ上へ文字列を表示するために必要な列の数を返します。

	The ZWIDTH() function triggers a run-time error if it encounters a malformed byte sequence irrespective of the setting of "BADCHAR".

With character set UTF-8 specified, the $ZWIDTH() function uses the ICU's glyph-related conventions to calculate the number of columns required to represent the expression.

GTM>S NG=$CHAR($$FUNC^%HD("200B"))GTM>S S=$CHAR(26032)_NG_$CHAR(26376) 
GTM>W STR
新​月
GTM>W $ZWIDTH(STR)
4
GTM>

GTM> W $ZWIDTH("Get ready to celebrate the new year in Shanghai")
47
GTM>S A="新年好"
GTM>W "123456",!,A
123456
新年好
GTM>W $ZWIDTH(A)
6

For complete description and UTF-8 mode examples, refer to the Cursor Position Variable section earlier in this document.

$ZPATN[UMERIC] is a read-only intrinsic special intrinsic variable that determines how GT.M interprets the patcode “N” used in the pattern match operator. With $ZPATNUMERIC="UTF-8", the patcode “N” matches any numeric character as defined by Unicode™. With $ZPATNUMERIC="M", GT.M restricts the patcode “N” to match only ASCII digits 0-9 (that is, ASCII 48-57). When a process starts in UTF-8 mode, special intrinsic variable $ZPATNUMERIC takes its value from the environment variable gtm_patnumeric. GT.M initializes the special intrinsic variable $ZPATNUMERIC to "UTF-8" if gtm_patnumeric is defined to "UTF-8". If gtm_patnumeric is not defined or set to a value other than "UTF-8", GT.M initializes $ZPATNUMERIC to "M".

$ZPATNUMERIC cannot appear on the left of an equal sign in a SET command. That is: GT.M populates it at process initialization from gtm_patnumeric and does not allow the process to change the value.

The read-only special intrinsic variable $ZCHSET takes its value from the environment variable gtm_chset. アプリケーションは、$ZCHSETの値によってGT.Mプロセスによって使用される文字セットを取得することができます。$ZCHSET can have only two values --"M", or "UTF-8” and it cannot appear on the left of an equal sign in the SET command.

Note that behavior for 7-bit ASCII characters is the same in both "M" and "UTF-8”. Customers operating in M mode are expected to use various ISO-Latin character sets.

GT.M only supports Unicode™ on Unix platforms. In OpenVMS, GT.M always gives special intrinsic variable $ZCHSET the value "M" and ignores the value of the environment variable gtm_chset even if it is defined.

$ZPROM [PT] は、ダイレクトモードの現在のプロンプトを指定する文字列の値が含まれています。デフォルトは、GTM> がダイレクトモードのプロンプトです。Mルーチンは、SETコマンドによって$ZPROMPTを変更することができます。$ZPROMPTは31バイトを超えることはできません。If an attempt is made to assign $ZPROMPT to a longer string, GT.M takes only the first 31 bytes and truncates the rest . もし31バイト目が有効なUTF-8文字の終わりではない場合、指定されたUTF-8の文字セットでは、GT.Mは完全に31バイトの制限内に収まる最後の文字の末尾に$ZPROMPT値を切り捨てます。

The MUPIP EXTRACT command adds the label "UTF-8" in the header label of the file extracted in the UTF-8 mode as follows:

GT.M MUPIP EXTRACT UTF-8

GT.M MUPIP EXTRACT

GDS BINARY EXTRACT LEVEL 
42006082413413901024002560006400000UTF-8 
GT.M MUPIP EXTRACT

GDS BINARY EXTRACT LEVEL 
42006082413413901024002560006400000GT.M 
MUPIP EXTRACT

GDSJEX03 UTF-8

GDSJEX03 

GDSJEX03 ROLLBACK PRIMARY INSTANCE1 UTF-8

GDSJEX03 ROLLBACK PRIMARY INSTANCE1

In UTF-8 mode, MUPIP LOAD triggers the LOADINVCHSET error if the header label of an extract file does not contain " UTF-8" as a suffix.

All MUPIP command qualifiers that require file names, keys, or data (for example, MUPIP SET -FILE, MUPIP INTEG -SUBSCRIPT, MUPIP REORG -SELECT qualifiers) accept characters in Unicode™ in UTF-8 mode. Database replication instance names must be ASCII. Although GT.M does not trigger an error if the name of a database replication instance is in Unicode™, FIS recommends the use of ASCII characters for naming all the database replication instances.

If the environment gtm_chset is not defined or is set to M, the MUPIP utility writes the byte-equivalent values of the globals containing characters in Unicode™ in the sequential output file. For example, if ^A has the value of 准备好庆祝新年在纽约, the sequential output file of the MUPIP EXTRACT command is:

09-OCT-2006  04:25:52 ZWR
GT.M MUPIP EXTRACT
^A=""_$C(135,134)_""_$C(135)_"好"_$C(134)_""_$C(157)_""_$C(150)_"?年"_$C(156)_"?纽约"_$C(128,130)

In both modes, if EXTRACT encounters an illegal character, it places $ZCH representation in the sequential output file.

	MUPIP EXTRACT or MUPIP LOAD respectively produce and accept only abbreviated forms of $CHAR() and $ZCHAR(), that is, $C() and $ZCH() .

dse dump -block=9
File    /home/V52/mumps.dat
Region  DEFAULT
Block 9   Size 24   Level 0   TN 9 V5
Rec:1  Blk 9  Off 10  Size 14  Cmpc 0  Key ^DD
      10 : | 14  0  0  9 44 44  0  0 E5 A4 AA E9 98 B3 E7 9A 84 E5 B9 B4|
           |  .  .  .  .  D  D  .  .       太       阳       的       年|

However, in M mode, DSE DUMP print dot characters for all non-ASCII characters and malformed characters.

In UTF-8 mode, DSE and LKE accept characters in Unicode™ in all their command qualifiers that require file names, keys, or data (such as DSE -KEY, DSE -DATA and LKE -LOCK qualifiers).

LKE SHOW now represents canonical numeric subscripts without quotes.

GTM>l ^A(1)
GTM>zsy
$ lke
LKE> show -all
DEFAULT
^A(1) Owned by PID= 8102 which is an existing process
LKE>GTM>l ^A(1) 

GT.M の %UTF2HEX ユーティリティは、UTF-8でエンコーディングされたGT.M文字列の内部エンコーディングのバイトの16進表記で返します。このルーチンは、対話的または非対話的のどちらの使用でのエントリポイントがあります。

DO ^%UTF2HEX converts the string stored in %S to the hexadecimal byte notation and stores the result in %U.

DO INT^%UTF2HEX converts the interactively entered string to the hexadecimal byte notation and stores the result in %U.

$$FUNC^%UTF2HEX(s) returns the hexadecimal byte representation of the character string s.

GTM> SET %S=”AÄB”
GTM> DO ^%UTF2HEX
GTM> ZWRITE %U
%U=”41C38442”
GTM> W $$FUNC^%UTF2HEX(“ABC”)
414243
GTM>

GT.Mの %HEX2UTFユーティリティは、16進表記で指定されたバイトストリームからGT.MのUTFエンコードの文字列へ変換します。このルーチンは、対話的または非対話的のどちらの使用でのエントリポイントがあります。

DO ^%HEX2UTF converts the hexadecimal byte stream stored in %U into a GT.M character string and stores the result in %S.

DO INT^%HEX2UTF converts the interactively entered hexadecimal byte stream into a GT.M character string and stores the result in %S.

$$FUNC^%HEX2UTF (s) returns the GT.M character string given the hexadecimal byte stream representation in s.

GTM> SET %U=”41C3A441”
GTM> DO ^%HEX2UTF
GTM> ZWRITE %S
%S=”AäA”
GTM> W $$FUNC^%HEX2UTF(“414243”)
ABCS
GTM>

Although the M standard patcodes (A,C,L,U,N,P,E) are extended to work with Unicode™, application developers can neither change their default classification nor define the non-standard patcodes ((B,D,F-K,M,O,Q-T,V-X) beyond the ASCII subset. これは、パターンテーブルより大きいコードの文字が含まれていないことを意味します最大ASCIIコード127。

In GT.M, strings are not implicitly normalized. Unicode™ normalization is a method of computing canonical representation of the character strings. Normalization is required if the strings contain combination characters (such as accented characters consisting of a base character followed by an accent character) as well as precomposed characters. The Unicode™ standard assigned code-points to such precomposed characters for backward compatibility with legacy code sets. For the applications containing both versions of the same character (or combining characters), Unicode™ recommends one of the normal forms. Because GT.M does not normalize strings, the application developers must develop the functionality of normalizing the strings, as needed, in order for string matching and string collation to behave in a conventional and wholesome fashion. In such a case, edit checks can be used that only accept a single representation when multiple representations are possible.

At process start-up, GT.M implicitly OPENs $PRINCIPAL before any application code is executed, using the encoding specified by $gtm_chset. $PRINCIPAL is never OPENed by any application code. ichset, ochset and chset device parameters are characteristics of the OPEN command rather than the USE command, since an IO device cannot conveniently switch encoding in mid-stream. Therefore, the character set of $PRINCIPAL is determined for the process, and cannot be changed.

One implication of this restriction on $PRINCIPAL (including Terminal, Sequential File and Socket devices) is that UTF-16, UTF-16LE and UTF-16BE encodings are never supported for $PRINCIPAL.

Due to the uncommon usage and lack of support for UTF-16 by UNIX terminals and terminal emulators, GT.M does not support UTF-16, UTF-16LE and UTF-16BE encodings for Terminal I/O devices. Note that UNIX platforms use UTF-8 as the defacto character encoding for Unicode™. The terminal connections from remote hosts (such as Windows) must communicate with GT.M in UTF-8 encoding.

GT.M has no facility for a translation of product error messages or on-line help into languages other than [American] English. All error message text (except the messages arguments that could include Unicode™ data) is in the [American] English language.

GT.M does not check for illegal characters in a string before passing it to an external routine or in a returned value before assigning it to a GT.M variable. This is because such checks add parameter-processing overhead. The application must ensure that the strings are in the encoding form expected by the respective routines. More robustly, external routines must interpret passed strings based on the value of the intrinsic variable $ZCHSET or the environment variable gtm_chset. The external routines can perform validation if needed.

The maximum length of an M identifier is restricted to 31 bytes. Since identifier names are restricted to be in ASCII, programmers can define M names up to 31 characters long.

The maximum length of an M string is restricted to 1,048,576 bytes. Therefore, depending on the characters used, the maximum number of characters could be reduced from 1,048,576 (1M) characters to as few as 262,144 (256K) characters.

The maximum length of a program or indirect source line is restricted to 2,048 bytes. Application developers must be aware of this byte limit if they consider using multi-byte source comments or string literals in a source line.

The maximum allowed size for database keys (both global and nref keys) is 255 bytes, and for database records is 32K bytes. Application developers must be aware that the keys or data containing multi-byte characters in Unicode™ are limited at a smaller number of characters than the number of available bytes.