RE: Notification Process

[rob@xxxxxxxxx]

http://www.bytware.com/
http://www.lxicorp.com/prod06.htm

Robot's pretty robust, but I've heard it's expensive.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Dwayne Allison" <Dwayne.Allison@xxxxxxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/17/2005 09:00 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Notification Process






Do you have a web site or a contact person for LXI and Byteware?  At my 
old company we had a product called ROBOT that worked good, but I don't 
know the company name that goes with it.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
Sent: Friday, May 13, 2005 9:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: Notification Process


Can you send emails directly from your 400 to the service for the cell 
phones and pagers using SNDDST, QTmmSendMail api, Dave Leland's freebie 
SNDEMAIL etc?  This will bypass the Exchange server issues.

Some say that a modem dial up into a paging service for backup purposes is 

a good idea in case you get errors on your 400 that shut down smtp (like 
disk threshold, lan line failures, etc).  Some services are dropping this 
backup method.

A robust 400 paging package might be able to do escalations.
- Page someone
- If error is still there x number of minutes later, then page someone 
else.
- If error is still there later then call someone etc.

We use software by LXI.  However, when they got into a finger pointing 
contest with Arch they really torked me off.

I've heard good things about Byteware.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Dwayne Allison" <Dwayne.Allison@xxxxxxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/13/2005 08:23 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion \(E-mail\)" 
<midrange-l@xxxxxxxxxxxx>
cc

Subject
Notification Process






We currently use a convoluted method in which a backup/cycle error is sent 

from the AS400 through our Exchange environment which is then passed to 
the technicians cell phone/pager. If our cell phone or pager vendor has an 

outage, the technician does not get an error notification - as well if we 
are performing after-hours/weekend maintenance on Exchange the 
notification gets queued which causes a notification delay. So, we are 
looking at AS400 tools that will eliminate a couple of steps in the 
notification process.

Anyone got ideas?


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.