Re: SMG Customer Notifier

Hello Graham,

I have loaded the 6.1.00 documentation to the FTP site for you, with more
documentation to follow. I will e-mail you directly with the directory.
Also, you will need to implement the DllInit and DllTerm functions.

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
>>
>> -----Original Message-----
>> From: Smith, Graham (EBM) <Graham_SmithEBM@heinz.co.uk>
>> To: 'BPCS-l@Midrange.com' <BPCS-l@midrange.com>
>> Date: Tuesday, March 14, 2000 2:04 PM
>> Subject: SMG Customer Notifier
>>
>>
>> >I'm trying to build a Customer Notifier that will talk to MQseries.
>> >
>> >The MQSeries portion is a piece of cake but the SMG USer guide doesnt
>> >provide enough information to sensibly build the Module that processes
>> the
>> >notification.
>> >
>> >Anyone tried to build a Customer Notifier with any success?
>> >
>> >SSA are attempting to charge for this info which is taking a liberty in
>> my
>> >book.
>> >
>> >Thanks
>> >Graham
>> >
>> >**********************************************************************
>> > This email and any attachments are confidential and solely
>> > for the use of the intended recipient.  They may contain
>> > material protected by legal professional or other privilege.
>> > If you are not the intended recipient or the person responsible
>> > for delivering to the intended recipient, you are not authorised
>> > to and must not disclose, copy, distribute or retain this email
>> > or its attachments.  Although this email and its attachments
>> > are believed to be free of any virus or other defect, it is the
>> > responsibility of the recipient to ensure that they are virus free
>> > and no responsibility is accepted by the company for any
>> > loss or damage arising from receipt or use thereof.
>> >
>> >**********************************************************************
>> >+---
>> >| 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
>> >+---
>> >
>>
>> +---
>> | 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
>> +---
>>
>**********************************************************************
> This email and any attachments are confidential and solely
> for the use of the intended recipient.  They may contain
> material protected by legal professional or other privilege.
> If you are not the intended recipient or the person responsible
> for delivering to the intended recipient, you are not authorised
> to and must not disclose, copy, distribute or retain this email
> or its attachments.  Although this email and its attachments
> are believed to be free of any virus or other defect, it is the
> responsibility of the recipient to ensure that they are virus free
> and no responsibility is accepted by the company for any
> loss or damage arising from receipt or use thereof.
>
>**********************************************************************
>+---
>| 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
>+---
>

+---
| 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
+---