Best IT books part 1

Here some of the best IT book out there :

SAP books

The Complete Guide to SAP NetWeaver Portal

SAP Administration - Practical Guide

SAP Solution Manager (3rd Edition)

Oracle

OCA/OCP Oracle Database 11g All-in-One Exam Guide with CD-ROM

Oracle Essentials: Oracle Database 11g

Oracle PL/SQL Programming: Covers Versions Through Oracle Database 11g Release 2

BAPI returned: EXM237 Receiver object could not be created

 

Last week some SAP jobs returned this error :

 Error message: - BAPI (BAPI_XBP_JOB_CLOSE) FAILED. BAPI returned: EXM237 Receiver object could not be created Error code: 237

 This error comes from a wrong "spool list recipient"

Go to SAP tab on Control-M and click on it

 

 ok, now delete all entry here :

  
 Done !

Ps: now say their (SAP boys) not to make mistakes. ^^

CONTROL-M/Agents and remote hosts

In earlier releases of CONTROL-M/Server, each computer on which you planned to
run jobs required installation of a CONTROL-M/Agent. Beginning with version
6.3.01, CONTROL-M/Server supports agentless job submission. This method enables
submitting and executing jobs on computers that do not have a resident

CONTROL-M/Agent installed. These agentless computers are referred to as remote
hosts.
Although remote host computers do not require a resident CONTROL-M/Agent,
remote hosts come under the control of CONTROL-M/Agents on other computers, as
follows:

■ When you install CONTROL-M/Server in UNIX, a CONTROL-M/Agent is
   automatically installed on the same account. When you install
  CONTROL-M/Server in Windows, a CONTROL-M/Agent is automatically
 installed on the same computer, unless one already exists or you are performing a
cluster install. This automatically installed CONTROL-M/Agent is known as the
<Local> agent and is, by default, the agent that is used to connect to remote hosts.

■ You can place remote hosts under the control of any other CONTROL-M/Agents
   installed on computers under the same CONTROL-M/Server.
You will need to define the following information for each remote host:

■ host communication settings
You can define specific settings for a host, or use the default settings. For more
information, see “Configuring and managing remote hosts”

■ owner authentication settings
These settings specify the owners of the jobs that are running on the remote host,
and owner authentication parameters that are used for connecting to the remote
host. In a CONTROL-M job that is destined to be run on a remote host, you must
define each job owner that is specified.

Manually starting and stopping CONTROL-M/EM infrastructure processes using the interactive Activation menu

Using Root Menu

1 Display the CONTROL-M/EM Root Menu (root_menu)

2 In the CONTROL-M/EM Root menu, enter the number for the Activation Menu

option.

3 In the Activation menu, enter the number of the appropriate start or stop process

option (or start all or stop all option).

4 Enter q to exit.

You can manually shutdown and startup infrastructure components using the

following methods:

 - CONTROL-M Configuration Manager (to shut down CONTROL-M/Server)

 - CONTROL-M Manager Menu, which you access from the CONTROL-M Main

   Menu (ctm_menu)

 - supplied utilities

Using CONTROL-M Configuration Manager to shut down or start up CONTROL-M/Server

1 In the CONTROL-M Configuration Manager, right-click the

CONTROL-M/Server.

2 Choose Desired State and then choose one of the following submenu options:

Up—bring the component up

Down—bring the component down

Using CONTROL-M Manager Menu to shut down or start up CONTROL-M/Server infrastructure components

1 Display the CONTROL-M Main menu (ctm_menu). For instructions on displaying

the Main menu, see “Using the CONTROL-M/Server Main Menu” on page 47.

2 In the CONTROL-M Main menu, enter the number of the CONTROL-M Manager

option.

3 In the CONTROL-M Manager menu, enter the number corresponding to the

component activity you want to perform.

4 When done, enter q.

Using pre-supplied utilities to shut down or start up CONTROL-M/Server infrastructure components

To shut down CONTROL-M/Server entities

1 Log on as the CONTROL-M/Server account owner.

2 Enter one of the following commands as appropriate:

To stop the SQL database server, specify the command: shutdb

To stop the CONTROL-M/Server Configuration Agent: shut_ca

To stop the CONTROL-M/Server, specify the command: shut_ctm

To start CONTROL-M/Server entities

1 Log on as the CONTROL-M/Server account owner.

2 Enter one of the following commands as appropriate:

To start the SQL server, specify the command: startdb

To start the CONTROL-M/Server Configuration Agent: start_ca

To start the CONTROL-M/Server, specify the command: start_ctm

Starting and stopping infrastructure processes in Windows

On Windows, all CONTROL-M/EM, CONTROL-M/Server, and
CONTROL-M/Agent processes are defined as services.

By default, they are automatically started when you bring Windows up, and they are automatically
stopped when you bring Windows down.

Therefore, it is normally not necessary for you to perform startup or shutdown of
these processes. However, you can bring these services down or up whenever useful.

To stop CONTROL-M/EM, CONTROL-M/Server, or CONTROL-M/Agent services in Windows

1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the service, and choose Stop.

To start CONTROL-M/EM, CONTROL-M/Server, or CONTROL-M/Agent services in Windows

1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the service, and choose Start.

CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M Agent Infrastructure processes

CONTROL-M/EM processes

CONTROL-M/EM provides the following processes:

Naming Service: TAO NT Naming Service

CONTROL-M/EM processes:
— CONTROL-M Configuration Management Server (CMS)
— CONTROL-M Web Server
— CONTROL-M/Enterprise Manager Configuration Agent

CONTROL-M/Server processes

CONTROL-M/Server provides the following processes:

ctmsrv_service (Windows only, where it runs as a service)
p_ctmsu (Unix only)
p_ctmrt
p_ctmsl
p_ctmtr
p_ctmcd
p_ctmcs
p_ctmlg
p_ctmwd
p_ctmco
p_ctmns
p_ctmca (Unix only; Known as CONTROL-M/Server Configuration Agent)
ctmsca_service (Windows only, where it runs as a service; Known as
CONTROL-M/Server Configuration Agent)

CONTROL-M/Agent processes

CONTROL-M/Agent provides the following processes:


p_ctmar
p_ctmag (Known as CONTROL-M/Agent Listener, which on Windows runs as a
service).
p_ctmat (Known as CONTROL-M/Agent Tracker)
ctmfw_service (Windows only, where it runs as a service; Known as CONTROL-M
File Watcher)
CONTROL-M/Agent (on Unix and Windows it runs as a service)
CONTROL-M FileWatcher (Windows only, where it runs as a service)