Ken,
Thanks for the explanation as well as the picture. However, that is not the case for me.
I usually have all my procedures inside of a service program... I always use a binding directory. If I include the copy source for the prototypes, but forget to include the binding directory in the CTL-OPT, I get a simple error in the Command View:
CRTSQLRPGI OBJ(ASTHHOBJ/CIT100) SRCFILE(HHPIFSRC/QRPGLESRC) SRCMBR(CIT100) COMMIT(*NONE) OPTION(*EVENTF) RPGPPOPT(*LVL2) REPLACE(*YES) DBGVIEW(*SOURCE)
Program CIT100 in library ASTHHOBJ not created.
Cause . . . . . : Program CIT100 could not be created in library ASTHHOBJ. Display the job log (using the DSPJOBLOG command) to determine why the program could not be created. Recovery . . . : Correct the errors and try the request again.
Compilation failed. Program CIT100 not created in library ASTHHOBJ.
Cause . . . . . : Compilation failure normally occurs when the severity of issued messages exceeds the value specified for the GENLVL parameter on the CRTBNDRPG command. See the compiler listing or the job log for error messages. Recovery . . . : Correct the errors or change the value specified for the GENLVL parameter. Compile again.
I cannot find the job log anywhere (including my spool file). Evidently, compile failures in RDi do not create job logs??
Greg
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Wednesday, August 29, 2018 12:53 PM
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
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
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
midrange.com
