Greg,
I am a visual sort of guy, so here is a screen shot:
https://imgur.com/a/M368XnP
This is sort of a simple dummy Test-Case program with 100% Bogus "ASSERT" statements.
(
http://rpgunit.sourceforge.net/) Read as "Assert that is this true..."
So, I am using the Method: "assert", as I phrase to my Microsoft co-workers. Or was we IBM i developers call it "Procedure". <LOL>
When I try to create the "DLL" for my Microsoft co-workers, or as we call it a "Service-Program". The creation failed! :(
But, I have the full information in the view: "Command Log". Just like I look at the command log on the Green "DOS" screen. <smirk> 5250 emulation. <smirk>
So, I do NOT have to leave my beloved RDI, to see my creation errors!<Joy Joy> This has been around since the old WDSC days. Nothing new! <Big Goofy Grin>
Here are my top errors that I miss on creating a service program:
1.) Forgetting to use "export" for procedures in Service program. If they are not INTERNAL only Procs.
2.) Forgetting to include proper binding directories to include all my service programs.
So, as my mentor would always tell me. Look at the job-log to examine for errors. Still here him whispering in my ear! <Big Smile>
So, now you know you can use the Command-View to view your compile statements.
I like to clear the erase to clear the "Command view" before I do my creation. Just saves me time from a lot of scrolling.
RDI knowledge is power, and certainly better than SEU!
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Wednesday, August 29, 2018 11:48 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Compiling a locked display file
Ken,
Can you elaborate on how to see binding errors? I have a PMR opened with IBM now regarding this. I can never see the actual message - the joblog does not get created in my spooled file unless I compile from the green screen.
Greg
midrange.com
