Sometimes hangs at "acpi bus type pnp registered"

Sometimes, not always, my vaio vgn-c25g hangs at acpi bus type pnp registered when booting, ctl+alt+del does no t work, it's just freezed, I have to keep pressing the power button until the laptop shutdown and restart again.

100% sure. Here is the output of parted /dev/sdb print:
Model: ATA KINGSTON SV300S3 (scsi)
Disk /dev/sdb: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 316MB 315MB ext4 boot legacy_boot
2 316MB 13.2GB 12.9GB ext4 var
3 13.2GB 21.8GB 8590MB linux-swap(v1) swap
4 21.8GB 120GB 98.2GB ext4 root
And the one for /dev/sda:
Model: ATA ST2000DM001-9YN1 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 32.3kB 2000GB 2000GB primary ext4
I am often booting on parted magic to check the drives. From this place I tried to copy a big amount of data using dd from /dev/null to a file on disk (100 Go). This was achieved without any problem. This is why I am so confused:
- on one side every symptom points to a damaged disk;
- but every test I tried indicate that the disk work like a charm.
Last edited by Tabs (2015-02-01 21:34:16)

Similar Messages

  • Installing Solaris 7 - System hangs while determining bus Types

    Hi,
    I am trying to install Solaris 7 on my Compaq Presario. My system hangs immediately after the first screen. It hangs on the screen where it says "Bus Enumeration Determining Bus Type and gathering hardware configuration data. Not sure why it is doing that. Any help would be appreciated
    Regards,
    Ashish.

    My system is not branded It is custom bulit.
    What more information you want write me.
    Thanks for all help
    Amit

  • Hang at "Bus Enumeration Determining Bus Type .."

    Solaris 8 2/02 (also Solaris 7, 11/99), diskette images from Sun Site and delivered and CD's, hangs in DCA, either at "Bus Enumeration Determining Bus Type .." or any simple scan.
    Anybody know if I can do anything to get Solaris installed ? Machine info :
    Packard Bell NEC 00000000000000000000000 P170107002,Board: MS6168
    System Serial Number: K115600045
    600 megahertz Intel Pentium III
    32 kilobyte primary memory cache,256 kilobyte secondary memory cache
    Bus Clock: 100 megahertz,BIOS: American Megatrends, Inc. V2.9 12/10/99

    And, you system is solman ? Right ?
    This is the problem
    1 ETA034 Source client........................ "001"
    1 ETA188 Source client user masters............"000"
    Please cancel your client copy and follow below note:
    1630984 - Which Client Copy options to use for SAP Solution Manager to create a new Client ?
    Divyanshu

  • TV screen sometimes hangs while using apple tv

    When I project the computer screen on the TV screen using the apple tv, the picture is not moving smoothly and sometimes hangs the TV screen.

    Does it just look darker all the time or does the brightness change over time?
    If it just looks darker, check Settings>Video and if set to RGB Low try RGB High or YCrCb.
    I was watching a digital copy of final Harry Potter last night that came bundled with the Blu Ray - could not believe how dark the film was - I used to routinely use RGB Low on AppleTV1, and such settings options have only just appeared on AppleTV2.  I could see hardly any shadow detail on RGB Low, much improved on RGB High.
    AC

  • Movement Type & Excise Register

    Hi Experts !
    Is there any configuration between movement type & Excise Register, where do we define Excise Register's receipt / issue indicator for movement type
    I want to define movement type 161 in RG23A Part I Issue side, at present with the existing setup it is coming in receipt side instead of issue side.
    How it is possible ?
    Pl. help,

    Thanks Prasanna,
    As per u r guidance , I could assignt register to movment type , but how i will assure that it will go in issue side of register ???
    Do any where we assign the Receipt or Issue Indicator ?
    Thnx & Rgds,
    Vikas

  • After IOS 5 upgrade my contacts can't be edited and whenever i choose group it blanks. Also my camera sometimes hang and wrong orientation landscape and potrait. Iphone 3GS

    After IOS 5 upgrade my contacts can't be edited and whenever i choose group it blanks. Also my camera sometimes hang and wrong orientation landscape and potrait. Iphone 3GS

    Try resetting it: hold the on/off and home buttons until you see the Apple logo (ignoring the off slider that appears first), and release.  If that doesn't work, connect to iTunes, go to the Summary tab and Restore.

  • My iPad2 will sometimes hang when loading an mp4. Gives an error message then attempts to resync which hangs until I unplug the iPad.

    My iPad2 will sometimes hang when loading an mp4. Gives an error message then attempts to resync which hangs until I unplug the iPad.
    I have an iPad 2and have not had any trouble until I up dated my os. I have a pc with win 7.  I do not sync since I have so much music on my computer. I synced my apps during the back up but I had to manually reload my music and videos. Since then I turned off all syncs.
    Since I have to load all my movies on this has been happening. I get through about 4 movies then it will hang up. I eventually get an error message that it cannot load this movie. I then attempts to close out. This seems to hang. When I attempt to eject the iPad it attempts to sync and that never finishes. I pull the plug and that stops the sync but I have to restart the computer before I plug back in the iPad or it will not recognize it or it will attempt to finish the sync which never ends. It sometimes hangs on something with safari and site protection.
    After I restart my computer I can put in 4 or so movies, including the one it hung on before, but it always hangs up again. Any suggestions?

    I am having an almost identical problem and hoped that iOS 6 and the new iTunes would fix it.  Regrettably, I again got 3 movies synced last night before iTunes locked up and gave me the xxxx cannot be synced "because the file cannot be written" message.  Same deal with iTunes hanging on "finishing sync" after that and me having to remove the iPad from the cable to get things to come back to life on the PC (Win 7 64 bit).
    I've also done a factory restore followed by a restore from backup and have the same problem. 

  • IPad Mini 2 goes ballistic when being charged -- in other words, it hangs abruptly ; does not type properly. Moreover, in some instances open apps peculiarly force quit without the screen being touched whatsoever.

    iPad Mini 2 goes ballistic when being charged -- in other words, it hangs abruptly ; does not type properly. Moreover, in some instances open apps peculiarly force quit without the screen being touched whatsoever.

    Hi, RomeroSalsa. 
    Thank you for visiting Apple Support Communities. 
    I understand that you are experiencing an issue with the responsiveness of your iPad mini while charging.  I would need a little more information on how you are charging the device to provide a better answer.  While the steps below are not exactly labeled for this issue, they may help resolve the issue.
    If the battery doesn’t charge
    If the battery doesn’t charge, unplug your device and try these steps:
    Look at the connector at the bottom of your device and make sure it’s free of debris.
    If you're using a USB power adapter, make sure it's plugged in all the way and the power outlet is working. If you're connecting to a computer, make sure it's on and can charge your device. To charge an iPad, you might need to use a USB power adapter and plug into a power outlet.
    Try a different USB cable, USB power adapter, or USB port.
    If everything seems to be working, reconnect your device and wait for 30 minutes.
    If your device still doesn’t charge, try to restart it while it's connected to power. If you can't restart, reset your device.
    If you can’t charge your iPhone, iPad, or iPod touch
    -Jason H. 

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

  • HDD sometimes "hangs" and makes repetitive noises after package instal

    So I installed Arch the other day on my old computer, after getting tired of Ubuntu's  slowness and outdated versions of software. But I seem to be having a problem. Now keep in mind that this HDD works fine at all other times, and the SMART data seems OK.
    When pacman is actually installing a package (i.e. "(1/2) installing [package]"), the process sometimes hangs, while the hard drive is making a repetitive noise. This only happens directly after the package install. The system does not freeze while it is doing this. At all other times, the hard drive behaves normally and the system runs smoothly. Is there anything that pacman reads/writes to directly after the package install that could be causing this?
    EDIT: This seems to be happening on removal of packages as well.
    Last edited by Degru (2013-10-30 17:46:09)

    - "click zzzzzzzz, click zzzzzzz, click zzzzzzz"
    - fire up Disk Utility. No HDD
    Are those early signs of a dying hard drive?
    It's definitely not normal behavior. The HDD could be dying, or there could be data corruption. Either way... not good.
    I strongly recommend that you back up any important files as soon as humanly possible.
    Get anything you need off that drive... and send the computer in for service.

  • X200s sometimes hangs/freezes when goes back from sleep

    There is a confirmed bug in ubuntu jaunty/karmic running on lenovo x200 series notebooks. Shortly, it sometimes hangs/freezes when goes back from sleep mode.
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/479842
    Does anyone know anything  about it? How do i contact lenovo engeneer about it?
    Here is filled bug report in ubuntu bugtracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/479842

    There is a confirmed bug in ubuntu jaunty/karmic running on lenovo x200 series notebooks. Shortly, it sometimes hangs/freezes when goes back from sleep mode.
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/479842
    Does anyone know anything  about it? How do i contact lenovo engeneer about it?
    Here is filled bug report in ubuntu bugtracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/479842

  • Impdp hangs on Processing object type... INDEX

    I'm trying to import dump files for many hours, but I's hangs on:
    Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEXThe status of import is:
    Import> status
    Job: SYS_IMPORT_SCHEMA_10
      Operation: IMPORT
      Mode: SCHEMA
      State: EXECUTING
      Bytes Processed: 25,072,580,204
      Percent Done: 99
      Current Parallelism: 1
      Job Error Count: 0
      Dump File: /backup/import/EXP_DB01.dmp
      Dump File: /backup/import/EXP_DB%u.dmp
      Dump File: /backup/import/EXP_DB2%u.dmp
      Dump File: /backup/import/EXP_DB201.dmp
      Dump File: /backup/import/EXP_DB3%u.dmp
      Dump File: /backup/import/EXP_DB301.dmp
      Dump File: /backup/import/EXP_DB401.dmp
      Dump File: /backup/import/EXP_DB4%u.dmp
      Dump File: /backup/import/EXP_DB02.dmp
      Dump File: /backup/import/EXP_DB202.dmp
      Dump File: /backup/import/EXP_DB302.dmp
      Dump File: /backup/import/EXP_DB402.dmp
    Worker 1 Status:
      State: EXECUTING
      Object Schema: PROJ
      Object Name: BKPIN6_PK
      Object Type: DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX
      Completed Objects: 295
      Worker Parallelism: 1And the SQL*Plus shows:
    OPNAME                    TARGET                    SOFAR  TOTALWORK UNITS      ELAPSED_SECONDS MESSAGE
    Table Scan                PROJ.TB_ENTR_001          1056002    1091871 Blocks                 363 Table Scan:  PROJ.TB_ENTR_001: 1056002 out
                                                                                                     of 1091871 Blocks doneSo, the "Table scan" above is done MANY TIMES and when I see the status on prompt import,
    the object name is the same: BKPIN6_PK
    So, Is it hanging?
    What can I do to solve this?
    Thank you very much!

    Hi,
    The only "process" in database is this import:
       SID    SERIAL# USERNAME       MACHINE              OSUSER       PROGRAM                   STATUS   LOGON
        98      29557 DBSNMP         ORASRV grid         emagent@ORASRV INACTIVE 20/09/11 22:39:59
                                                                     (TNS V1-V3)
       136      44447 DBSNMP         ORASRV grid         emagent@ORASRV INACTIVE 20/09/11 22:39:59
                                                                     (TNS V1-V3)
       107         52 DBSNMP         ORASRV grid         emagent@ORASRV ACTIVE   20/09/11 22:41:29
                                                                     (TNS V1-V3)
        55       1348 PROJ         ORASRV oracle      oracle@ORASRV ACTIVE   21/09/11 11:10:53
                                                                     (DW01)
       151          9 SYS            ORASRV oracle      racgimon@ORASRV INACTIVE 16/08/11 13:05:29
                                                                     (TNS V1-V3)
       150         11 SYS            ORASRV oracle      racgimon@ORASRV ACTIVE   16/08/11 13:05:34
                                                                     (TNS V1-V3)
       135          5 SYS            ORASRV oracle      racgimon@ORASRV INACTIVE 16/08/11 13:05:34
                                                                     (TNS V1-V3)
       132         49 SYS            ORASRV oracle      racgimon@ORASRV INACTIVE 16/08/11 13:06:34
                                                                     (TNS V1-V3)
        51      42168 SYS            ORASRV oracle      udi@ORASRV ACTIVE   21/09/11 11:10:40
                                                                    rp (TNS V1-V3)
        85      13018 SYS            ORASRV oracle      oracle@ORASRV ACTIVE   21/09/11 11:10:49
                                                                     (DM00)
        64       8930 SYS            ORASRV oracle      udi@ORASRV INACTIVE 21/09/11 14:45:13
                                                                    rp (TNS V1-V3)
        87       9380 SYS            ORASRV oracle      sqlplus@ORASRV ACTIVE   21/09/11 15:26:16
                                                                     (TNS V1-V3)thank you!

  • 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

  • Applications Sometimes Hang Finder

    I relatively recently upgraded from a G3 IMac with 10.3 to a G4 IMac with 10.5.
    I've noticed one or two discrepancies in performance quality which I initially ignored, but they've persisted long enough that they've become annoying and I really do want to resolve them. All issues occur only sometimes, but if I switch between a couple running applications enough I can sometimes cause them to happen.
    1.) The first issue is that Finder hangs when I switch to it from a running application. I don't know why, or what sequence of actions causes it, but most often it will occur immediately after trying to click my desktop from Firefox or VLC.
    I'll usually habitually click my desktop to shift out of the current application and to Finder. It won't and I only really end up noticing it when I start selecting or renaming files. When I try to select files, I can never deselect them, so I end up selecting more than I want in attempt to shake the issue. Also when I want to rename a file, the name text simply vanishes until I click away, and it returns to normal. I just can't rename files when this issue arises. All the while during whatever application I was leaving still appears in the menu bar even if I'm specifically selecting files in Finder.
    I can only seem to shake the issue if I open a Finder window and click the window's menu bar area, when my menu switches back to Finder and I deselect and rename files again.
    This is the biggest issue as it happens the most often.
    2.) The second issue is a problem I encounter when I'm in the middle of renaming a file. Out of nowhere the name change text box will close when I type in a letter, and reopening it just leads to the problem repeating itself. A bit of fidgeting with windows and selections stifles the problem, but it's quite irritating when it comes up. Doesn't happen very often.
    3.) And seems to have started happening. My third issue is that I'll quit an application like Firefox, Quicktime, or VLC, and then move to something else while it quits. I soon notice that it hasn't quit. The window's still open, the icon's still in the dock, and it's still "on". I don't get the "application is not responding" from the control-click or force-quit menus, and it immediately disappears if I click the still-open window, like it had already quit, but just forgot to leave my screen until I poked it.
    So for the most part, it's just a bunch of issues with applications, selections, and renaming, and that ends up hurting when you're organizing lots of files.
    Is this expected from a "top-heavy" computer? Is this an unresolved Leopard problem, or does my computer have the hiccups? I'm hoping it's the latter, cause I'd really like to fix it.
    Message was edited by: MasterDogma

    Hi James
    It sounds like you might have moved all your applications into the folder that's on your desktop, for one thing. First, close all your open applications (except for Finder). If any of them are still in the trash, get them out, and move them all back to the correct location. While many applications will work fine wherever they are, it's a good idea to keep them in the main Applications folder at the top of the hard drive.
    Once the apps are back where they should be (and the desktop folder is empty), trash the desktop folder. Then, open a new Finder window, and click on the Macintosh HD icon in the sidebar. You should see your Applications folder on the right, which you can now pull into the sidebar to create a shortcut.
    Matt

  • T61 sometimes hangs during boot

    Sometimes when booting my T61  it hangs about 4 sec into it after displaying one icon in the system tray.  After that the only activity is the hard drive indicator blicking about once every 5 seconds.  When I manually turn off the computer then reboot sometimes it repeats this and sometimes not.  Sometimes it takes 3 or 4 manual reboots before it starts booting normally again.  The last time it started right after I removed the AC power and went on battery then rebooted but the problem has occurred regardless of power source.

    speedkreature, welcome to the forum,
    what you have experienced is definitely not normal, I'd go as far as saying weird.
    Does the same happen running without the battery? Has your RAM also been swapped out? If you are running with two sticks of RAM, does the same happen running with one, (swapping sticks and slots etc.)?
    All that would then remain would be to remove the WLAN and BT cards.
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

Maybe you are looking for

  • Can't access youtube and google docs.

    I can't access some websites, like youtube (I can only see a page with text and links) and google docs (firefox stops downloading like everything is correct, but nothing happens). Allready fully uninstalled (as far as I know, forgot bookmarks, passwo

  • Purchase Order  - matrix

    Hi,   I would like to place some data from an array in my code to the matrix in Purchase Order Screen.But the Below code is throwing "Invalid Column" error If oApplication.Forms.ActiveForm.TypeEx = "142" Then                 oMatrix = oApplication.Fo

  • Map XML tag to an object style

    Hi everyone! I am not sure this is the correct place to post it, but i didn't find any "tagging" department of the forums. I do import some XML into ID document. Text nodes of my XML are imported properly, and i can map any tag of XML to one of the p

  • SWF_XI_CUSTOMIZING error

    Hi all, In transaction SWF_XI_CUSTOMIZING, when I run the customizing step: Maintain Runtime Environment -> Schedule Background Job for Deadline Monitoring I have SP14. I get this error: Error within CL_SWF_ADM_JOB_FACTORY=>GET_INSTANCE Any ideas? Or

  • Cannot find safari view and toolbar

    Safari toolbar and view icon keeps disappearing on my iMac OS X Mountain Lion 10.8.2. I've tried all solutions I found online in vein.... Can anyone help...? Thank you.