The following procedures can help you determine if the Query Processor server installation completed correctly. These procedures are not required. If you had any problems during the installation process, or if you want to confirm that all components of the Query Processor server were installed, you can run some or all of the troubleshooting procedures.

Verifying Release Identifiers

Action

To verify the installation of the most recent support libraries, enter the following CANDE commands:

LFILES *SYSTEM/MCPSQL ON SYSNEW :RELEASEID
LFILES *DESCRIPTION/SQLDIR/MCPSQL-CATALOG :RELEASEID
LFILES *SYMBOL/MCPSQL ON SYSNEW :RELEASEID

Solution

If any files are missing or if the RELEASEID attribute of the files is not correct, perform the following procedures.

Verifying the Query Processor Configuration System Library

Action

Enter the following ODT command:

SL *MCPSQLCONFIG

Result

The following statement is displayed:

SL MCPSQLCONFIG = *SYSTEM/MCPSQL/CONFIG ON SYSNEW

Solution

If the MCOSQLCONFIG statement points to another file or if the Query Processor configuration system library function does not exist, enter the following ODT command:

SL MCPSQLCONFIG = *SYSTEM/MCPSQL/CONFIG ON SYSNEW

Verifying the SCode Compiler System Library

Action

Enter the following ODT command:

SL * MCPSQLSCODE

Result

The following statement is displayed:

SL MCPSQLSCODE = *SYSTEM/MCPSQL/SCODE ON SYSNEW

Solution

If the MCPSQLCODE statement points to an incorrect file or if the Scode compiler system library function does not exist, enter the following ODT command:

SL MCPSQLSCODE = *SYSTEM/MCPSQL/SCODE ON SYSNEW

Verifying the SQL Driver System Library

Action

Enter the following ODT command:

SL *MCPSQLCLI

Result

The following statement is displayed:

SL MCPSQLCLI = *SYSTEM/MCPSQL/INTERFACE/ ON SYSNEW TRUSTED

Solution

If the MCPSQLCLI statement points to another file, if the TRUSTED parameter is missing, or if the SQL driver system library function does not exist, enter the following ODT command:

SL MCPSQLCLI = *SYSTEM/MCPSQL/INTERFACE ON SYSNEW  :TRUSTED

Verifying the Existence and Location of the Query Processor Configuration File

Action

Enter the following CANDE command:

RUN $SYSTEM/MCPSQL/CONFIG ON SYSNEW

Result

The following text is displayed:

# RUNNING 8864
>   The MCPSQL/CONFIG file just validated is:
>   *MCPSQL/CONFIG ON HL511D0 10/11/2005 16:03:05
>   No errors.
# ET=0.1 PT=0.0 IO=0.1

Solution

If the Query Processor configuration file does not exist, refer to Creating the Server Configuration File (MCPSQL/CONFIG) earlier in this section for instructions on creating an Query Processor configuration file.

If the Query Processor configuration file does exists, but syntax errors occur, refer to Query Processor Configuration Control Facility for instructions about creating an Query Processor configuration file.

Verifying the Contents of the Query Processor Configuration File

Action

After verifying the existence and location of the Query Processor configuration file, enter the following command to display the contents of the Query Processor configuration file:

LIST *MCPSQL/CONFIG ON SYSNEW

Result

The exact text of your Query Processor configuration file might differ, but ensure the following information is contained in your file:

RELEASE MYSQL (PACK = SYSNEW)

Solution

If the RELEASE or VIEWCONNECTION option is missing from your Query Processor configuration file, modify your Query Processor configuration file to include these options. For detailed information about the Query Processor configuration file, refer to Query Processor Configuration Control Facility.

Verifying the Query Processor Server Code File

Action

Enter the following ODT command:

SL *MCPSQLSERVER

Result

The following text is displayed:

SL MCPSQLSERVER = *SYSTEM/MCPSQL/SERVER ON SYSNEW
:TRUSTED, LINKCLASS=1

Solution

If the MCPSQLSERVER statement points to an incorrect file, if either the TRUSTED parameter or the LINKCLASS parameter is missing, or if the code file does not exist, enter the following ODT command:

SL MCPSQLSERVER = *SYSTEM/MCPSQL/SERVER ON SYSNEW
:TRUSTED, LINKCLASS=1

Verifying the Query Processor Server Provider

Action

Enter the following ODT command:

NA REG SHOW PROV MCPSQLPROV

Result

The following text is displayed:

Provider name: MCPSQLPROV, Task type: NonMonitoredSupportLibrary
Interface: Message
SL: MCPSQLSERVER
DSSes provided: MCPSQL

Solution

If the MCPSQLPROV provider does not exist, enter the following ODT command:

NA REG ADD PROV MCPSQLPROV SL=MCPSQLSERVER, TASK TYPE=NMSL,
INTERFACE=MESSAGE, DSS=MCPSQL  

If the MCPSQLPROV provider exists but the displayed information differs from the preceding result, enter the following ODT command:

 NA REG MODIFY PROV MCPSQLPROV <provider attribute>=<value>

For example:

NA REG MODIFY PROV MCPSQLPROV SL = MCPSQLSERVER

Verifying Query Processor Distributed Systems Services (DSS) Information

Action

Enter the following ODT command:

NA REG SHOW DSS MCPSQL

Result

The following text is displayed:

DSSName: MCPSQL, Class: OTHER
Recovery after Halt/Load: FALSE, Initialize DSS: TRUE
Endpoints: MCPSQL_TCPIP

Solution

If the MCPSQL DSS does not exist, enter the following ODT command:

NA REG ADD DSS MCPSQL EP=(MCPSQL_TCPIP), CLASS=OTHER, INIT=TRUE 

If the MCPSQL DSS exists but the displayed information differs from the preceding result, enter the following ODT command:

NA REG MODIFY DSS MCPSQL <DSS attribute>=<value>

For example:

NA REG MODIFY DSS MCPSQL INITIALIZE = TRUE

Verifying the TCP/IP Endpoint

Action

Enter the following ODT command:

NA REG SHOW EP MCPSQL_TCPIP

Result

The following text is displayed:

Endpoint Name: MCPSQL_TCPIP, Public Endpoint: TRUE
Filename: MCPSQL_TCPIP, Applicationgroup:
Myname: "2012"

Solution

If the MCPSQL_TCPIP endpoint does not exist, enter the following ODT command:

NA REG ADD EP MCPSQL_TCPIP FILENAME=MCPSQL_TCPIP, MYNAME="2012", PUBLIC=TRUE

If the MCPSQL_TCPIP endpoint exists but the displayed information differs from the preceding result, enter the following ODT command:

NA REG MODIFY EP MCPSQL_TCPIP <EP attribute>=<value>

For example:

NA REG MODIFY EP MCPSQL_TCPIP MYNAME = "2012"

Listing the Status of the Query Processor Server

Action

Enter the following ODT commands:

NA MCPSQL -
NA MCPSQL +
NA MCPSQL STATUS

Result

The following text is displayed:

MCPSQL Server Status Report for job 4318/4318.
Monday, October 11, 2012 11:50:26.6582.
DSS Name is MCPSQL.
DSS Provider Name is MCPSQLPROV.
MCPSQL Server <version>.
Server : *SYSTEM/MCPSQL/SERVER ON MCPSQL.
Trace Information not available.
0 MCPSQL connections
TCPIP Options :
      BlockedTimeout: 10 mins
      DialogCheckInterval: 5 mins
      Subfiles offered: 3
      Using port: 2012

Solution

If the required information is missing from your Query Processor server configuration file (MCPSQL/SERVER/CONFIG), modify your server configuration file.