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



Would be interesting to know why the difference, but it does appear to be
documented:

v In a free-form definition, the file-name and format-name parameters must
be character literals or
named constants representing character literals. If a parameter is a named
constant, the constant must
be defined prior to the definition statement.
v In a fixed-form definition, the file-name and format-name parameters can
be either names or character
literals.

Charles


On Tue, Apr 15, 2014 at 4:12 PM, Kurt Anderson
<Kurt.Anderson@xxxxxxxxxxxx>wrote:

You're right. I didn't think to look at the help for Like. Though I just
did and didn't see anything about a supported second parameter. But in
trying it, it works. Looks like it only works in freeform, however.
RNF0202: A SECOND PARAMETER FOR KEYWORD LIKE IS ONLY ALLOWED IN FREE FORM.

I just found a piece of code that worked pre-freeform, but does not work
post-freeform.

Works:
D dsT_InvRptLD E DS ExtName(SpecChgP) Template
Qualified
Doesn't work:
dcl-ds dsT_InvRptLD ExtName( SpecChgP ) Template Qualified;
RNF0202: THE PARAMETER FOR EXTNAME OR EXTFLD MUST BE A DEFINED NAMED
CONSTANT OR LITERAL.

Looks like I have to use the literal now. I get more freeform, but have
to add in more caps to make it happen.
dcl-ds dsT_InvRptLD ExtName( 'SPECCHGP' ) Template Qualified;

Seems like this one took a step backwards, unless I'm missing something.



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.