Highlighted
Anonymous_User Absent Member.
Absent Member.
3398 views

messenger load script

Hopefully my final question on load scripts:

I want to start my messenger agent and archive agent with the single command nmstart.ncf. This is located on my resource volume (bkpdomvl) in system folder.

According to the documentation, i can start both these agents by typing this in my load script

bkpdomvl:\system\nmstart.ncf

but it does nothing. Works from the server console though.

Thanks
Stacie
Labels (1)
0 Likes
11 Replies
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

p.s. the unload scripts do not work either - leaves messenger running.

i have "unload nmma.nlm", and "unload nmaa.nlm" in the unload script
"Stacie White" <stacie.white@arvig.com> wrote in message news:GCAkj.22191$k06.965@kovat.provo.novell.com...
Hopefully my final question on load scripts:

I want to start my messenger agent and archive agent with the single command nmstart.ncf. This is located on my resource volume (bkpdomvl) in system folder.

According to the documentation, i can start both these agents by typing this in my load script

bkpdomvl:\system\nmstart.ncf

but it does nothing. Works from the server console though.

Thanks
Stacie
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

What is the exact load script?

What if you simply put in nmstart.ncf file in the load script, without
bkpdomvl:\system?

(Also, try copying the file to sys:system of all the cluster nodes?)

Craig Johnson
Novell Support Connection SysOp

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

Thanks Craig
My agents aren't installed to the node - i suppose this doesnt matter since
the ncf will call it from the resource volume? I can try nmstart.ncf with no
path.

here is my load script ( i never figured out what secondary ip address meant
but it works for now):

nss /poolactivate=BKPDOMPL
mount BKPDOMVL VOLID=253
CLUSTER CVSBIND ADD BKPDOMVS_SERVER 192.168.148.222
NUDP ADD BKPDOMVS_SERVER 192.168.148.222
add secondary ipaddress 192.168.148.222

load address space=bkmta SYS:\SYSTEM\GWMTA @BKP_DOM.MTA
load delay
delay 10
protection restart bkmta

load address space=gwia SYS:\system\gwia @gwia.cfg
protection restart gwia


load address space=webac SYS:\system\gwinter @WEBAC70A.waa
protection restart webac

bkpdomvl:\system\nmstart.ncf
unload delay

_________________
and here is my unload

unload address space=gwia
delay 10
unload kill address space=gwia

unload address space=bkmta
delay 10
unload kill address space=bkmta

unload nmma.nlm
unload nmaa.nlm

delay 10
del secondary ipaddress 192.168.148.222
NUDP DEL BKPDOMVS_SERVER 192.168.148.222
CLUSTER CVSBIND DEL BKPDOMVS_SERVER 192.168.148.222
nss /pooldeactivate=BKPDOMPL /override=question

unload delay



"Craig Johnson" <craigsj@ix.netcom.com> wrote in message
news:VA.00003d3b.01e8a1d8@ix.netcom.com...
> What is the exact load script?
>
> What if you simply put in nmstart.ncf file in the load script, without
> bkpdomvl:\system?
>
> (Also, try copying the file to sys:system of all the cluster nodes?)
>
> Craig Johnson
> Novell Support Connection SysOp
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

Stacie,

Your issue is simple.

You need to copy a certain file to the sys:\system directory on all cluster
nodes for IM to load properly. File is: QFind217.NLM. Otherwise IM will
not load from a cluster resource.

Go to: http://www.novell.com/coolsolutions/feature/18889.html --at the
bottom.
--

Take Care.

Gregg A. Hinchman
Consultant
Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )

A Novell Consulting Partner
317.329.0288 Office
413.254.2819 eFax

"Courage is doing what is right."

"Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
All systems of thought are guiding means, not absolute truth." Thich Nhat
Hanh, Vietnamese monk.



>>> On 1/20/2008 at 3:55 PM, in message

<QyOkj.22501$k06.720@kovat.provo.novell.com>, Stacie
White<stacie.white@arvig.com> wrote:
> Thanks Craig
> My agents aren't installed to the node - i suppose this doesnt matter
> since
> the ncf will call it from the resource volume? I can try nmstart.ncf
> with no
> path.
>
> here is my load script ( i never figured out what secondary ip address
> meant
> but it works for now):
>
> nss /poolactivate=BKPDOMPL
> mount BKPDOMVL VOLID=253
> CLUSTER CVSBIND ADD BKPDOMVS_SERVER 192.168.148.222
> NUDP ADD BKPDOMVS_SERVER 192.168.148.222
> add secondary ipaddress 192.168.148.222
>
> load address space=bkmta SYS:\SYSTEM\GWMTA @BKP_DOM.MTA
> load delay
> delay 10
> protection restart bkmta
>
> load address space=gwia SYS:\system\gwia @gwia.cfg
> protection restart gwia
>
>
> load address space=webac SYS:\system\gwinter @WEBAC70A.waa
> protection restart webac
>
> bkpdomvl:\system\nmstart.ncf
> unload delay
>
> _________________
> and here is my unload
>
> unload address space=gwia
> delay 10
> unload kill address space=gwia
>
> unload address space=bkmta
> delay 10
> unload kill address space=bkmta
>
> unload nmma.nlm
> unload nmaa.nlm
>
> delay 10
> del secondary ipaddress 192.168.148.222
> NUDP DEL BKPDOMVS_SERVER 192.168.148.222
> CLUSTER CVSBIND DEL BKPDOMVS_SERVER 192.168.148.222
> nss /pooldeactivate=BKPDOMPL /override=question
>
> unload delay
>
>
>
> "Craig Johnson" <craigsj@ix.netcom.com> wrote in message
> news:VA.00003d3b.01e8a1d8@ix.netcom.com...
>> What is the exact load script?
>>
>> What if you simply put in nmstart.ncf file in the load script, without
>> bkpdomvl:\system?
>>
>> (Also, try copying the file to sys:system of all the cluster nodes?)
>>
>> Craig Johnson
>> Novell Support Connection SysOp
>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

Ahhh, ok. I copied to my system folder on my cluster resource....

I think it might be a case of wrong documentation in the interoperatbility
guide again...Here is what it said:

From the node where the Messenger volume was mounted during installation,
copy the following files to the cluster volume:

Table 11-2 LDAP and QuickFinder Files to Copy

Copy From:
Copy To:

sys:\system\ldapsdk.nlm
clustervol:\system\ma

sys:\system\ldapssl.nlm
clustervol:\system\ma

sys:\system\ldapx.nlm
clustervol:\system\ma

sys:\system\qfind217.nlm
clustervol:\system\aa



Thanks Greg.

"Gregg A. Hinchman" <gregg@hinchmanconsulting.com> wrote in message
news:4794A3A4.FDA7.003C.3@hinchmanconsulting.com...
> Stacie,
>
> Your issue is simple.
>
> You need to copy a certain file to the sys:\system directory on all
> cluster
> nodes for IM to load properly. File is: QFind217.NLM. Otherwise IM will
> not load from a cluster resource.
>
> Go to: http://www.novell.com/coolsolutions/feature/18889.html --at the
> bottom.
> --
>
> Take Care.
>
> Gregg A. Hinchman
> Consultant
> Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )
>
> A Novell Consulting Partner
> 317.329.0288 Office
> 413.254.2819 eFax
>
> "Courage is doing what is right."
>
> "Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
> All systems of thought are guiding means, not absolute truth." Thich Nhat
> Hanh, Vietnamese monk.
>
>
>
>>>> On 1/20/2008 at 3:55 PM, in message

> <QyOkj.22501$k06.720@kovat.provo.novell.com>, Stacie
> White<stacie.white@arvig.com> wrote:
>> Thanks Craig
>> My agents aren't installed to the node - i suppose this doesnt matter
>> since
>> the ncf will call it from the resource volume? I can try nmstart.ncf
>> with no
>> path.
>>
>> here is my load script ( i never figured out what secondary ip address
>> meant
>> but it works for now):
>>
>> nss /poolactivate=BKPDOMPL
>> mount BKPDOMVL VOLID=253
>> CLUSTER CVSBIND ADD BKPDOMVS_SERVER 192.168.148.222
>> NUDP ADD BKPDOMVS_SERVER 192.168.148.222
>> add secondary ipaddress 192.168.148.222
>>
>> load address space=bkmta SYS:\SYSTEM\GWMTA @BKP_DOM.MTA
>> load delay
>> delay 10
>> protection restart bkmta
>>
>> load address space=gwia SYS:\system\gwia @gwia.cfg
>> protection restart gwia
>>
>>
>> load address space=webac SYS:\system\gwinter @WEBAC70A.waa
>> protection restart webac
>>
>> bkpdomvl:\system\nmstart.ncf
>> unload delay
>>
>> _________________
>> and here is my unload
>>
>> unload address space=gwia
>> delay 10
>> unload kill address space=gwia
>>
>> unload address space=bkmta
>> delay 10
>> unload kill address space=bkmta
>>
>> unload nmma.nlm
>> unload nmaa.nlm
>>
>> delay 10
>> del secondary ipaddress 192.168.148.222
>> NUDP DEL BKPDOMVS_SERVER 192.168.148.222
>> CLUSTER CVSBIND DEL BKPDOMVS_SERVER 192.168.148.222
>> nss /pooldeactivate=BKPDOMPL /override=question
>>
>> unload delay
>>
>>
>>
>> "Craig Johnson" <craigsj@ix.netcom.com> wrote in message
>> news:VA.00003d3b.01e8a1d8@ix.netcom.com...
>>> What is the exact load script?
>>>
>>> What if you simply put in nmstart.ncf file in the load script, without
>>> bkpdomvl:\system?
>>>
>>> (Also, try copying the file to sys:system of all the cluster nodes?)
>>>
>>> Craig Johnson
>>> Novell Support Connection SysOp
>>>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

In article <P76lj.22985$k06.498@kovat.provo.novell.com>, Stacie White
wrote:
> Ahhh, ok. I copied to my system folder on my cluster resource....
>

Did Greg's answer work?

What I was thinking of was simply to run the startup file from the
node, rather than the cluster (virtual server). Not as elegant, and
you have to have copies on each node in the cluster, but sometimes the
brute force method works fine and saves time.

Craig Johnson
Novell Support Connection SysOp

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

I haven't restarted the agents yet - will do that tonite after i apply
service pack 3 because of the random disconnect issue. And in the process I
will test the failover. I discovered that I did have those files copied to
the nodes and to the cluster volume before gregg's message - except for the
Qfind217 was not located on node 2. So that might have been the holdup.

If it fails, will try the startup file on the node. I am guessing then I
would modify my load script accordingly... I'll post back tomorrow.


"Craig Johnson" <craigsj@ix.netcom.com> wrote in message
news:VA.00003d3d.06a8ddec@ix.netcom.com...
> In article <P76lj.22985$k06.498@kovat.provo.novell.com>, Stacie White
> wrote:
>> Ahhh, ok. I copied to my system folder on my cluster resource....
>>

> Did Greg's answer work?
>
> What I was thinking of was simply to run the startup file from the
> node, rather than the cluster (virtual server). Not as elegant, and
> you have to have copies on each node in the cluster, but sometimes the
> brute force method works fine and saves time.
>
> Craig Johnson
> Novell Support Connection SysOp
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

Yeah you can actually run all NLMS for Messenger from the Cluster resource
-start it/stop it/etc. But you MUST have just that 1 Q217 NLM on the
sys:\system directory to make it work -that is the ONLY one. A quirk for
sure.
--

Take Care.

Gregg A. Hinchman
Consultant
Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )

A Novell Consulting Partner
317.329.0288 Office
413.254.2819 eFax

"Courage is doing what is right."

"Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
All systems of thought are guiding means, not absolute truth." Thich Nhat
Hanh, Vietnamese monk.



>>> On 1/22/2008 at 5:13 PM, in message

<AUtlj.23723$k06.6986@kovat.provo.novell.com>, Stacie
White<stacie.white@arvig.com> wrote:
> I haven't restarted the agents yet - will do that tonite after i apply
> service pack 3 because of the random disconnect issue. And in the
> process I
> will test the failover. I discovered that I did have those files copied
> to
> the nodes and to the cluster volume before gregg's message - except for
> the
> Qfind217 was not located on node 2. So that might have been the holdup.
>
> If it fails, will try the startup file on the node. I am guessing then I
>
> would modify my load script accordingly... I'll post back tomorrow.
>
>
> "Craig Johnson" <craigsj@ix.netcom.com> wrote in message
> news:VA.00003d3d.06a8ddec@ix.netcom.com...
>> In article <P76lj.22985$k06.498@kovat.provo.novell.com>, Stacie White
>> wrote:
>>> Ahhh, ok. I copied to my system folder on my cluster resource....
>>>

>> Did Greg's answer work?
>>
>> What I was thinking of was simply to run the startup file from the
>> node, rather than the cluster (virtual server). Not as elegant, and
>> you have to have copies on each node in the cluster, but sometimes the
>> brute force method works fine and saves time.
>>
>> Craig Johnson
>> Novell Support Connection SysOp
>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

Ok - then I still have something up with the load/unload scripts. That file
is copied to sys:system, but no go on failover.

Then again, my one mta (load in protected memory) also sometimes unloads
with the wrong resource or doesn't load at all during a failover. I think
based on discussions here and documentation that I have the scripts
correctly configured... maybe its something else?


"Gregg A. Hinchman" <gregg@hinchmanconsulting.com> wrote in message
news:47986BF4.FDA7.003C.3@hinchmanconsulting.com...
> Yeah you can actually run all NLMS for Messenger from the Cluster resource
> -start it/stop it/etc. But you MUST have just that 1 Q217 NLM on the
> sys:\system directory to make it work -that is the ONLY one. A quirk for
> sure.
> --
>
> Take Care.
>
> Gregg A. Hinchman
> Consultant
> Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )
>
> A Novell Consulting Partner
> 317.329.0288 Office
> 413.254.2819 eFax
>
> "Courage is doing what is right."
>
> "Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
> All systems of thought are guiding means, not absolute truth." Thich Nhat
> Hanh, Vietnamese monk.
>
>
>
>>>> On 1/22/2008 at 5:13 PM, in message

> <AUtlj.23723$k06.6986@kovat.provo.novell.com>, Stacie
> White<stacie.white@arvig.com> wrote:
>> I haven't restarted the agents yet - will do that tonite after i apply
>> service pack 3 because of the random disconnect issue. And in the
>> process I
>> will test the failover. I discovered that I did have those files copied
>> to
>> the nodes and to the cluster volume before gregg's message - except for
>> the
>> Qfind217 was not located on node 2. So that might have been the holdup.
>>
>> If it fails, will try the startup file on the node. I am guessing then I
>>
>> would modify my load script accordingly... I'll post back tomorrow.
>>
>>
>> "Craig Johnson" <craigsj@ix.netcom.com> wrote in message
>> news:VA.00003d3d.06a8ddec@ix.netcom.com...
>>> In article <P76lj.22985$k06.498@kovat.provo.novell.com>, Stacie White
>>> wrote:
>>>> Ahhh, ok. I copied to my system folder on my cluster resource....
>>>>
>>> Did Greg's answer work?
>>>
>>> What I was thinking of was simply to run the startup file from the
>>> node, rather than the cluster (virtual server). Not as elegant, and
>>> you have to have copies on each node in the cluster, but sometimes the
>>> brute force method works fine and saves time.
>>>
>>> Craig Johnson
>>> Novell Support Connection SysOp
>>>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

Maybe a strectch ---do you have SLP and HOST file filled out with all
cluster nodes and cluster resources properly.
--

Take Care.

Gregg A. Hinchman
Consultant
Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )

A Novell Consulting Partner
317.329.0288 Office
413.254.2819 eFax

"Courage is doing what is right."

"Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
All systems of thought are guiding means, not absolute truth." Thich Nhat
Hanh, Vietnamese monk.



>>> On 1/24/2008 at 3:08 PM, in message

<Ne6mj.24700$k06.6022@kovat.provo.novell.com>, Stacie
White<stacie.white@arvig.com> wrote:
> Ok - then I still have something up with the load/unload scripts. That
> file
> is copied to sys:system, but no go on failover.
>
> Then again, my one mta (load in protected memory) also sometimes unloads
>
> with the wrong resource or doesn't load at all during a failover. I
> think
> based on discussions here and documentation that I have the scripts
> correctly configured... maybe its something else?
>
>
> "Gregg A. Hinchman" <gregg@hinchmanconsulting.com> wrote in message
> news:47986BF4.FDA7.003C.3@hinchmanconsulting.com...
>> Yeah you can actually run all NLMS for Messenger from the Cluster

> resource
>> -start it/stop it/etc. But you MUST have just that 1 Q217 NLM on the
>> sys:\system directory to make it work -that is the ONLY one. A quirk

for
>> sure.
>> --
>>
>> Take Care.
>>
>> Gregg A. Hinchman
>> Consultant
>> Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )
>>
>> A Novell Consulting Partner
>> 317.329.0288 Office
>> 413.254.2819 eFax
>>
>> "Courage is doing what is right."
>>
>> "Do not be bound to any doctrine, theory or ideology, even Buddhist

> ones.
>> All systems of thought are guiding means, not absolute truth." Thich

> Nhat
>> Hanh, Vietnamese monk.
>>
>>
>>
>>>>> On 1/22/2008 at 5:13 PM, in message

>> <AUtlj.23723$k06.6986@kovat.provo.novell.com>, Stacie
>> White<stacie.white@arvig.com> wrote:
>>> I haven't restarted the agents yet - will do that tonite after i apply
>>> service pack 3 because of the random disconnect issue. And in the
>>> process I
>>> will test the failover. I discovered that I did have those files copied
>>> to
>>> the nodes and to the cluster volume before gregg's message - except for
>>> the
>>> Qfind217 was not located on node 2. So that might have been the holdup.
>>>
>>> If it fails, will try the startup file on the node. I am guessing then

I
>>>
>>> would modify my load script accordingly... I'll post back tomorrow.
>>>
>>>
>>> "Craig Johnson" <craigsj@ix.netcom.com> wrote in message
>>> news:VA.00003d3d.06a8ddec@ix.netcom.com...
>>>> In article <P76lj.22985$k06.498@kovat.provo.novell.com>, Stacie White
>>>> wrote:
>>>>> Ahhh, ok. I copied to my system folder on my cluster resource....
>>>>>
>>>> Did Greg's answer work?
>>>>
>>>> What I was thinking of was simply to run the startup file from the
>>>> node, rather than the cluster (virtual server). Not as elegant, and
>>>> you have to have copies on each node in the cluster, but sometimes the
>>>> brute force method works fine and saves time.
>>>>
>>>> Craig Johnson
>>>> Novell Support Connection SysOp
>>>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: messenger load script

No, I don't think I do... I will check it.

"Gregg A. Hinchman" <gregg@hinchmanconsulting.com> wrote in message
news:4798EE6F.FDA7.003C.3@hinchmanconsulting.com...
> Maybe a strectch ---do you have SLP and HOST file filled out with all
> cluster nodes and cluster resources properly.
> --
>
> Take Care.
>
> Gregg A. Hinchman
> Consultant
> Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )
>
> A Novell Consulting Partner
> 317.329.0288 Office
> 413.254.2819 eFax
>
> "Courage is doing what is right."
>
> "Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
> All systems of thought are guiding means, not absolute truth." Thich Nhat
> Hanh, Vietnamese monk.
>
>
>
>>>> On 1/24/2008 at 3:08 PM, in message

> <Ne6mj.24700$k06.6022@kovat.provo.novell.com>, Stacie
> White<stacie.white@arvig.com> wrote:
>> Ok - then I still have something up with the load/unload scripts. That
>> file
>> is copied to sys:system, but no go on failover.
>>
>> Then again, my one mta (load in protected memory) also sometimes unloads
>>
>> with the wrong resource or doesn't load at all during a failover. I
>> think
>> based on discussions here and documentation that I have the scripts
>> correctly configured... maybe its something else?
>>
>>
>> "Gregg A. Hinchman" <gregg@hinchmanconsulting.com> wrote in message
>> news:47986BF4.FDA7.003C.3@hinchmanconsulting.com...
>>> Yeah you can actually run all NLMS for Messenger from the Cluster

>> resource
>>> -start it/stop it/etc. But you MUST have just that 1 Q217 NLM on the
>>> sys:\system directory to make it work -that is the ONLY one. A quirk

> for
>>> sure.
>>> --
>>>
>>> Take Care.
>>>
>>> Gregg A. Hinchman
>>> Consultant
>>> Gregg@HinchmanConsulting.com ( mailto:Gregg@HinchmanConsulting.com )
>>>
>>> A Novell Consulting Partner
>>> 317.329.0288 Office
>>> 413.254.2819 eFax
>>>
>>> "Courage is doing what is right."
>>>
>>> "Do not be bound to any doctrine, theory or ideology, even Buddhist

>> ones.
>>> All systems of thought are guiding means, not absolute truth." Thich

>> Nhat
>>> Hanh, Vietnamese monk.
>>>
>>>
>>>
>>>>>> On 1/22/2008 at 5:13 PM, in message
>>> <AUtlj.23723$k06.6986@kovat.provo.novell.com>, Stacie
>>> White<stacie.white@arvig.com> wrote:
>>>> I haven't restarted the agents yet - will do that tonite after i apply
>>>> service pack 3 because of the random disconnect issue. And in the
>>>> process I
>>>> will test the failover. I discovered that I did have those files copied
>>>> to
>>>> the nodes and to the cluster volume before gregg's message - except for
>>>> the
>>>> Qfind217 was not located on node 2. So that might have been the holdup.
>>>>
>>>> If it fails, will try the startup file on the node. I am guessing then

> I
>>>>
>>>> would modify my load script accordingly... I'll post back tomorrow.
>>>>
>>>>
>>>> "Craig Johnson" <craigsj@ix.netcom.com> wrote in message
>>>> news:VA.00003d3d.06a8ddec@ix.netcom.com...
>>>>> In article <P76lj.22985$k06.498@kovat.provo.novell.com>, Stacie White
>>>>> wrote:
>>>>>> Ahhh, ok. I copied to my system folder on my cluster resource....
>>>>>>
>>>>> Did Greg's answer work?
>>>>>
>>>>> What I was thinking of was simply to run the startup file from the
>>>>> node, rather than the cluster (virtual server). Not as elegant, and
>>>>> you have to have copies on each node in the cluster, but sometimes the
>>>>> brute force method works fine and saves time.
>>>>>
>>>>> Craig Johnson
>>>>> Novell Support Connection SysOp
>>>>>



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.