Rule Import CC 5.2 - Home Grown
My current client has defined an SOD Rule Set apart from the delivered rule set. Is there a way to import this file into CC 5.2? I'm aware that the delivered rule set must be generated after it is imported which may mean that a "home-grown" rule set may not be suitable for import. Any insight is appreciated.
The client has defined several pages of conflicting tcodes as well as pages of authorization object violations. This was all completed before they were introduced to SAP's GRC Suite. Now that they have the GRC suite they are looking to upload all of their defined information into CC. They have already gone through the exercise of identifying which rules are pertinent to the way they do business and would really enjoy not having to go through all of the delivered rules to get back to their current place. I am hoping that there is a way that we can format what they have into CC-Speak so that we do not have review all of the rules (or even go through the rules area by area).
To your point about having a separate rule set aside from the delivered rule set, I'm going to keep the delivered rule set separate from the uploaded rule set (if I can get it uploaded correctly)
There must be someone out there that has had this requirement before and was able to format the input files (because there will be more than one) to make this work.
Any help....??
Similar Messages
-
How do I import a playlist on home sharing? I get the songs, but not packaged in the playlist from which they were imported. Now I have duplicate songs in my music library.
You can't import media from one Home Sharing library to another by any other means except selecting the individual items you want to import. For example, you can't select a playlist and then click on the 'Import' button to import all the items in that playlist. You have to select all the items in the playlist before you can click on the 'Import' button. By extension, the playlist on the other Home Sharing computer will not be re-created on your computer. You can select more than one item using the 'Shift' or 'Command' keys.
What you can do is create a playlist on your computer first, with the same name if you want, and then use drag and drop to copy the media from the remote playlist to your playlist. Note that the playlist on your computer cannot be a 'Smart' playlist it must be a regular playlist for drag and drop copying to work.
Regarding 'Smart' playlists. If you create a 'Smart' playlist on your computer that uses the exact same filtres as the ones on the remote library when you import the media from the remote library they will show up in the same 'Smart' playlist on your computer. -
How to import a playlist in Home Sharing From Computer to ...
How to import a playlist in Home Sharing From Computer to computer and other devices?
No need to "import". Just find the photo in iPhoto (i.e. within the application), click it once so it's highlighted with a blue outline, then select Edit menu > Copy (or just ⌘-C). Go to Address Book, select the contact, click the Edit button at the bottom, click once on the blank photo icon so it's highlighted with a blue outline, then select Edit menu > Paste (or just ⌘-V).
FYI, the original iPhoto images are stored as individual files, in ~/Pictures/iPhoto Library/Originals/subfolders.
Hope this helps... -
Hi, I met some problems in business rules import.
1. The buisness rules import cannot be overwritten, everytime when I deployed a rule to a new environment, I need to delete the old one first. Can I do some setting to enable overwriting?
2. When the rule contains a character ">", the export xml will add a special character like "space" after it. Sometimes caused the rules failed after the deployment. Seems it is a bug.
3. When the rule has the property "hide" for some run-time prompts, sometimes it will lose after the import, is it also a bug or any workaround?
If any good suggestion or experience for the above problems? ThanksHi,
It would be helpful to others if you say which version/patch you are using.
To answer number 1, that has always been a feature of business, you don't get the option to overwrite, its always been a pain.
I have not come across issue 2 and I am sure I have imported many rules with the cross dimensional operator in them ->
Cheers
John
http://john-goodwin.blogspot.com/ -
Home-grown ABAP report sometimes hangs & sometimes finishes successfully
Dear All,
I am re-posting the below thread, which was previously posted on the : SAP on DB2 UDB for i5/OS (DB4) forum, maybe I will get a reply :
We are implementing SAP ECC 6.0 (ABAP stack) on IBM System i (iSeries), i5/OS V5R4, Kernel patch level 173
We have a home-grown ABAP report that sometimes finishes successfully and sometimes just hangs; i.e. through the OS/400 job monitoring, no change happens in the database records I/O counts.
Below is the OS/400 job log, related to a case where the report did not complete successfully (actually the below is an excerpt from the beginning and the end of the OS/400 job log)
I would highly appreciate any advise about the cause of this problem :
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 1
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPC2196 Completion 00 05/11/08 11:44:32.099024 QLICUSRL QSYS 0113 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library QGY added to library list.
Cause . . . . . : If the ADDLIBLE command was used, QGY was added to the
user library list. If the CHGSYSLIBL command was used, QGY was added to the
system portion of the library list.
CPC2198 Completion 00 05/11/08 11:44:32.099232 QLICHLLE QSYS 01A3 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Current library changed to R3PRODATA.
Cause . . . . . : The current library in the library list was changed to
R3PRODATA.
*NONE Information 05/11/08 11:44:32.214488 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: File Version: 7000, 173, 0, 0
*NONE Information 05/11/08 11:44:32.214640 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Product Version: 700, patch 173,
changelist 0
*NONE Information 05/11/08 11:44:32.214808 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Platform: os400 for releases OS400 3 5,
OS400 4 5, OS400 1 6
*NONE Information 05/11/08 11:44:32.214904 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Special Build Description: OPT (Aug 11
2008, 08:14:03) (ASCII in PASE ASCII build)
*NONE Information 05/11/08 11:44:32.230728 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 2
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Connect from Client Protocol: 610
*NONE Information 05/11/08 11:44:32.230840 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Remote Link: /usr/sap/PRO/SYS/exe/run/DBSLDB4RMT
*NONE Information 05/11/08 11:44:32.268688 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Kernel Library: SAPPROUCN
CPF9897 Completion 40 05/11/08 11:44:32.286120 QDBENCWT QSYS 0066 DBSLENCWT SAPPROUCN *STMT
To module . . . . . . . . . : DBSLENCWT
To procedure . . . . . . . : main
Statement . . . . . . . . . : 14
Message . . . . : CONCURRENT WRITE IS ENABLED.
Cause . . . . . : No additional online help information is available.
CPF9897 Completion 40 05/11/08 11:44:32.286136 QDBENCWT QSYS 0066 DBSLENCWT SAPPROUCN *STMT
To module . . . . . . . . . : DBSLENCWT
To procedure . . . . . . . : main
Statement . . . . . . . . . : 14
Message . . . . : CONCURRENT WRITE WILL BE ENABLED NEXT IPL.
Cause . . . . . : No additional online help information is available.
CPC2197 Completion 00 05/11/08 11:44:32.323144 QLICHLBL QSYS 013C QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library SAPPROUCN removed from library list.
Cause . . . . . : If the RMVLIBLE command was used, SAPPROUCN was removed
from the user library list. If the CHGSYSLIBL command was used, SAPPROUCN
was removed from the system portion of the library list.
CPC2196 Completion 00 05/11/08 11:44:32.323368 QLICUSRL QSYS 0113 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library SAPPROUCN added to library list.
Cause . . . . . : If the ADDLIBLE command was used, SAPPROUCN was added to
the user library list. If the CHGSYSLIBL command was used, SAPPROUCN was
added to the system portion of the library list.
SAP4000 Information 00 05/11/08 11:44:32.336544 DBSLDB4RMT SAPPROUCN *STMT DBSLDB4RMT SAPPROUCN *STMT
From module . . . . . . . . : O4SAPUCI_E
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 3
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : O4_QMHSNDPM__FPCcN21iN21T4PUcR11O4_ERRC0100
Statement . . . . . . . . . : 4
To module . . . . . . . . . : DBSLDB4RMT
To procedure . . . . . . . : CXXPEP__Fv
Statement . . . . . . . . . : *N
Message . . . . : Connect from workprocess w2 on MASAPPRO_PRO_00
CPC2196 Completion 00 05/11/08 11:44:32.975448 QLICHLBL QSYS 013C CHGR3SYSLE SAPPROUCN *STMT
To module . . . . . . . . . : CHGR3SYSLE
To procedure . . . . . . . : CHGR3SYSLE
Statement . . . . . . . . . : 13600
Message . . . . : Library R3SYS added to library list.
Cause . . . . . : If the ADDLIBLE command was used, R3SYS was added to the
user library list. If the CHGSYSLIBL command was used, R3SYS was added to
the system portion of the library list.
SQL7917 Information 00 05/11/08 11:47:23.199272 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16590
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPF9898 Information 40 05/11/08 11:54:11.399680 QXDAUTIL QSYS *STMT QXDAEDRS QSYS *STMT
From module . . . . . . . . : QXDATRACE
From procedure . . . . . . : QxdaWriteJoblog__FPciT1R16QxdaTraceControl
Statement . . . . . . . . . : 13
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaConnectEDRSInternal__FPvPcT1PiT2T1R16clean
upMutexes_tP19XDAGlobalDataStruct
Statement . . . . . . . . . : 3266
Message . . . . : Connection #2, Server Job: 303463/QUSER/QXDARECVR.
Cause . . . . . : This message is used by application programs as a general
escape message.
CPF5009 Diagnostic 10 05/11/08 11:54:32.741480 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 22987
Message . . . . : Duplicate record key in member RSEUINC.
Cause . . . . . : The output or update operation to member number 1 record
number 4942 format RSEUINC, for member RSEUINC file RSEUINC in library
R3PRODATA, failed. Member number 1 record number 4941 format RSEUINC has the
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 4
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
same record key as member number 1 record number 4942 format RSEUINC. If
the record number is zero, the duplicate record key occurred on an output
operation. Recovery . . . : Change either record key so that the keys are
unique. Then try your request again.
CPF5034 Sender copy 30 05/11/08 11:54:32.741536 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 4942 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member RSEUINC file RSEUINC in library
R3PRODATA, or in a based-on member of RSEUINC. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file RSEUINC in library R3PRODATA. Recovery
. . . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
CPF5034 Notify 30 05/11/08 11:54:32.741552 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 22987
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 4942 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member RSEUINC file RSEUINC in library
R3PRODATA, or in a based-on member of RSEUINC. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file RSEUINC in library R3PRODATA. Recovery
. . . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
SQL0803 Diagnostic 30 05/11/08 11:54:32.748064 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint RSEUINC in R3PRODATA exists over one or
more columns of table RSEUINC in R3PRODATA. The operation cannot be
performed because one or more values would have produced a duplicate key in
the unique index or constraint. Recovery . . . : Change the statement so
that duplicate keys are not produced. For information on what rows contain
the duplicate key values, look at the previously listed messages in the job
log (DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 5
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
SQL7917 Information 00 05/11/08 12:33:54.649416 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:33:54.709808 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:33:54.745288 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 6
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:34:28.245160 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16643
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.875752 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.935840 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 7
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.965560 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPF9898 Information 40 05/11/08 12:50:51.470216 QXDAUTIL QSYS *STMT QXDAEDRS QSYS *STMT
From module . . . . . . . . : QXDATRACE
From procedure . . . . . . : QxdaWriteJoblog__FPciT1R16QxdaTraceControl
Statement . . . . . . . . . : 13
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaConnectEDRSInternal__FPvPcT1PiT2T1R16clean
upMutexes_tP19XDAGlobalDataStruct
Statement . . . . . . . . . : 3266
Message . . . . : Connection #2, Server Job: 303480/QUSER/QXDARECVR.
Cause . . . . . : This message is used by application programs as a general
escape message.
SQL7917 Information 00 05/11/08 12:59:55.956784 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16590
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 8
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPC2206 Completion 00 05/11/08 13:06:49.865608 QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . . : Ownership of object SAPFGUTRBL in R3PRO02070 type *SQLPKG
changed.
Cause . . . . . : The ownership of object SAPFGUTRBL in library R3PRO02070
type *SQLPKG has changed.
CPC2206 Completion 00 05/11/08 13:06:50.312272 QSYCHONR QSYS 0665 QSQXPGM QSYS 0469
Message . . . . : Ownership of object SAPFGUTRBL in R3PRO02070 type *SQLPKG
changed.
Cause . . . . . : The ownership of object SAPFGUTRBL in library R3PRO02070
type *SQLPKG has changed.
SQL0204 Diagnostic 30 05/11/08 13:06:51.011064 QSQPRCED QSYS *STMT QSQPRCED QSYS *STMT
From module . . . . . . . . : QSQPRCED
From procedure . . . . . . : SENDDIAG
Statement . . . . . . . . . : 19346
To module . . . . . . . . . : QSQPRCED
To procedure . . . . . . . : QSQPRCED
Statement . . . . . . . . . : 18435
Message . . . . : T801WEI in R3PRO32060 type *SQLPKG not found.
Cause . . . . . : T801WEI in R3PRO32060 type *SQLPKG was not found. If the
member name is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement and the type is *N, a constraint or partition was not found. If
this is not an ALTER TABLE statement and the type is *N, a function,
procedure, trigger or sequence object was not found. If a function was not
found, T801WEI is the service program that contains the function. The
function will not be found unless the external name and usage name match
exactly. Examine the job log for a message that gives more details on which
function name is being searched for and the name that did not match.
Recovery . . . : Change the name and try the request again. If the
object is a node group, ensure that the DB2 Multisystem product is installed
on your system and create a nodegroup with the CRTNODGRP CL command. If an
external function was not found, be sure that the case of the EXTERNAL NAME
on the CREATE FUNCTION statement exactly matches the case of the name
exported by the service program.
CPC2206 Completion 00 05/11/08 13:06:51.378408 QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . . : Ownership of object T801WEI in R3PRO32060 type *SQLPKG
changed.
Cause . . . . . : The ownership of object T801WEI in library R3PRO32060 type
*SQLPKG has changed.
CPC2206 Completion 00 05/11/08 13:06:51.439824 QSYCHONR QSYS 0665 QSQXPGM QSYS 0469
Message . . . . : Ownership of object T801WEI in R3PRO32060 type *SQLPKG
changed.
Cause . . . . . : The ownership of object T801WEI in library R3PRO32060 type
*SQLPKG has changed.
CPF5009 Diagnostic 10 05/11/08 13:06:51.708688 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 9
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member T801W.
Cause . . . . . : The output or update operation to member number 1 record
number 0 format T801W, for member T801W file T801W in library R3PRODATA,
failed. Member number 1 record number 751 format T801W has the same record
key as member number 1 record number 0 format T801W. If the record number
is zero, the duplicate record key occurred on an output operation. Recovery
. . . : Change either record key so that the keys are unique. Then try
your request again.
CPF5034 Sender copy 30 05/11/08 13:06:51.708736 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 0 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member T801W file T801W in library
R3PRODATA, or in a based-on member of T801W. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file T801W in library R3PRODATA. Recovery .
. . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
CPF5034 Notify 30 05/11/08 13:06:51.708776 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 0 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member T801W file T801W in library
R3PRODATA, or in a based-on member of T801W. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file T801W in library R3PRODATA. Recovery .
. . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:51.710352 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint T801W in R3PRODATA exists over one or more
columns of table T801W in R3PRODATA. The operation cannot be performed
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 10
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
SQL0518 Diagnostic 30 05/11/08 13:06:51.732720 QSQROUTS QSYS *STMT QSQROUTS QSYS *STMT
From module . . . . . . . . : QSQCLNUP
From procedure . . . . . . : SQROUTE_CLEANUP
Statement . . . . . . . . . : 3814
To module . . . . . . . . . : QSQCLNUP
To procedure . . . . . . . : SQROUTE_CLEANUP
Statement . . . . . . . . . : 3814
Message . . . . : Prepared statement RD0IAAAABA not found.
Cause . . . . . : An EXECUTE statement referred to the statement RD0IAAAABA.
RD0IAAAABA is not a valid prepared statement. The statement has one of the
following conditions: -- The statement has never been prepared. -- The
statement identifies a prepared SELECT or DECLARE PROCEDURE statement. --
The statement was in error at prepare or bind time. -- The statement was
prepared in another program or another call of this program and the program
was created with CLOSQLCSR(*ENDPGM). -- The statement was prepared in
another module or another call of this module and the module was created
with CLOSQLCSR(*ENDMOD). -- The statement was prepared in another call of
this program and programs which have run SQL statements have ended and the
program was created with CLOSQLCSR(*ENDSQL). -- The statement was prepared
in another call of this module and the activation group ended between calls.
The module was created with CLOSQLCSR(*ENDACTGRP). -- The prepared statement
was destroyed by a COMMIT or ROLLBACK statement. This only occurs when
connected to a database other than DB2 UDB for iSeries. Recovery . . . :
Do one of the following: -- If RD0IAAAABA identifies a prepared SELECT or
DECLARE PROCEDURE statement, a different prepared statement must be named in
the EXECUTE statement. -- If the statement had errors, correct the errors
and either prepare the statement again or precompile the program again. --
Make certain that RD0IAAAABA has been prepared in the same program or module
call prior to using the EXECUTE statement or specify either
CLOSQLCSR(ENDSQL), CLOSQLCSR(ENDJOB), or CLOSQLCSR(*ENDACTGRP) when
precompiling the application. -- If the statement was deleted by a COMMIT or
ROLLBACK, either specify PREPARE WITH HOLD or bind the program with the
correct option to preserve prepared statements.
CPF5009 Diagnostic 10 05/11/08 13:06:56.094184 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635738 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 51
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.094240 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.094256 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.094376 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.096008 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 52
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635779 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.096048 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.096080 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.096208 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 53
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.098520 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635819 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.098552 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.098568 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.098720 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 54
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.101560 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635865 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.101592 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.101608 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.101760 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 55
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.105864 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635906 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.105904 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.105920 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 56
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.106056 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.107696 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635948 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.107736 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.107752 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 57
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.107880 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
SQL0204 Diagnostic 30 05/11/08 13:06:56.159320 QSQPRCED QSYS *STMT QSQPRCED QSYS *STMT
From module . . . . . . . . : QSQPRCED
From procedure . . . . . . : SENDDIAG
Statement . . . . . . . . . : 19346
To module . . . . . . . . . : QSQPRCED
To procedure . . . . . . . : QSQPRCED
Statement . . . . . . . . . : 18435
Message . . . . : T801LEI in R3PRO32060 type *SQLPKG not found.
Cause . . . . . : T801LEI in R3PRO32060 type *SQLPKG was not found. If the
member name is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement and tI don't have FIOS but I do use Safari to access the discussion forums without encountering the issue you've described (knock on wood). It's always hard to diagnose and troubleshoot connection issues without actually sitting in front of the computer (even more so when the problem is intermittent). Let me ask some questions:
Is your computer connecting wirelessly?
Have you tried resetting Safari and/or emptying the cache?
Have you tried Private Browsing to note any differences?
How about going to Safari's->Preferences->Security and checking/unchecking Web Contents and/or enabling/disabling cookies?
Have you tried creating another user account on your machine and log in with that user account to access the discussion board to see if there's a difference?
Good luck,
TK -
Why does my iMac lose internet connection when importing music via iTunes Home sharing?
Hi, I tried searching for a solution but could not find anything to solve my problem.
I recently purchased an iMac and am attempting to import my iTunes library from my old Windows 7 laptop using the Home sharing function. As far as I can tell, everything works fine - both computers are connected to my wireless network, I can see and connect to the library, I can begin importing my music but after 5 or so minutes my iMac will stop transferring music and I can no longer access any internet sites, even though i seem to be connected to the internet. Turning wifi on and off allows me to access the internet again. I have tried many solutions, but nope seem to have helped. Both computers have the latest version of iTunes. I have tried disabling the firewall on my router, resetting the router, resetting both computers, reopening iTunes.
Does anybody have any ideas as to what could solve the problem? Thank youjjcardil
I've noticed that Lion automatically reconnects in about 5-10 seconds after being waken from sleep mode.
Make sure that you've set you Network connections up properly in System Preferences and then, after waking from sleep mode, wait to see if it automatically reconnects.
In System Preferences:
Network / Wi-Fi:
Make sure "Network Name" is specified.
Advanced:
Make sure your "Preferred Networks" are specified. (The order is significant).
Also make sure that the "Remember networks this computer has joined" is checked.
Also, you may want to try playing with the "Energy Saver" Settings in System Preferences, perhaps disabling sleep mode but turning off the screen (although I don't prefer this method since it kind of defeats the whole purpose of having a sleep mode IMHO).
-Mike -
Why can't I import songs from iTunes Home Sharing?
I have two Macs - mine and my dad's. Both computers have Home Sharing on and we are using the same iTunes Account.
We are able to see and play each other's music, but cannot import any songs.
Where other people seem to see a Home Share icon (the house), we only have blue playlist symbols.
Any ideas?Restart both of your computers, and restart your Internet modem. Then try again. It may just be a glitch.
-
How long does it take to import a library using home sharing?
I have about 82GB of music on an older iMac and want to import it permanently into the iTunes on a newer iMac but have never done this before.
Before I start, I'd like to know if I'm going to be tying up my computers for a week!
Should I go for the whole 4,000-plus songs at once, or should I try to plod through playlist by playlist and tell it each time not to import songs that may already be in the new computer. (If I do that, will the song show up in the playlists anyway?)
How have other users approached this with large libraries and what has their experience been like? I'm so glad there's a community here to share their experiences and help other Apple owners!
Thanks so much for any and all responses!To transfer your songs, don't use Home Sharing. It uses your network to transfer the songs, and it will be so slow (days or weeks to transfer 82 GB).
Instead, you can copy the whole iTunes library to an external disk and transfer it to your new iMac > http://support.apple.com/kb/HT1751 This is much faster and useful, because you will transfer all your iTunes data from your old Mac, not only songs -
Importing 3rd source dvd home footage into FCE
Dear Forum,
I'm not sure if I'm wording this correctly, but I am putting some footage together for a high school sports team. I have captured video from my canon camera. I also have dvds from another parent from the team. Can anyone suggest an easy way to import the home dvd, burned on a pc, into FCE so I can create a team video?
Jamiehttp://www.fcpbook.com/Video6.html
-
Why is the import button missing on Home Sharing?
I just got a MacBook Pro and when I open Home Sharing the import button is missing on my Mac but I am able to see it on my PC. I checked and I authorized both computers and have the same accounts on both also. I have turned Home Sharing "on" and "off" on both computers and there still isn't a solution. On my PC, by the Home Sharing tab is a house with a music note but on my Mac it doesn't look like that. I also checked and when I go to Preferences>Sharing, it says my Home Sharing is on but I don't have any devices connected to it. I don't want to re-download over 1,000 songs. Does anyone have any suggestions?
You can find the Import menu entry in the Bookmarks Manager (Library)
*Bookmarks > Show All Bookmarks > Import & Backup > Import Data from Another Browser
*http://kb.mozillazine.org/Import_bookmarks -
IMovie temporary files; importing fails on network home directory
Hi all,
I work in a laboratory and manage a bunch of Macs. We have a 2x2.5GHZ G5 with 4G of memory and iMovie 6. The mac has two 300 GB disks that are in a concatenated raid group, so the system has about 450GB of free disk.
The mac is bound to an Open Directory server and users have network home directories. (The network file system happens to be AFS, which is probably unusual)
The problem I am having is that whenever I am importing a clip from any external source (in this case I have tried a Sony GL-2 and an external DV deck), after about 13 minutes of importing, imovie stops importing, and iMovie displays the blue screen that you get when a video source is connected but not playing... but, the camera is clearly still playing, if I look in the viewfinder. this failure mode is completely reproducible, and always fails at the exact same place. (but works fine on another mac, see below)
I have tried saving the iMovie project onto both local disk and into the networked home directory, with the same results in either case.
I've tried the same setup on an identical mac that is not using networked home directories (local only), which works fine. I suspect that the problem has to do with the way the network file system caches/buffers, but I have no idea where iMovie keeps its housekeeping/temporary files. I was under the impression that it is all kept in the project directory, wherever you happen to create it. Are there some files that get written to the home directory no matter where you save the project?
mjp
2x 2.5 GHz G5 PowerMac 4GB RAM Mac OS X (10.4.6)iMovie doesn't have temporary files. All files are kept in the project folder (or "package").
iMovie: How to Save Projects to Another Hard Disk
http://docs.info.apple.com/article.html?artnum=93296
See "Important Considerations" at the bottom. -
Business Rules: import .RL file into RuleAuthor
We have been doing building our rules (10.1.3) Application in jdev 10.1.3. All of our rules are in .rl files, which we use the CommandLine application to test. Now we need to move all our facts, rulesets, rules, etc into the RuleAuthor application. How do we take our rl file and import it into rule author? Now dev is done, the app admin will be using the RA app to modify rules as needed.
Thanks,
MattRuleAuthor is able to only edit rule dictionaries. There is no way to import RL to the dictionary format.
-
Hi All,
I am working on Hyperion Planning 11.1.1.3 and Essbase the same version.
I took the back of my project related BR back like this.
1) Right Click on the Business Rule and imported
2) Selected my project related BR
3) Select the dependants and click on Export.
4) Saved in C drive.
I successfully migrated the application to another system. But BR cant imported.
Please, any one help me out on this.
Thank You
EPHi,
Make sure you add the location in the locations tab of the business rule, then give the user access in the next tab along.
Cheers
John
http://john-goodwin.blogspot.com/ -
Update rules import/export
Hi expterts,
I'm trying to export some structures from a BW system in order to import them in to another one.
I'm using the XML import/export tool and it seems to work fine for ODS but I'm finding some problems to export the update rules because when I import them it simply does not create anything.
Is there a way to manage this issue ?
best regards,
mircoYou can try using the Microsoft.Office.Server.Search.Portability namespace in the object model. This can be done per site collection and does include query rules.
http://technet.microsoft.com/en-us/library/jj871675.aspx
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer -
Can I import a playlist over home sharing?
I have my main music collection on my iMac running iTunes 12. It includes some playlists I would like to have in an older Macbook Pro, running iTunes 11.4. I have my Home Sharing turned on, and can import the items in the playlist, but have not figured out how to get the playlist itself.
Is there an easy way to share a playlist within Home Sharing?Hello Burn16
You should be able to, but if it is not working you can export your playlist and copy the file over and import the playlist that way.
iTunes 11 for Mac: Save a copy of your playlists
http://support.apple.com/kb/PH12145
Regards,
-Norm G.
Maybe you are looking for
-
Reverse in Factory Sales (TAXINN)
Dear Friends, I'm facing a situation in the current project where the customer deals in Final Price, inclusive of basic price, excise duty & the sales tax (either vat or cst). We are using TAXINN tax procedure & this scenario is for factory sales. I
-
First I installed 9i client on F:\ It was working and gettin connected to 10g servers. After this I installed 10g client on E:\ and even this was working... then I tried to change the oracle path from environment variables..to set path again for 9i c
-
HT4236 how do i upload my pictures from the device
hello, I just wanted to know how to upload pictures from my iphone to my computer or itunes
-
I have accidentally deleted a Numbers spreadsheet. Is there any way to recover it?
I have accidentally deleted a Numbers spreadsheet. Is there any way to recover it?
-
I downloaded and installed the latest firefox update and it told me I had to update adobe flash
I clicked on the link, then the install bar across the top to install and then I got this little tiny window that say Completing and then nothing its been like this for over two hours. Here is a picture if this will allow me to post link: [url=http:/