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



Hi Thomas, testing mostly STRPREPRC.

It generally works, but when I compile a MODULE I got something strange if
the compilation fails:

ISPHERE/STRPREPRC USESRCFILE(MULSRC/QRPGLESRV) USESRCMBR(MULET)
OPTION(*EVENTF) CHGOBJD(*NO) LIB(MULOBJ4) OBJ(MULET) SRCLIB(MULSRC)
SRCFILE(QRPGLESRV) SRCMBR(MULET) USER0('Service su letture')
STRPREPRC: CRTRPGMOD SRCFILE(MULSRC/QRPGLESRV) SRCMBR(MULET)

MODULE(MULMOD/MULET) OPTION(*EVENTF) DBGVIEW(*ALL)

REPLACE(*YES) ALWNULL(*USRCTL)

Verarbeitung in Zeile 5,00 abgebrochen.
Hinweis . . . . : Ist als fehlerhafte Programmzeilenummer 0,00 angegeben,
so trat der Fehler bei der Prèfung der èber gebenen Befehlszeichenkette auf.

And no errors (about the module) in the error view, only errors from
STRPREPRC:

RNS9308 La compilazione si è arrestata. Nel programma sono stati trovati
errori di gravità 30.
RNS9309 La compilazione non ha avuto esito positivo. Il modulo MULET non è
stato creato nella libreria MULMOD.
PRZ0029 STRPREPRC: CRTRPGMOD SRCFILE(MULSRC/QRPGLESRV) SRCMBR(MULET)
PRZ0029 MODULE(MULMOD/MULET) OPTION(*EVENTF) DBGVIEW(*ALL)
PRZ0029 REPLACE(*YES) ALWNULL(*USRCTL)
PRZ0029 STRPREPRC v1.19.1 - 26.01.2021
CPD4090 Non è stata trovata l'unità di stampa PRT01. La coda di emissione è
stata modificata con QPRINT nella libreria QGPL.

When the compile is successful:

ISPHERE/STRPREPRC USESRCFILE(MULSRC/QRPGLESRV) USESRCMBR(MULET)
OPTION(*EVENTF) CHGOBJD(*NO) LIB(MULOBJ4) OBJ(MULET) SRCLIB(MULSRC)
SRCFILE(QRPGLESRV) SRCMBR(MULET) USER0('Service su letture')
Command has completed

and the error view is as usual: EVFF5133 ...

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno dom 2 mag 2021 alle ore 19:01 Tools/400 <
thomas.raddatz@xxxxxxxxxxx> ha scritto:

Hi Folks,

Yes, it is true. The iSphere 4.0 release had a very bad start. The
reason for that is very simple. iSphere has been undergone massive
changes under the cover because we had the idea of opening it to other
Eclipse applications.

In order to accomplish that, we had to add a thin abstraction layer to
decouple the IBM RSE connections from iSphere. For example as a result
of that the message file compare editor is available without RDi, now.
More things may follow over the time.

So what went wrong? The problem was that I did not pay enough attention
to "Remote System Profiles", maybe because I do not use them. Although I
did some tests with connections stored in different profiles I must have
changed something afterwards, which had a bigger impact than expected.

Things should be fixed, now. And that is where I count on the bravest
guys. Please download iSphere 4.1.0.b002 and help me testing iSphere. I
think that I almost went through all features of iSphere, but I am not
sure. There are too many features. Some are obvious, but others are a
bit hidden. So come on and help me testing.

Thanks,

Thomas.

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.