Hi Edmund,

The 31s0 data type is a historical thing. Now it is impossible to change
the procedure interface without breaking binary backward compatibility.
RPGUnit from "lacton" is were the history of RPGUnit began:

https://sourceforge.net/projects/rpgunit/?source=directory

https://sourceforge.net/p/rpgunit/feature-requests/3/
No response to my posting from 2014-08-25.

https://sourceforge.net/p/rpgunit/discussion/608727/thread/6c55c5fd/
No response to my posting from 2012-05-15.

https://sourceforge.net/p/rpgunit/discussion/608727/thread/09367a0d/
Mihaels's opinion regarding the project activity from 2017-12-14.

Then Mihael Schmidt forked the RPG code because there was no response
from the original developer and he assumed the project is dead. Mihael
basically added the user space interface to integrate RPGUnit into
RPGNextGen. He called the utility ILEUnit but never made the plug-in
portion available:

https://sourceforge.net/projects/ileunit/?source=directory

I do not remember the details, but Mihael passed his plug-in code (used
in RPGNextGen) to me for whatever reasons (that I do not remember). I
refactored some aspects in the RPG code and greatly enhanced the
plug-in. Basically I fixed some quick & dirty RPG things and I improved
the user space interface to get more information back into RDi. Next I
spend a lot of work in making the RPG code more robust when it comes to
unexpected runtime errors. Last but not least I translated the plug-in
to German and added the help pages. I called the utility iRPGUnit:

https://sourceforge.net/projects/irpgunit/?source=directory

Now the idea is to join ILEUnit and iRPGUnit again. I hope that we get
it done until the end of the year. I have a whole bunch of other ideas
what to do in Summer and Autumn.

You can already compare DATE, TIME and TIMESTAMP values using the pure
assert() procedure:

assert(actualDate = expectedDate: errorMsg);

But of course it is not a big deal to add special procedures for that.
People may add a feature request if they are interested in that.

Comparing UCS data, however, is a good idea, although you can also use
assert() for it. People may also add a features request for that.

Thomas.

Am 10.05.2018 um 06:53 schrieb Edmund Reinhardt:
Thanks Thomas
I appreciate the tip about the new location of RPGUNIT, I will inform the
folks at COMMON about it.

One thing that appears to be missing.
The current assert for numerics does not ever test decimals and packed
numbers could be much larger now..
D iEqual pr extproc('iEqual')
D expected 31s 0 const //<------ why limit
decimals to 0 and length to only 31
D actual 31s 0 const
D fieldName 64a const varying options(*nopass:
*omit)

As a future thought, it would be useful to compare date, time and
timestamps and UCS data.



----- Original message -----
From: Tools/400 <thomas.raddatz@xxxxxxxxxxx>
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Cc:
Subject: Re: [WDSCI-L] "Run RPG Unit Test" prompt?
Date: Wed, May 9, 2018 1:07 PM

Hi Edmund,

Thank you for your kind words about RPGUnit. I really think that it is
worth a try. Thank you for promoting it.

I wished I could debug the problem Justin has. I have no idea what the
problem could be, because the plug-in uses the same RPG code as
RUCALLTST on a 5250 command line. Really annoying.

By the way the plug-in has been moved to SourceForge at:

[1]https://sourceforge.net/projects/irpgunit/

Last but not least Mihael Schmidt and I joined out unit test utilities
because both utilities came from the same basis.

Thomas.

Am 08.05.2018 um 19:29 schrieb Edmund Reinhardt:
> Hi Thomas
> When I set an SEP on SRVPGM that I am using your integrated RPGUNIT
action
> on, it seems to hang. This happens in both Debug or Code Coverage
mode.
> I can certainly send you my trivial example here. (Barbara and I
are
> giving a talk on TDD for COMMON and we will be featuring your
RPGUNIT in
> the talk. Great work, by the way).
>
> So where do I find the setting to " Debug: Enforce new connection"
> Thanks
> Edmund
>
>
> ----- Original message -----
> From: Thomas Raddatz <thomas.raddatz@xxxxxx>
> Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
> To: "Rational Developer for IBM i / Websphere Development Studio
Client
> for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
> Cc:
> Subject: Re: [WDSCI-L] "Run RPG Unit Test" prompt?
> Date: Tue, May 8, 2018 5:29 AM
>
> Justin,
>
> I do not have our emails at my hands, because I am in the office.
> Therefore I do not know how we ended up. Did we end up that it is
> impossible to create a tiny test service program that I can call
to
> debug the problem? Otherwise I would love to debug the problem.
>
> I assume that you could not debug it using a SEP, right? But did
you use
> a second workspace for setting the SEP or did you check option
"Debug:
> Enforce new connection"? What was the problem that you could not
debug
> it.
>
> You need to start RDi with a different workspace when using SEPs
for
> debugging RPGUnit _or_ you need to check option "Debug: Enforce
new
> connection".
>
> Thomas.
>
> -----Urspr**ngliche Nachricht-----
> Von: WDSCI-L [[1][2]mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im
Auftrag von
> Justin Taylor
> Gesendet: Mittwoch, 2. Mai 2018 22:46
> An: Rational Developer for IBM i / Websphere Development Studio
Client
> for System i & iSeries
> Betreff: Re: [WDSCI-L] "Run RPG Unit Test" prompt?
>
> I've already worked with the plugin dev, and he gave up on
finding a
> fix. I'm just trying to work around it.
>
> I decided to check the jobname at the start of the test, and if
it's
> running from RDI just have the troublesome test fail right off
the bat.
> I still can't do that test in RDi, but I can run the others
within the
> *SRVPGM.
>
> Thanks
>
> -----Original Message-----
> From: Ken Killian [[2][3]mailto:kkillian@xxxxxxxxxxxx]
> Sent: Wednesday, May 02, 2018 3:20 PM
> To: Rational Developer for IBM i / Websphere Development Studio
Client
> for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
> Subject: Re: [WDSCI-L] "Run RPG Unit Test" prompt?
>
> Justin,
>
> I have been using RPG-UNIT for about 1-year. Still learning it...
>
> But, you might want to check your preferences for RPG-UNIT.
>
> I have this for my preferences:
> Run order..........................: *API Library
> List.......................: *CURRENT Reclaim
> resources..................: *NO Product
library....................:
> RPGUNIT
> Check Test Suite Service Program...: *NONE <-- I do not use the
naming
> standard
> Enforce new connection (Check-box is CHECKED) Position editor to
line of
> assertion(source must be compiled with option *SRCSTMT)
>
> I usually put an S.E.P on my RPG-UNIT test case program. And it
pops up
> in debug. When I check the properties on the job, I can see what
job it
> "spawned off". In my example it did this job: Process ID
> 094249/QUSER/QZRCSRVS
>
> Then I can do the WRKJOB Process ID 094249/QUSER/QZRCSRVS to look
at the
> job-log. To see what the problem.
>
> For me, it is usually my library list is wrong, or I am missing a
> program in my test environment.
>
> Often, I discover that I have record-lock, or one our data-queues
is
> overloaded. It is NOT monitor regularly on our test system.
>
> I learn a lot by looking at the job log.
>
> So, I recommend looking at the job log for a start of your
issues. I
> often do the Green Screen RPGUNIT command: RUCALLTST. And see it
works
> that way. And then I debug it in RDI and check why it does not
run
> inside of RDI. For me, it is usually the setup of the
library-list.
>
> My library-list ISSUES have almost been 100% eliminated. I have
my user
> profile use a job-description for my library-list. So, my Green
Screen
> and RDI session use the exact same library-list! To me that is
the way
> to do it!
>
> Best of luck to you! See what the job log shows you...
>
> Oh yeah, don't forget to check the error log too!
> Alt+Shift+Q, and then "L"=Log
>
> -Ken Killian-
>
> --
> 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:
> [3][4]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
> [4][5]https://archive.midrange.com/wdsci-l.
> --
> IMPORTANT NOTICE:
> This email is confidential, may be legally privileged, and is for
the
> intended recipient only. Access, disclosure, copying,
distribution, or
> reliance on any of it by anyone else is prohibited and may be a
criminal
> offence. Please delete if obtained in error and email
confirmation to
> the sender.
>
> --
> 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:
> [5][6]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
> [6][7]https://archive.midrange.com/wdsci-l.
>
>
>
>
> References
>
> Visible links
> 1. [8]mailto:wdsci-l-bounces@xxxxxxxxxxxx
> 2. [9]mailto:kkillian@xxxxxxxxxxxx
> 3. [10]https://lists.midrange.com/mailman/listinfo/wdsci-l
> 4. [11]https://archive.midrange.com/wdsci-l
> 5. [12]https://lists.midrange.com/mailman/listinfo/wdsci-l
> 6. [13]https://archive.midrange.com/wdsci-l
>

--
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: [14]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 [15]https://archive.midrange.com/wdsci-l.




References

Visible links
1. https://sourceforge.net/projects/irpgunit/
2. mailto:wdsci-l-bounces@xxxxxxxxxxxx
3. mailto:kkillian@xxxxxxxxxxxx
4. https://lists.midrange.com/mailman/listinfo/wdsci-l
5. https://archive.midrange.com/wdsci-l
6. https://lists.midrange.com/mailman/listinfo/wdsci-l
7. https://archive.midrange.com/wdsci-l
8. mailto:wdsci-l-bounces@xxxxxxxxxxxx
9. mailto:kkillian@xxxxxxxxxxxx
10. https://lists.midrange.com/mailman/listinfo/wdsci-l
11. https://archive.midrange.com/wdsci-l
12. https://lists.midrange.com/mailman/listinfo/wdsci-l
13. https://archive.midrange.com/wdsci-l
14. https://lists.midrange.com/mailman/listinfo/wdsci-l
15. https://archive.midrange.com/wdsci-l



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