A fix is available
APAR status
Closed as documentation error.
Error description
Problem description: We referred the section "Starting System Automation Application Manager automatically" of information center, and set as described. http://pic.dhe.ibm.com/infocenter/tivihelp/v48r1/index.jsp?topic =%2Fcom. ibm.sco.doc_2.3%2Fc_start_saam.html We created startup script in /etc/opt/IBM/tsamp/eez directory, chmod, and added entries to /etc/inittab. We ensured the default run level is 5. However, DB2, WAS, and SAAM (including agentless adapter) didn't start automatically when OS reboot. So, we copied the startup script to /etc/rc.d/init.d, and create a symbolic link to it under /etc/rc.d/rc$runlevel.d. This time, DB2, WAS, and SAAM (including agentless adapter) can start automatically when OS reboot. Can this workaround be supported ? Also, we wonder why the setting described in information center didn't work for us. . I got the following infromations about attachment files. - "startup" file The customer made "startup" script that contents were described about bolow at /etc/opt/IBM/tsamp/eez as root. ----- su db2inst1 -c /home/db2inst1/sqllib/adm/db2start sleep 10 /opt/IBM/WebSphere/AppServer/bin/startServer.sh server1 sleep 30 eezdmn start eezaladapter start ----- - "inittab" file The customer added the following line at the tail end of /etc/inittab. ----- # start of SA AM saam:5:wait:/etc/opt/IBM/tsamp/eez/startup ----- - "runlevel.txt" file This file is result that the customer executed "/sbin/runlevel". - "chkconfig--list.txt" file This file is result that the customer executed "/sbin/chkconfig --list". Note from L3 team: the configuratoin used by the customer is correct. They can, or better, they must stay with the configuration they have found. If you look into the inittab file, you will notice the following line: # ADDING OTHER CONFIGURATION HERE WILL HAVE NO EFFECT ON YOUR SYSTEM. In fact, with "modern" RHEL OS-es (like the 6.x), the correct way to proceed is exactly the way performed by the customer. I believe we need to fix the documentation, the procedure we provide could be valid for older RHEL versions (e.g. 5.x), but neither for RHEL 6.x nor the new coming RHEL versions (e.g. 7.x). Think of raising an APAR for doc.
Local fix
no workaround
Problem summary
**************************************************************** * USERS AFFECTED: All users of SmartCloud Orchestrator 2.3.0 **************************************************************** * PROBLEM DESCRIPTION: The online documentation (INFOCENTER) needs to be fixed regarding the section: Installing->High Availability->"Starting System Automation Application Manager automatically" **************************************************************** * RECOMMENDATION: Review the next update of SmartCloud Orchestrator 2.3 Installation Guide ('High Availability' section) when available. The documentation changes can also be found in the conclusion section below.
Problem conclusion
In the section of SmartCloud Orchestrator 2.3 Installation Guide ('High Availability' section) named 'Starting System Automation Application Manager automatically', the following annotation has been added: 'Note: This step in only valid for RHEL 5.x, but not for RHEL6.x and beyond. For these newer versions of RHEL, you must copy the startup script to /etc/rc.d/init.d, and create a symbolic link to it under /etc/rc.d/rc$runlevel.d.'
Temporary fix
Comments
APAR Information
APAR number
ZZ00209
Reported component name
SMRTCLOUD ORCHS
Reported component ID
5725H2800
Reported release
230
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-30
Closed date
2014-02-26
Last modified date
2014-02-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4KMC","label":"IBM Cloud Orchestrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
03 November 2021