Troubleshooting

This chapter describes how to troubleshoot some of the problems that might occur, due to an incorrect installation properties file.

1. Overview

There are three ways to determine what (if any) errors occurred during installation.

  • Open $OPENFRAME_HOME/UninstallerData/log/install_OSC.log with a text editor and check for errors.

  • Check the errors recorded when you manually execute the script after OpenFrame is installed.

  • This appears when OpenFrame/Base is started.

2. Error Types and Resolutions

This section introduces some of the problems which might occur while installing OpenFrame, as well as their resolutions.

2.1. License File

If the license file is missing, corrupted or has expired, the following error occurs.

  • Problem

    The module server for starting up OpenFrame is not running properly, and the server status is marked as NRDY when checked through tmadmin. Run the si command after executing tmadmin to check for the correct server operation. For more information, refer to Installation Verification.

    For example, if an error occurs in the licosc.dat file, which is a license file for application server of OpenFrame/OSC, application servers will fail to run normally. Assuming that the name of the application server is OSCOIVP1, the following error details will be shown in the OSCOIVP1_TCL1MMDDYYYY.err log file located in the ${OPENFRAME_HOME}/log/tmax/ulog directory.

    If no license file exists, the following error will occur.

    191516 U CHK0001 /home/oframe/OpenFrame/license/licosc.dat file open fail: 2
(I) SVR3016 SVR OSCOIVP1 (19/51) tpsvrinit fail. [SVR0027]

  • Resolution

    Contact TmaxSoft Technical Support to inquire about licenses.

2.2. Shared Memory

If the shared memory key value is duplicated, the following error occurs.

  • Problem

    If a shared memory key value that is registered in an installation properties file is already being used by another user or program, the OpenFrame server that is trying to use the shared memory cannot work properly.

    The server will be shown as NRDY in the list of servers displayed with tmadmin in Installation Verification.

    The following messages will appear during oscboot when a shared memory key value is duplicated.

    OSCBOOT : OSC RTSD loading(OSCOIVP1)                                  [fail]
OSCBOOT : OSC Region(OSCOIVP1)                                        [fail]
OSCBOOT : cics_ctrl_boot(region=OSCOIVP1)=-53017 error

  • Resolution

    Check what type of error occurred by using the oferror tool. Modify a shared memory key value that is registered in the installation properties file and then reinstall OpenFrame, or modify the relevant value in ${OPENFRAME_HOME}/config and retry.

2.3. Security Module

If the security module blocks access to a library, the following error occurs.

  • Problem

    When SELinux, a security module of the Linux system, denies access to the library by security policy, the following error will occur.

    "cannot restore segment prot after reloc: Permission denied"

  • Resolution

    There are two ways to resolve the problem.

    • Run chcon on the library, where permission denied occurred. For certain libraries, users may need to use a superuser permission to run the command.

      chcon -t texrel_shlib_t [desired so library]

    • Modify the /etc/sysconfig/selinux file like the following with superuser permission and then disable SELinux. However, this method may decrease the security level and thus is not recommended.

      SELINUX=disabled

2.4. VTAM DB Table

If a VTAM DB table is not previously created, the following error occurs.

  • Problem

    A VTAM DB table must be previously created to start OpenFrame/OSC. If not, the following message will be displayed.

    OSCBOOT : vtam_appl_register_region() failed: rc(-109922), region(OSCOIVP1)

  • Resolution

    Check for the VTAM DB table creation.

    A VTAM DB table is created when running baseinit. For more information, refer to OpenFrame Tool Reference Guide.