Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.
We've got a bit of a naming issue here. We just built a CL command that allows you to translate data between CCSIDs. The idea is to allow you to translate CL variable data from one CCSID to another.
The command naming convention that we are using is CLxxxxxxx where the xxxxxxx is the real name and all the command names start with "CL" to avoid conflict when IBM "steals" the idea.
Do you, someone who codes regularly in CL, have any suggestions for a good name for this new command?
I'll give it a shot (don't know how good it is). How about CVTCCSID (Convert CCSID), or if you're prefixing with "CL", then CLCVTCCSID?
That's the name of the corresponding function (subprocedure) you'd call in RPG IV. So it is a good choice Brian.
Someone here suggested CLXLATE (CL xLate) but an issue I have with that is we already have a CLCase (CL convert case) command and the term XLATE might confuse people between case translation and ccsid translation; Not sure. Thanks for the suggestion.
Glad you liked it. The other problem with using XLATE is that people might think it refers to the same functionality as the RPG XLATE op code or function, which is entirely different than CCSID conversion.