Toolkit errors after update

[timo_karvinen]

As far as I can remember, nothing significant has changed on this machine, except I updated Toolkit and CW to newest versions.
Don't hold me to that though, I may have changed something and I just don't remember, but nothing comes to mind right now.
I'm on iASP/PowerHA environment on this machine.

So a script that used to work now does this:

Code: Select all

Creating new conn with database: 'KOLME', user or i5 naming flag: 'WSM2012', ext prefix: '', persistence: '1'
Going to create a new db connection.
Exec start: 2012-09-21 12:40:47
IPC: ''. Control key: *cdata *here
Stmt: call ZENDSVR.iPLUG512K(?,?,?,?)
Input XML: <?xml version="1.0" encoding="ISO-8859-1" ?><script>
<pgm name='RMWSLOG' lib='*LIBL'>
<parm io='in' comment='PI_Service'><data var='PI_Service' type='100a'>provider "uddi"</data></parm>
<parm io='in' comment='PI_IP'><data var='PI_IP' type='15a'>172.17.66.58</data></parm>
<parm io='in' comment='PI_Caller'><data var='PI_Caller' type='10a' /></parm>
<parm io='in' comment='PI_ProReq'><data var='PI_ProReq' type='1a'>P</data></parm>
<parm io='in' comment='PI_Type'><data var='PI_Type' type='1a'>U</data></parm>
<parm io='in' comment='PI_ErrorCode'><data var='PI_ErrorCode' type='1a'>0</data></parm>
<parm io='in' comment='PI_Note'><data var='PI_Note' type='128a' /></parm>
</pgm>
</script>
Output XML: <?xml version="1.0" encoding="ISO-8859-1" ?>
<report>
<version>XML Toolkit 1.7.2</version>
<error>
<errnoxml>1100004</errnoxml>
<xmlerrmsg><![CDATA[XML run loop failed]]></xmlerrmsg>
<xmlhint><![CDATA[p(54) <pgm name='RMWSLOG' lib='*LIBL']]></xmlhint>
</error>
<error>
<errnoxml>1000005</errnoxml>
<xmlerrmsg><![CDATA[PASE resolve failed]]></xmlerrmsg>
<xmlhint><![CDATA[RMWSLOG]]></xmlhint>
</error>
<error>
<errnoxml>1100016</errnoxml>
<xmlerrmsg><![CDATA[XML run pgm failed]]></xmlerrmsg>
<xmlhint><![CDATA[<pgm name='RMWSLOG' lib='*LIBL'>
<parm io='in' comment='PI]]></xmlhint>
</error>
<error>
<errnoxml>1100004</errnoxml>
<xmlerrmsg><![CDATA[XML run loop failed]]></xmlerrmsg>
<xmlhint><![CDATA[p(54) <pgm name='RMWSLOG' lib='*LIBL']]></xmlhint>
</error>
<jobinfo>
<jobipc>€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€</jobipc>
<jobipcskey>FFFFFFFF</jobipcskey>
<jobname>QRWTSRVR</jobname>
<jobuser>QUSER</jobuser>
<jobnbr>371446</jobnbr>
<jobsts>*ACTIVE</jobsts>
<curuser>QTMHHTTP</curuser>
<ccsid>65535</ccsid>
<dftccsid>278</dftccsid>
<paseccsid>819</paseccsid>
<langid>FIN</langid>
<cntryid>FI</cntryid>
<sbsname>QUSRWRK</sbsname>
<sbslib>QSYS</sbslib>
<curlib></curlib>
<syslibl>QSYS QSYS2 QHLPSYS QUSRSYS</syslibl>
<usrlibl>QGPL QTEMP</usrlibl>
<jobcpffind>see log scan, not error list</jobcpffind>
</jobinfo>
<joblogscan>
<joblogrec>
<jobcpf>CPF1124</jobcpf>
<jobtime><![CDATA[21.09.12  12:40:47,805747]]></jobtime>
<jobtext><![CDATA[Job 371446/QUSER/QRWTSRVR started on 21.09.12 at 12:27:26 QCNTEDDM SNDMSG 8047 QRWTSRVR main 352 Target job assigned to handle D]]></jobtext>
</joblogrec>
<joblogrec>
<jobcpf>CPF1301</jobcpf>
<jobtime><![CDATA[21.09.12  12:40:47,805747]]></jobtime>
<jobtext><![CDATA[QTMHHTTP QRWTSECR SWPNCHG 6091 ACGDTA for 371446/QUSER/QRWTSRVR not journaled; reason 1.]]></jobtext>
</joblogrec>
<joblogrec>
<jobcpf>MCH3401</jobcpf>
<jobtime><![CDATA[21.09.12  12:40:47,805747]]></jobtime>
<jobtext><![CDATA[QTMHHTTP PLUGILE ILERSLV 7801         *PRCLT Cannot resolve to object RMWSLOG. Type and Subtype X'0201' Either a system pointer]]></jobtext>
</joblogrec>
</joblogscan>
<joblog job='QRWTSRVR' user='QUSER' nbr='371446'>
<![CDATA[5770SS1 V7R1M0 100423                        Display Job Log                        I1       21.09.12 12:40:48          Page    1
  Job name . . . . . . . . . . :   QRWTSRVR        User  . . . . . . :   QUSER        Number . . . . . . . . . . . :   371446
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :   QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
CPF1124    Information             00   21.09.12  12:27:27,028424  QWTPIIPP     QSYS        04C0     *EXT                    *N
                                     Message . . . . :   Job 371446/QUSER/QRWTSRVR started on 21.09.12 at 12:27:26
                                       in subsystem QUSRWRK in QSYS. Job entered system on 21.09.12 at 12:27:26.
CPI9162    Information             00   21.09.12  12:40:46,323674  QCNTEDDM     QSYS        *STMT    QRWTSRVR    QSYS        *STMT
                                     From module . . . . . . . . :   QCNTEDDM
                                     From procedure  . . . . . . :   SNDMSG
                                     Statement . . . . . . . . . :   8047
                                     To module . . . . . . . . . :   QRWTSRVR
                                     To procedure  . . . . . . . :   main
                                     Statement . . . . . . . . . :   352
                                     Message . . . . :   Target job assigned to handle DDM connection started by
                                       source system over TCP/IP.
                                     Cause . . . . . :   A distributed data management (DDM) connection has been
                                       started over TCP/IP by source system job 372241/QTMHHTTP/ZENDSVR on source
                                       system I1. See source job 372241/QTMHHTTP/ZENDSVR for all additional
                                       messages regarding the DDM connection. DDM uses remote IP address
                                       172.16.64.30 and remote port 16823 for this TCP/IP connection.
CPF1301    Information             30   21.09.12  12:40:46,546785  QWTCHGJB     QSYS        1201     QRWTSECR    QSYS        *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     To module . . . . . . . . . :   QRWTSECR
                                     To procedure  . . . . . . . :   SWPNCHG
                                     Statement . . . . . . . . . :   6091
                                     Message . . . . :   ACGDTA for 371446/QUSER/QRWTSRVR not journaled; reason 1.
                                     Cause . . . . . :   Job resource accounting data for job 371446/QUSER/QRWTSRVR
                                       was not journaled to the system accounting journal QSYS/QACGJRN. -- Reason
                                       codes and their meanings follow: -- 1-The accounting level system value
                                       (QACGLVL) indicated that this level of resource accounting was not to be
                                       done when the job entered the system. -- 2-The accounting journal
                                       QSYS/QACGJRN is unable to receive the data.  The accounting data was sent to
                                       the history log (QHST) as the text of a CPF1303 message.  See CPF1302 in the
                                       history log (QHST) for recovery action. -- 3-The accounting journal
                                       QSYS/QACGJRN  was allocated to another job.  The accounting data was sent to
                                       the history log (QHST) as the text of a CPF1303 message.
CPIB8EA    Information             00   21.09.12  12:40:46,559294  QYASPPG1     QSYS        *STMT    QYASPACT    QSYS        *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     From module . . . . . . . . :   QYASPPG1
                                     From procedure  . . . . . . :   sendCPIB8EA
5770SS1 V7R1M0 100423                        Display Job Log                        I1       21.09.12 12:40:48          Page    2
  Job name . . . . . . . . . . :   QRWTSRVR        User  . . . . . . :   QUSER        Number . . . . . . . . . . . :   371446
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :   QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
                                     Statement . . . . . . . . . :   15
                                     To module . . . . . . . . . :   QYASPACT
                                     To procedure  . . . . . . . :   main
                                     Statement . . . . . . . . . :   438
                                     Message . . . . :   ASP group set to KOLME.
                                     Cause . . . . . :   ASP group for thread X'0000000000000001' set to KOLME.
CPI3E01    Information             00   21.09.12  12:40:46,783242  QRWTBAS      QSYS        *STMT    QCNTEDDM    QSYS        *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     From module . . . . . . . . :   QRWTARDB
                                     From procedure  . . . . . . :   SNDMSG
                                     Statement . . . . . . . . . :   6521
                                     To module . . . . . . . . . :   QCNTEDDM
                                     To procedure  . . . . . . . :   PRCRH
                                     Statement . . . . . . . . . :   7437
                                     Message . . . . :   Local relational database accessed by I1.
MCH3401    Escape                  40   21.09.12  12:40:47,805747  Ämnrnrl                  000518   XMLSTOREDP  ZENDSVR     *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     To module . . . . . . . . . :   PLUGILE
                                     To procedure  . . . . . . . :   ILERSLV
                                     Statement . . . . . . . . . :   7801         *PRCLT
                                     Message . . . . :   Cannot resolve to object RMWSLOG. Type and Subtype X'0201'
                                       Authority X'0000'.
                                     Cause . . . . . :   Either a system pointer or a data pointer can not be
                                       resolved. For a system pointer, it can not be resolved to object RMWSLOG,
                                       type and subtype X'0201', authorization X'0000', because either the named
                                       object was not in any context referred to or the correct object was located
                                       but the user profile did not have the required authority. The object types
                                       for some common type or subtype codes follow: -- 0190-Access group,
                                       0201-Program, 0401-Library, -- 0701-Journal receiver, 0801-User profile,
                                       0901-Journal, -- 0B90-Data space, 0C01-Directory, 0C90-Data space index, --
                                       0E01-Job queue, 0E02-Output queue, 0E03-Message file, -- 0E02-User index,
                                       0A01-Data queue, 1401-Class of service description -- 1501-Mode description,
                                       0E05-Session description, -- 1001-Device description, 1101-Line description,
                                       -- 1201-Controller description, 1901-File, 1902-Message queue, -- 1903-Job
                                       description, 1904-Class, 1905-Command, 1906-Table, -- 1908-Edit description,
                                       1909-Subsystem description, -- 190A-Data area, 190C-Graphic symbol set,
                                       190D-Chart format, -- 1911-Query definition, 1912-Folder, -- 1915-Panel
5770SS1 V7R1M0 100423                        Display Job Log                        I1       21.09.12 12:40:48          Page    3
  Job name . . . . . . . . . . :   QRWTSRVR        User  . . . . . . :   QUSER        Number . . . . . . . . . . . :   371446
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :   QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
                                       group, 1916-Menu group description, -- 1920-Data dictionary, 192D-Management
                                       collection, 19D0 Work control block table, -- 19D2-System value,
                                       1B01-Process control space, -- 1E01-Byte stream file, 1E03-Local socket,
                                       1E06-Character special file, -- 1E07-First-in first-out special file For a
                                       data pointer, it can not be resolved because the named object is not located
                                       within any program activation currently known to the process. Recovery  . .
                                       . :   Either specify the correct object name or specify the correct
                                       authority for the object.
]]>
</joblog>
</report>

Exec end: 2012-09-21 12:40:49. Seconds to execute: 2,4305138587952.


Same program call with stateless = false

Code: Select all

Creating new conn with database: 'KOLME', user or i5 naming flag: 'WSM2012', ext prefix: '', persistence: '1'
Going to create a new db connection.
Exec start: 2012-09-21 12:59:52
IPC: '/tmp/ipc_cw_WSM2012_505c3a9816b1c'. Control key: *cdata *sbmjob(ZENDSVR/ZSVR_JOBD/XTOOLKIT)
Stmt: call ZENDSVR.iPLUG512K(?,?,?,?)
Input XML: <?xml version="1.0" encoding="ISO-8859-1" ?><script>
<pgm name='RMWSLOG' lib='*LIBL'>
<parm io='in' comment='PI_Service'><data var='PI_Service' type='100a'>provider "uddi"</data></parm>
<parm io='in' comment='PI_IP'><data var='PI_IP' type='15a'>172.17.66.58</data></parm>
<parm io='in' comment='PI_Caller'><data var='PI_Caller' type='10a' /></parm>
<parm io='in' comment='PI_ProReq'><data var='PI_ProReq' type='1a'>P</data></parm>
<parm io='in' comment='PI_Type'><data var='PI_Type' type='1a'>U</data></parm>
<parm io='in' comment='PI_ErrorCode'><data var='PI_ErrorCode' type='1a'>0</data></parm>
<parm io='in' comment='PI_Note'><data var='PI_Note' type='128a' /></parm>
</pgm>
</script>
Output XML: <?xml version="1.0" encoding="ISO-8859-1" ?>
<report>
<version>XML Toolkit 1.7.2</version>
<error>
<errnoile>3025</errnoile>
<errnoilemsg><![CDATA[No such path or directory.]]></errnoilemsg>
<errnoxml>1400001</errnoxml>
<xmlerrmsg><![CDATA[client call failed]]></xmlerrmsg>
<xmlhint><![CDATA[failure]]></xmlhint>
</error>
<error>
<errnoile>3025</errnoile>
<errnoilemsg><![CDATA[No such path or directory.]]></errnoilemsg>
<errnoxml>1301021</errnoxml>
<xmlerrmsg><![CDATA[IPC ftok fail]]></xmlerrmsg>
<xmlhint><![CDATA[È_øÑø#^#Ï^ïë(‘^••#“/™˜‘–‘#]]></xmlhint>
</error>
<error>
<errnoile>3025</errnoile>
<errnoilemsg><![CDATA[No such path or directory.]]></errnoilemsg>
<errnoxml>1301021</errnoxml>
<xmlerrmsg><![CDATA[IPC ftok fail]]></xmlerrmsg>
<xmlhint><![CDATA[È_øÑø#^#Ï^ïë(‘^••#“/™˜‘–‘#]]></xmlhint>
</error>
<error>
<errnoile>3025</errnoile>
<errnoilemsg><![CDATA[No such path or directory.]]></errnoilemsg>
<errnoxml>1301022</errnoxml>
<xmlerrmsg><![CDATA[IPC ftok loop fail]]></xmlerrmsg>
<xmlhint><![CDATA[È_øÑø#^#Ï^ïë(‘^••#“/™˜‘–‘# : 210]]></xmlhint>
</error>
<error>
<errnoile>3025</errnoile>
<errnoilemsg><![CDATA[No such path or directory.]]></errnoilemsg>
<errnoxml>1400001</errnoxml>
<xmlerrmsg><![CDATA[client call failed]]></xmlerrmsg>
<xmlhint><![CDATA[failure]]></xmlhint>
</error>
<jobinfo>
<jobipc>È_øÑø#^#Ï^ïë(‘^••#“/™˜‘–‘#</jobipc>
<jobipcskey>FFFFFFFF</jobipcskey>
<jobname>QRWTSRVR</jobname>
<jobuser>QUSER</jobuser>
<jobnbr>371446</jobnbr>
<jobsts>*ACTIVE</jobsts>
<curuser>QTMHHTTP</curuser>
<ccsid>65535</ccsid>
<dftccsid>278</dftccsid>
<paseccsid>0</paseccsid>
<langid>FIN</langid>
<cntryid>FI</cntryid>
<sbsname>QUSRWRK</sbsname>
<sbslib>QSYS</sbslib>
<curlib></curlib>
<syslibl>QSYS QSYS2 QHLPSYS QUSRSYS</syslibl>
<usrlibl>QGPL QTEMP</usrlibl>
<jobcpffind>see log scan, not error list</jobcpffind>
</jobinfo>
<joblogscan>
<joblogrec>
<jobcpf>CPF1124</jobcpf>
<jobtime><![CDATA[21.09.12  12:40:47,805747]]></jobtime>
<jobtext><![CDATA[Job 371446/QUSER/QRWTSRVR started on 21.09.12 at 12:27:26 QCNTEDDM SNDMSG 8047 QRWTSRVR main 352 Target job assigned to handle D]]></jobtext>
</joblogrec>
<joblogrec>
<jobcpf>CPF1301</jobcpf>
<jobtime><![CDATA[21.09.12  12:40:47,805747]]></jobtime>
<jobtext><![CDATA[QTMHHTTP QRWTSECR SWPNCHG 6091 ACGDTA for 371446/QUSER/QRWTSRVR not journaled; reason 1.]]></jobtext>
</joblogrec>
<joblogrec>
<jobcpf>MCH3401</jobcpf>
<jobtime><![CDATA[21.09.12  12:40:47,805747]]></jobtime>
<jobtext><![CDATA[QTMHHTTP PLUGILE ILERSLV 7801         *PRCLT Cannot resolve to object RMWSLOG. Type and Subtype X'0201' Either a system pointer]]></jobtext>
</joblogrec>
</joblogscan>
<joblog job='QRWTSRVR' user='QUSER' nbr='371446'>
<![CDATA[5770SS1 V7R1M0 100423                        Display Job Log                        I1       21.09.12 13:00:02          Page    1
  Job name . . . . . . . . . . :   QRWTSRVR        User  . . . . . . :   QUSER        Number . . . . . . . . . . . :   371446
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :   QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
CPF1124    Information             00   21.09.12  12:27:27,028424  QWTPIIPP     QSYS        04C0     *EXT                    *N
                                     Message . . . . :   Job 371446/QUSER/QRWTSRVR started on 21.09.12 at 12:27:26
                                       in subsystem QUSRWRK in QSYS. Job entered system on 21.09.12 at 12:27:26.
CPI9162    Information             00   21.09.12  12:40:46,323674  QCNTEDDM     QSYS        *STMT    QRWTSRVR    QSYS        *STMT
                                     From module . . . . . . . . :   QCNTEDDM
                                     From procedure  . . . . . . :   SNDMSG
                                     Statement . . . . . . . . . :   8047
                                     To module . . . . . . . . . :   QRWTSRVR
                                     To procedure  . . . . . . . :   main
                                     Statement . . . . . . . . . :   352
                                     Message . . . . :   Target job assigned to handle DDM connection started by
                                       source system over TCP/IP.
                                     Cause . . . . . :   A distributed data management (DDM) connection has been
                                       started over TCP/IP by source system job 372241/QTMHHTTP/ZENDSVR on source
                                       system I1. See source job 372241/QTMHHTTP/ZENDSVR for all additional
                                       messages regarding the DDM connection. DDM uses remote IP address
                                       172.16.64.30 and remote port 16823 for this TCP/IP connection.
CPF1301    Information             30   21.09.12  12:40:46,546785  QWTCHGJB     QSYS        1201     QRWTSECR    QSYS        *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     To module . . . . . . . . . :   QRWTSECR
                                     To procedure  . . . . . . . :   SWPNCHG
                                     Statement . . . . . . . . . :   6091
                                     Message . . . . :   ACGDTA for 371446/QUSER/QRWTSRVR not journaled; reason 1.
                                     Cause . . . . . :   Job resource accounting data for job 371446/QUSER/QRWTSRVR
                                       was not journaled to the system accounting journal QSYS/QACGJRN. -- Reason
                                       codes and their meanings follow: -- 1-The accounting level system value
                                       (QACGLVL) indicated that this level of resource accounting was not to be
                                       done when the job entered the system. -- 2-The accounting journal
                                       QSYS/QACGJRN is unable to receive the data.  The accounting data was sent to
                                       the history log (QHST) as the text of a CPF1303 message.  See CPF1302 in the
                                       history log (QHST) for recovery action. -- 3-The accounting journal
                                       QSYS/QACGJRN  was allocated to another job.  The accounting data was sent to
                                       the history log (QHST) as the text of a CPF1303 message.
CPIB8EA    Information             00   21.09.12  12:40:46,559294  QYASPPG1     QSYS        *STMT    QYASPACT    QSYS        *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     From module . . . . . . . . :   QYASPPG1
                                     From procedure  . . . . . . :   sendCPIB8EA
5770SS1 V7R1M0 100423                        Display Job Log                        I1       21.09.12 13:00:02          Page    2
  Job name . . . . . . . . . . :   QRWTSRVR        User  . . . . . . :   QUSER        Number . . . . . . . . . . . :   371446
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :   QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
                                     Statement . . . . . . . . . :   15
                                     To module . . . . . . . . . :   QYASPACT
                                     To procedure  . . . . . . . :   main
                                     Statement . . . . . . . . . :   438
                                     Message . . . . :   ASP group set to KOLME.
                                     Cause . . . . . :   ASP group for thread X'0000000000000001' set to KOLME.
CPI3E01    Information             00   21.09.12  12:40:46,783242  QRWTBAS      QSYS        *STMT    QCNTEDDM    QSYS        *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     From module . . . . . . . . :   QRWTARDB
                                     From procedure  . . . . . . :   SNDMSG
                                     Statement . . . . . . . . . :   6521
                                     To module . . . . . . . . . :   QCNTEDDM
                                     To procedure  . . . . . . . :   PRCRH
                                     Statement . . . . . . . . . :   7437
                                     Message . . . . :   Local relational database accessed by I1.
MCH3401    Escape                  40   21.09.12  12:40:47,805747  Ämnrnrl                  000518   XMLSTOREDP  ZENDSVR     *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     To module . . . . . . . . . :   PLUGILE
                                     To procedure  . . . . . . . :   ILERSLV
                                     Statement . . . . . . . . . :   7801         *PRCLT
                                     Message . . . . :   Cannot resolve to object RMWSLOG. Type and Subtype X'0201'
                                       Authority X'0000'.
                                     Cause . . . . . :   Either a system pointer or a data pointer can not be
                                       resolved. For a system pointer, it can not be resolved to object RMWSLOG,
                                       type and subtype X'0201', authorization X'0000', because either the named
                                       object was not in any context referred to or the correct object was located
                                       but the user profile did not have the required authority. The object types
                                       for some common type or subtype codes follow: -- 0190-Access group,
                                       0201-Program, 0401-Library, -- 0701-Journal receiver, 0801-User profile,
                                       0901-Journal, -- 0B90-Data space, 0C01-Directory, 0C90-Data space index, --
                                       0E01-Job queue, 0E02-Output queue, 0E03-Message file, -- 0E02-User index,
                                       0A01-Data queue, 1401-Class of service description -- 1501-Mode description,
                                       0E05-Session description, -- 1001-Device description, 1101-Line description,
                                       -- 1201-Controller description, 1901-File, 1902-Message queue, -- 1903-Job
                                       description, 1904-Class, 1905-Command, 1906-Table, -- 1908-Edit description,
                                       1909-Subsystem description, -- 190A-Data area, 190C-Graphic symbol set,
                                       190D-Chart format, -- 1911-Query definition, 1912-Folder, -- 1915-Panel
5770SS1 V7R1M0 100423                        Display Job Log                        I1       21.09.12 13:00:02          Page    3
  Job name . . . . . . . . . . :   QRWTSRVR        User  . . . . . . :   QUSER        Number . . . . . . . . . . . :   371446
  Job description  . . . . . . :   QDFTSVR         Library . . . . . :   QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST
                                       group, 1916-Menu group description, -- 1920-Data dictionary, 192D-Management
                                       collection, 19D0 Work control block table, -- 19D2-System value,
                                       1B01-Process control space, -- 1E01-Byte stream file, 1E03-Local socket,
                                       1E06-Character special file, -- 1E07-First-in first-out special file For a
                                       data pointer, it can not be resolved because the named object is not located
                                       within any program activation currently known to the process. Recovery  . .
                                       . :   Either specify the correct object name or specify the correct
                                       authority for the object.
QSH0005    Completion              00   21.09.12  12:40:48,833283  QZSHRUNC     QSHELL      *STMT    XMLSTOREDP  ZENDSVR     *STMT
                                     From user . . . . . . . . . :   QTMHHTTP
                                     From module . . . . . . . . :   QZSHRUNC
                                     From procedure  . . . . . . :   main
                                     Statement . . . . . . . . . :   149
                                     To module . . . . . . . . . :   PLUGILE
                                     To procedure  . . . . . . . :   ILECMDEXC
                                     Statement . . . . . . . . . :   5094
                                     Message . . . . :   Command ended normally with exit status 0.
]]>
</joblog>
</report>

Exec end: 2012-09-21 13:00:03. Seconds to execute: 11,10483288765.


Any idea what's going on here?

-Timo

[aseiden]

Timo,

It's almost certainly a library list issue. Here's the clue:

Code: Select all

Cannot resolve to object RMWSLOG. Type and Subtype X'0201'

According to the log you posted, the library lists are:

Code: Select all

<syslibl>QSYS QSYS2 QHLPSYS QUSRSYS</syslibl>
<usrlibl>QGPL QTEMP</usrlibl>


What library is RMWSLOG in?

To test this theory, specify the library instead of *LIBL when you call RMWSLOG. Or do $conn->ClCommand('ADDLIBLE mylib'); See if those work.

--Alan

[timo_karvinen]

Yes, the basic error is most definitely a library list error.
But my question is why the library list error exists?
Like I said, I'm pretty sure this used work fine, and when we look at the path that should result in wanted library list, the question becomes why the library list isn't what it's supposed to be.

As you can see in the debug logs, I'm using user WSM2012, so we check that user on the machine:

Code: Select all

User profile . . . . . . . . . . . . . . . :   WSM2012
Job description  . . . . . . . . . . . . . :   WM2012
  Library  . . . . . . . . . . . . . . . . :     MERXJ


Then we check that job description:

Code: Select all

Job description:   WM2012         Library:   MERXJ
Sequence         
number   Library
    10    MERXTEMP
    20    MERXP   
    30    MERXF   
    40    MERXJ   
    50    MERXO   
    60    MERXA   
    70    MERXS   
    80    QGPL   
    90    QTEMP   


And in that library list we have the needed "MERXP" library, where the program recides.

Code: Select all

Object      Type      Library     Attribute
RMWSLOG     *PGM      MERXP       RPGLE   


So why isn't the WM2012 job description controlling the library list in the job like it's supposed to?

-Timo

[timo_karvinen]

I tested this on our other machine also, no iASP/PowerHA on this machine, so only *LOCAL database and V5R4 versus V7R1 on the other machine.
The same problem, the loss of library list, occurs here too.
Username now is "WEBSMERX" which has job description with all the needed libraries in there.
But still when we make the call from toolkit the library list is "plain", none of the libraries from job description got added.

On this machine there seems to be difference with stateless=true/false though, on other machine neither worked.
Running the script with stateless = true, everything works as expected, but changing only stateless = false and nothing else, we get:

Code: Select all

25 Sep 2012 16:37:5.896424 Not private but not stateless; running with IPC '/tmp/ipc_cw_WEBSMERX_5061b381dabaf'. CW version 1.3.1. Service library: XMLSERVICE
25 Sep 2012 16:37:6.535492 i5Error: num=312 cat=9 msg="UNEXPECTED" desc="XML run loop failed (p(54) <pgm name='RMWSLOG' lib='*LIBL')"

Code: Select all

Creating new conn with database: '*LOCAL', user or i5 naming flag: 'WEBSMERX', ext prefix: '', persistence: '1'
Going to create a new db connection.
Exec start: 2012-09-25 16:37:05
IPC: '/tmp/ipc_cw_WEBSMERX_5061b381dabaf'. Control key: *cdata *sbmjob(ZENDSVR/ZSVR_JOBD/XTOOLKIT)
Stmt: call XMLSERVICE.iPLUG512K(?,?,?,?)
Input XML: <?xml version="1.0" encoding="ISO-8859-1" ?><script>
<pgm name='RMWSLOG' lib='*LIBL'>
<parm io='in' comment='PI_Service'><data var='PI_Service' type='100a'>wsdl: GetControlInfo</data></parm>
<parm io='in' comment='PI_IP'><data var='PI_IP' type='15a'>172.17.64.46</data></parm>
<parm io='in' comment='PI_Caller'><data var='PI_Caller' type='10a' /></parm>
<parm io='in' comment='PI_ProReq'><data var='PI_ProReq' type='1a'>P</data></parm>
<parm io='in' comment='PI_Type'><data var='PI_Type' type='1a'>W</data></parm>
<parm io='in' comment='PI_ErrorCode'><data var='PI_ErrorCode' type='1a'>0</data></parm>
<parm io='in' comment='PI_Note'><data var='PI_Note' type='128a' /></parm>
</pgm>
</script>
Output XML: <?xml version="1.0" encoding="ISO-8859-1" ?>
<report>
<version>XML Toolkit 1.7.2</version>
<error>
<errnoxml>1100004</errnoxml>
<xmlerrmsg><![CDATA[XML run loop failed]]></xmlerrmsg>
<xmlhint><![CDATA[p(54) <pgm name='RMWSLOG' lib='*LIBL']]></xmlhint>
</error>
<error>
<errnoxml>1000005</errnoxml>
<xmlerrmsg><![CDATA[PASE resolve failed]]></xmlerrmsg>
<xmlhint><![CDATA[RMWSLOG]]></xmlhint>
</error>
<error>
<errnoxml>1100016</errnoxml>
<xmlerrmsg><![CDATA[XML run pgm failed]]></xmlerrmsg>
<xmlhint><![CDATA[<pgm name='RMWSLOG' lib='*LIBL'>
<parm io='in' comment='PI]]></xmlhint>
</error>
<error>
<errnoxml>1100004</errnoxml>
<xmlerrmsg><![CDATA[XML run loop failed]]></xmlerrmsg>
<xmlhint><![CDATA[p(54) <pgm name='RMWSLOG' lib='*LIBL']]></xmlhint>
</error>
<jobinfo>
<jobipc>/tmp/ipc_cw_WEBSMERX_5061b381dabaf</jobipc>
<jobipcskey>011E1DF3</jobipcskey>
<jobname>XTOOLKIT</jobname>
<jobuser>WEBSMERX</jobuser>
<jobnbr>031006</jobnbr>
<jobsts>*ACTIVE</jobsts>
<curuser>WEBSMERX</curuser>
<ccsid>65535</ccsid>
<dftccsid>278</dftccsid>
<paseccsid>819</paseccsid>
<langid>FIN</langid>
<cntryid>FI</cntryid>
<sbsname>ZENDSVR</sbsname>
<sbslib>ZENDSVR</sbslib>
<curlib></curlib>
<syslibl>THSYS QSYS QSYS2 QHLPSYS QUSRSYS QADM</syslibl>
<usrlibl>ZENDSVR QGPL QTEMP</usrlibl>
<jobcpffind>see log scan, not error list</jobcpffind>
</jobinfo>
<joblogscan>
<joblogrec>
<jobcpf>CPF1124</jobcpf>
<jobtime><![CDATA[25.09.12  16:37:05,988032]]></jobtime>
<jobtext><![CDATA[Työ 031006/WEBSMERX/XTOOLKIT aloitettu 25.09.12 kello Työ 031006/WEBSMERX/XTOOLKIT on viety työjonoon.]]></jobtext>
</joblogrec>
<joblogrec>
<jobcpf>*NONE</jobcpf>
<jobtime><![CDATA[25.09.12  16:37:05,988032]]></jobtime>
<jobtext><![CDATA[CALL PGM(XMLSERVICE/XMLSERVICE)]]></jobtext>
</joblogrec>
<joblogrec>
<jobcpf>MCH3401</jobcpf>
<jobtime><![CDATA[25.09.12  16:37:05,988032]]></jobtime>
<jobtext><![CDATA[PLUGILE ILERSLV 7801         *PRCLT Cannot resolve to object RMWSLOG. Type and Subtype X'0201' Either a system pointer or a data]]></jobtext>
</joblogrec>
</joblogscan>
<joblog job='XTOOLKIT' user='WEBSMERX' nbr='031006'>
<![CDATA[5722SS1 V5R4M0 060210                        Työlokin näyttö                        TTH400   25.09.12 16:37:06          Sivu    1
  Työ  . . . . . . . . . . . . :   XTOOLKIT        Käyttäjä  . . . . :   WEBSMERX     Numero . . . . . . . . . . . :   031006
  Työn kuvaus  . . . . . . . . :   ZSVR_JOBD       Kirjasto  . . . . :   ZENDSVR
SAN.TUN.   LAJI                    VAK  PVM       AIKA             LÄHDEOHJ.    KIRJASTO    ASENN.   KOHDEOHJ.   KIRJASTO    ASENN.
CPF1124    Ilmoitussanoma          00   25.09.12  16:37:05,943928  QWTPIIPP     QSYS        0671     *EXT                    *N
                                     Sanoma  . . . . :   Työ 031006/WEBSMERX/XTOOLKIT aloitettu 25.09.12 kello
                                       16:37:05 kirjastossa ZENDSVR olevassa alijärjestelmässä ZENDSVR. Järjestelmä
                                       otti vastaan työn 25.09.12 kello 16:37:05.
CPI1125    Ilmoitussanoma          00   25.09.12  16:37:05,944360  QWTPCRJA     QSYS        010F     *EXT                    *N
                                     Sanoma  . . . . :   Työ 031006/WEBSMERX/XTOOLKIT on viety työjonoon.
                                     Selitys . . . . :   Työ 031006/WEBSMERX/XTOOLKIT on viety kirjastossa ZENDSVR
                                       olevaan työjonoon ZSVR_JOBQ. Työn aloittanut työ on 026430/QUSER/QSQSRVR.
                                       Työ 031006/WEBSMERX/XTOOLKIT on aloitettu komennolla SBMJOB (työn vienti
                                       työjonoon) ja työn määritteet ovat seuraavat: JOBPTY(5) OUTPTY(5) PRTTXT()
                                       RTGDTA(QCMDB) SYSLIBL(THSYS      QSYS       QSYS2      QHLPSYS    QUSRSYS
                                       QADM) CURLIB(*CRTDFT) INLLIBL(ZENDSVR    QGPL       QTEMP) INLASPGRP(*NONE)
                                       LOG(4 00 *NOLIST) LOGCLPGM(*YES) LOGOUTPUT(*JOBEND) OUTQ(QGPL/QPRINT2)
                                       PRTDEV(QSUPPRT) INQMSGRPY(*RQD) HOLD(*NO) DATE(*SYSVAL) SWS(00000000)
                                       MSGQ(QUSRSYS/WEBSMERX) CCSID(65535) SRTSEQ(*N/*HEX) LANGID(FIN) CNTRYID(FI)
                                       JOBMSGQMX(16) JOBMSGQFL(*WRAP) ALWMLTTHD(*NO) SPLFACN(*KEEP).
*NONE      Komentosanoma                25.09.12  16:37:05,944552  QWTSCSBJ                 *N       QCMD        QSYS        0194
                                     Sanoma  . . . . :  -CALL PGM(XMLSERVICE/XMLSERVICE)
                                       PARM('/tmp/ipc_cw_WEBSMERX_5061b381dabaf')
MCH3401    Katkosanoma             40   25.09.12  16:37:05,988032  Ämnrnrl                  0004E8   XMLSERVICE  XMLSERVICE  *STMT
                                     Moduuliin . . . . . . . . . :   PLUGILE
                                     Toimintosarjaan . . . . . . :   ILERSLV
                                     Käsky . . . . . . . . . . . :   7801         *PRCLT
                                     Sanoma  . . . . :   Cannot resolve to object RMWSLOG. Type and Subtype X'0201'
                                       Authority X'0000'.
                                     Cause . . . . . :   Either a system pointer or a data pointer can not be
                                       resolved. For a system pointer, it can not be resolved to object RMWSLOG,
                                       type and subtype X'0201', authorization X'0000', because either the named
                                       object was not in any context referred to or the correct object was located
                                       but the user profile did not have the required authority. The object types
                                       for some common type or subtype codes follow: -- 0190-Access group,
                                       0201-Program, 0401-Library, -- 0701-Journal receiver, 0801-User profile,
                                       0901-Journal, -- 0B90-Data space, 0C01-Directory, 0C90-Data space index, --
                                       0E01-Job queue, 0E02-Output queue, 0E03-Message file, -- 0E02-User index,
                                       0A01-Data queue, 1401-Class of service description -- 1501-Mode description,
                                       0E05-Session description, -- 1001-Device description, 1101-Line description,
                                       -- 1201-Controller description, 1901-File, 1902-Message queue, -- 1903-Job
                                       description, 1904-Class, 1905-Command, 1906-Table, -- 1908-Edit description,
                                       1909-Subsystem description, -- 190A-Data area, 190C-Graphic symbol set,
                                       190D-Chart format, -- 1911-Query definition, 1912-Folder, -- 1915-Panel
                                       group, 1916-Menu group description, -- 1920-Data dictionary, 192D-Management
                                       collection, 19D0 Work control block table, -- 19D2-System value,
                                       1B01-Process control space, -- 1E01-Byte stream file, 1E03-Local socket,
                                       1E06-Character special file, -- 1E07-First-in first-out special file For a
                                       data pointer, it can not be resolved because the named object is not located
                                       within any program activation currently known to the process. Recovery  . .
                                       . :   Either specify the correct object name or specify the correct
                                       authority for the object.
]]>
</joblog>
</report>

Exec end: 2012-09-25 16:37:06. Seconds to execute: 0.63495182991028.



-Timo

[aseiden]

Timo, thanks, I understand what you're seeing now. I am at a conference now (COMMON) but will get back to you soon.

Alan

[aseiden]

Hi, Timo,

Responding to your question, we've updated XMLSERVICE so that your *LIBL should be preserved when connecting in "stateful" mode. Stateful is like a private connection; a new job is submitted to answer requests. Now we use INLLIBL *CURRENT, which should keep the same library list as that from the DB2 job that submits it.

Please try XMLSERVICE 1.7.3 and let us know:
http://www.youngiprofessionals.com/wiki/XMLSERVICE

Changelog:

Code: Select all

Changed default LIBL statefull to INLLIBL(*CURRENT)

plugconf_h.rpgle
      *****************************************************
      * server program library configuration
      * INLLIBL *JOBD changed to *CURRENT via Alan (1.7.3)
      *****************************************************
     DSBMOPTS          ds
     D sbm1                          50    inz('CURLIB(*CURRENT)')
     D                               50    inz('INLLIBL(*CURRENT)')
     D                               50    inz('SRTSEQ(*CURRENT)')
     D                               50    inz('LANGID(*CURRENT)')
     D                               50    inz('CNTRYID(*CURRENT)')
     D                               50    inz('CCSID(*CURRENT)')
     D SBMNBR          c                   %div(%size(SBMOPTS):%size(sbm1))
     D pSBMOPTS        s               *   inz(%addr(SBMOPTS))
     D SBMARRAY        s             50    dim(SBMNBR) based(pSBMOPTS)


[timo_karvinen]

Thank you very much for this update.
This works now fine on our other machine, with the provided update.

However our other machine is still all messed up with this, or it might be entirely different problem with similar symptoms.
I'll post more info about the other machine some day when I have time to go through it with thought.

-Timo

[aseiden]

Hi, Timo,

Glad the update helped. With your other machine, remember to end XTOOLKIT jobs so that the new release can go into effect.

Let me know.

Alan

[timo_karvinen]

It's nice that we got that other problem fixed in this thread, but like I suspected, the other machine has similar symptoms, but it's totally different error.

So the problem described in the first post of this thread still exists on our other machine, I dug up bit more information on it, and the problem is actually twofold.
The first problem seems to be that instead of using the normal method (what we have on other machine) of using QSQSRVR jobs, this machine for some reason has started to use QRWTSRVR jobs.
Even though it's the local machine that's running Zend Server / php scripts and I haven't intentionally told it to do this.
If I have unintentionally done something to make it do this, please tell me what I have done and how to fix it.
I also noticed that this only seems to happen when I'm connection to iASP configured in WRKRDBDIRE, not if connection to *LOCAL database.
And also since this is in our PowerHA testing environment, if I do switchover to the other machine everything works again, so it's something specific on this machine and it's configurations.

As I understand it, if I'd use remote client: php running on my own laptop or so on, the jobs would intentionally be those QRWTSRVR, this brings me to the other problem.
If I was intentionally running in QRWTSRVR, there's still same kind of error as what we had with statefull connection not retaining the library lists.
We only have:
<curlib></curlib>
<syslibl>QSYS QSYS2 QHLPSYS QUSRSYS</syslibl>
<usrlibl>QGPL QTEMP</usrlibl>
here instead of the list that job should get from user/users job description.


Here's some joblog entries from our PowerHA machines.

Working one (QSQSRVR):

Code: Select all

Job . . :   ZENDSVR       User . . :   QTMHHTTP      Number . . . :   030601
                                                                           
    Job 030417/QUSER/QSQSRVR used for SQL server mode processing.           
   
Message ID . . . . . . :   SQL7908       Severity . . . . . . . :   00       
Message type . . . . . :   Completion                                         
Date sent  . . . . . . :   10/26/12      Time sent  . . . . . . :   11:18:25 
                                                                             
Message . . . . :   Job 030417/QUSER/QSQSRVR used for SQL server mode         
  processing.                                                                 
Cause . . . . . :   A Structured Query Language (SQL) statement was executed 
  while running in SQL server mode.  SQL statements for this connection or   
  thread will be processed in job 030417/QUSER/QSQSRVR.                       
Technical description . . . . . . . . :   SQL server mode was requested by   
  either setting the SQL server mode job attribute, or by setting the server 
  mode environment attribute via the SQL Call Level Interface.  When running 
  in this mode, SQL statements are processed by a separate job, which runs   
  under the user profile specified for the connection. The thread identifier 
  is 2 and the connection is to Relational Database KOLME.  If the Relational
  Database name is *N, this means that all connections for the thread will use
  the same job.


The failing one (QRWTSRVR):

Code: Select all

Message ID . . . . . . :   CPI9160       Severity . . . . . . . :   00       
Message type . . . . . :   Information                                       
Date sent  . . . . . . :   26.10.12      Time sent  . . . . . . :   12:19:53 
                                                                             
Message . . . . :   Database connection started over TCP/IP or a local socket.
Cause . . . . . :   The database server job 405429/QUSER/QRWTSRVR has been   
  allocated on system I1 for handling a new TCP/IP or local socket connection
  using DDM protocols.  The connection uses IP address 172.16.64.30, port 446,
  and user ID QTMHHTTP at the server.  (If the IP address is all zeros, it   
  indicates that the connection uses a local socket.)  The connection has a   
  scope of *ACTGRP level in activation group *N with an activation group     
  number of 2.                                                               


-Timo

[rangercairns]

1st reminder ...
I am NEVER authorised public product to product compares, so any path leading this direction immediately voids my help (maybe permanently). Again, if you need/want only Easycom product, please seek business relationship with the good Aura company.

LIBL ...
You are obviously a smart guy, so you already know that your can simply use CHGLIBL from many interfaces PHP Toolkit / XMLSERVICE. So, this is more likely another extended public complaint about differences in design between Easycom and XMLSERVICE.

Code: Select all

CHGLIBL LIBL($schematest) CURLIB($schematest)


Frankly, I find your whole rant tiresome, but very well ...

You are completely missing the point here Timo. Unlike some other toolkits, XMLSERVICE does NOT REQUIRE proprietary software "connection", therefore you can use all manner of 1-tier (IBM i-2-IBM i) and 2-tier (any-2-IBM i) connection transports. PHP Toolkit / XMLSERVICE cannot control the behaviour of each and every connection possible, and in fact, there are 2-tier connections that don't have any idea what a LIBL would be because this is a truly unique feature of IBM i. IN ANY EVENT, you can simply call CHGLIBL in any staeless or staefull XMLSERVICE job and change the state of the LIBL.