RE: The value of *MSG in a CL Program

["Hiebert, Chris" <chris.hiebert@xxxxxxxxxxxxxx>]

Don, I'd suggest making sure to wrap all those values with quotes. 
Because it could lead other into falling for the *BLANKS trap.

In the past I've come across CLLE programs with 
> IF         COND(&XXX *EQ *BLANKS) THEN(DO)

Which does NOT check for blanks like:
> IF         COND(&XXX *EQ ' ') THEN(DO)

It works like this how Scott mentioned below and checks for the value "*BLANKS" within the field.
> IF         COND(&XXX *EQ '*BLANKS') THEN(DO)


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Scott Klement
Sent: Monday, June 29, 2020 9:40 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: The value of *MSG in a CL Program

Don,

Coding COND(&XXX *EQ *MSG) is identical to coding COND(&XXX *EQ '*MSG')
-- they do exactly the same thing.

-SK


On 6/28/2020 9: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