Limited support

 

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 Open link .

Troubleshooting UIM server issues

Use the following information to troubleshoot common issues with the User Interface Middleware (UIM) server:

Tip

If you contact BMC Customer Support, you might be asked to enable or disable overall tracing options or specific tracing options. For information about enabling and disabling tracing options temporarily, see Enabling or disabling the overall tracing option temporarily and Enabling or disabling specific tracing options temporarily.

UIM server displays message LSCX902 in SYSTERM DD

Message LSCX902 is displayed in the SYSTERM DD output and states that an error occurred when the following conditions exist:

  • Interlink or CA TCPAccess is installed instead of IBM TCP/IP stack
  • The command to start the UIM server is issued

You can solve this problem by inserting the TCPAccess LINKLIB as the first data set in the UIM server STEPLIB DD. Inserting the LINKLIB first provides the correct socket API interface modules.

Warning

Insert only the LINKLIB library, not the LOAD library, because TCPAccess uses SAS/C. Using TCPAccess SAS/C might cause an incompatibility in the runtime modules.

UIM server displays message LSCX904 in SYSTERM DD

Message LSCX904 is displayed and states that an access error occurred when the following conditions exist:

  • The TCPIP PROFILE file specifies a reserved port number for a specific started task name that does not match the UIM server started task name
  • The command to start the UIM server is issued

This error occurs because the port number that is specified for the UIM server in the TCPIP PROFILE file is reserved for a job name under which the UIM server is not running.

To solve this problem, specify a different port number for the UIM server, or correct the started task name.

To specify a different port number in the TCIP PROFILE file

  1. Look in the SYSTERM DD output for the following message:

    LSCX904 **** WARNING **** ERRNO = EACCES
    Generated in     BIND called from line 
    Unexpected failure in bind, reason code 744C7246
  2. If the message is in the SYSTERM DD output, the wrong name job name was used in the TCPIP PROFILE file, an you need to correct the job name.

  3. If the message is not in the SYSTERM DD output, select another port number for the UIM server.

    Here is a sample entry in the TCPIP PROFILE file:

    8300 TCP STFTUIM             ; BMC UIM server


    This entry reserves the port number 8300 for the job named STFTUIM that is associated with the UIM server. Any other job trying to access that port number receives the EACCES error in the SYSTERM DD output.

UIM server does not start and displays message LSCX902 in SYSTERM DD

When you start the UIM server, it looks for the TCP/IP address space by using the default space name (TCPIP). Error LSCX902 occurs when any of the following conditions exist:

  • No TCP/IP address space with started task name TCPIP exists because the address space has been renamed.

  • Multiple TCP/IP address spaces exist, but none are named TCPIP.

You can solve the problem by changing the name of the TCP/IP started task name to TCPIP. 

To change the name of the TCP/IP started task name to TCPIP

Perform one of the following tasks:

  • Determine the name of the TCPIP file (TCPIP.DATA). This file is used by TCP/IP client address spaces to determine local TCP/IP configuration information.

    The local TCP/IP configuration information includes the name of the TCP/IP address space that is specified by the TCPIPUSERID parameter. Update the UIM server procedure to include a SYSTCPD DD statement that specifies the appropriate TCPIP.DATA file.

  • Specify the TCP/IP address space name in a parameter to the UIM server by using the procedure parameter ENV as follows:

    // ENV-"-TCPIP_MACH-<startedTaskName>"

UIM server does not start because the OMVS segment is not defined

If the started task is missing a RACF OMVS segment, one of the following messages is displayed in the job log output when you issue the UIM server start command:

  • Message IEF695I, stating that the job name is assigned to the specified user

  • Message ICH408I, stating that the OMVS segment is not defined

In addition, message LSCX902 is displayed in the SYSTERM DD output stating that an MVS initialization error occurred.

To solve this problem, include a RACF OMVS segment for the UIM server address space.

To determine whether a started task is missing a RACF OMVS segment

  1. Check the JES Message log for the following messages:
    • IEF695I START RGSTEMP WITH JOBNAME RGSTEMP IS ASSIGNED TO USER ++++++++
    • ICH408I JOB(RGSTEMP) STEP(RGSTEMP) CL(PROCESS) OMVS SEGMENT NOT DEFINED
  2. Check the SYSTERM DD output for the following message:

    LSCX902 **** WARNING **** ERRNO = EMVSINITIAL

    Generated in PFSCTL called from line . . .

    If you find the preceding message, one of the following conditions exists:

    • No RACF rule has assigned a user to the started task.
    • A RACF rule assigned a user to the started task, but the user does not have an associated OMVS segment.

    The UIM server uses TCP/IP. TCP/IP requires UNIX system services, and a RACF OMVS segment must exist for the UIM server address space. To define an OMVS segment for a user of the started tasks, contact your security administrator.

Was this page helpful? Yes No Submitting... Thank you

Comments