<<< I wonder, how you could compile this program, when it's not
syntactically correct? >>>

I changed no coding from the existing functioning program which I used to
clone my program. What I typed as an example was from memory, not sitting
in front of the program. If the parentheses don't need to be there, blame
my faulty memory. I have not coded a COBOL program since 2003 when I last
worked at a COBOL-only shop. `They` mean it when `they` say "use it or lose
it".

Thanks for the note.



Robert Munday
Munday Software Consultants
Montgomery, AL
On assignment in Jacksonville, FL


-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of RMiklos@xxxxxx
Sent: Friday, August 07, 2009 3:51 AM
To: COBOL Programming on the iSeries/AS400; RMunday@xxxxxxxxxxxxx
Subject: Re: [COBOL400-L] Identifier Does Not Exist

Hi,

If I try to code what you posted in SEU I get errors like

Message ID . . . . . . : LNC1349 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic

Message . . . . : Data-name, literal, or constant expected; '(' found.
Statement or clause ignored.
Cause . . . . . : A data-name, literal, or constant was expected and not
found.
Recovery . . . : Specify a valid data-name, literal, or constant.

and I cannot save this source in SEU.

However, WDSC warns with
LNC1349E Data-name, literal, or constant expected; '(' found. Statement or
clause ignored.
and allows saving this source. But the compilation with CRTBNDCBL failes
with messages like
MSGID: LNC1349 SEVERITY: 30 SEQNBR: 002100
Message . . . . : Data-name, literal, or constant expected; '('

I wonder, how you could compile this program, when it's not syntactically
correct?

Don't use parentheses after VALUE, instead use this

05 Parm-Field-One.
10 Subfield-One Pic X(10) Value "PROGRAM".
10 Subfield-Two Pic X(10) Value "*LIBL".
10 Subfield-Three Pic X(10) Value "*ALL".



From:
"RWMunday" <rwmunday@xxxxxxxxxxxxx>
To:
"'COBOL Programming on the iSeries/AS400'" <cobol400-l@xxxxxxxxxxxx>
Date:
07.08.2009 02:57
Subject:
[COBOL400-L] Identifier Does Not Exist
Sent by:
cobol400-l-bounces@xxxxxxxxxxxx



Greeting from sunny Florida.


I'm a trained but infrequent COBOL programmer working in a multilingual
shop. I must utilize a routine to get a sequence number from a data queue
which was written in 1993 and has no documentation. I attempted to
rewrite
it in RPG /Free but gave up and tried a different approach... modify an
existing functioning COBOL program and call it from my RPG program. By
copying out only the routines I needed, I've created a program which does
precisely what is necessary to get this number from the data queue. My
problem is that it doesn't work and gives a really nasty error when one of
the internal routines makes a call to an outside program and passes parms.
While running it through debug and checking the values of each field each
step of the way, I discovered that elements of the parms in the offending
call `do not exist`. They are arranged thus:

05 Parm-Field-One.
10 Subfield-One Pic X(10) Value("PROGRAM")
10 Subfield-Two Pic X(10) Value("*LIBL")
10 Subfield-Three Pix X(10) Value("*ALL")

When I run the program through debug, subfield one is blank and the other
two list as "Identifier Does Not Exist". I thought it may have been the
positioning of subfields two and three but I have another parm field with
four elements... it finds one and four but two and three do not exist.

My clone has all of the necessary elements of the original which works.
Why
would 10 level defined fields not be available to my program?

If you reply after 7am eastern Friday, please write to me at
RMunday@xxxxxxxxxxxxx as I do not have access to online e-mail at work
(company directive).

Thanks,



Robert Munday
Munday Software Consultants
Montgomery, AL
On assignment in Jacksonville, FL


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