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.

Similar Messages

  • 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

  • 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

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

  • Firefox sometimes hangs for about a minute. Fedora 12, firefox 6.0.2

    I am using ff 6.0.2 with Fedora 12, and have a problem of the browser hanging sometimes. I have started firefox in safe mode, but it still happens.
    It usually happens when I am trying to open a bookmark inside a folder inside the Bookmarks toolbar. When I click on such a folder on the toolbar, firefox starts to hang, which can be more than a minute! Animations from commercials etc. continue to work though.
    As I have not yet selected the actual bookmark, It is not a problem of downloading the webpage itself. It happens maybe every 1-2 hours or so. Also, I did not experience such a long hanging time ever with a previous version of firefox.
    I would appreciate any help in this matters.
    Alex

    Locked or Damaged places.sqlite
    * http://kb.mozillazine.org/Bookmarks_history_and_toolbar_buttons_not_working_-_Firefox
    Check and tell if its working.

  • 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

  • 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

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

  • 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

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

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

  • 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

  • Satellite L650-10h - New Win7 installation cannot see HDD

    Hi!
    i have Satellite L650-10H and i want to format him to install WINDOWS 7 ULTIMATE.
    So i tried to format and make new partition to my hard drive and i'm used acronis disk director 11 and he can't see the hard drive!
    Even partition magic 8 or paragon server 10 and no one of this software can see the hard drive!!
    In the same way i tried to make an image to my hard drive and acronis true image 2010 can't see it.
    Only GHOST15 see the hard drive and make an image but he can change partitions.
    In the bios i didn't see somthing that maby can make this problem and in the drivers i didn't find any bios update about this situation.
    important to know that i used acronis disk director from a boot able disk and so paragon and others but even if some software have problem with some hard drive the other read him but here no budy can see him!
    so i'm askink what is he problem?? something in this laptop is diffrent from others i'm know.what is the sulotion for this problem?
    pls ur fast help
    thank's
    ofek

    hi friends!
    thank's for ur help.
    first of all i know about sata mode and compatible and i check it in the begining the same result can't see the hdd.
    second i know that i can use the windows tool but sometime u want to make things that he don't make so well i want the pro way
    third,it's principle! why it's not working??? and if i want to make an image to the partition????? it's not work too! paragon and acronis i'm using the last version of them so that why i can't understand it.acronis disk director 11 it's somthing like few month only.
    and remember that not all the 3rd party can import sata drivers...
    i have another sulotion for now...to take out the hdd to another computer and there he work just fine and the 3rd party see him no problem but it's not so fun... :)
    wait to ur answer
    ofek

Maybe you are looking for

  • How do I activate a used iPhone 3 with no SIM card for use as an ipod touch?

    How do I activate a used iPhone 3G with no SIM card for use like an iPod Touch? It was apparently on AT&T previously and I have another iPhone 3 that is active on AT&T if that is helpful. Thanks!

  • Workflow Mailer Service not starting

    Hi Friends, My Environment OS : OEL4U5 Application Vers : R12.1.3 Db Version : 11.1.0.7 Hostname : erptest01 Here we configuring the Workflow Notification Mailer Service in our R12 instance. When we trying to start services in the workflow service co

  • My Mac Pro ONLY Boots up in safe mode

    My Mac Pro hangs in boot mode forever (screen after the Gray Logo Screen).  I'm unable to use the recovery partion, or boot from USB installation.  I did all the usual troubleshooting e.g. reset SMC, NVRAM, etc.  I tested the boot drive externally on

  • Connection server not started

    Hello, I've problem with ConnectionServer. It not started. I've only messages: ConnectionServer stopped with exit code = 128 (0x80). ConnectionServer is considered failed because it has stopped 5 time(s) within 60 minute(s). Please restart this serve

  • Parts of Mail

    Hi All ! How can i change this line in Mail message from ------=_Part_0_14659537.1051269870247 to --Custom-messageHandler-BoUnDaRy-=_-56161233 Thanks in Advance -Mathul