Ooops....Sorry, hit the ENTER key to quickly :(

Actually, I think the Cobol committee permitted user-defined functions
in the last draft standard - at least in the copy that I have:

Reference number of working document: ISO/IEC/JTC 1/SC 22/WG 4 N 0147
Date: 2001-12-04
Reference number of document: ISO/IEC IS 1989:2001
Section 8.4.5.6

Not sure how many compiler vendors took advantage of it, but I know that
it doesn't exist in the iSeries compilers.

Terry

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, June 27, 2012 11:04 AM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] CALLing other pgms - what is a good
method of handling different parm lengths


On 2012-06-27, at 10:20 AM, Stone, Joel wrote:

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?


Nope - sadly when the COBOL gods introduced functions they
never went beyond the equivalent of RPG BIFS - no way to
write your own. If you wanted simple upper-casing for example
you could do this:

move function upper-case(CUST-ADDRESS-1) to PRINT-LINE.

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 would do the same in RPG surely? or are you using a
varying string? I think ProperCase needs to be modified to
take the length of the field it is handling. Then it could
constrain its operation to the defined length. Simple pass
the "length of" value to make sure the length is accurate.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

Confidentiality Notice:

The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.




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-2021 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.