Add Case Conversion to RPG Subprocedure Parameters

IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this request.

Hi Barbara,
Yes, you are correct. My procedure only handles data without any special characters. In our case, that has been enough but, if we had to worry about any special characters then, I would write a procedure around the QlgConvertCase API and go from there. That's my approach to this particular problem.

Marina, your procedure will work for data, but it would not handle a name like "Bergström". That would get uppercased as "BERGSTRöM" if you only handle A-Z.

The requested option to handle this with the OPTIONS keyword would handle all the characters for the LANGID of the job, and the name would be uppercased as "BERGSTRÖM".

But your point is well taken, since you could easily call the QlgConvertCase API from your procedure, and it would handle all the characters in the LANGID of your job.

I understand maybe not wanting to have to manipulate the case of the input parameters but, this is easily handled with creating procedures in a service program and then just call them as soon as you enter your procedure.

For example, I have my ToUpperCase and toLowerCase procedures that we use all of the time.

dcl-c Uppercase const('ABCDEFGHIJKLMNOPQRSTUVWXYZ');
dcl-c Lowercase const('abcdefghijklmnopqrstuvwxyz');

dcl-proc toUpperCase export;

dcl-pi *n varchar(64000);
data varchar(64000) value;
end-pi;

dcl-s newData varchar(64000);

newData = %xlate(Lowercase:Uppercase:data);

return newData;

end-proc;

dcl-proc toLowerCase export;

dcl-pi *n varchar(64000);
data varchar(64000) value;
end-pi;

dcl-s newData varchar(64000);

newData = %xlate(Uppercase:Lowercase:data);

return newData;

end-proc;

Then just call them as you need them

toLowerCase( input); or toUpperCase( input )

The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

Therese Eaton – CEAC Program Manager, IBM

Thanks Barbara. Glad to have comments from people who know, vs people who apparently just want to make their knowledge of the obvious known to others.

KristerK, RFE is related to 92793, but the two RFEs are different. RFE 92793 is about new built-in functions %UPPER and %LOWER. This RFE is about an option for prototyped parameters to automatically perform upper or lower casing for the parameter.

Isn´t this duplicate of this request?
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=92793

Or something like this

if %xlate('xml' : 'XML': extension ) = '.XML';

It handles the situation where extension contains the strings .XML, .xml, .XmL etc.

Why do you need a workfield for this ?

Just write a wrapper (which I did day one procedures became available) around QlgConvertCase so you can code;

If Uppercase(myParm) = '*PRINT';