Re: The value of *MSG in a CL Program -- MIDRANGE-L

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

Subject: Re: The value of *MSG in a CL Program
From: mlazarus <mlazarus@xxxxxxxxxxxx>
Date: Sun, 28 Jun 2020 23:59:16 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Don,

CL generally does not require quotes for an uppercase constant comparison.

-mark

On 6/28/2020 10:48 PM, Don Brown via MIDRANGE-L wrote:

I came across this line of code in a program and I have not been able to
find any documentation for it.

DCL VAR(&XXX) TYPE(*CHAR) LEN(4)

IF COND(&XXX *EQ *MSG) THEN(DO)

The program is called with a value of '*MSG' for the variable&XXX

There are no quotes around the *MSG

Have you seen this before ?

Don

As an Amazon Associate we earn from qualifying purchases.

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.