Re: Compilation errors

Thanks for the clarification ,

but this program was an attempt to achieve followings:-

"This program is designed to perform program call tracing in an RPGLE (RPG
IV) program. Here's how it works:

1. The program declares three procedure interfaces for SubprogramA,
SubprogramB, and SubprogramC. These are external programs that will be
called later in the code.
2. The program defines constants for the names of SubprogramA,
SubprogramB, and SubprogramC.
3. The program calls SubprogramA, SubprogramB, and SubprogramC one after
the other.
4. An output file DDS (Data Description Specification) is defined using
a data structure named CallDetails. This file will store information about
the program calls made during the tracing process.
5. The program defines a driver program name and initializes a reference
list and a counter for the number of references found.
6. The program calls the subprocedure CallProgramReferences, passing the
reference list, number of references, and driver program name as parameters.
7. Inside the CallProgramReferences subprocedure, the current program
name is added to the reference list. Then, the QBNRPRV API is called to
retrieve program references for the current program.
8. The subprocedure traverses through the received programs and
recursively calls itself for each program, retrieving program information
and storing it in the reference list.
9. After the recursive calls are complete, the subprocedure updates the
length of the reference list.
10. Finally, the program displays the referenced programs in the
reference list. If there are no referenced programs, it displays a message
indicating that no references were found.

Essentially, this program helps trace program calls and builds a list of
referenced programs in an RPGLE environment."


But since it's giving compilation errors, so I'm unable to get desired
results from it, any suggestions to get rid off these compilation errors in
terms of any modified program for the same version which could achieve
desired functionality would be greatly appreciated.


Thanks a lot..


On Thu, 22 Jun 2023 at 19:27, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 6/22/2023 9:10 AM, tim ken wrote:

Thanks for these inputs and this was compiled successfully but when it

was

used with my main program as mentioned in this link then again got these
many compilation errors:-

https://code.midrange.com/935667cdc4.html

This is an entirely different program to the one I responded to. It's
really difficult to help with a moving target.

May I suggest that you get a simple program compiled, tested, and
working to your satisfaction. Then add/change one thing. Introduce new
concepts one at a time, rather than many all at once.

Also what does this mean here "As an aside, chgjob log(0 0 *nolist) tends
to stop useful messages from
getting into the job log. As a beginner, try log(4 0 *seclvl) to get the
maximum amount of information possible."

The first command in the snippet you posted was chgjob log(0 0 *nolist).
Why did you execute that command, what was your goal, what end result
did you want to achieve?

Does it mean while compiling and executing the 'Create Bound RPG

Program

(CRTBNDRPG)' command which is used to compile the program mentioned in

the

above link, is there some parameter which needs to be set specifically
here? was it meant for Generation severity level . . . GENLVL

10

which is by default set while compiling this program as '10'?

No. CHGJOB LOG(...) is about what messages go into the job log, and does
not relate to any other commands you might run in that job.

--
--buck

http://wiki.midrange.com
Your updates make it better!


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.