Basis Errors and Solutions

IBM i:Expression operator not allowed for parameter INSTHOST

July 22, 2009 at 9:35 am

[.. is not allowed] [405 not allowed] [AS/400] [CRTR3INST] [i5] [install] [iSeries] [method not allowed] [not allowed] [OS400] [SAPinst] [SCS]

Fallback Codepage 1160 not allowed.Symptom You execute transaction SPUMG to prepare a system for a Unicode conversionThe system is configured as Single Codepage SystemOn the first screen in SPUMG you checked on an option to replace...
IBM i: Java error in host names with hyphensSymptom You execute an upgrade or an installation for a Java stack. Various SAP commands (for example, STARTSAP, STOPSAP) require the host name of your IBM i as a parameter. Other terms...
IBM i: Standalone installation of CCMS agentSymptom You use the CCMS agent SAPCCMSR to transfer data about the system status from a server to a central monitoring system. This note describes how you can install the CCMS agent...
IBM i: Error when starting a remote instanceSymptom If you want to stop a remote instance from the central instance host, the command STOPSAP has no effect. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and Prerequisites This...
IBM i: Checking already completed child processesSymptom Terminating an SAP system takes longer than usual. Sometimes only the job SAPSTART is active in the subsystem without being terminated. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and...
IBM i: Overwriting when determining communication dataSymptom SAPOSCOL ends due to a termination, and MCH3601 is displayed in the function AiUpCall in the job log. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and Prerequisites When determining...
IBM i: Missing replacement of R3INLPGM in R3400Symptom When you apply a patch, the program R3INLPGM in the library R3400 should be replaced automatically. However, this does not occur. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and...
IBM i: Changing a table with an Encoded Vector Index (EVI)Symptom Changing a table for which there is an Encoded Vector Index (EVI) fails, for example, when you include a dimension in an InfoCube. Apart from the following information in the developer...

Symptom

Installation fails in step createInstanceOS4 due to problem with command CRTR3INST when using a hostname containing special characters.

Other terms

OS/400, AS/400, install, SAPinst, AS/400, iSeries, SCS, i5, CRTR3INST
Reason and Prerequisites

Installation tools need to use single quotes around CRTR3INST command input parameter INSTHOST. Not using quotes causes a failure when the hostname of the system contains special characters. (i.e. ‘my-hostname’)

Solution

When running into this problem while running SAPinst the solution will be using ” around host name or use *LOCAL.
To solve this problem, select to stop SAPinst. Go to the installation directory, open and edit file control.xml as follows:
1) Find the following codeline using the editor’s find/search function:
os4_executeCommandLib(”CRTR3INST SID(” + sid + “) INST(” + instno + “) ROLE(” + instrole + “) INSTHOST(” +installer.getHostName()+ “)” …
2) Replace with the following (add single quotes for INSTHOST):
os4_executeCommandLib(”CRTR3INST SID(” + sid + “) INST(” + instno + “) ROLE(” + instrole + “) INSTHOST(’” +installer.getHostName()+ “‘)” …
3) Restart SAPinst and continue with the failed installation. The routine will now correctly create the system instance and the installation will continue.