Hi Mike,
Thank you for the follow up. I did finally find a document that describes
the history of Rational Developer for i. (And a what mess that is! No
wonder web development has taken so long for AS/400, iSeries, System I, IBM
I to catch some traction.)
RDP V7.5 was the first release of the production copy for the screen and
report designer. Wouldn't you think they would have given it a new number
like 7.6?
I has the old CODE/400 designer on my PC but when I installed RDi V7.5 it
did not find it and include it as an editor for screens. I need this in
order to make changes for Webfacing. I uninstalled and reinstalled CODE/400
and it now works.
I spent 2 solid days just to get RDi V7.5, Developer, Business Designer,
Websphere App Server, HATS and CODE/400 installed and working. Not quite
the same level of quality of product delivery that I normally expect from
IBM.
Thank you for the assist. I was able to get my first Webfacing project done
- that only took an hour. Yeah!
Pat Barrett
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of wdsci-l-request@xxxxxxxxxxxx
Sent: Thursday, March 07, 2013 3:07 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: WDSCI-L Digest, Vol 11, Issue 102
Send WDSCI-L mailing list submissions to
wdsci-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
wdsci-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
wdsci-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."
*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.
Today's Topics:
1. Re: Q: What's the difference between RDi V7.5 and RDP V7.5
(MichaelQuigley@xxxxxxxxxx)
2. Re: RDP Debug when STRDBG active (Anderson, Kurt)
3. Re: RDP Debug when STRDBG active (CRPence)
4. Latest member source changes not being retrieved (Peter Thomas)
5. Re: Latest member source changes not being retrieved
(Frank Hildebrandt)
6. Re: Latest member source changes not being retrieved (Paul Bailey)
----------------------------------------------------------------------
message: 1
date: Wed, 6 Mar 2013 15:55:54 -0500
from: MichaelQuigley@xxxxxxxxxx
subject: Re: [WDSCI-L] Q: What's the difference between RDi V7.5 and
RDP V7.5
Pat,
I don't know if your question was answered by Mike Hockings' response or
not. But RDi 7.5 was released in October 2008. IBM re-branded it to RDP
7.5 in February 2010. So RDi 7.5 and RDP 7.5 weren't the same thing.
If I recall correctly, the graphical display file editor(which is supposed
to cover the functionality of SDA) was included as a "Technology Preview"
in RDi 7.5. Again testing my memory here, but I believe RDP 7.5 included
the "DDS Design perspective" graphical display files and printer files.
I'm sure there were a few other changes, but that's the biggest one I
recall. (I was stuck on WDSC 7.0 until RDP 8.5 so I'm a little murky in
my recollection of what was in the intervening releases.)
Michael Quigley
Computer Services
The Way International
www.TheWay.org
wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/05/2013 07:52:45 PM:
----- Message from "Pat Barrett" <prbarrett@xxxxxxxxx> on Tue, 5 Mar
2013 18:47:02 -0600 -----
To:
<WDSCI-L@xxxxxxxxxxxx>
Subject:
[WDSCI-L] Q: What's the difference between RDi V7.5 and RDP V7.5
I have the IBM Rational Developer for I V7.5 installed and I am trying
to
complete a Webfacing Project. I read an article from Aug 30 2010 from
developerworks by David Dykstal saying that RDp V7.5 includes SDA and
RLU.
My version only contains the preview SDA version. I need to know if I
have
to install the old CODE/400 editor in order to make DDS changes. If
these
are the same version and I am up-to-date with updates how do I get these
2
pieces? Thanks for any help you can lend.
Pat Barrett
prbarrett@xxxxxxxxx
------------------------------
message: 2
date: Wed, 6 Mar 2013 21:07:23 +0000
from: "Anderson, Kurt" <KAnderson@xxxxxxxxxxxx>
subject: Re: [WDSCI-L] RDP Debug when STRDBG active
Chuck,
I'm definitely curious, so if you don't mind posting the code I'd love to
see it.
And I appreciate your feedback.
Thanks,
Kurt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of CRPence
Sent: Tuesday, March 05, 2013 10:16 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDP Debug when STRDBG active
On 05 Mar 2013 14:33, Anderson, Kurt wrote:
I was actually avoiding putting a MONMSG on STRDBG in case it errored
due to some reason other than debug already being active.
That is a concern. Because the escape error messages for STRDBG are not
[documented as being] granular, there is more concern for using MONMSG than
if there were a specific escape message issued for "job is being serviced by
another job". That is because handling the errors is instead mostly
dependent upon what is\are the preceding diagnostic message(s). Placing the
STRDBG UPDPROD(*NO) request in its own CLP makes the processing easier, and
keeps cleaner the CLP that otherwise would be wanting to issue the request
to STRDBG UPDPROD(*NO).
Can you think of any other reasons why STRDBG would fail?
None that I am aware of; well, specifically for monitoring the
CPF1999 error. But unfortunately for lack of documentation on what are the
possible preceding diagnostics, one can only presume that the only
diagnostic will be the CPF1937. Best to code additionally, and
specifically, for the CPF1937 as the expected preceding diagnostic.
I know the command can fail for CPF1992, probably for CPF1993, and I
suppose even for CPF1994 [as undocumented :-( *ESCAPE Messages], so even
more reason than ever to avoid monitoring CPF0000 or even CPF1900 message
ranges.
There is also the possibility for CPF0001, as for any command. But for
STRDBG the error is more likely and most likely a failure is due to the
preceding CPD0039 "Command &2 not valid in this mode." diagnostic because of
the attribute setting of MODE(*PROD) on the command definition for STRDBG.
Should I not be concerned with that?
Probably not too much, if monitoring just for the CPF1999; and possibly
even not too much of a concern if also monitoring for CPF0001 to ignore the
possibility that the STRDBG has run already in the job.
However if interested, I have just finished coding a new\reincarnated
version of DLWUPDPROD command and a CLP as CPP from what I remember of what
I had written in the past... but I made the code just ignore both "debug not
allowed; already in debug" and "debug not allowed; this job is being
serviced by another job", and for anything other error to move the
diagnostics and resend the exception to the caller. Let me know if you want
a copy... and I can post a copy to code.midrange.com
Regards, Chuck
CRPence on Tuesday, March 05, 2013 3:51 PM wrote:
<<SNIP>> This means that STRDBG also fails <ed: when the job issuing
the STRDBG is being serviced by another job>, but instead of due to
mode-checking by the command analyzer [ed: per MODE() on CRTCMD], due
to the debugger detecting that the job is being serviced by another
job.
To learn that the job is being serviced is straightforward; using the
aforementioned ability of the STRDBG to detect and diagnose the
condition:
CPF1999 on STRDBG preceded by the diagnostic CPF1937 "STRDBG is not
allowed because job is being serviced." is how I checked this for the
/same/ means to prevent updating production files in my job; no
PGM() was specified for debug however. I actually had created a CL
command called Disallow Update Production DLWUPDPROD that did the
STRDBG, monitored for the failure, verified the expected diagnostic
for the monitored failure and then cleared the messages, or effected
the Start Debug with UPDPROD(*NO), and then returned, or determined
that the condition was not for the expected diagnostic and sent the
diagnostic as the escape to the invoker to know something unexpected
occurred.
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
------------------------------
message: 3
date: Wed, 06 Mar 2013 15:28:35 -0800
from: CRPence <CRPbottle@xxxxxxxxx>
subject: Re: [WDSCI-L] RDP Debug when STRDBG active
On 06 Mar 2013 13:07, Anderson, Kurt wrote:
I'm definitely curious, so if you don't mind posting the code I'd
love to see it.
For whatever reason I did not library-qualify the API invocations.
_i DlwUpdProd i_
http://code.midrange.com/242d729fc4.html
"Description:
A CLP that performs a Start Debug with Update Production files setting
turned off. The likely error conditions of "job already being serviced"
and "debug already active in this job" are both ignored; no record of
the exception is left in the joblog, but that is easily modified. Other
errors, e.g. authority {CPF0001 with diagnostic CPD0032}, would be
resignaled to the invoker.
..."
midrange.com
