Wilyhost Agent setup finished successfully with limitations - SMD SPS15
Dear all,
we have connected different SAP J2EE systems to our Solution Manager Diagnostics without any problems. Now we are trying to connect the corresponding ABAP backend systems to the SMD. The Setup Wizard for these systems are completed with a warning. Everything seems to work fine, but the warning are spurious (we get only the yellow light, not a green one).
Did anyone has the same "problems" with ABAP managed systems and has anyone a solution for the yellow light ?
Thanks and best regards
Patrick
Error/Warning Message -
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager.
Created destination RT5|s3p5012_RT5_00
Created action RT5 - RT5 AbapSystem
Created action RT5|s3p5012_RT5_00 - RT5|s3p5012_RT5_00 AbapInstance
Created 2 action(s).
1 Wilyhost Agent(s) and 0 EP Agent(s) from host s3p2012 are connected to the EM.
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: RT5
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: RT5|s3p5012_RT5_00
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager.
Error/Warning Message -
Hi to all,
I have addition information about the Wily HostAgent problem. Here are some other alerts/warnigs from another SAP portal :
============================================================================
Jul 15, 2008 10:34:15 AM [Thread[SAP GC|FB7_J02_server3,5,main]] Error com.sap.smd.wily.hostagent.action.GcScannerAction - scanInitial(): scan for file /usr/sap/FB7/J02/j2ee/../work/std_server3.outterminated: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
Jul 15, 2008 10:34:15 AM [Thread[SAP GC|FB7_J02_server3,5,main]] Error com.sap.smd.wily.hostagent.action.GcScannerAction - doRun(): Action temporarily stopped: SAP GC|FB7_J02_server3
[EXCEPTION]
com.sap.smd.wily.hostagent.TransientException: java.io.FileNotFoundException: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:259)
at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:391)
at com.sap.smd.wily.hostagent.action.GcScannerAction.doRun(GcScannerAction.java:135)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:52)
at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.FileNotFoundException: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:372)
... 4 more
Jul 15, 2008 10:35:15 AM [Thread[Thread-364,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|FB7_J02_server2 not running because status is WAITING_FOR_DESTINATION
Jul 15, 2008 10:35:15 AM [Thread[Thread-366,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|FB7_J02_server1 not running because status is WAITING_FOR_DESTINATION
============================================================================
Similar Messages
-
Wilyhost Agent setup finished successfully with limitations.
Solution Manager EHP1
While executing Managed system for Non-ABAP ( JAVA ) System , we are getting the problem
The Wily & SMD agent is already installed on the managed system
The error in Managed System Configuration :
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager
Logs of the SMDAgentApplication :
*Oct 12, 2009 2:33:23 PM [Thread[Thread-165,5,main]] Error Error to retrieve the process from Message Server (detail: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine)*
[EXCEPTION] java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
at java.net.PlainSocketImpl.socketConnect(Native Method)
Oct 12, 2009 2:33:35 PM [Thread[Thread-177,5,main]] Error RemoteOSService: operation failed - command is: mode=jstartup,mshost=epdev,msport=0,node=733441 [EXCEPTION]
com.sap.smd.plugin.remoteos.exception.ThreadDumpCommandException: Message Server Port must be specified!
at com.sap.smd.plugin.command.tda.ThreadDumpCommand.init(ThreadDumpCommand.java:89)
at com.sap.smd.plugin.remoteos.RemoteOSService.triggerDump(RemoteOSService.java:276)
Oct 12, 2009 3:03:27 PM [Thread[Thread-165,5,main]] Error com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: Configuration Error: invalid property sysno for destination SapStartSrv_epdev_EPD_ at com.sap.smd.wily.hostagent.sapcontrol.SapControlDestination.open(SapControlDestination.java:52)
at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:82)
Oct 12, 2009 3:03:27 PM [Thread[Thread-165,5,main]] Error com.sap.smd.wily.hostagent.SapAgent - startActions():
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: java.io.IOException: CreateProcess: saposcol error=2 at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:324)
at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:467)
at com.sap.smd.wily.hostagent.action.SapOsColAction.initSapOsCol(SapOsColAction.java:405)
at com.sap.smd.wily.hostagent.action.SapOsColAction.init(SapOsColAction.java:110)
at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:383)Hi Rohan Pawar,
did you find some solutions. I've not the same problem but perhaps you now what the error means
i don't know which folder is expected.
Best regards
Thorsten Stracke
]] Error com.sap.smd.wily.hostagent.SapAgent - startActions():
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: java.io.IOException: error=2, No such file or directory
at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:324)
at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:467)
at com.sap.smd.wily.hostagent.action.SapOsColAction.initSapOsCol(SapOsColAction.java:405)
at com.sap.smd.wily.hostagent.action.SapOsColAction.init(SapOsColAction.java:110)
at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:383)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:96)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:112)
at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:62)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:119)
at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:233)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:307)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:271)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:145)
at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:504)
at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:381)
at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)
at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:253)
at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:164)
at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:300)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
at java.lang.Thread.run(Thread.java:664)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at java.lang.Runtime.exec(Runtime.java:326)
at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:465)
... 23 more -
Diagnostics Setup - Warning on Step "Wilyhost Agent Details"
Hi All
I am having a bit of dificulty configuring the Wily Agent via Solution Manager diagnostics.
I am currently getting the following errors when trying to set up the Wilyhost Agent when I run the setup wizard I am getting the following results:
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(solman:6001).
Step Wilyhost Agent Details
Created destination EPT_JC01_server0
Created destination SapStartSrv_nwportal_EPD_04
Created destination EPD_JC04_server0
Created destination SapStartSrv_nwportal_EPT_01
Created action SAP GC|EPT_JC01_server0 - SAP GC|EPT_JC01_server0
Created action EPD|perth_EPD_04 - SapStartSrv_nwportal_EPD_04
Created action SAP GC|EPD_JC04_server0 - SAP GC|EPD_JC04_server0
Created action EPT|perth_EPT_01 - SapStartSrv_nwportal_EPT_01
Created 4 action(s).
1 Wilyhost Agent(s) from host perth is connected to the EM.
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: SAP OsCol - null
Please check SMDAgentApplication log files for warnings and errors.
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(solman:6001).
The Diagnostics agent log is:
Apr 6, 2010 4:56:35 PM [Thread[SAPOsCol,5,main]] Error com.sap.smd.wily.hostagent.action.SapOsColAction - processXml(): Error processing saposcol output: saposcol -xml
AdjustTokenPrivileges failed with 1300
<?xml version="1.0" encoding="utf-8" ?>
<saposcol version="COLL 20.95 700 - 20.65 NT 08/02/06" date="1270569346" status="running">
<!-- Last collection: 2010/04/06 16:55:46 -->
<OperatingSystem>
<property name="OpSysRelease">
<value>Windows NT</value>
<!-- Version of operating system, `uname -r' -->
</property>
<property name="OpSysReleaseName">
<value>Windows NT 5.2</value>
<!-- freely choosable text describing OS release name, e.g. 'SUSE LINUX Enterprise Server 9 (i586)' -->
</property>
<property name="OpSysCategory">
<value>Windows NT</value>
<!-- MANDATORY: operating system, e.g. 'HP-UX', 'Linux', 'Windows NT', ... -->
</property>
</OperatingSystem>
[EXCEPTION]
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:146)
at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:420)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
at java.lang.Thread.run(Thread.java:664)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:146)
at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:420)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
at java.lang.Thread.run(Thread.java:664)
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
... 6 moreHi,
This seems to be a bug and please install the saposcol version 710 as saposcol 710 is downward compatible with release 700 and this issue must be resolved. -
Error during Managed system setup "Wilyhost Agent" type
Hello All,
Managed system setup finished with one error. Iam using this for selfmonitoring (solman itself as managed system)
Error msg as follows.
0 Wilyhost Agent(s) from host inbbssun02 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (TDCTBI.india.tcs.com:6001) no Wilyhost Agent was detected from host inbbssun02. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
I checked jvm_SMDAgent.out. and log as follows.
/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.4.2_20-rev" from S
un Microsystems Inc.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.ag
entProfile"
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sa
p.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.ag
ent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval i
s set to 1800
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to
500
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is
set to 3000
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to
locate the extensions directory.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/SMD/J98/SMDAgent/applications.config/
com.sap.smd.agent.application.wilyhost/ext was successfully located
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Pro
perty "com.wily.introscope.agent.agentName".
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
1/06/10 02:55:30 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
[p4://inbbssun02:50004] Agent ready.
1/06/10 02:55:34 PM IST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise
Manager at TDCTBI.india.tcs.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "inbbssun02", Proce
ss = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
Is there any seperate setting for wilyhost agent connection to EM ?
Regards,
ShyamI have restarted the agent at OS level and it appears in the Agent Admin page.
I then re-ran the Managed System Config for this system and receive the same error.
I have looked at the jvm_smdagent.out file on the wilyhost and found the following errors
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/19/10 12:34:08 PM CET [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly. Keeping the connection alive.
The agent on the solution manager box is version 7.0 and the version od the agent on the PI box is 7.11
Regards
Stephen -
Wilyhost Agent could connect to the Enterprise Manager
Hi Gurus,
I'm trying to setup Diagnostic for Solman 7.0. I'd installed Wily Introscope and SDM Agent in Solution Manager. The Agent was configured for this server. The Application Agent in Diagnostic Setup -> Managed system was OK, but when I try to run the Setup Wizard for Self-Monitoring, every steps are in green (OK) but the first was in red with this error:
Step Wilyhost Agent Details
Created destination SM1_DVEBMGS00_server0
Created destination SM1|qfmasr003_SM1_00
Created action SAP GC|SM1_DVEBMGS00_server0 - SAP GC|SM1_DVEBMGS00_server0
Created action SM1 - SM1 AbapSystem
Created action SM1|qfmasr003_SM1_00 - SM1|qfmasr003_SM1_00 AbapInstance
Created 3 action(s).
0 Wilyhost Agent(s) and 0 EP Agent(s) from host qfmasr003 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (qfmasr003.xxxxxxxx.com:6000) no Wilyhost Agent was detected from host qfmasr003. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
The file jvm_smdagent.out said this:
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=qfmasr003_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
j2ee.dbhost=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/exe/jstartup.jar:/usr/sap/SMD/exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.00.15.20080806065909/launcher/smdagentlauncher.jar
java.class.version=48.0
java.endorsed.dirs=/j2sdk1.4.2_17/jre/lib/endorsed
java.ext.dirs=/j2sdk1.4.2_17/jre/lib/ext
java.home=/j2sdk1.4.2_17/jre
java.io.tmpdir=/tmp
java.library.path=/j2sdk1.4.2_17/jre/lib/i386/server:/j2sdk1.4.2_17/jre/lib/i386:/j2sdk1.4.2_17/jre/../lib/i386:/usr/sap/SMD/exe:/tmp/sapinst_exe.18845.1222346568:/usr/sap/SMD/exe:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.4.2_17-b06
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.4.2_17
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=1.4.2_17-b06
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=G1082288837
jstartup.ownProcessId=1666
jstartup.whoami=server
line.separator=
memory.manager=128M
os.arch=i386
os.name=Linux
os.version=2.6.9-5.ELsmp
path.separator=:
sun.arch.data.model=32
sun.boot.class.path=/j2sdk1.4.2_17/jre/lib/rt.jar:/j2sdk1.4.2_17/jre/lib/i18n.jar:/j2sdk1.4.2_17/jre/lib/sunrsasign.jar:/j2sdk1.4.2_17/jre/lib/jsse.jar:/j2sdk1.4.2_17/jre/lib/jce.jar:/j2sdk1.4.2_17/jre/lib/charsets.jar:/j2sdk1.4.2_17/jre/classes
sun.boot.library.path=/j2sdk1.4.2_17/jre/lib/i386
sun.cpu.endian=little
sun.cpu.isalist=
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sun.os.patch.level=unknown
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
Running SMD Agent ...
[Runtime] START
==> Loading application com.sap.smd.agent.application.runtime : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.global.configuration : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.connectors : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.wily : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.filesystem : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.tracing : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.remotesetup : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.wilyhost : 7.0015.20080806065229.0000
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent Release 7.2.0.0 (Build 540138)
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) Server VM 1.4.2_17" from Sun Microsystems Inc.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Loaded file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Property "com.wily.introscope.agent.agentName".
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at qfmasr003.quickfood.com.ar:6000,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "qfmasr003", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent] Remote Agent Configuration Service is enabled
==> Loading application com.sap.smd.agent.application.logviewer : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.flightrecorderdumpscan : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.telnet : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.database : 7.0015.20080806065229.0000
==> Loading application com.sap.smd.agent.application.datacollector : 7.0015.20080806065229.0000
Initialization done.
[ms://qfmasr003.xxxxxxxxxxxxxxxxxx:8101/P4] Agent ready.
==> Loading application com.sap.smd.agent.application.remoteos : 7.0015.20080806065229.0000
only Initial Configuration files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only file configuration information will be considered
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
only Abap configuration will be considered
only Abap configuration will be considered
only file version information will be considered
only End2End log files will be considered
only software change logs will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
10/15/08 01:16:17 PM ARST [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly. Keeping the connection alive.
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only file configuration information will be considered
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
only Abap configuration will be considered
only Abap configuration will be considered
only file version information will be considered
only End2End log files will be considered
only software change logs will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only End2End log files will be considered
only Initial Configuration files will be considered
This error is the same, when I try to connecto other system for Diagnostics,
Any comments, suggestions, recomendations.... anythings.....
Thanks in advice,
Sergio Mazzeo.Hi Sergio,
did you already stop and start your SMD agent on OS level ? It is not enough to restart it from the SMD.
kind regards
Davy -
Wilyhost Agent(s) from host hostname are connected to the EM
Hi All!
I tried complte setup managed system/. And received following message:
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (host:port) no Wilyhost Agent was detected from host SSM. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
in jvm_smdagent.out:
11/12/09 03:40:40 PM GMT+03:00 [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
11/12/09 03:40:40 PM GMT+03:00 [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com.sap.guid.GUIDGeneratorFactory
11/12/09 03:40:41 PM GMT+03:00 [INFO] [IntroscopeAgent] Started Error Reporting service
11/12/09 03:40:42 PM GMT+03:00 [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at host:port,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "HOST", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com.sap.guid.GUIDGeneratorFactory
Could anybody help me resolve it?
Thanks for your advance,
AlexanderHi,
we also have the same error...
LM-SERVICE 7.01 SP5 (1000.7.01.5.2.20091211060559)
LM-TOOLS 7.01 SP4 (1000.7.01.4.2.20090723091137)
My problem is that I don't get any data of our KWP ABAPsystem in Wily. The Agent is running and is well connected (The lights in agent administration are all green). Also in the logs I don't see any probs.
I have restarted the agent 1000 times..., reseted the server name and ran the agent setup again... I also registered it via
./smdsetup.sh sldconf hostname:"solman" port:"59500" user:"username" pwd:"xxxxx"
./smdsetup.sh managingconf hostname:"sapms://solman" port:"8196" user:"SMD_ADMIN" pwd:"xxxxx"
Do u have any ideas???
Regards
Johannes -
Hello.
I am having much difficulty using any software drum program. I am trying to use EZ Drummer and the drum programs in Logic, with limited success. I was using them, and they were working, but this is no longer the case. Please help me navigate my way through these issues, if possible.
Thanks.
EricAha! I have sorted it.
For those with similar problems, the solution is this:
Macintosh HD > Library > Audio > MIDI Drivers
Then delete DigiDioMidiDriver.plugin -
Santa recently purchased 2 iPads for my kids.
I currently have my own apple id for my iphone.
I have created 2 aple ids for each child and succesfully setup one iPad with one of the new apple ids, but the other iPad has my own apple id.
Can I change the apple id on a device (iPad 2)? And how?You sign off and sign in with the correct Apple ID.
See this tip and is still valid for IOS 6
iOS 5 & iCloud Tips: Sharing an Apple ID With Your Family -
Success with adding an external eSATA drive to a Verizon FIOS DVR
August 4, 2012 - Success with adding an external eSATA drive to a Verizon FIOS DVR
I just upgraded from a Comcast DVR to a Verizon FIOS DVR. I upgraded because my old DVR was limited to 500GB (1/2 TB) on the internal drive and the new FIOS DVR allowed for a much larger external eSATA drive. Selecting a viable external drive for the FIOS DVR was easier said than done. The three drives listed on the Verizon web site as compatible with FIOS DVRs are no longer manufactured by western digital and are not available on the market.
The DVR that I received from Verizon was a Cisco "CHS 435 HD DVR" that came with a 500GB (1/2 TB) internal drive. This is one of their "Multi-Room DVRs" that allows other set top boxes (not DVRs) to watch videos recorded on it.
I selected a western digital "WD30EURS" eSATA disk drive because it was a follow on product to one of the three listed as acceptable by Verzion on their web page and it was 3TB in size. I ordered from amazon.com for $170.99. This drive is a "bare drive" so it does not come with an external encloser or a eSATA cable.
According to the Western Digial web site this is a AV-GP drive: "These drives are designed to last in high temperature always-on, streaming digital audio/video environments such as PVR/DVR, IPTV, and video surveillance systems."
http://www.wdc.com/wdproducts/library/AAG/ENG/2178-771131.pdf
I got a "Macally G-S350SU Hi-Speed eSata/USB2.0 External Storage Enclosure for 3.5inch SATA HDD" to hold the drive for $34.39. I chose this one because it does not use a fan that could cause continious noise. The box is made out of metal so it cools itself as long as it is exposed to air (not covered up). This box comes with an external power supply that has a small transformer that plugs into a wall outlet.
Then I needed a eSATA cable. I got a "StarTech 6-Feet Shielded External eSATA Cable M/M (ESATA6)" for $6.50 and a 3-foot version for $5.90. I went with the longer one so that the cable would be less likely to become accidentally unplugged if I need to move the drive or the DVR. The cables and the drive houseing came from the same Amazon provider so it saved me on shipping. The drive came from Amazon/Western Digial directly but they do not have external housings or eSATA cables on that site.
The total cost was $255.56 including shipping for all these items.
I went with the largest (3TB) drive from western digial's AV-GP line to avoid a future upgrade from a smaller drive to a larger drive. There is no way to copy videos from one external eSATA drive to another drive because they are formatted by the FIOS DVR in a propriatary format. That would mean that any future upgrade would require losing all recorded files during an upgrade. That also means that there is no way to back up the contents of the drive to protect yourself from hard drive failure.
The installer who setup the DVR did not want me to plug in the drive while he was there and explained that I was on my own when I attached this kind of personal device to the DVR. When I plugged in the new eSATA drive it was automatically discovered. I was asked by the DVR if I wanted to format the new drive. I answered yes and within 2 hours the drive completed formatting. I did not watch the boring format so it could have finished faster.
When I started recording new videos they go directly to the external drive automatically and avoids the internal drive. It had no trouble recording two HD shows and playing a recording at the same time. I now have 20 hours of HD video recorded and the 3TB external drive is 17% full. So far my experience with the external drive has been great. No problems or issues. Learning the new remote control, new DVR menu system, and web browser control of the DVR from a laptop is another story. It will take some time to figure out how to make all the new features work.
It took me a while to figure out how to make this work since the verizon web site made useless suggestions and pointed me to products that are not available any more. I could not tell if this really would work until I plugged it in and then I was pleasantly suprised that it did. I have had this working for 3 days without any issues. I hope this post makes it easier for you to add an external eSATA drive to your DVR.
Here are the three items ordered from Amazon to make this work:
Western Digital 3 TB AV-GP 3 TB SATA 2 Intellipower 64 MB Cache Bulk/OEM 3.5-Inch Internal Bare Driv...
Macally G-S350SU Hi-Speed eSata/USB2.0 External Storage Enclosure for 3.5inch SATA HDD
StarTech 6-Feet Shielded External eSATA Cable M/M (ESATA6)You are right. I can only access 2TB of my 3TB external drive. That gives me a total of 2.5 TB counting the internal (0.5 TB) and external (2.0 TB) drives. This is a significant improvement over the just the 0.5 TB internal drive. I have not been able to find a reason for this limitation. Cisco and Verizon do not mention any limits that I can find. I hope that a future BIOS upgrade could provide access to more space but this would probably require me to reformat the drive and lose everything recorded.
I paid $170.99 for the 3 TB WD30EURS drive at amazon. I could have gotten away with spending only $116.99 for the 2 TB WD20EURS drive. Not worth returning at this point so I will stay with it. Makes me glad I didn't buy the most expensive 6 TB external monster drive available from another company.
I bought: 3TB drive: Western Digital 3 TB AV-GP 3 TB SATA 2 Intellipower 64 MB Cache Bulk/OEM 3.5-Inch Internal Bare Drive WD30EURS by Western Digital
I could have bought: 2TB drive: Western Digital AV-GP 2 TB SATA II Intellipower 64 MB Cache Bulk/OEM Internal Hard Drive - WD20EURS by Western Digital
Details of what I learned:
The external 2 TB drive now has 41 hours of HD video recorded and claims to be 34% full (66% free). My estimate would allow me to have aprox 120 hours of HD on the external drive (2TB) and 30 hours of HD on the internal drive (500GB) for a total of 150 hours of HD. This will keep me happy for the near future.
There is a hidden "diagnostic menu" that is not normally accessible or documented by CISCO or Verizon. This menu has a lot of interesting info on the inner working of the DVR. There was an obscure reference to this menu on another forum.
To access this diagnostics menu:
1) Get the DVR into normal live tv mode (no menu, no guide, no pause ...)
2) Go to the Cisco CHS 435 HD DVR (not the remote control) and press these buttons on the front of the DVR: Press both the Left Arrow "<-" button and "OK" button at the same time and hold them both down for aprox 5 seconds.
3) The "Verizon FiOS TV Diagnostics Menu" menu will appear. The menu can then be used by the remote control.
4) I chose "D03 Memory / HDD" and then "Hard Disk Information" and finally "OK"
A five page disk report appeared. With a little bit of interpretation I discovered:
The Internal Drive is know as "drive 1/hdc1" has 461 GB total space with 454 GB free.
The External Drive is split into two partitions "hdc2" and "hdc3" (aka two mount points).
"drive 2/hdc2" has 1007 MB total with 317 GB free
"drive 3/hdc3" has 1007 MB total with 974 GB free
The normal DVR menu has an "Eject" feature that allows you to stop the external drive and make it safe to remove it from the DVR without losing anything via an unplanned drive removal. This can be found at "DVR" button on remote then "Settings"->"External Hard Drive"->"Eject". -
Hi,
I am trying to setup Introscope Agent. I have installed it with Software Deployment Manager with no issues and setting up the agent using Diagnostic Agent Setup -> Managed System -> Introscope Agent.
I am getting this error. Please suggest on this.
ISAgent Setup on node:
Operation Faile
Introscope Agent Configuration
Remote Operation Failed
Introscope Agent Extraction
Remote Operation Succeeded
Detailed Information
Operation skipped - Introscope Agent is already deployed at : filesystem
\SMDAgent\applications.config\com.sap.smd.agent.application.wily\BytecodeAgent\ISAGENT.8.2.2.0-2010-04-22
Updating Introscope Agent Profiles
Remote Operation Succeeded
ISAgent Profile Generation: IntroscopeAgent.profile ,
Remote Operation Succeeded
Detailed Information
Operation Failed - <SID> - 254006950 - java.lang.NullPointerException
Regards,
SandeepHello Sandeep-
Please do as follows
Install IS Agent (Wiley Introscope agent) in Solution Manger systems
Make sure wily is not running by looking for unix/windows processes with strings like u201Cintrou201D, u201Cemu201D, u201Cwilu201D. Uninstall wilyintroscope 7.1 by renaming the wily directory.
and deploy it with SDM it should work
Start SDM - 9> RemoteGui.sh
(IS Agent file is /sapcds/SMD2/ISAGENTSMD72_02-10005468.SCA)
then hit next and deploy after that you should be good to go.
George
Edited by: george rayi on Jul 20, 2010 10:14 PM -
I have a new Windows tablet computer with limited hard drive space (32 GB), and cannot transfer my itunes library to the hard drive. Can I run itunes from an external hard drive? I have tried to follow some of the directions on this site, but am having no success. Thanks.
iTunes will run fine with the media on an external drive.
However, I suggest that a tablet computer with a tiny hard drive is not ideal as the primary computer for managing an iTunes library, even a small one. If you have another machine, perhaps a big, boxy, inexpensive old desktop with a decent amount of storage, that might be a better choice.
http://support.apple.com/kb/HT1364 -
I am trying to use apple configurator with ipads. I have been successful with preparing and supervising all ipads but one. When preparing it in configurator, I receive an error that it is refreshed but with an error. Under supervise, I am not able to add apps. I have erased all content to start over but this does not work either
Are you trying to restore a backup, or just sync some apps? Do you have profiles installed on the device?
Have you plugged the ipad into iTunes, and did a fresh install? I'm assuming the device went through the prepare setup properly. You many have to unsupervise it first, then plug it into iTunes to wipe it completely.
I'd then do each step seperately. Prepare it, then install 1 app, if that works, try another app, then maybe a profile. -
How to setup Slingbox AV with Linksys E2500
I just purchased a new Linksys E2500 and I am unable to setup internet viewing with it. I have went in and done the port forwarding and still I have not had any success. I would appreciate any helpful information.
So the concern that you said is the configuration of the Router ( E2500 ) at home.. So could please inform us the name of the ISP( Internet Service Provider )... So it all depends upon the ISP( Internet Service Provider ) setup...
If you want to configure the router with the help of the CD so for that you need to unistall the existing Cisco Connect Software from the computer...
Reset the Router and power cycle the network...Make the following connectivity:
Modem ----> Router -----> Computer
They all should be connected with the Ethernet Cable... Then install the Cisco Connect Software... It will help you in configuring the Router...
As far as Slingbox is concern you did port forwarding but until and unless you are not online it would work.... -
Success with VNC Accesing 2 Computers on Netork?
Hi Everyone,
Has anyone had success using VNC and being able to access 2 separate computers on their Linksys network?
I understand that this should be able to be accomplished by going into the port forwarding section of the router setup screen and forwarding a different port for each computer using the computer’s internal, static IP address.
I’ve found a few messages of people having problems doing this, but didn’t come across any who reported they were finally successful with this setup.
I’ve been trying to accomplish this using PCAnywhere, but after spending 2 hours on the phone working with one of Symantec’s own techs, who couldn’t get this to work, I am ready to give up on PCAnywhere and am thinking about giving VNC a try.
Any feedback and experiences with this would be greatly appreciated.
Thanks,
BrianCorrect. You can only forward a single port once. The router also does not do port redirection which means you must use different ports on the computers.
For example:
Computer 1, 192.168.1.31, uses server with port 7000.
Computer 2, 192.168.1.32, uses server with port 7001.
Computer 3, 192.168.1.33, uses server with port 7002.
Now you forward port 7000 on the router to 192.168.31, 7001 to 192.168.1.32 and 7002 to 192.168.1.33.
The important thing is to reconfigure the server on the computer to use different ports as well. You must also make sure to open the port in the firewall of the computer if it runs any.
See here for a more complete checklist regarding port forwarding issues. -
Home-grown ABAP report sometimes hangs & sometimes finishes successfully
Dear All,
I am re-posting the below thread, which was previously posted on the : SAP on DB2 UDB for i5/OS (DB4) forum, maybe I will get a reply :
We are implementing SAP ECC 6.0 (ABAP stack) on IBM System i (iSeries), i5/OS V5R4, Kernel patch level 173
We have a home-grown ABAP report that sometimes finishes successfully and sometimes just hangs; i.e. through the OS/400 job monitoring, no change happens in the database records I/O counts.
Below is the OS/400 job log, related to a case where the report did not complete successfully (actually the below is an excerpt from the beginning and the end of the OS/400 job log)
I would highly appreciate any advise about the cause of this problem :
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 1
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPC2196 Completion 00 05/11/08 11:44:32.099024 QLICUSRL QSYS 0113 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library QGY added to library list.
Cause . . . . . : If the ADDLIBLE command was used, QGY was added to the
user library list. If the CHGSYSLIBL command was used, QGY was added to the
system portion of the library list.
CPC2198 Completion 00 05/11/08 11:44:32.099232 QLICHLLE QSYS 01A3 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Current library changed to R3PRODATA.
Cause . . . . . : The current library in the library list was changed to
R3PRODATA.
*NONE Information 05/11/08 11:44:32.214488 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: File Version: 7000, 173, 0, 0
*NONE Information 05/11/08 11:44:32.214640 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Product Version: 700, patch 173,
changelist 0
*NONE Information 05/11/08 11:44:32.214808 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Platform: os400 for releases OS400 3 5,
OS400 4 5, OS400 1 6
*NONE Information 05/11/08 11:44:32.214904 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Special Build Description: OPT (Aug 11
2008, 08:14:03) (ASCII in PASE ASCII build)
*NONE Information 05/11/08 11:44:32.230728 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 2
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Connect from Client Protocol: 610
*NONE Information 05/11/08 11:44:32.230840 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Remote Link: /usr/sap/PRO/SYS/exe/run/DBSLDB4RMT
*NONE Information 05/11/08 11:44:32.268688 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Kernel Library: SAPPROUCN
CPF9897 Completion 40 05/11/08 11:44:32.286120 QDBENCWT QSYS 0066 DBSLENCWT SAPPROUCN *STMT
To module . . . . . . . . . : DBSLENCWT
To procedure . . . . . . . : main
Statement . . . . . . . . . : 14
Message . . . . : CONCURRENT WRITE IS ENABLED.
Cause . . . . . : No additional online help information is available.
CPF9897 Completion 40 05/11/08 11:44:32.286136 QDBENCWT QSYS 0066 DBSLENCWT SAPPROUCN *STMT
To module . . . . . . . . . : DBSLENCWT
To procedure . . . . . . . : main
Statement . . . . . . . . . : 14
Message . . . . : CONCURRENT WRITE WILL BE ENABLED NEXT IPL.
Cause . . . . . : No additional online help information is available.
CPC2197 Completion 00 05/11/08 11:44:32.323144 QLICHLBL QSYS 013C QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library SAPPROUCN removed from library list.
Cause . . . . . : If the RMVLIBLE command was used, SAPPROUCN was removed
from the user library list. If the CHGSYSLIBL command was used, SAPPROUCN
was removed from the system portion of the library list.
CPC2196 Completion 00 05/11/08 11:44:32.323368 QLICUSRL QSYS 0113 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library SAPPROUCN added to library list.
Cause . . . . . : If the ADDLIBLE command was used, SAPPROUCN was added to
the user library list. If the CHGSYSLIBL command was used, SAPPROUCN was
added to the system portion of the library list.
SAP4000 Information 00 05/11/08 11:44:32.336544 DBSLDB4RMT SAPPROUCN *STMT DBSLDB4RMT SAPPROUCN *STMT
From module . . . . . . . . : O4SAPUCI_E
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 3
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : O4_QMHSNDPM__FPCcN21iN21T4PUcR11O4_ERRC0100
Statement . . . . . . . . . : 4
To module . . . . . . . . . : DBSLDB4RMT
To procedure . . . . . . . : CXXPEP__Fv
Statement . . . . . . . . . : *N
Message . . . . : Connect from workprocess w2 on MASAPPRO_PRO_00
CPC2196 Completion 00 05/11/08 11:44:32.975448 QLICHLBL QSYS 013C CHGR3SYSLE SAPPROUCN *STMT
To module . . . . . . . . . : CHGR3SYSLE
To procedure . . . . . . . : CHGR3SYSLE
Statement . . . . . . . . . : 13600
Message . . . . : Library R3SYS added to library list.
Cause . . . . . : If the ADDLIBLE command was used, R3SYS was added to the
user library list. If the CHGSYSLIBL command was used, R3SYS was added to
the system portion of the library list.
SQL7917 Information 00 05/11/08 11:47:23.199272 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16590
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPF9898 Information 40 05/11/08 11:54:11.399680 QXDAUTIL QSYS *STMT QXDAEDRS QSYS *STMT
From module . . . . . . . . : QXDATRACE
From procedure . . . . . . : QxdaWriteJoblog__FPciT1R16QxdaTraceControl
Statement . . . . . . . . . : 13
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaConnectEDRSInternal__FPvPcT1PiT2T1R16clean
upMutexes_tP19XDAGlobalDataStruct
Statement . . . . . . . . . : 3266
Message . . . . : Connection #2, Server Job: 303463/QUSER/QXDARECVR.
Cause . . . . . : This message is used by application programs as a general
escape message.
CPF5009 Diagnostic 10 05/11/08 11:54:32.741480 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 22987
Message . . . . : Duplicate record key in member RSEUINC.
Cause . . . . . : The output or update operation to member number 1 record
number 4942 format RSEUINC, for member RSEUINC file RSEUINC in library
R3PRODATA, failed. Member number 1 record number 4941 format RSEUINC has the
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 4
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
same record key as member number 1 record number 4942 format RSEUINC. If
the record number is zero, the duplicate record key occurred on an output
operation. Recovery . . . : Change either record key so that the keys are
unique. Then try your request again.
CPF5034 Sender copy 30 05/11/08 11:54:32.741536 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 4942 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member RSEUINC file RSEUINC in library
R3PRODATA, or in a based-on member of RSEUINC. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file RSEUINC in library R3PRODATA. Recovery
. . . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
CPF5034 Notify 30 05/11/08 11:54:32.741552 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 22987
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 4942 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member RSEUINC file RSEUINC in library
R3PRODATA, or in a based-on member of RSEUINC. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file RSEUINC in library R3PRODATA. Recovery
. . . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
SQL0803 Diagnostic 30 05/11/08 11:54:32.748064 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint RSEUINC in R3PRODATA exists over one or
more columns of table RSEUINC in R3PRODATA. The operation cannot be
performed because one or more values would have produced a duplicate key in
the unique index or constraint. Recovery . . . : Change the statement so
that duplicate keys are not produced. For information on what rows contain
the duplicate key values, look at the previously listed messages in the job
log (DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 5
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
SQL7917 Information 00 05/11/08 12:33:54.649416 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:33:54.709808 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:33:54.745288 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 6
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:34:28.245160 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16643
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.875752 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.935840 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 7
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.965560 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPF9898 Information 40 05/11/08 12:50:51.470216 QXDAUTIL QSYS *STMT QXDAEDRS QSYS *STMT
From module . . . . . . . . : QXDATRACE
From procedure . . . . . . : QxdaWriteJoblog__FPciT1R16QxdaTraceControl
Statement . . . . . . . . . : 13
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaConnectEDRSInternal__FPvPcT1PiT2T1R16clean
upMutexes_tP19XDAGlobalDataStruct
Statement . . . . . . . . . : 3266
Message . . . . : Connection #2, Server Job: 303480/QUSER/QXDARECVR.
Cause . . . . . : This message is used by application programs as a general
escape message.
SQL7917 Information 00 05/11/08 12:59:55.956784 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16590
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 8
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPC2206 Completion 00 05/11/08 13:06:49.865608 QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . . : Ownership of object SAPFGUTRBL in R3PRO02070 type *SQLPKG
changed.
Cause . . . . . : The ownership of object SAPFGUTRBL in library R3PRO02070
type *SQLPKG has changed.
CPC2206 Completion 00 05/11/08 13:06:50.312272 QSYCHONR QSYS 0665 QSQXPGM QSYS 0469
Message . . . . : Ownership of object SAPFGUTRBL in R3PRO02070 type *SQLPKG
changed.
Cause . . . . . : The ownership of object SAPFGUTRBL in library R3PRO02070
type *SQLPKG has changed.
SQL0204 Diagnostic 30 05/11/08 13:06:51.011064 QSQPRCED QSYS *STMT QSQPRCED QSYS *STMT
From module . . . . . . . . : QSQPRCED
From procedure . . . . . . : SENDDIAG
Statement . . . . . . . . . : 19346
To module . . . . . . . . . : QSQPRCED
To procedure . . . . . . . : QSQPRCED
Statement . . . . . . . . . : 18435
Message . . . . : T801WEI in R3PRO32060 type *SQLPKG not found.
Cause . . . . . : T801WEI in R3PRO32060 type *SQLPKG was not found. If the
member name is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement and the type is *N, a constraint or partition was not found. If
this is not an ALTER TABLE statement and the type is *N, a function,
procedure, trigger or sequence object was not found. If a function was not
found, T801WEI is the service program that contains the function. The
function will not be found unless the external name and usage name match
exactly. Examine the job log for a message that gives more details on which
function name is being searched for and the name that did not match.
Recovery . . . : Change the name and try the request again. If the
object is a node group, ensure that the DB2 Multisystem product is installed
on your system and create a nodegroup with the CRTNODGRP CL command. If an
external function was not found, be sure that the case of the EXTERNAL NAME
on the CREATE FUNCTION statement exactly matches the case of the name
exported by the service program.
CPC2206 Completion 00 05/11/08 13:06:51.378408 QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . . : Ownership of object T801WEI in R3PRO32060 type *SQLPKG
changed.
Cause . . . . . : The ownership of object T801WEI in library R3PRO32060 type
*SQLPKG has changed.
CPC2206 Completion 00 05/11/08 13:06:51.439824 QSYCHONR QSYS 0665 QSQXPGM QSYS 0469
Message . . . . : Ownership of object T801WEI in R3PRO32060 type *SQLPKG
changed.
Cause . . . . . : The ownership of object T801WEI in library R3PRO32060 type
*SQLPKG has changed.
CPF5009 Diagnostic 10 05/11/08 13:06:51.708688 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 9
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member T801W.
Cause . . . . . : The output or update operation to member number 1 record
number 0 format T801W, for member T801W file T801W in library R3PRODATA,
failed. Member number 1 record number 751 format T801W has the same record
key as member number 1 record number 0 format T801W. If the record number
is zero, the duplicate record key occurred on an output operation. Recovery
. . . : Change either record key so that the keys are unique. Then try
your request again.
CPF5034 Sender copy 30 05/11/08 13:06:51.708736 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 0 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member T801W file T801W in library
R3PRODATA, or in a based-on member of T801W. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file T801W in library R3PRODATA. Recovery .
. . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
CPF5034 Notify 30 05/11/08 13:06:51.708776 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 0 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member T801W file T801W in library
R3PRODATA, or in a based-on member of T801W. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file T801W in library R3PRODATA. Recovery .
. . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:51.710352 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint T801W in R3PRODATA exists over one or more
columns of table T801W in R3PRODATA. The operation cannot be performed
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 10
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
SQL0518 Diagnostic 30 05/11/08 13:06:51.732720 QSQROUTS QSYS *STMT QSQROUTS QSYS *STMT
From module . . . . . . . . : QSQCLNUP
From procedure . . . . . . : SQROUTE_CLEANUP
Statement . . . . . . . . . : 3814
To module . . . . . . . . . : QSQCLNUP
To procedure . . . . . . . : SQROUTE_CLEANUP
Statement . . . . . . . . . : 3814
Message . . . . : Prepared statement RD0IAAAABA not found.
Cause . . . . . : An EXECUTE statement referred to the statement RD0IAAAABA.
RD0IAAAABA is not a valid prepared statement. The statement has one of the
following conditions: -- The statement has never been prepared. -- The
statement identifies a prepared SELECT or DECLARE PROCEDURE statement. --
The statement was in error at prepare or bind time. -- The statement was
prepared in another program or another call of this program and the program
was created with CLOSQLCSR(*ENDPGM). -- The statement was prepared in
another module or another call of this module and the module was created
with CLOSQLCSR(*ENDMOD). -- The statement was prepared in another call of
this program and programs which have run SQL statements have ended and the
program was created with CLOSQLCSR(*ENDSQL). -- The statement was prepared
in another call of this module and the activation group ended between calls.
The module was created with CLOSQLCSR(*ENDACTGRP). -- The prepared statement
was destroyed by a COMMIT or ROLLBACK statement. This only occurs when
connected to a database other than DB2 UDB for iSeries. Recovery . . . :
Do one of the following: -- If RD0IAAAABA identifies a prepared SELECT or
DECLARE PROCEDURE statement, a different prepared statement must be named in
the EXECUTE statement. -- If the statement had errors, correct the errors
and either prepare the statement again or precompile the program again. --
Make certain that RD0IAAAABA has been prepared in the same program or module
call prior to using the EXECUTE statement or specify either
CLOSQLCSR(ENDSQL), CLOSQLCSR(ENDJOB), or CLOSQLCSR(*ENDACTGRP) when
precompiling the application. -- If the statement was deleted by a COMMIT or
ROLLBACK, either specify PREPARE WITH HOLD or bind the program with the
correct option to preserve prepared statements.
CPF5009 Diagnostic 10 05/11/08 13:06:56.094184 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635738 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 51
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.094240 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.094256 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.094376 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.096008 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 52
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635779 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.096048 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.096080 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.096208 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 53
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.098520 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635819 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.098552 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.098568 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.098720 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 54
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.101560 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635865 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.101592 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.101608 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.101760 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 55
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.105864 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635906 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.105904 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.105920 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 56
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.106056 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.107696 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635948 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.107736 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.107752 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 57
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.107880 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
SQL0204 Diagnostic 30 05/11/08 13:06:56.159320 QSQPRCED QSYS *STMT QSQPRCED QSYS *STMT
From module . . . . . . . . : QSQPRCED
From procedure . . . . . . : SENDDIAG
Statement . . . . . . . . . : 19346
To module . . . . . . . . . : QSQPRCED
To procedure . . . . . . . : QSQPRCED
Statement . . . . . . . . . : 18435
Message . . . . : T801LEI in R3PRO32060 type *SQLPKG not found.
Cause . . . . . : T801LEI in R3PRO32060 type *SQLPKG was not found. If the
member name is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement and tI don't have FIOS but I do use Safari to access the discussion forums without encountering the issue you've described (knock on wood). It's always hard to diagnose and troubleshoot connection issues without actually sitting in front of the computer (even more so when the problem is intermittent). Let me ask some questions:
Is your computer connecting wirelessly?
Have you tried resetting Safari and/or emptying the cache?
Have you tried Private Browsing to note any differences?
How about going to Safari's->Preferences->Security and checking/unchecking Web Contents and/or enabling/disabling cookies?
Have you tried creating another user account on your machine and log in with that user account to access the discussion board to see if there's a difference?
Good luck,
TK
Maybe you are looking for
-
Is there any way to erase all files from a broken macbook without switching it on??
My macbook air died when I stupidly spilled nail polish remover over the keyboard- this was actually about two years ago and for various reasons I've only just gotten round to figuring out the best way to dispose of it. The problem is that it no long
-
Network and Bandwidth Monitor Suggestion?
I was wondering if anyone had a suggestion for a network monitor application that runs well on Leopard Server. I would hope it could provide statistics on different ethernet interfaces as well as filter down to ip addresses. I've used Network Monitor
-
WD My cloud mirror and Lightroom
I have bought WD My Cloud mirror to store all my photos. But I'm having trouble with: 1. At all finding WD My cloud Mirror in Lightroom, so I can work with my pictures. 2. It takes forever to import my photos from my SD card to the external hard driv
-
Hi, I try to develop a Photoshop CC extension panel with the Extension Builder V3. But when I try to run the panel I get an error message saying that the CEP Service is not found. I check the file system and cannot find it either. Any suggestions? Th
-
All links are for IE not firefox
Before I updated to version 4.0.1, I could open any webpage with Firefox, now I can only open with IE. For example CCleaner, at the bottom when I click check for new versions it opens up the home page with IE instead of FF. Another example my friends