× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I have a pgm ProperCase to change an UPPER-CASE string to Mixed-Case.

For example, "123 ELM ST" changes to "123 Elm St"

The field that I want to pass as a parm may be different lengths for example

CUST-NAME PIC x(50).

CUST-ADDRESS-1 PIC X(30).


I have been coding as follows:

move CUST-ADDRESS-1 of CUST-FILE to ws-string
call 'ProperCase' using ws-string
move ws-string to PRINT-LINE.



I would much prefer to do something like

Move ProperCase (CUST-ADDRESS-1) to PRINT-LINE

/|\
|
|------subprocedure name



Is this possible?



Surely not, but

My next choice, to make fewer lines of code and thus more readable code, would be to

move CUST-ADDRESS-1 to PRINT-LINE
call 'ProperCase' using PRINT-LINE

Problem is that in the pgm ProperCase, the parm is defined as very long x(1000) to accommodate a long string. But when I make this call, it wipes out everything in memory past the field that I am passing as a parm.

Any way to avoid this?

Thanks!

______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.