Re: RDI 9.6 bug, unable to save my source...

Hi,

SEU saved my Bacon, when RDi 9.6/9.5.1.2 failed to save my source.

Yup, I am ticked off, that RDI 9.6/9.5.1.2 could not save my source. That is a *MUST HAVE* no matter what. It is NOT an authority issue.

Open New IBM PMR# 86064 442 -- RDI 9.6/RDI 9.5.1.2 unable to save source.

I believe since RDI 9.6 WIPED OUT my source member, is the reason I could NOT open in RDI 9.5.1.2! As the log below shows it renamed it to RSE1177821.sqlrpgle, but wipe out the source on our IBM i 7.3. Ouch! Ridiculous!

Last week I got a quite a few of these type of messages:

EVFF5037 -- An exception stack trace is not available.
Error uploading member -- org.eclipse.rse.services.clientserver.messages.SystemMessageException: Save failed. Could not copy temporary member /QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE/RSE1177821.SQLRPGLE to member /QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE/MCPRQSRL.SQLRPGLE.

I cannot replicate the problem, but sending the Error Logs & workspace to IBM for analysis.

Under IBM Support, it only shows me RDi 9.5.1, so I create an IBM PMR under that version.

PS. Over all, I am really liking RDI 9.6.

I am really just hoping that was a complete fluke and out of the ordinary!

-Ken Killian-


-----Original Message-----
Subject: Re: [WDSCI-L] RDI 9.6 bug, unable to save my source...

Sorry, I don't have time at the moment.

Before going back to yucky SEU, I tried RDI 9.5.1.2. and that also fails.

So sadly, it this forces me to go back to SEU temporarily...

My code as TONS of errors. Because I am doing a refactor to new fields. I wrong thought I could correct the errors using RDI. And then test & verify.

Next month, when time allows, I will open 2 PMR to report. No time at the moment, because of my huge time crunch. Sorry.

It is my fault, I should not have generated some errors in my code for refactoring... MY bad.

-Ken Killian-

-----Original Message-----
Subject: Re: [WDSCI-L] RDI 9.6 bug, unable to save my source...

Guess you are going to have to submit a PMR rather than complaining to this list.

On Wed, Nov 22, 2017 at 11:01 AM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:

Hi,

Using RDI 9.6 and unable to save my source!

Unable to save my source, here is the error Log:
Member /QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE/MCPRQSRL.SQLRPGLE could
not be saved successfully because an attempt to copy temporary member
/QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE/RSE5955218.SQLRPGLE to source
member /QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE/MCPRQSRL.SQLRPGLE failed.
Check the allow-write or allow-update flags for source file
/QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE are set to *YES. Also make sure
file member /QSYS.LIB/KKILLIAN.LIB/QRPGLESRC.FILE/MCPRQSRL.SQLRPGLE is
not locked by another job. During a save, the Remote Systems LPEX
Editor first creates a temporary member, uploads the changes to the
temporary member and then copies the temporary member over the
original member if the upload was successful. The temporary member is
then deleted. If this problem persists you can change the member save
behavior on the Remote Systems > IBM i > Objects Subsystem preference
page and then try saving again.
Below is the message returned from the server when attempting to run
the CPYSRCF command:

0 records copied to QRPGLESRC in KKILLIAN.

Error-Log
EVFF5037
Error uploading member
Live RPG Parsing thread killed

My source even got wiped out in my workspace! Ouch!

But, I think I was able to recover my code in temporary member
RSE5955218.SQLRPGLE

PS. Mind you my source HAS TONS of errors, because I am doing a
complete refactor of data-structure to another data-structure and
trying to update to use the new format. And use %EditW, instead of
Move/Movel in punch card format. And using field name over the old
punch-card standard of only 6-characters. A complete re-map of several fields to be more meaningful.

I guess RDI will not allow me to save my code, which is a
work-in-progress... <Puzzled-Look>

Back to SEU for this one...

Tried turning off parsing, and I still could not save my changes. I
get this error: EVFF5037-- An exception stack trace is not available.


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

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