Peter,
Perhaps you meant "PTC Implementer"? David Gibbs can speak to that.
In general, I think that what you described is pretty much how most, if not all, of the change management products in the IBM i space, would handle that scenario ...?
I do not think S/36 SSP ever had a "debugger" -- at least, not from IBM.
Hope that helps,
Mark S. Waterbury
On Friday, March 27, 2020, 8:09:18 PM EDT, Peter Dow <petercdow@xxxxxxxxx> wrote:
I've just recently started using RDi (v9.6.0.6) and I have a couple of
questions.
1. RDi and PK Implementer. The PK Implementer set up I'm working with
has my environment, a QA environment, and then production. I check
something out, modify it, compile it, then promote it to QA to test (no
real data in my environment for testing), and if all goes well, it gets
promoted to production.
The issue I have with that is using RDi to debug a program that's in QA,
which is where the main testing occurs. If I do that, it's kind of a
pain to have to switch back to Implementer, reject the program back from
QA to my environment, re-open it in RDi, fix it, promote it, re-open it
in RDi in QA, etc. Is there a better way?
2. I haven't tried this yet, but when debugging, does RDi have the
ability to display the values of the key fields in a key list by
hovering over the key list name? I remember being able to do that back
on the S/36 (I think) and losing it when the S/38 and following machines
came along.
--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
midrange.com
