[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:NAS Message Queuing Bus
Notice:KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:PAMSRC::MARCUSEN
Created:Wed Feb 27 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2898
Total number of notes:12363

2812.0. "Self Describing Messages on non core platforms" by BEAVER::MCKEATING () Tue Mar 18 1997 06:49

Has any thought been given as to how access to the SDM code/decode will
be implemented for customers who use the Q adapter, MQ series Bridge etc?

The more customers we see requiring connect to IBM environments require
consistent interface across both DECmessageQ and MQ series, Q adapter
(falcon....) If we are to use DECmessageQ SDM across these boundaries then we
need access to SDM on non core platforms. Otherwise the old wheel gets
re-invented again with DECmessageQ SDM ignored.

comments,

Bob (who wants to get rid of our DDIS ASN.1 SDM in favour of something faster,
     and does not want to re-write SDM code again)
T.RTitleUserPersonal
Name		DateLines
2812.1standalone SDMAZUR::GALVANJean-Philippe GALVAN - Sophia-Antipolis - 828-5621Tue Mar 18 1997 10:356
The SDM code was specifically developed to be used in a non-DMQ environment
(for instance to be used by ORB or to write SDM records in files and do FTP
or FTAM exchanges or share them such as NFS)

As such the SDM exists as a standalone library and it is planned to port it
to platforms like MVS and AS/400 (and all platforms where Q-ADAPTER runs).
2812.2Who controls access to the SDM code then?BEAVER::MCKEATINGTue Mar 18 1997 11:4318
JPG, re 

"As such the SDM exists as a standalone library and it is planned to port it to
platforms like MVS and AS/400 (and all platforms where Q-ADAPTER runs)."

I was on the phone to Gavon yesterday and he has no plans for the next 6 months
etc to do something with this. 

As I understand it BEA is not taking the Q adapter so is the situation with SDM
that it is available to DIGITAL for use with other projects and integration 
solutions such as MSG+ and use with MQ series through the bridge,....

we have customer requests at the moment for Stratus, AS/400 and highly likely
Tandem so it is an issue for us as a big DECmessageQ customer.

thanks in advance,

Bob
2812.3Contact PMAZUR::GALVANJean-Philippe GALVAN - Sophia-Antipolis - 828-5621Wed Mar 19 1997 14:112
For licensing issues, you need to contact Product Management.
Ellery Willett is still Digital. Gavon as PM for the Q-Adapter also.
2812.4Yes, we are interested.PAMSRC::MACKOGlen, 860-258-5281Fri Mar 21 1997 15:1351
    Bob,
    
    I glad to know that there is interest in greater use of SDM.
    
    re:  .0
    
    > Has any thought been given as to how access to the SDM code/decode will
    > be implemented for customers who use the Q adapter, MQ series Bridge etc?
    
    We are now investigating the porting effort to place SDM routines on
    MVS for inclusion with the MVS Client and as a add-on licenses for
    customers using MQSeries on MVS and wanting to exchange messages with
    DECmessageQ V4.0 programs on other platforms.  Hopefully, we will have
    this available with the MVS Client V4.0 and MQSeries connection later
    this year.
    
    The Q-adapter is a more difficult issue since there are MANY V4.0
    features (e.g. large msgs, PAMS_BIND, SDM, etc) that are not included
    with the Q-Adapter.  For the moment, Gavon and I have agreed that
    Q-Adapter customers will be constrained to V3.2 features.
    
    re:  .2
    
>As I understand it BEA is not taking the Q adapter so is the situation with SDM
>that it is available to DIGITAL for use with other projects and integration 
>solutions such as MSG+ and use with MQ series through the bridge,....
    
    It is true that the Q-adapter is not going to BEA.
    
    BEA certainly wants to encourage and expand relationships where DmQ is
    integrated with other software.  However, there is not currently in
    place a general policy concerning re-use of SDM.  I encourage you to
    propose a plan to us for your specific needs.  It might involve either
    a Binary license (where BEA does the ports and supplies binaries to
    you), or a Source license where you are specifically sublicensed to
    embed the SDM modules with your offerings.

> we have customer requests at the moment for Stratus, AS/400 and highly likely
> Tandem so it is an issue for us as a big DECmessageQ customer.
    
    I believe that BEA has a porting center that includes all of these
    platforms.  There is a significant chance that we will be porting our
    MVS Client onto AS/400 to have a standard offering.

> If we are to use DECmessageQ SDM across these boundaries then we
> need access to SDM on non core platforms. Otherwise the old wheel gets
> re-invented again with DECmessageQ SDM ignored.
    
    Ageed.  
    
    Glen
2812.5BEA<->DIGITAL .....Who is the client and who is the server?BEAVER::MCKEATINGThu Mar 27 1997 09:2517
Glan re .4 

"BEA certainly wants to encourage and expand relationships where DmQ is
    integrated with other software."

then 

"I encourage you to
    propose a plan to us for your specific needs"

If you want to do the first part, then surely it should be BEA who 
proposes the plan on how it can help encourage and expand the relationship?


thanks in advance,

Bob