On Jan 23, 10:02*pm, Jonathan Ball wrote:
> We've had IBM Director (v5.10) running on our iSeries
> partitions for something over a year. *We have the
> Director Server running on one partition, and Director
> Agent on the others (Agent is incorporated into the
> Server for that one partition.) *On all of them, I set
> up i5/OS message queue "action plan" events to monitor
> some queues for messages and relay them to the sysadmin
> staff in e-mail, or for some critical messages, to send
> a text message to cell phones. *It worked great, until
> it stopped working entirely a couple of weeks ago. *I
> can't figure out why it's not working. *I've verified
> that all the action plans are still in place, and
> configured to run on all the partitions.
>
> I thought it might have something to do with the SMTP
> server, or perhaps MSF, but that's not it. *I know this
> because I have some threshold action plans that also
> send e-mails, and these are continuing to appear as
> before, from more than one of the partitions (including
> the partition running Director Server.)
>
> Does anyone out there in c.s.i.a.m. have any experience
> with Director, and specifically with this kind of problem?

Jonathan, when you say stopped working, just the email part or?? Does
the email use the smtp to send out etc. If it does see if you can
ping the email server from the I5, if you cannot then I would say
there is the breakpoint.

On Jan 24, 3:55*am, jacko wrote:
> On Jan 23, 10:02*pm, Jonathan Ball wrote:
>
>
>
>
>
> > We've had IBM Director (v5.10) running on our iSeries
> > partitions for something over a year. *We have the
> > Director Server running on one partition, and Director
> > Agent on the others (Agent is incorporated into the
> > Server for that one partition.) *On all of them, I set
> > up i5/OS message queue "action plan" events to monitor
> > some queues for messages and relay them to the sysadmin
> > staff in e-mail, or for some critical messages, to send
> > a text message to cell phones. *It worked great, until
> > it stopped working entirely a couple of weeks ago. *I
> > can't figure out why it's not working. *I've verified
> > that all the action plans are still in place, and
> > configured to run on all the partitions.
>
> > I thought it might have something to do with the SMTP
> > server, or perhaps MSF, but that's not it. *I know this
> > because I have some threshold action plans that also
> > send e-mails, and these are continuing to appear as
> > before, from more than one of the partitions (including
> > the partition running Director Server.)
>
> > Does anyone out there in c.s.i.a.m. have any experience
> > with Director, and specifically with this kind of problem?
>
> Jonathan, when you say stopped working, just the email part or?? *Does
> the email use the smtp to send out etc. *If it does see if you can
> ping the email server from the I5, if you cannot then I would say
> there is the breakpoint.

What stopped working are the actions tied to event filters that are
part of action plans. Specifically, I configured several event
filters to monitor standard i5/OS message queues, and to relay the
messages that arrive at the queues to various users as e-mail. I also
set up another filter to monitor Director events, such as when someone
signs on to Director Console or a console sign-on fails. These events
also send an e-mail. The Director events are successfully sending an
e-mail, but the message queue events are not. The e-mail "action" is
the same, so I know the SMTP router is working.

Jonathan Ball wrote:
> We've had IBM Director (v5.10) running on our iSeries partitions for
> something over a year. We have the Director Server running on one
> partition, and Director Agent on the others (Agent is incorporated into
> the Server for that one partition.) On all of them, I set up i5/OS
> message queue "action plan" events to monitor some queues for messages
> and relay them to the sysadmin staff in e-mail, or for some critical
> messages, to send a text message to cell phones. It worked great, until
> it stopped working entirely a couple of weeks ago. I can't figure out
> why it's not working. I've verified that all the action plans are still
> in place, and configured to run on all the partitions.
>
> I thought it might have something to do with the SMTP server, or perhaps
> MSF, but that's not it. I know this because I have some threshold
> action plans that also send e-mails, and these are continuing to appear
> as before, from more than one of the partitions (including the partition
> running Director Server.)
>
> Does anyone out there in c.s.i.a.m. have any experience with Director,
> and specifically with this kind of problem?

After months of poking at this, and several weeks of tap-dancing with
the IBM Advocate, I finally figured it out. There are a couple of PTFs
needed to be applied for the licensed programs (5722DR1 - Director
Server, and 5722DA1 - Director Agent). Director stopped handling i5/OS
message queue events correctly beginning in 2008 (a Y2K+8 problem). But
it was worse than it looked. I ultimately had to uninstall Director on
all six i5 partitions where we use it (five Director Agent, one Director
Server) and reinstall it. I even had to do that multiple times, because
the uinstall (DLTLICPGM) left folders and files in
/QIBM/USERDATA/DIRECTOR, and until I manually deleted them, the message
queue monitoring wouldn't work.

I am trying on a new installation to monitor a msgq on the i5. I have Director Server (5.20.2) running on one partition that is doing the monitoring, another Server (5.10.3) in a partition that is used only for Integrated xSeries Servers, and then the agent (5.20.2) running in a third partition. I have the Event Action Plan setup to monitor QSYSOPR for an MSGID, and send me an email, but when I generate the event, it doesn't send me the email. I know everything else is working, I'm starting and ending a subsystem, and I have the process monitor setup to watch for that job name and I the email that says the process started, but I'm monitoring for CPF1804 (Subsystem SBSNAME in library LIBNAME starting.)

I don't get an email though. Can you tell me what PTF's you installed?

This is the only thing I don't have working, I have figured out a lot on my own, but I have been stumped on this for a month. I was very excited to see your last post!

I found the PTF's

for 5722DA1 you need UK32885
for 5722DR1 you need UK32821

This is something else that I had to pull teeth to get an answer on, I hope it helps someone.
************************************************** ***
To call a program on the i5 from Director in an Event Action Plan

Program Specification: system -v "call mylib/myprogram"
Working Directory: /qsys.lib/mylib.lib
************************************************** ***

Sorry, I didn't see your post until now.

Yes, those are the PTFs. Note that UK32885, for Director Agent (5722DA1), is only applicable to i5/OS V5R4. A pity, because I have two V5R3 partitions with the Agent installed, and I still can't get the message queue monitoring/forwarding on them to work, despite having upgraded the Agent from V5.10 to V5.20.

Regarding your point about the program call in response to an event: do you mean in the "Customize action" setup window, I have to precede the call statement with 'system -v'?

Can you elaborate a little on the program call? I tried doing it exactly as you have it coded, and have also tried replacing the double quotes with single quotes, and it still doesn't work.

I did determine that "system" is the name of a program in library QSHELL. Just for fun, I ran the following:

qsh cmd('system -v "call mylib/mypgm" ')

and it worked. But I would think Director, which does a lot of qsh stuff under the covers, would already know to invoke the system program to process the command.

In any case, I can't get the program call to work as a triggered event.