Re: [IBMiOSS] Using Nodev6 db2i/itoolkit

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

> Do you have any idea what we might be missing?

Do a WRKOBJ QXMLSERV/*ALL and paste the results back here.

Aaron Bartell
IBM i hosting, starting at $157/month.  litmis.com/spaces


On Mon, Apr 2, 2018 at 5:18 PM, Kevin Nunn <nunn.kevin@xxxxxxxxx> wrote:

> Aaron,
>
> We are trying to figure out what our system is missing that is causing
> this. We didn't have "XML Toolkit" and installed that, but it still is not
> working. In the job log I noticed it said "ensure that the DB2 Multisystem
> product is installed on your system", so our admin is going to check that
> after a client visit in the morning and maybe see if that might be the
> issue.
>
> Do you have any idea what we might be missing? Below is a copy of the
> message in the job log.
>
> From user . . . . . . . . . : KEVIN
> From module . . . . . . . . : QSQPROC
> From procedure . . . . . . : CLEANUP
> Statement . . . . . . . . . : 54610
> To module . . . . . . . . . : QSQPROC
> To procedure . . . . . . . : CLEANUP
> Statement . . . . . . . . . : 54610
> Message . . . . : IPLUG512K in QXMLSERV type *N not found.
> Cause . . . . . : IPLUG512K in QXMLSERV type *N 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, IPLUG512K 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.