Acvance Timer, schedule Outbond messages.

[John Hamilton]

I have a need to wake up every 15 minutes and dump the messages to a database.   They don’t want a constant flow of data. Don’t ask.

I have created the upoc and it runs.  But I can’t get the MSGID to send to the database.

Has anybody used a UPOC as an outbound timed event?

If so how did you get the MSGID that should be there.

I did echo out the ARGS and there is nothing in there at all.

HELP ?

Topic

[garry r fisher]

Hi John,

First question – Is your code in the Time section of your TPS?

I’m not sure how this would work myself. I assume any messages sent are stored in recovery until the thread starts and then it tries to send them. Are you sure messages are getting to the o/b thread and do you have recovery enabled?

Regards

Garry

[John Hamilton]

Yes the code it in the time mode of the TPS.

The recovery database is turned on.

I see in the database the messages are marked as the destination thread.

[garry r fisher]

Hi John,

I’ve never used a UPoC this way either. I’ll set one up and test it.

Regards

Garry

[John Hamilton]

I just got off the phone with support. They suggested this could not be done and gave me another option which I already knew.

I just wanted to know if I could do it this way.

This way would be less complex at least to my way of thinking.

If you have any success with this let me know. I’ve gotten side tracked with another project but I will get back to this.

[Scott Folley]

Okay, how about something crazy like this:

On the outbound TPS you “fail” to disposition the message but you write the message ID into a global variable (lappend it really).  This should leave the message bound in the recovery database and give you a list of message IDs that you can then use in the Timer part of the upoc protocol driver to handle getting the messages out of recovery and pushed into the database.  You have a separate inbound thread that uses a UPOC driver and sends a flag message when 15 minutes is up.  This message is dispositioned out of the OB-TPS with a continue so that it will hit the protocol UPOC.

In theory it should work but the problems that would be left to solve are the “what ifs”.  The global variables will be lost when the process is bounced so you have to have a mechanism for addressing this (off the cuff, writing the global variable to a file and looking for that file on startup might work).

This type of method is the only way that I can think of that would allow you to use the recovery database as a “repository” for a period of time.  And while it does seem like it would work, I have not tried it.  I HAVE seen where failing to disposition a message has caused it to stay bound into the recovery database though, so I know that is a possibility.

[Author]

Replies