RWMunday wrote:

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?

Robert:

More info, please...

Is Parm-Field-One a LINKAGE SECTION field? I.e., is it an input or an output parm? It _looks_ like it's intended to be an output parm from your "internal routine" that you're sending to that "outside program", but I want to be sure.

Is this ILE or OPM COBOL?

Is the error encountered in the "outside program" after you issue the CALL or is it in your "internal routine" after returning from the CALL (or is the CALL statement itself that fails?)

Are you debugging your "internal routine" or the "outside program" in the debug session?

I suspect someone else will have more to say, but I might as well prompt more info to save you a little time.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.