Modifying the MCPSQL/CONFIG File

If you are requested by Unisys to run the MCPSQL diagnostic software, modify the MCPSQL/CONFIG file, as follows:

  1. Duplicate the release specification and append the new specification and the included release files with DIAGNOSTICS. For example, the configuration file might be similar to the following, where RELEASE MCPSQL is the default release specification, and RELEASE MCPSQLDIAG is the diagnostic release specification that you create:

    Note: For more information on the MCPSQL/CONFIG file, see Creating the Server Configuration File (MCPSQL/CONFIG). 
    RELEASE MCPSQL (PACK = DISK)                                             
           SL MCPSQLDRIVER       =  *SYSTEM/MCPSQL/DRIVER                       
           SL MCPSQLSUPPORT      =  *SYSTEM/MCPSQL/SUPPORT                      
           SL MCPSQLFILESUPPORT  =  *SYSTEM/MCPSQL/FILESUPPORT                  
           SL MCPSQLDMSIIMAPPER  =  *SYSTEM/MCPSQL/DMSIIMAPPER                  
           SL MCPSQLCOBOLDESC    =  *SYSTEM/MCPSQL/COBOLDESC                    
           SL MCPSQLADMIN        =  *SYSTEM/MCPSQL/ADMIN                        
           SL MCPSQLCATALOG      =  *DESCRIPTION/SQLDIR/MCPSQL-CATALOG          
           SL MCPSQLSCODESUPPORT =  *SYSTEM/MCPSQL/SCODESUPPORT                 
           SL MCPSQLPARSER       =  *SYSTEM/MCPSQL/PARSER                       
           SL MCPSQLSCODE        =  MCPSQLSCODE                                 

 RELEASE MCPSQLDIAG (PACK = DISK)
           SL MCPSQLDRIVER       =  *SYSTEM/MCPSQL/DRIVER/DIAGNOSTICS
           SL MCPSQLSUPPORT      =  *SYSTEM/MCPSQL/SUPPORT/DIAGNOSTICS
           SL MCPSQLFILESUPPORT  =  *SYSTEM/MCPSQL/FILESUPPORT/DIAGNOSTICS
           SL MCPSQLDMSIIMAPPER  =  *SYSTEM/MCPSQL/DMSIIMAPPER/DIAGNOSTICS
           SL MCPSQLCOBOLDESC    =  *SYSTEM/MCPSQL/COBOLDESC/DIAGNOSTICS
           SL MCPSQLADMIN        =  *SYSTEM/MCPSQL/ADMIN/DIAGNOSTICS
           SL MCPSQLCATALOG      =  *DESCRIPTION/SQLDIR/MCPSQL-CATALOG
           SL MCPSQLSCODESUPPORT =  *SYSTEM/MCPSQL/SCODESUPPORT/DIAGNOSTICS
           SL MCPSQLPARSER       =  *SYSTEM/MCPSQL/PARSER/DIAGNOSTICS
           SL MCPSQLSCODE        =  MCPSQLSCODEDIAG
    Note: SL MCPSQLSCODE=MCPSQLCODEDIAG requires that SL MCPSQLCODEDIAG=*SYSTEM/MCPSQL/SCODE/DIAGNOSTICS is configured on MCP server.

  2. Define the user specification to assign users to the MCPSQLDIAG release specification. For example, the configuration file might be similar to the following, where USER DEFUSER MCPSQL is the default user specification, and USER DIAGUSER MCPSQLDIAG is the diagnostic user specification that you define: 

     USER DEFUSER MCPSQL
 USER DIAGUSER MCPSQLDIAG

    Alternatively, you can temporarily modify the default user specification to use the MCPSQLDIAG release specification. However, ensure that you return the user specification to the default when the MCPSQL diagnostic software has completed.

  3. Save the updated configuration file.

    In this instance, you should run the DIAGNOSTICS test under the DIAGUSER usercode to create the diagnostic material.

Prev  Up  Next
Obtaining Log and Trace Information using MCPSQL Diagnostic Software  Home  Creating an Initialization File