×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I think I have a solution.
I did not think about the VBA macro, and I do love VBA macros, but I
think it would be more troublesome (like distributing to the team) than
what I am now thinking of trying.
I may have to resort to adding one line of code before the Exfmt to
accomplish what I want.
The one line I would add to PGM_A Unit-Tester would be a call to PGM_B.
Within PGM_B, it would extract of the name of it's *caller Pgm (PGM_A),
then a DSPPGMREF PGM_A which shows the Screen file and the one
Screen-Format in PGM_A, and then with that information and link to the
database for more info, I think I can do an ASSUME and KEEP with PGM_B's
screen so that the info that I need kept on the screen as PGM_A runs
it's unit's tests.
In theory, it should work.
But thanks for the suggestions.
========================================
from: vhamberg@xxxxxxxxxxx
I agree - try macros in PC5250 emulation.
If you record it in VBA mode, you can do some pretty hairy programming
with it.
As an Amazon Associate we earn from qualifying purchases.