ibm-information-center/dist/eclipse/plugins/i5OS.ic.nls_5.4.0.1/rbagsccsidmsgsup2.htm

169 lines
13 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="CCSID support for messages" />
<meta name="abstract" content="Use CCSID support for handling messages and message catalogs on i5/OS." />
<meta name="description" content="Use CCSID support for handling messages and message catalogs on i5/OS." />
<meta name="DC.Relation" scheme="URI" content="rbagsccsidsyssupport.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsobjlevccsidmesghand.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsmessagelevelccsid.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsmsgdescriplevelccsid.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsmsgqueuesccsidsupport.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsjobmsgqueccsidsuprt.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagssysreplstccsidsuprt.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagshistlogccsidsuprt.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagssetmsghandccsidsup.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsmsgcatccsidsup.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsconcharrepdtatypef.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsretmsgcomapiccsidsup.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsrecmsgcomapissup.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagshandmsgccsidsupquest.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsprogrammessagedesign.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsccsiddispfilesup.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/crtmsgf.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/crtmsgq.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/chgmsgq.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/addrpyle.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/chgrpyle.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/chgmsgd.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/rtvmsg.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/rcvmsg.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/sndbrkmsg.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/sndmsg.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/sndpgmmsg.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/sndrpy.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/sndusrmsg.htm" />
<meta name="DC.Relation" scheme="URI" content="rbagsmessagecatalogs.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbagsccsidmsgsup2" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>CCSID support for messages</title>
</head>
<body id="rbagsccsidmsgsup2"><a name="rbagsccsidmsgsup2"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">CCSID support for messages</h1>
<div><p>Use CCSID support for handling messages and message catalogs on i5/OS™.</p>
<p>You can send messages tagged with one CCSID to users with a different CCSID.
You can use CCSID support to handle messages by using commands and application
programming interfaces.</p>
<div class="note"><span class="notetitle">Note:</span> You do not need a multinational character set (MNCS) when using CCSIDs
for handling messages.</div>
<p>For example, if you do not set CCSID support on, the following message,
encoded in CCSID 00037:</p>
<pre> Joe, I need to see you right away!</pre>
<p>appears to a user with CCSID 00500 as</p>
<pre> Joe, I need to see you right away]</pre>
<p>Instead of seeing an exclamation mark (!), Joe sees a right square bracket
(]). If you set CCSID support on, the text in a message encoded in CCSID 00037
is converted to CCSID 00500. Both the person sending the message and the person
receiving the message see identical text.</p>
<p>CCSID support helps preserve data integrity in messages. As you read through
this information, you will see other advantages to using CCSID support for
messages.</p>
<p>Object-level CCSIDs</p>
<ul><li>Message files <ul><li>Message-level support</li>
<li>Message description-level support</li>
</ul>
</li>
<li>Message queues</li>
<li>Job message queues</li>
<li>System reply lists</li>
<li>History log</li>
</ul>
<p>The following topics provide detailed information about message support:</p>
<ul><li>Setting up CCSID support for message handling</li>
<li>CCSID support for message catalogs</li>
<li>Converted character replacement data type field</li>
<li>Retrieve messages</li>
<li>Receive messages</li>
<li>Common questions about CCSID support for message handling</li>
</ul>
<div class="section"><h4 class="sectiontitle">Message-handling commands for CCSIDs</h4><p>The following
message handling commands support CCSIDs:</p>
<ul><li>CRTMSGF (Create Message File)</li>
<li>CRTMSGQ (Create Message Queue)</li>
<li>CHGMSGQ (Change Message Queue)</li>
<li>ADDRPYLE (Add Reply List Entry)</li>
<li>CHGRPYLE (Change Reply List Entry)</li>
<li>CHGMSGD (Change Message Description)</li>
<li>RTVMSG (Retrieve Message)</li>
<li>RCVMSG (Receive Message)</li>
<li>SNDBRKMSG (Send Break Message)</li>
<li>SNDMSG (Send Message)</li>
<li>SNDPGMMSG (Send Program Message)</li>
<li>SNDRPY (Send Reply)</li>
<li>SNDUSRMSG (Send user Message)</li>
</ul>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbagsobjlevccsidmesghand.htm">Handle messages with a specific object-level CCSID</a></strong><br />
The objects listed in this topic support CCSIDs. Each of them has an object-level CCSID.</li>
<li class="ulchildlink"><strong><a href="rbagsmessagelevelccsid.htm">Message-level support</a></strong><br />
When a message is sent to a message queue, you must communicate the CCSID of the replacement data or the immediate message text to the operating system. Use the CCSID parameter on any of the send message commands or APIs to communicate this CCSID to the operating system.</li>
<li class="ulchildlink"><strong><a href="rbagsmsgdescriplevelccsid.htm">Message description-level support</a></strong><br />
When a message description is added to a message file, the CCSID of the message text must be communicated to the operating system. These topics also discuss how the CCSID of a message description is set and how to change the CCSID of a message description.</li>
<li class="ulchildlink"><strong><a href="rbagsmsgqueuesccsidsupport.htm">Message queues</a></strong><br />
If you set CCSID processing on, system-supplied display files and printer files that display or print messages convert the CCSID of the message queue to the CCSID of the job before displaying or printing the messages.</li>
<li class="ulchildlink"><strong><a href="rbagsjobmsgqueccsidsuprt.htm">Job message queues</a></strong><br />
The CCSID for all job message queues is 65534. You cannot change or display this value. A job message queue CCSID of 65534 requires fewer CCSID conversions. Fewer CCSID conversions of text result in better performance and improved data integrity.</li>
<li class="ulchildlink"><strong><a href="rbagssysreplstccsidsuprt.htm">System reply list</a></strong><br />
The system reply list has a CCSID of 65534. You cannot change or display this value.</li>
<li class="ulchildlink"><strong><a href="rbagshistlogccsidsuprt.htm">History log</a></strong><br />
The history log is a database file that is tagged with CCSID 65535. You cannot change the CCSID of the history log. No conversions occur when you do database retrievals from the history file.</li>
<li class="ulchildlink"><strong><a href="rbagssetmsghandccsidsup.htm">Set up CCSID support for message handling</a></strong><br />
The default setting of the CCSID for creating message queues and message files is 65535. Most message files delivered with the operating system have a CCSID of 65535.</li>
<li class="ulchildlink"><strong><a href="rbagsmsgcatccsidsup.htm">CCSID support for message catalogs</a></strong><br />
The Message catalog CCSID (CLGCCSID) parameter allows you to specify the CCSID for storing data in a message catalog.</li>
<li class="ulchildlink"><strong><a href="rbagsconcharrepdtatypef.htm">Converted character replacement data type field</a></strong><br />
A replacement data type field supports CCSID processing. This replacement data type field is called a convertible character field (*CCHAR). A *CCHAR replacement data type field is a variable-length field. This field may increase or decrease in length when the field is converted.</li>
<li class="ulchildlink"><strong><a href="rbagsretmsgcomapiccsidsup.htm">Retrieve messages</a></strong><br />
The Retrieve Message (RTVMSG) command and retrieve message (QMHRTVM) application programming interface (API) have a CCSID-to-convert-to parameter. This parameter determines which CCSID the first- and second-level text is converted to before the text is returned to the user.</li>
<li class="ulchildlink"><strong><a href="rbagsrecmsgcomapissup.htm">Receive messages</a></strong><br />
The Receive Message (RCVMSG) command, the Receive Nonprogram Message (QMHRCVM) API, and the Receive Program Message (QMHRCVPM) API have a CCSID-to-convert-to parameter. This parameter determines which CCSID the text or data is converted to before it is returned to the user.</li>
<li class="ulchildlink"><strong><a href="rbagshandmsgccsidsupquest.htm">Common questions about CCSID support for handling messages</a></strong><br />
Here are some common questions asked about CCSID support for handling messages.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsccsidsyssupport.htm" title="The server provides support for CCSIDs in the functions as shown in the table.">i5/OS function support for CCSIDs</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rbagsprogrammessagedesign.htm" title="A message can be predefined or immediate.">Program message design</a></div>
<div><a href="rbagsccsiddispfilesup.htm" title="When a display file object is created, it is tagged with the coded character set identifier (CCSID) of the source file.">Display files</a></div>
<div><a href="rbagsmessagecatalogs.htm" title="The operating system can use message catalogs to store messages. Messages in a message catalog are grouped as sets. Each message has a unique number within a set. You can create a message catalog as a stream file, a source file member, or a user space object type from one or more source files.">Use message catalogs</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="../cl/crtmsgf.htm">Create Message File (CRTMSGF) command</a></div>
<div><a href="../cl/crtmsgq.htm">Create Message Queue (CRTMSGQ) command</a></div>
<div><a href="../cl/chgmsgq.htm">Change Message Queue (CHGMSGQ) command</a></div>
<div><a href="../cl/addrpyle.htm">Add Reply List Entry (ADDRPYLE) command</a></div>
<div><a href="../cl/chgrpyle.htm">Change Reply List Entry (CHGRPYLE) command</a></div>
<div><a href="../cl/chgmsgd.htm">Change Message Description (CHGMSGD) command</a></div>
<div><a href="../cl/rtvmsg.htm">Retrieve Message (RTVMSG) command</a></div>
<div><a href="../cl/rcvmsg.htm">Receive Message (RCVMSG) command</a></div>
<div><a href="../cl/sndbrkmsg.htm">Send Break Message (SNDBRKMSG) command</a></div>
<div><a href="../cl/sndmsg.htm">Send Message (SNDMSG) command</a></div>
<div><a href="../cl/sndpgmmsg.htm">Send Program Message (SNDPGMMSG) command</a></div>
<div><a href="../cl/sndrpy.htm">Send Reply (SNDRPY) command</a></div>
<div><a href="../cl/sndusrmsg.htm">Send User Message (SNDUSRMSG) command</a></div>
</div>
</div>
</body>
</html>