× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: SMG Customer Notifier
  • From: "Genyphyr Novak" <novakg@xxxxxxxx>
  • Date: Fri, 17 Mar 2000 16:36:30 -0600

Hello Graham,

I wasn't on line for a couple of days so sorry for not replying sooner. I am
trying to figure out what version of SMGs and BPCS you are using. I see
HelpLine incidents for Heinz on 6.1.00 SMGs - For that release, I can't find
anything called 'Users Guide' (prior releases DID have something called
that) - there is an Installation Guide, a Configuration Guide, an
Introduction to SMGs and a Programmers Guide and an Availability Guide which
are shipped on the 6.1.00 CD-ROM that I looked at - if you have the document
number from the first page, I can search on that document number.

I did search inside the Programmers Guide for 'Customer Notifier' - there is
a section about building a 'Custom Notifier' sub class. I am assuming this
is what you are speaking about, and that you perhaps want to register
interest in the Customer? I am arranging to have some documentation put on
our FTP site for you to download that may help to explain this more than
what you are reading thus far. Before I do that, do you have access to the
SSA FTP site?

You are right about lack of documentation on this particular subject. Over
time, the SMG team came up with what they felt is an easier way to do this
than sub classing Notifier, as was in the original User Guide documentation,
and started to remove references to sub classing Notifier from the
documentation. There is an example program called CHECKEVENT.C which we can
provide source for via the FTP site as well. But this program is not a sub
class of Notifier (so does not automatically get used); it instead is
another process which must be started separately and listens via sockets to
the outbound world for notifications. This adds a point of failure, as
naturally, if this process is not started up, nothing sees the notifications
that are coming from the world.

Let me know if you can access the FTP site or not, and I will start loading
up the documentation that we do have (which was not previously available in
any shipped version of SMGs), and if that is not sufficient, let me know and
we can get your questions answered in another way. I will let you know the
URL when it is up there.

Thanks

Genyphyr Novak
SSA

-----Original Message-----
From: Smith, Graham (EBM) <Graham_SmithEBM@heinz.co.uk>
To: 'BPCS-L@midrange.com' <BPCS-L@midrange.com>
Date: Wednesday, March 15, 2000 7:38 AM
Subject: RE: SMG Customer Notifier


>Genyphyr,
>
>Thanks for the reply.
>
>Firstly the MQSeries bit is perhaps a red herring.
>
>Also we're not asking SSA to actually code the Customer Notifier. We need
to
>keep that in house for on going support reasons.
>
>There does not seem enough information in the SMG User guide to write a C
>module that implements the Notification method.
>
>In the section Subclassing the Base Notifier Object all it says is "In the
>Method Notification enter the code required to handle the messages destined
>for the external application"
>
>Doesn't give me any clue how the message data is passed to that method.
>Obviously comes as an SDO but what would be the variable name that holds
it?
>Or am I being very thick?
>
>Also there is nothing in the SMG User Guide the indicates that you need to
>use the NWIDLL module in the Customer Notifier or that the NWIDLL module
>contains the program entry proceedure - main() function.  I've had to glean
>that sort of information from the LOGNTFR object itself.
>
>Should I be implementing the DllInit and DllTerm functions?
>
>My argument is that the source for the Log Notifier should be available,
all
>it would appear to do is implement the SdsCopyToFile API so no state
secrets
>are being given away.  Additionally the SMG User guide should be more
>explicit.  The Property Notifier source is there but doesn't work the same
>way as the Customer Notifier.
>
>Again thanks for the reply and any help would be appreciated.
>
>Regards
>Graham
>
>
>> ----------
>> From: Genyphyr Novak[SMTP:novakg@ssax.com]
>> Sent: 15 March 2000 00:24
>> To: BPCS-L@midrange.com
>> Subject: Re: SMG Customer Notifier
>>
>> Hello,
>>
>> I am not familiar with MQSeries as a product - is this doing outbound
>> notification from BPCS customers into the MQ database or inbound from MQ
>> customer data into BPCS? You are right, you will be charged by SSA
>> Services
>> for doing any custom programming work for you - I don't see that as a
>> strange thing in the software industry. But there should be enough
>> information in the current 6.1.00 SMG Users Guide to get you pointed in
>> the
>> right direction to do it yourself if you are familiar with C programming
>> (don't attempt this in RPG) - what version of SMGs and BPCS do you have ?
>> (Please don't say 6.0.02. . . . because the documentation for that
release
>> was not so hot). I can try to fill in some of the blanks, but you will
>> have
>> to be more specific about what you are trying to do and what questions
you
>> want answered.
>>
>> Thanks
>>
>> Genyphyr Novak
>> SSA
>>


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.