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



When I double click on a message in the message file editor I get a Problem
Occurred Dialog stating "An error has occurred. See error log for more
details.
Parameter 'ccsid' must not be [null]."

I also see this in the error log:

eclipse.buildId=unknown
java.fullversion=JRE 1.8.0 IBM J9 2.8 Windows 7 amd64-64 Compressed
References 20170722_357405 (JIT enabled, AOT enabled)
J9VM - R28_20170722_0201_B357405
JIT - tr.r14.java_20170722_357405
GC - R28_20170722_0201_B357405_CMPRSS
J9CL - 20170722_357405
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -clean -product
com.ibm.rational.developer.ibmi.product.ide

org.eclipse.jface
Error
Tue May 29 08:00:22 EDT 2018
Problems occurred when invoking code from plug-in: "org.eclipse.jface".

java.lang.IllegalArgumentException: Parameter 'ccsid' must not be [null].
at
biz.isphere.core.internal.Validator.getExtraCharacters(Validator.java:165)
at biz.isphere.core.internal.Validator.<init>(Validator.java:150)
at biz.isphere.core.internal.Validator.<init>(Validator.java:119)
at
biz.isphere.core.internal.Validator.getMessageIdInstance(Validator.java:64)
at
biz.isphere.core.messagefileeditor.MessageDescriptionDetail.createHeader(MessageDescriptionDetail.java:200)
at
biz.isphere.core.messagefileeditor.MessageDescriptionDetail.createContents(MessageDescriptionDetail.java:125)
at
biz.isphere.core.messagefileeditor.MessageDescriptionDetailDialog.createDialogArea(MessageDescriptionDetailDialog.java:58)
at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:767)
at biz.isphere.base.jface.dialogs.XDialog.createContents(XDialog.java:79)
at org.eclipse.jface.window.Window.create(Window.java:426)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
at
biz.isphere.core.messagefileeditor.MessageDescriptionDetailDialog.create(MessageDescriptionDetailDialog.java:49)
at org.eclipse.jface.window.Window.open(Window.java:783)
at
biz.isphere.core.messagefileeditor.MessageDescriptionViewer$6.doubleClick(MessageDescriptionViewer.java:344)
at
org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:833)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at
org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:830)
at
org.eclipse.jface.viewers.StructuredViewer.handleDoubleSelect(StructuredViewer.java:1151)
at
org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1264)
at
org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)


On Tue, May 29, 2018 at 7:59 AM, Mark Murphy <jmarkmurphy@xxxxxxxxx> wrote:

Ok, updated iSphere to v3.3.1.r

On Startup I see in the error log:

eclipse.buildId=unknown
java.fullversion=JRE 1.8.0 IBM J9 2.8 Windows 7 amd64-64 Compressed
References 20170722_357405 (JIT enabled, AOT enabled)
J9VM - R28_20170722_0201_B357405
JIT - tr.r14.java_20170722_357405
GC - R28_20170722_0201_B357405_CMPRSS
J9CL - 20170722_357405
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -clean -product
com.ibm.rational.developer.ibmi.product.ide

biz.isphere.core
Error
Tue May 29 07:54:45 EDT 2018
Failed to connect to iSphere update server.

javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: PKIX path
building failed: java.security.cert.CertPathBuilderException:
PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause
is:
java.security.cert.CertPathValidatorException: The certificate issued by
CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford,
ST=Greater Manchester, C=GB is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error
at com.ibm.jsse2.k.a(k.java:17)
at com.ibm.jsse2.at.a(at.java:851)
at com.ibm.jsse2.D.a(D.java:333)
at com.ibm.jsse2.D.a(D.java:113)
at com.ibm.jsse2.E.a(E.java:79)
at com.ibm.jsse2.E.a(E.java:107)
at com.ibm.jsse2.D.r(D.java:610)
at com.ibm.jsse2.D.a(D.java:372)
at com.ibm.jsse2.at.a(at.java:558)
at com.ibm.jsse2.at.i(at.java:73)
at com.ibm.jsse2.at.a(at.java:357)
at com.ibm.jsse2.at.startHandshake(at.java:723)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:215)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:34)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(
HttpURLConnection.java:1561)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
HttpURLConnection.java:1489)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:491)
at com.ibm.net.ssl.www2.protocol.https.b.getResponseCode(b.java:80)
at biz.isphere.core.internal.SearchForUpdates.followRedirects(
SearchForUpdates.java:187)
at biz.isphere.core.internal.SearchForUpdates.followRedirects(
SearchForUpdates.java:191)
at biz.isphere.core.internal.SearchForUpdates.run(
SearchForUpdates.java:89)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.ibm.jsse2.util.h: PKIX path building failed:
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl
could not build a valid CertPath.; internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued by
CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford,
ST=Greater Manchester, C=GB is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error
at com.ibm.jsse2.util.f.a(f.java:70)
at com.ibm.jsse2.util.f.b(f.java:75)
at com.ibm.jsse2.util.e.a(e.java:14)
at com.ibm.jsse2.aB.a(aB.java:79)
at com.ibm.jsse2.aB.a(aB.java:48)
at com.ibm.jsse2.aB.checkServerTrusted(aB.java:9)
at com.ibm.jsse2.E.a(E.java:5)
... 17 more
Caused by: java.security.cert.CertPathBuilderException:
PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause
is:
java.security.cert.CertPathValidatorException: The certificate issued by
CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford,
ST=Greater Manchester, C=GB is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error
at com.ibm.security.cert.PKIXCertPathBuilderImpl.engineBuild(
PKIXCertPathBuilderImpl.java:422)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
at com.ibm.jsse2.util.f.a(f.java:61)
... 23 more
Caused by: java.security.cert.CertPathValidatorException: The certificate
issued by CN=COMODO RSA Certification Authority, O=COMODO CA Limited,
L=Salford, ST=Greater Manchester, C=GB is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error
at com.ibm.security.cert.BasicChecker.<init>(BasicChecker.java:111)
at com.ibm.security.cert.PKIXCertPathValidatorImpl.engineValidate(
PKIXCertPathValidatorImpl.java:199)
at com.ibm.security.cert.PKIXCertPathBuilderImpl.myValidator(
PKIXCertPathBuilderImpl.java:749)
at com.ibm.security.cert.PKIXCertPathBuilderImpl.buildCertPath(
PKIXCertPathBuilderImpl.java:661)
at com.ibm.security.cert.PKIXCertPathBuilderImpl.buildCertPath(
PKIXCertPathBuilderImpl.java:607)
at com.ibm.security.cert.PKIXCertPathBuilderImpl.engineBuild(
PKIXCertPathBuilderImpl.java:368)
... 25 more
Caused by: java.security.cert.CertPathValidatorException: Certificate
chaining error
at com.ibm.security.cert.CertPathUtil.findIssuer(CertPathUtil.java:316)
at com.ibm.security.cert.BasicChecker.<init>(BasicChecker.java:108)
... 30 more




On Sat, May 26, 2018 at 11:41 AM, Tools/400 <thomas.raddatz@xxxxxxxxxxx>
wrote:

Mark,

In your RDi workspace, do you have a project directory
"iSphereSpooledFiles" with a ".project" file with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>iSphereSpooledFiles</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>


[workspace]
+-- iSphereSpooledFiles
+-- .project

That project is used for storing spooled files when loading them into an
editor.

You may also try to open the "Project Explorer" perspective, delete the
"iSphereSpooledFiles" project and restart RDi.

Thomas.

Am 25.05.2018 um 15:30 schrieb Mark Murphy:
Is it possible that this issue is also responsible for the
java.lang.NullPointerException that I receive when attempting to open a
spool file? All other spooled file operations work properly including
Save,
so that has me puzzled a bit.

On Fri, May 25, 2018 at 2:40 AM, Thomas Raddatz <thomas.raddatz@xxxxxx>
wrote:

I have to confirm that this issue is a bug. There will be an update
this
evening.

Thomas.


-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mark
Murphy
Gesendet: Donnerstag, 24. Mai 2018 14:21
An: Rational Developer for IBM i / Websphere Development Studio Client
for
System i & iSeries
Betreff: [WDSCI-L] iSphere Message File Editor

IBM i: 7.1
RDi: 9.6.0.3
iSphere: 3.3.0.r

I have finally gotten iSphere loaded, and I am liking it. But, I am
having
a problem with the Message File Editor. I cannot Preview or Display, or
Change messages. It just does nothing. If I double-click on a message
I get
the following error:

An error has occurred. See error log for more details. Parameter
'ccsid' must not be [null].

Our system has QCCSID set to 65535.

Jobs have:
Coded character set identifier . . . . . . . . . : 65535
Default coded character set identifier . . . . . : 37

Unfortunately messages in the message file also have CCSID 65535.

I am guessing that is the problem. Could we have a preference to state
which CCSID we are using to replace the 65535? Or is there an easy way
to
change the CCSID of messages?
--
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.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email confirmation to
the
sender.

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




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.