• Subject: Re: QEZBKMSG looking for source or parm list
  • From: watern@xxxxxxxxxxxxxx
  • Date: Wed, 29 Sep 1999 03:51:23 -0400
  • Illegal-Object: Syntax error in From: address found on firewall.cbs.fiserv.com:From: LNCBS.FISERVCBS.watern<watern@cbs.fiserv.com> ^-missing end of mailbox


couldnt find QEZBKMSG anywhere in the manuals !  strange.....   maybe it is 
just a program used by the message apis ?

The QEZSNDMG api is documented in the Operational Assistant APIs manual - will 
this do what you want ? (dont know why it isnt even mentioned in the message 
apis manual !)

The manual says....

" This API combines the functions of the Send Message (SNDMSG) and Send      
 Break Message (SNDBRKMSG) commands.  In addition, it provides the ability  
  Send inquiry messages to more than one user                            
  Send break messages to user profiles                                   
  Send break and inquiry messages to all active users                    
  Send nonbreak and inquiry messages to display stations
This API can be called with or without parameters. "

I have used this api and the QMHSNDM api, at a previous workplace. 
Unfortunately neither are in the qsysinc library so its a case of copying the 
parameters out of the manual.  I dont have my old source to-hand or I'd paste 
it in for you.


| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

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

This mailing list archive is Copyright 1997-2019 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].