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



I always mark changes to my CL's with a project number beginning in position one [1] of the CL line, thus: /*1459*/ . If one prompts on the command while entering/changing CL and puts the /*1459*/ in the 'Comment' line, it puts the mod-mark at the end of the command; effectively, in my view, hiding it.

Anyway, if I read Simon correctly, the parser must be assuming the position zero [0] as the preceding blank space.

In the interest of full disclosure, real comments (aka documentation) are either put at the end of the command line (if brief) or on lines preceding the command if lengthy (which is usually the case - when I get anal and actually document).

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Tuesday, December 15, 2009 2:23 PM
To: Midrange Systems Technical Discussion
Subject: Re: Parsing CL comments


On 16/12/2009, at 6:52 AM, Dennis Lovelady wrote:

WRKOBJ MYOBJ/*Shows a list of objects of name MYOBJ*/

I thought I had tried this same form yesterday hence the third example
in my previous append but after seeing Charles' earlier response I
tried again and it failed with a syntax error. Your example above also
fails.

CPD0011 Qualifier missing from qualified name 'MYOBJ* '.
CPF0001 Error found on *N command.

The first /* must have either a leading or trailing space to be
considered a start of comment flag. Since a space starts a new token
and a space is not valid in a parameter value (unless quoted) then a
parser can "know" that a comment is not allowed at that point and
therefore interprets the /* as the start of a qualified name. Note
that when examining the above message the complaint is about missing
data after the closing slash which indicates that parser has accepted
the /*Shows as a valid qualifier for the first MYOBJ and has accepted
each of the remaining words as valid tokens. Thus this error must
occur very early in the parsing sequence before validation of the
tokens themselves occurs.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.