IBM i: Standalone installation of CCMS agent

[] [] [] [] [] [] [] [] [] []

  1. 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...
  2. 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...
  3. 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...
  4. 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...
  5. 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...
  6. IBM i:Expression operator not allowed for parameter INSTHOSTSymptom 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...
  7. 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...
  8. IBM i: IT4J: Xlp64k is not supported by some processorsSymptom After the conversion of your SAP NetWeaver system to IT4J using CONFIGJVM, the system no longer starts. The Java processes terminate, and the system issues the following message: JVMJ9GC032E System configuration...

Symptom

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 for the operating system IBM i if there is no full SAP kernel on the server or in the partition.

Other terms

AS/400, OS/400, OS400, iSeries, i5/OS, legacy monitoring

Reason and Prerequisites

As of Release 6.40, the CCMS agent runs in the PASE runtime environment. PASE stands for “Portable Application Solution Environment” and is provided as option 33 of the operating system. Parts of the agent access other PASE components and the service program O4PRTLIB, so you must set the environment variables and the library list correctly in order for the CCMS agent to function.
To unpack the CCMS agent, you require the tool SAPCAR that is described in SAP Note 863821. To set up the runtime environment correctly, you require the package SAPHOSTAGENT (that is described in SAP Note 10310960) and the enhancements from SAP Note 1299618 (Release 7.10: SAPHOSTAGENT.SAR level 32 or higher, Release 7.11: SAPHOSTAGENT.SAR level 9 or higher). The CCMS agent must be from the same release as the package SAPHOSTAGENT. However, the release is independent of the central monitoring system release.

Solution
1. Install the package SAPHOSTAGENT in accordance with the instructions attached to Note 1031096. The PASE version of SAPCAR is installed in accordance with Note 863821 as part of these instructions.2. Download the package SAPCCMSR<...>.SAR from SAP Service Marketplace into the directory /tmp/hostctrl, which you created when you installed the package SAPHOSTAGENT. If you have chosen a different directory name, change it according to the following commands.3. Log on as QSECOFR or a user with equivalent authorization.4. Start an interactive PASE terminal session with the command:
CALL PGM(QP2TERM)5. Switch to the directory that contains the package SAPCCMSR and the program SAPCAR:
cd /tmp/hostctrl6. Unpack the archive SAPCCMSR<...>.SAR with the command
./SAPCAR -xvf SAPCCMSR<...>.SAR7. Exit the interactive PASE terminal session by choosing F3.8. Copy the program SAPCCMSR into the run directory of SAPHOSTAGENT with the command:
CPY OBJ(’/tmp/hostctrl/SAPCCMSR’)
TOOBJ(’/usr/sap/hostctrl/exe/SAPCCMSR’)9. Create an executable program for the operating system IBM i by copying the program SAPOSCOL:
CRTDUPOBJ OBJ(SAPOSCOL) FROMLIB(R3SAP400)
OBJTYPE(*PGM) NEWOBJ(SAPCCMSR)

If you want to execute the agent in an interactive session (to register it with the central monitoring system, for example), you must enter the following commands (after logging on) to set up the runtime environment:
CALL PGM(R3SAP400/R3INLPGM)
ADDLIBLE LIB(R3SAP400)
The agent is called by the parameters that are described in the official documentation, for example, to display the version:
CALL PGM(SAPCCMSR) PARM(’-v’).
To register using a configuration file, use the following command syntax:
CALL PGM(SAPCCMSR)
PARM(’-R’ ‘-f’ ‘/usr/sap/tmp/sapccmsr/csmconf’)

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment