JFileChooser hangs sometimes

Hi,
When I open a JFileChooser save dialog the EDT thread hangs indefinitely. From the stack trace I can see that it is waiting indefinitely when it tries to check if a file is a link or not. This happens only sometimes.The default selected directory(My Documents) does not contain any links or shortcuts.
Following is the stack trace of AWT-EventQueue thread:
"AWT-EventQueue-2" prio=6 tid=0x039c9400 nid=0x1210 waiting on condition [0x0400e000..0x0400fb94]
java.lang.Thread.State: WAITING (parking)
     at sun.misc.Unsafe.park(Native Method)
     - parking to wait for <0x0ae38cd0> (a java.util.concurrent.FutureTask$Sync)
     at java.util.concurrent.locks.LockSupport.park(Unknown Source)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Unknown Source)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(Unknown Source)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown Source)
     at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
     at java.util.concurrent.FutureTask.get(Unknown Source)
     at sun.awt.shell.Win32ShellFolderManager2$ComInvoker.invoke(Unknown Source)
     at sun.awt.shell.Win32ShellFolder2.hasAttribute(Unknown Source)
     at sun.awt.shell.Win32ShellFolder2.isLink(Unknown Source)
     - locked <0x0ae38b00> (a sun.awt.shell.Win32ShellFolder2)
     at javax.swing.filechooser.FileSystemView.isFileSystem(Unknown Source)
     at javax.swing.filechooser.FileSystemView.getSystemDisplayName(Unknown Source)
     at javax.swing.plaf.basic.BasicFileChooserUI$BasicFileView.getName(Unknown Source)
     at javax.swing.JFileChooser.getName(Unknown Source)
     at sun.swing.FilePane$FileRenderer.getListCellRendererComponent(Unknown Source)
     at javax.swing.plaf.basic.BasicListUI.updateLayoutState(Unknown Source)
     at javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(Unknown Source)
     at javax.swing.plaf.basic.BasicListUI.getPreferredSize(Unknown Source)
     at javax.swing.JComponent.getPreferredSize(Unknown Source)
     at javax.swing.ScrollPaneLayout.layoutContainer(Unknown Source)
     at java.awt.Container.layout(Unknown Source)
     at java.awt.Container.doLayout(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validateTree(Unknown Source)
     at java.awt.Container.validate(Unknown Source)
     - locked <0x0914e040> (a java.awt.Component$AWTTreeLock)
     at java.awt.Dialog.conditionalShow(Unknown Source)
     - locked <0x0914e040> (a java.awt.Component$AWTTreeLock)
     at java.awt.Dialog.show(Unknown Source)
     at javax.swing.JFileChooser.showDialog(Unknown Source)
     at javax.swing.JFileChooser.showSaveDialog(Unknown Source)
     at com.text.SaveApp.launchExportDialog(ActionManager.java:1356)
     at com.text.SaveApp.actionPerformed(ActionManager.java:608)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.AbstractButton.doClick(Unknown Source)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
"Basic L&F File Loading Thread" prio=6 tid=0x03413800 nid=0x1438 waiting on condition [0x0503f000..0x0503fd94]
java.lang.Thread.State: WAITING (parking)
     at sun.misc.Unsafe.park(Native Method)
     - parking to wait for <0x0ae389c0> (a java.util.concurrent.FutureTask$Sync)
     at java.util.concurrent.locks.LockSupport.park(Unknown Source)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Unknown Source)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(Unknown Source)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown Source)
     at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
     at java.util.concurrent.FutureTask.get(Unknown Source)
     at sun.awt.shell.Win32ShellFolderManager2$ComInvoker.invoke(Unknown Source)
     at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread.run0(Unknown Source)
     at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread.run(Unknown Source)
"Swing-Shell" daemon prio=6 tid=0x03b8e800 nid=0x7e4 waiting for monitor entry [0x0437f000..0x0437fb14]
java.lang.Thread.State: BLOCKED (on object monitor)
     at sun.awt.shell.Win32ShellFolder2.isFileSystem(Unknown Source)
     - waiting to lock <0x0ae38b00> (a sun.awt.shell.Win32ShellFolder2)
     at sun.awt.shell.Win32ShellFolder2.equals(Unknown Source)
     at java.util.AbstractList.equals(Unknown Source)
     at java.util.Vector.equals(Unknown Source)
     - locked <0x0ae38b90> (a java.util.Vector)
     at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread$1.call(Unknown Source)
     at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread$1.call(Unknown Source)
     at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
     at java.util.concurrent.FutureTask.run(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at sun.awt.shell.Win32ShellFolderManager2$ComInvoker$3.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Let me know if any one has faced similar problems.

"AWT-EventQueue-2"
- locked <0x0ae38b00> (a sun.awt.shell.Win32ShellFolder2)
"Swing-Shell"
- waiting to lock <0x0ae38b00> (a sun.awt.shell.Win32ShellFolder2)
That's definitely a symptom of the problem. AWT-EventQueue-2 has not released that lock because it is:
- parking to wait for <0x0ae38cd0> (a java.util.concurrent.FutureTask$Sync)
Can you find that object "0x0ae38cd0" somewhere else in the thread dump? It might be revealing to see who has ahold of it and why they haven't released it yet.

Similar Messages

  • HT4623 Ater installing IOS 6 for my iphone 4,some apps are hang sometimes and Mail apps totally hang ,tried to reset again and again but still hang

    Ater installing IOS 6 for my iphone 4,some apps are hang sometimes and Mail apps totally hang ,tried to reset again and again but still hang.How to solve this problem??

    well in thatcase, i need another help .
    thanks for your instant reply.
    i have currently bought a new laptop (windows 8) and my iphone is not being recognized by itunes.
    because i have no backup on my previous laptop, i downloaded touchcopy but even touch copy is not recognizing my iphone.

  • HT1222 I have iphone 4 and the software is ios 7.0.2. I am facing problems with my phone. Since the last software update my phone has started giving problems. like it hangs sometime when i recieve an incoming call. The carrier status bar shifts down a bit

    I have iphone 4 and the software is ios 7.0.2. I am facing problems with my phone. Since the last software update my phone has started giving problems. like it hangs sometime when i recieve an incoming call. The carrier status bar shifts down a bit and sometimes it vanishes automatically. I,m confused.
    Secondly i have an update IOS 7.0.4 waiting in my Software Update menu. I have tried so many times to update my iphone but it always fails to update the IOS 7.0.4. Any body suggest anything regarding this

    Wow. Lots of help. Thanks apple

  • Why does my A to D hang sometimes?

    I have been using a VXIpc-850 (200 MHz) controller and a VM2616 DAC with good success.  Now I switched to a VXIpc-872B (1.26 GHz) controller and I get a hang sometimes when I do an instrument write.  Here is the process I use: 1. Reset instrument, set voltage range and triggering.  2. Send data to instrument.  3. Write to instrument with following string: STATPER:COND?.  4. Read instrument.  5. Write to instrument with the following string: REG:ADDR 0,(@1).  Most of the time it hangs at the first write (STATPER:COND?), sometimes it hangs at the reset, sometimes it hangs at the last write, sometimes it proceeds without errors and gives me the data I expect.  I updated the drivers and added delays in various places to account for the faster processor but I suspect there is something else.
    Does anybody have any clues?
    Kendrick Krause
    PS. That is supposed to be STAT colon OPER:COND?.  It is interpreting the colon O as a smiley face.

    Hello John,
    THANKS for the response.
    I have tried adding delays up to 1 full second and boolean indicators all over the place to track the flow.
    Still works with the other controller.
    Ooops, forgot to mention that old controller and code is LV 5.1 - Win'98, new controller and code is LV 7.1 - WinXP. (yes, re-compiled)
    Still, I don't suspect the code because of the "somtimes it hangs".
    I can run it over and over several times with no problem, then... stuck.
    70% of the time it hangs at the first write the other 30% is spread between Reset, the second Write and Read, once it hung on a config.
    I haven't given up adding delays, I'll dig deeper but the system and its software are not mine.
    Will keep you posted, unless you or somone else has any other ideas.
    Thanks,
    Kendrick

  • JFileChooser hangs when clicking OK or CANCEL

    I have created an applet to run primarily in Netscape 6 with JRE 1.3.1. I have also adjusted the policy file to give my applet all permissions on the local system. In my Applet I want the user to select a file from the local hard drive. To achieve this I am using the JFileChooserClass however after I select a file from the FileChooser and click OK the dialog does not disappear and Netscape hangs.
    Has anyone else seen this behaviour? Is there a way to workaround it?
    I have included my code just in case I am doing something wrong.
    import java.awt.*;
    import javax.swing.*;
    import javax.swing.filechooser.*;
    System.setSecurityManager(null);
    int returnVal = 0;
    String fileName = "";
    //Create a file chooser
    final JFileChooser fc = new JFileChooser();
    returnVal = fc.showOpenDialog(this.getParent());
    if (returnVal == JFileChooser.APPROVE_OPTION) {
    File file = fc.getSelectedFile();
    fileName = file.getAbsolutePath();
    Thanks,
    Anthony

    Hi,
    I am having a similar problem. We have a signed applet that presents a JFileChooser and the user selects a file to open. The JFileChooser hangs IE. The applet worked fine on JRE1.3.0.2. The problem arose when we upgraded to JRE1.3.1. Down grading to 1.3.0.2 is not an option for us. Does anyone have a workaround ?
    regards,
    Joag

  • My Satellite L650 sometimes hang sometimes

    Hello,
    My Satellite L650 sometimes hang sometimes, most of time it happens when im gaming, the sounds "hangs" it makes wierd sounds when it does and also my video graphics are laggy. Never had it on any other pc/laptop before :S
    How can I fix this?
    Greetings,
    Arnie

    Hi buddy,
    Can you post a little bit more details? Also some information about operating system would be nice, nobody knows what you use. Do you use a Linux distribution?
    If you play games I would recommend high performance power plan as as*** already wrote. It offers best option and performance for games and other high CPU usage programs.
    Furthermore keep your system clean: uninstall programs that you dont need and disable start up programs that you dont need. This can improve the performance a lot!
    But you must understand its very hard to say something about sometimes errors.

  • In Windows Vista 7, SP2, Firefox takes several minutes to launch, is non-responsive, hangs sometimes launches additional windows without my clicking. I get error code 10003.

    I'm using Firefox 6.0.2 in Wndows Vista 7, SP2. I'm using Norman Security Suite anti-virus software. Firefox behaves erratically. Sometimes it takes several minutes to launch. If I launch an new window it sometimes hangs. It launches two extra windows without my having clicked to launch. Always two. I get an error code 10003 but when I search for this I get no information about it.
    Windows Task Manager shows plugin-container for Firefox running in addition to firefox.exe.

    Troubleshooting extensions and themes
    * https://support.mozilla.com/en-US/kb/Troubleshooting%20extensions%20and%20themes
    Restore the default home page
    * https://support.mozilla.com/en-US/kb/How%20to%20set%20the%20home%20page#w_restore-the-default-home-page
    Clear Cookies & Cache
    * https://support.mozilla.com/en-US/kb/Template:clearCookiesCache
    Clear the Network Cache
    * https://support.mozilla.com/en-US/kb/How%20to%20clear%20the%20cache#w_clear-the-cache
    Check and tell if its working.

  • ITunes 10.2.1.1 (64 bit) freezes/hangs sometimes after playing videos

    On a fresh install of Windows 7 64 bit on Basecamp, using iTunes 64 bit. iTunes will sometimes just hang when a video or video podcast finishes. I have to kill iTunes and restart it. There is a thread about this at:
    http://discussions.apple.com/thread.jspa?messageID=12606470&#12606470
    But it was ignored and archived.
    Note the same thing was also happening on my Dell XPS Laptop with Windows 7 64-bit.

    Same thing is happening to me also.
    this new itunes doesnt seem windows 7 x64 bit happy.
    i am also experiencing itunes freezing when clicking on podcasts on the left sidebar.
    i tried installing sp1 for windows 7 but didnt fix it.

  • IMac hangs (sometimes) on wake up

    Hello everyone
    Over the last month or so, my iMac has sometimes started hanging on wake up.  The mouse still moves and I can click on icons to open programmes but they just bounce and never open.  I can force them to shut down and I can close any programmes I had left open.  It will not go on the wireless network when this happens nor will it let me turn wireless off and on.  I have to do a hard shut down to make it work again.  Normal shut down just results in it sitting doing nothing.
    I copied the system log from this morning's hang up.  I have had my computer for over a year now but some of the inner workings of Macs are still very strange to me (I was a PC user before) so please be patient and do not assume that I will understand a reply.
    Thank you for your help!
    PS I have removed my name from some of the log entries so if a gmail bit looks funny, that's why.
    18/07/2013 07:37:31.198 hidd[59]: MultitouchHID: device bootloaded
    18/07/2013 07:37:31.294 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2139140(2004), shield 0x7f8ad222a170(2001), lock state 3
    18/07/2013 07:37:31.320 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: err 0x0
    18/07/2013 07:37:31.321 WindowServer[86]: Created shield window 0x359 for display 0x003f003d
    18/07/2013 07:37:31.321 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2139140(2002), shield 0x7f8ad222a170(2001), lock state 3
    18/07/2013 07:37:31.321 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: err 0x0
    18/07/2013 07:37:31.321 WindowServer[86]: Created shield window 0x35a for display 0x003f003e
    18/07/2013 07:37:31.322 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2139140(2002), shield 0x7f8ad222a170(2001), lock state 3
    18/07/2013 07:37:31.322 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: err 0x0
    18/07/2013 07:37:31.332 WindowServer[86]: Created shield window 0x35b for display 0x003f003f
    18/07/2013 07:37:31.332 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2139140(2002), shield 0x7f8ad222a170(2001), lock state 3
    18/07/2013 07:37:31.332 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: err 0x0
    18/07/2013 06:02:44.000 kernel[0]: Wake reason: EHC2
    18/07/2013 07:37:31.000 kernel[0]: Previous Sleep Cause: 5
    18/07/2013 07:37:31.000 kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
    18/07/2013 07:37:31.000 kernel[0]: The USB device BRCM2046 Hub (Port 1 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
    18/07/2013 07:37:31.000 kernel[0]: TBT W (1): 0 [x]
    18/07/2013 07:37:31.000 kernel[0]: The USB device Bluetooth USB Host Controller (Port 1 of Hub at 0xfa110000) may have caused a wake by issuing a remote wakeup (3)
    18/07/2013 07:37:31.000 kernel[0]: 33088.340656: performCountryCodeOperation: Not connected, scan in progress[0]
    18/07/2013 07:37:31.000 kernel[0]: HID tickle 205 ms
    18/07/2013 07:37:35.702 loginwindow[55]: resume called when there was already a timer
    18/07/2013 07:37:46.840 WindowServer[86]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    18/07/2013 07:37:46.841 loginwindow[55]: find_shared_window: WID -1
    18/07/2013 07:37:46.841 loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff
    18/07/2013 07:37:46.841 loginwindow[55]: find_shared_window: WID -1
    18/07/2013 07:37:46.841 loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff
    18/07/2013 07:37:46.852 loginwindow[55]: ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
    18/07/2013 07:37:46.956 WindowServer[86]: Created shield window 0x35f for display 0x04280300
    18/07/2013 07:37:46.956 WindowServer[86]: device_generate_desktop_screenshot: authw 0x7f8ad2114220(2000), shield 0x7f8ad16286c0(2001)
    18/07/2013 07:37:46.990 WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x7f8ad2114220(2000), shield 0x7f8ad16286c0(2001)
    18/07/2013 07:37:48.115 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2114220(2000), shield 0x7f8ad16286c0(2001), lock state 2
    18/07/2013 07:37:48.116 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0
    18/07/2013 07:37:48.117 WindowServer[86]: Created shield window 0x360 for display 0x003f003d
    18/07/2013 07:37:48.117 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2114220(2000), shield 0x7f8ad16286c0(2001), lock state 2
    18/07/2013 07:37:48.118 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0
    18/07/2013 07:37:48.119 WindowServer[86]: Created shield window 0x361 for display 0x003f003e
    18/07/2013 07:37:48.119 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2114220(2000), shield 0x7f8ad16286c0(2001), lock state 2
    18/07/2013 07:37:48.119 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0
    18/07/2013 07:37:48.120 WindowServer[86]: Created shield window 0x362 for display 0x003f003f
    18/07/2013 07:37:48.120 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f8ad2114220(2000), shield 0x7f8ad16286c0(2001), lock state 2
    18/07/2013 07:37:48.120 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0
    18/07/2013 07:38:05.681 CalendarAgent[210]: [com.apple.calendar.store.log.caldav.queue] [Got error on refresh, but not rectifying principal because it was manually configured: Error Domain=NSURLErrorDomain Code=-1001 "Time-out van het verzoek." UserInfo=0x7f9cfc182170 {NSUnderlyingError=0x7f9cfc0ddd10 "Time-out van het verzoek.", NSErrorFailingURLStringKey=https://%[email protected]/calendar/dav/40gmail.com///%[email protected]/calendar/dav/40gmail.com/, NSErrorFailingURLKey=https://%[email protected]/calendar/dav/tristanjovanovic%40gmail.c om///%[email protected]/calendar/dav/tristanjovanovic%40gmail.com/, NSLocalizedDescription=Time-out van het verzoek.}]
    18/07/2013 07:38:05.695 CalendarAgent[210]: [com.apple.calendar.store.log.caldav.queue] [Account .com@https://calendar.google.com/calendar/dav/%40gmail.com/user/ timed out when executing operation: <CalDAVAccountRefreshQueueableOperation: 0x7f9cfc639e10; Sequence: 0>]
    18/07/2013 07:38:05.705 CalendarAgent[210]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=NSURLErrorDomain Code=-1001 "Time-out van het verzoek." UserInfo=0x7f9cfc1bef90 {NSUnderlyingError=0x7f9cfc0ddd10 "Time-out van het verzoek.", NSErrorFailingURLStringKey=https://%[email protected]/calendar/dav/40gmail.com///%[email protected]/calendar/dav/40gmail.com/, NSErrorFailingURLKey=https://@calendar.google.com/calendar/dav/tristanjovanovic%40gmail.com///@calendar.google.com/calendar/dav/tristanjovanovic%40gmail.com/, AccountName=Gmail, CalDAVErrFromRefresh=YES, NSLocalizedDescription=Time-out van het verzoek.}]
    18/07/2013 07:38:05.758 com.apple.backupd[3347]: Starting automatic backup
    18/07/2013 07:38:06.713 com.apple.backupd[3347]: Backing up to: /Volumes/Time Machine/Backups.backupdb
    18/07/2013 07:38:07.964 com.apple.backupd[3347]: Using file event preflight for Macintosh HD
    18/07/2013 07:38:08.852 com.apple.backupd[3347]: Will copy (1.01 GB) from Macintosh HD
    18/07/2013 07:38:08.868 com.apple.backupd[3347]: Found 1106 files (1.01 GB) needing backup
    18/07/2013 07:38:08.890 com.apple.backupd[3347]: 3.29 GB required (including padding), 131.78 GB available
    18/07/2013 07:39:54.724 com.apple.backupd[3347]: Copied 5526 files (1.03 GB) from volume Macintosh HD.
    18/07/2013 07:39:54.748 com.apple.backupd[3347]: Using file event preflight for Macintosh HD
    18/07/2013 07:39:54.752 com.apple.backupd[3347]: Will copy (Zero KB) from Macintosh HD
    18/07/2013 07:39:54.752 com.apple.backupd[3347]: Found 15 files (Zero KB) needing backup
    18/07/2013 07:39:54.753 com.apple.backupd[3347]: 2.08 GB required (including padding), 130.74 GB available
    18/07/2013 07:39:58.643 com.apple.backupd[3347]: Copied 435 files (5.6 MB) from volume Macintosh HD.
    18/07/2013 07:39:58.790 com.apple.backupd[3347]: Created new backup: 2013-07-18-073958
    18/07/2013 07:40:13.279 com.apple.launchd.peruser.501[178]: ([0x0-0x37e37e].com.apple.Notes[3349]) Exited: Terminated: 15

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac. 
    These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing. 
    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands. 
    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
    Launch the Terminal application in any of the following ways: 
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
    Step 1 
    Triple-click the line of text below on this page to select it:
    kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit 
    Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
    Step 2 
    Repeat with this line:
    { sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; sudo defaults read com.apple.loginwindow LoginHook; sudo crontab -l; } 2> /dev/null | open -f -a TextEdit 
    This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. 
    Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step. 
    Step 3
    { launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; crontab -l 2> /dev/null; } | open -f -a TextEdit 
    Step 4
    ls -1A /e*/{la,mach}* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -f -a TextEdit  
    Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
    Step 5
    osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit 
    Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output. 
    You can then quit Terminal.

  • Report Service 10g sometimes hang, sometimes not

    Hi.
    We have a big problem.
    We installed AS 10g R2 on a Windows 2k3 Server. The AS itself is running fine, the form application is also running fine.
    But when we try to create a report from form, than sometimes the form hangs (look like do nothing and wait until ...). And sometimes it works fine.
    We don´t start the report service as in-process.
    We now find out over the trace log, that the reports engine stop with the message:
    rwa:rwadri quit
    It is also very strange that the same report, first let the report service hang, works on a other time.
    And we have the suspicion (we think so), that the report service will not more hang on any time, when it created one report. Until we restart the server.
    But it often hangs, when you restart the whole windows 2003 and than start to create a report from form the first time.
    Mostly it hangs starting a report the first time, when we want to create a report where the form take a date from the user.
    Maybe we have there this pre filled value (for example) in the text-field: "13.06.2006" (dd.mm.yyyy; german format) than it hangs. When we now start the same form and change the day (maybe to "13.06.06") it works. First we thought it is a problem with the date format. But why the same date, first let the report service (and the form) hang, work fine a next time, when the report server create fine a report before?
    And when it works the first time (after rebooting) to create a report it will also work with any form next times.
    Has anyone any suggestions for us?
    We are happy for any tips.
    Thanks.

    Has noone any suggestions to this problem?
    I find out, that the memory usage on the Win2k3 Ent. Server is very large. We have 2GB RAM. When a report from form is started and hangs (run and run and run ...) the memory usage shown at Enterprise Manager for "Others" goes slowly over 1.3GB (more than 50%). The free memory is (when you wait long enough) slowly running down to round about 450MB.
    Mabye that´s the problem!?
    Free disk space on C: (for the temp dir.) is also available (round about 64GB).
    Virtual Memory is set between 2GB and 4GB

  • N73 Hangs Sometimes after sending SMS

    I am using N73(non music edition). I am having a strange problem in my phone. Sometimes after sending sms the phone hangs. When I press menu key to check the background applications it shows "message" there. When I try to kill it by pressing 'c' key of my phone it displays exit application? When I click on yes nothing happens. The message application still remain there in background process. I tried many times but I am unable to kill this application from running in background. Another surprising point is that how message application goes in the background process as I always property exit from message after sending the sms. The only way to get out of this problem is to restart the phone. But I dont want to restart my phone every time. Can anyone help me to get out of this problem?? plz help..

    Sounds like your phone is having some software issues.
    you wanna try to do a software update using NSU. you may get this from http://europe.nokia.com/get-support-and-software/download-software/non-fota-update-phone
    Or alternatively you may key in *#7370# on your phone when on stand by mode., This will also reflash your software, DO NOT FORGET TO DO A BACK UP AS THIS WILL WIPE OUT YOUR PHONE MEMORY.
    Mark me a KUDOS if this has helped...

  • 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 t

    I 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

  • JFileChooser hang when brosing root directory of Truecrypt Encrypted drive

    Hi,
    I have been consistently having a problem with netbeans where if I try to browse to the root directory of my encrypted drive, it hangs for a long time (say 5 - 10 minutes). It then eventually comes back with the correct file choose dialog.
    At first I thought this was just a Netbeans issues. However, I was also developing a Java Swing app (in eclipse) that uses a JFileChooser dialog. If I browse a standard drive I have no problems. If I then go to browse my encrypted file, I get this hang. When I compared the netbeans scenario with this, the only thing in common is that I was trying to browse my encrypted drive.
    This only seems to happen when I want to browser to the root directory of this drive. If I am able to get the dialog to open (on a normal drive) and I directly enter a sub directory of the encrypted drive into the file name field, I can browse there without the hang.
    So just wondering if anyone else has had this problem. I know it isolated to swing JFIleChooser, to at least swing on Windows XP as I don't get this problem through the native file chooser, or through the native file chooser via SWT.
    My drive was encrypted using Truecrypt.
    Truecrypt details
    Size: 41943039488 bytes
    Type: Normal
    Encryption Agorithm: AES
    Key Size: 256 bits
    Block Size: 128 bits
    Mode of Operation: LRW
    Can anyone give me some idea of what might be happening here?
    Regards
    Steve

    I don't know if this is what you are looking for.
    If you need the real roots, you can use this
    File[] file = File.listRoots();
    It should return the available filesystem roots.

  • FF 17.0.1 OS (Mac 10.6.8) gradually slows then hangs, sometimes crashes.

    Since I started using FF 17.0.1 I've had problems. The longer I'm on the slower FF goes. Sometimes it will hang. Might start working again or might need restarted. Sometimes it just crashes completely. Just started happening with FF 17.

    Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
    *Do not click the Reset button on the Safe mode start window or otherwise make changes.
    *https://support.mozilla.org/kb/Safe+Mode
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    If you have submitted crash reports then please post the IDs of one or more crash reports that have this format:
    *bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    You can find the IDs of the submitted crash reports on the <i>about:crashes</i> page.
    *You can open the <b>about:crashes</b> page via the location bar, like you open a website.
    See:
    *http://kb.mozillazine.org/Mozilla_Crash_Reporter
    *https://support.mozilla.org/kb/Mozilla+Crash+Reporter

  • Nokia N95 8GB hangs sometimes

    Hi all,
    I just purchased Nokia N95 8GB 2 weeks backs. I ensured that all softwares are latest. But it is very slow and sometimes hangs. I dont know. First time it hung when I took a photo. Then I restarted it. It worked fine. Then when I was browing through GPRS it hannged. After restart it is OK. Now third time when I try to load a video from the Nokia music CD, it came out of it. Restarted itself. Dont know why this expensive model has such problems?
    Anybody have solution?
    Jayant

    i got N95 8GB from UK 3 which had f/w 11.xxxxx
    i have upgraded to latest f/w available from Nokia 31.xxx.15 but i have to debrand it now i m curious to have latest f/w from UK 3 does UK 3 upgraded its f/w to v.31xxx or they are still stucked to v.20xxx ?

Maybe you are looking for

  • IPad 2 can only connect to unsecured Wireless network.  It won't connect to my secured network at home or at work

    Two days ago my ipad 2 with (wifi only) will not connect to my secured network even though it show's up as available with a strong signal.  It keeps rejecting my password.  I brought the Ipad to work and the same issue.  However I am able to connect

  • Any Ideas for speeding up Macbook Pro?

    My Mac has been acting really slow lately. I have had to get it wiped once already because it was stuck on the grey screen at boot. I know now that I can fix this with safe mode, but I have also been having some big issues using the mac itself. I occ

  • System Profiler Has Duplicate Copies of Apps, why?

    I have 2 identical model enterprise disks from WD @7200rpm, 1TB. When I run the Black Magic disk speed test program, the newest disk reports read& write @ 116 mbps and the older disk reports about 126 mbps. That difference is enough to enable the old

  • Text editing in Web Dynpro for ABAP

    Hi I am interested in getting ideas on the best way to achieve the following functionality in Web Dynpro for ABAP: 1) A text-editor where some basic formatting is possible (Italic, Bold, etc.) for the user to enter formatted text. 2) Save this text i

  • Planning functions IRR, NPV in BI + SEM 6.0

    Hi everybody!, I'm looking for the older financial functions like IRR, NPV calculations. Somebody told me that they are not longuer in BI unless you install SEM 6.0. We've just install it this morning but the functions doesn't appear when I try to cr