|
Note the usage of CRTDUPOBJ I just did, particularly DATA(*YES) parameter. Here is the joblog from my successful attempt (sorry for any wrapping): 5722SS1 V5R1M0 010525 Display Job Log MAGIC 08/14/03 17:16:25 Page 1 Job name . . . . . . . . . . : QPADEV000D User . . . . . . : ELVIS Number . . . . . . . . . . . : 064014 Job description . . . . . . : QDFTJOBD Library . . . . . : QGPL MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST CPF1124 Information 00 08/14/03 17:15:47 QWTPIIPP QSYS 067E *EXT *N Message . . . . : Job 064014/ELVIS/QPADEV000D started on 08/14/03 at 17:15:48 in subsystem QBASE in QSYS. Job entered system on 08/14/03 at 17:15:48. *NONE Request 08/14/03 17:15:59 QPTCHECK *N QCMD QSYS 0173 Message . . . . : -CRTDUPOBJ OBJ(QAQQINI) FROMLIB(QSYS) OBJTYPE(*FILE) TOLIB(QGPL) DATA(*YES) CPI321A Information 00 08/14/03 17:16:04 QDBTRIG2 QSYS *STMT QDBDUPFI QSYS 01D0 From module . . . . . . . . : QDBTRIG2 From procedure . . . . . . : QDBGEN_SEND_PGM_MSG Statement . . . . . . . . . : 1351 Message . . . . : Trigger Q__OSYS_QAQQINI_BEFORE_INSERT_______ in library QGPL was added to file QAQQINI in library QGPL. CPI321A Information 00 08/14/03 17:16:04 QDBTRIG2 QSYS *STMT QDBDUPFI QSYS 01D0 From module . . . . . . . . : QDBTRIG2 From procedure . . . . . . : QDBGEN_SEND_PGM_MSG Statement . . . . . . . . . : 1351 Message . . . . : Trigger Q__OSYS_QAQQINI_AFTER_INSERT________ in library QGPL was added to file QAQQINI in library QGPL. CPI321A Information 00 08/14/03 17:16:04 QDBTRIG2 QSYS *STMT QDBDUPFI QSYS 01D0 From module . . . . . . . . : QDBTRIG2 From procedure . . . . . . : QDBGEN_SEND_PGM_MSG Statement . . . . . . . . . : 1351 Message . . . . : Trigger Q__OSYS_QAQQINI_BEFORE_UPDATE_______ in library QGPL was added to file QAQQINI in library QGPL. CPI321A Information 00 08/14/03 17:16:04 QDBTRIG2 QSYS *STMT QDBDUPFI QSYS 01D0 From module . . . . . . . . : QDBTRIG2 From procedure . . . . . . : QDBGEN_SEND_PGM_MSG Statement . . . . . . . . . : 1351 Message . . . . : Trigger Q__OSYS_QAQQINI_AFTER_UPDATE________ in library QGPL was added to file QAQQINI in library QGPL. CPI321A Information 00 08/14/03 17:16:04 QDBTRIG2 QSYS *STMT QDBDUPFI QSYS 01D0 From module . . . . . . . . : QDBTRIG2 From procedure . . . . . . : QDBGEN_SEND_PGM_MSG Statement . . . . . . . . . : 1351 Message . . . . : Trigger Q__OSYS_QAQQINI_BEFORE_DELETE_______ in library QGPL was added to file QAQQINI in library QGPL. CPI321A Information 00 08/14/03 17:16:04 QDBTRIG2 QSYS *STMT QDBDUPFI QSYS 01D0 From module . . . . . . . . : QDBTRIG2 From procedure . . . . . . : QDBGEN_SEND_PGM_MSG Statement . . . . . . . . . : 1351 Message . . . . : Trigger Q__OSYS_QAQQINI_AFTER_DELETE________ in library QGPL was added to file QAQQINI in library QGPL. CPI2101 Information 00 08/14/03 17:16:06 QLICRDUP QSYS 05A5 QCMD QSYS 01A1 Message . . . . : Object QAQQINI in QGPL type *FILE created. CPC2130 Completion 00 08/14/03 17:16:06 QLICRDUP QSYS 01B2 QCMD QSYS 01A1 Message . . . . : 1 objects duplicated. Cause . . . . . : All the objects with supported object types specified on the Create Duplicate Object (CRTDUPOBJ) command were duplicated. See low level messages to determine if any objects were not duplicated. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gerald Kern Sent: Thursday, August 14, 2003 4:19 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: Triggers on QAQQINI I've tried to do the CRTDUPOBJ signed on as QSECOFR, so it's not an authority problem. The file does get duplicated into Qusrsys but the member is empty. When I explore the job messages they point to the fact that there are triggers on the file and that is why I cannot make a duplicate object. I even saw in the IBM manual where they refer to the triggers. I'll try again and post the resulting messages and perhaps that will shed some more light on the subject. Regards, Jerry
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.