ITEM: G4132L

Alert Manager not starting on production system.

Question:

I am trying to run alert manager from the command line using the following
command:  startam -p AMP &   (AMP is the Alert Manager profile name).
When I do this, I receive a "0513-059" message.

This has not been running on this system before, but I do have
it running on another system.  I copied the profile file from 
the other system to set this one up.  I believe the profile 
file (AMP) is correct.

Here is my AMP configurations in SMIT:

Type = Collection Point
Destination Node = BCBS.SNA    (this should match my Attachment Profile name
                                in SNA Services)
Nettype = SNA
SSCIPID = 050000001B5A          (this is a number I received the host folks
                                 and is converted to hex)
                                
Hold Alert while host in unlinked  and inactive = YES
Resend Alert when host becomes linked and active = YES

All others are defaults.

This is running on a production system, so I haven't been able to stop and then 
restart SNA Services.

Response:

Since you state that you are unable to start and restart SNA Services, I am
assuming that you are configuring the Alert Manager to use the existing (running)
SNA Services profiles on this new machine.  

Unless Alert Manager has been configured and running on this machine, the 
"nmvt_action_when_no_nmvt_process" parameter in the SNA Node profile is
still set to the default value of "reject".  This parameter needs to be changed
to "queue".

This parameter cannot be changed using smit.  SNA Services must be stopped and 
then the profiles exported.  A line editor can be used to change the
nmvt_action_when_no_nmvt_process parameter from "reject" to "queue".  Then import
the profiles and to restart SNA and the attachment.



Support Line: Alert Manager not starting on production system. ITEM: G4132L

Dated: February 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:50

Comments or suggestions?
Contact us