Collector for AS400 stops after a while with an error.
search cancel

Collector for AS400 stops after a while with an error.

book

Article ID: 87086

calendar_today

Updated On:

Products

CA Automic Sysload

Issue/Introduction

Affects Release version(s): 5

Error Message :
On the collector log (sldrmd_log) these error messages may appear:

#########
 Tue Aug 27 12:40:01 2013: coll - (fnCreateShrHst) error shmget HISn (3457)
 Tue Aug 27 12:40:01 2013: coll - (fnCreateAndInitShrHst) error fnCreateShrHst
 Tue Aug 27 12:40:01 2013: coll - (fnMajMoyHISn) error fnCreateAndInitShrHst
 Tue Aug 27 12:40:01 2013: coll - (fnMajHist) error fnMajMoyHISn
 Tue Aug 27 12:40:01 2013: coll - fnMajHist failed
######### 

Patch level detected:Sysload Agent for OS/400
Product Version: Sysload 5.6.0

Description :Collector for AS400 stops after a while with an error.

Environment

OS: IBM AS/400
OS Version: all AS/400

Cause

Cause type:
Configuration
Root Cause: The IPCs of the collector (semaphore and shared memory) were not properly removed while stopping the collector.

Resolution

Stop all the jobs launched as SYSLOAD (collector and file-server)

Then remove the IPCs that remain on the system.

- With Iseries Navigator:
. Go to the concerned server.
. Go to Application development.
. Go to Task communications.
. Go to Shared memory.
. Go to List of IPCs.
. Delete the entries for which "SYSLOAD" is the owner.


- With OS/400 commands:
. List IPCs with "QP0ZIPCS".
. CALL QP0ZIPCS
. Delete IPCs with "QP0ZIPCR".
. IPCs of type Shared Memory: CALL QP0ZIPCR PARM("-M")
. IPCs of type Semaphore: CALL QP0ZIPCR PARM("-S")


EXAMPLE
List IPCs: CALL QP0ZIPCS
Result looks likes this:
IPC STATUS AS OF Tue Jun 10 15:43:30 2006
MESSAGE QUEUES:
T ID KEY MODE OWNER GROUP
SHARED MEMORY:
T ID KEY MODE OWNER GROUP
M 532 0X5800A8D3 --RW-RW-RW- SYSLOAD *NONE
Delete the IPC of type Shared Memory with ID 532: CALL QP0ZIPCR PARM("-M532")

Then restart the file server and the collector.

Fix Status: Released

Fix Version(s):
Component: Agents
Version: Sysload 5.6.0

Additional Information

Workaround :
N/A