StarQuest Technical Documents

Changing the Installing User

Last Update: 10 Aug 2011
Product: SQDR Plus for iSeries
Version: 3.6x or later
Article ID: PL007

Abstract

Due to the mechanism used by DB2 when registering Java stored procedures, the installer for SQDR Plus for iSeries enforces a restriction that updates must be performed using the same user ID as was used during the original installation. This technical note describes a procedure to update SQDR Plus for iSeries using a different installing user ID.

You will need the password of the original installing user.

Solution

  1. On the SQDR client machines, pause any I/R groups.
  2. On the iSeries server, stop the SQDR Plus Capture Agent (ADDLIBLE SQDR, enter CAMAINT; choose option 7 to stop the Capture Agent).
  3. If you need to identify the original installing user ID, use CAMAINT and choose option 9. Support.
  4. Log on to the iSeries server as the original installing user.
  5. Determine the CCSID (Coded character set identifier) of the current job with DSPJOB OPTION(*DEFNA). The CCSID is displayed on the last page of output. If the CCSID is set to the AS/400 default of 65535, change it to 37 or another appropriate value:

CHGJOB CCSID(37)

  1. Issue the following command:

JAVA CLASS('/home/sqdr/AgentUtil.jar') PARM('-r' SQDR CAPTUREPROCS_JAR)

The output should consist of several DROP PROCEDURE statements followed by the statement Successfully removed jar file.

You should now be able to run the update as a different user. During the post-install phase, the installer will attempt and fail to unregister the stored procedures; those error messages can be ignored.

 

 


DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.