×
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.
Are you coding a global level MONMSG, i.e. immediately after the variable
declarations, or is it associated with a command? If my memory serves,
global MONMSG's can't have DO structures assigned and I think they're
limited to EXEC(GOTO CMDLBL(xxxxx)).
Failing that, I'll ask the obvious question - have you checked there aren't
any extra ENDDO statements in the program?
If the MONMSG is after a command, what command are you monitoring? I'm
wondering if the command has messages that can be monitored for, and if not
whether that would have an effect on causing the compiler to ignore the
MONMSG.
Has the MONMSG statement been commented out at all?
Jonathan
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Gross
Sent: 23 July 2007 22:37
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CL Error
Jonathan:
Here's the code and compile message.
monmsg cpf0000 exec(do)
chgvar &sts 'N'
enddo
* CPD0707 30 No matching DO command for ENDDO command. ENDDO ignored.
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.