Re: [Bulk] CCSIDs and command parameters

Tim:

You can code CCSID(*UTF16) on any command parameter of type *CHAR or *PNAME and the system will automatically translate the value to UTF16 for you, before passing the value to your program. Then, you can convert from UTF16 to whatever CCSID you want...? e.g.:

PARM KWD(PARM1) TYPE(*CHAR) LEN(10) CCSID(*UTF16)

(That's been supported since at least V5R4 ...)

HTH,

Mark S. Waterbury

> On 5/5/2016 11:03 AM, Tim Bronski wrote:

We have some emailing commands that can be used interactively or compiled into programs. A parameter of these commands includes an email address which has the @ character which doesn't map to the same code point in certain EBCDIC CCSID's. When the command is used interactively it can be presumed that the job ccsid can be used for the parameter value. When the command is used in a compiled CL and the parameter is initialized or has a hard coded value then the ccsid depends on the ccsid of the source file. The issue I have is not being able to know for sure what the ccsid of the passed value is. We currently make a best guess based on the options for @ but has anyone got a better way?

Tim