× 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.



Hello, 

I don't know about the documentation, but we have a mhp over qsysopr since
'93 - never had a real problem with it.

Regards,

Oliver

> -----Ursprüngliche Nachricht-----
> Von:  barsa@barsaconsulting.com [SMTP:barsa@barsaconsulting.com]
> Gesendet am:  Donnerstag, 19. Juli 2001 22:28
> An:   MIDRANGE-L@midrange.com
> Betreff:      Re: QSYSOPR message queue segregation
> 
> 
> It used to say in the documentation to never hang a message handling
> program over QSYSOPR.  Does anyone know if this recommendation had
> changed?
> 
> Al
> 
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
> 
> 400>390
> 
> 914-251-1234
> 914-251-9406 fax
> 
> http://www.barsaconsulting.com
> http://www.taatool.com
> 
> 
> 
> 
> 
>  
> 
>                     "Steve Richter"
> 
>                     <srichter@AutoCoder        To:
> <MIDRANGE-L@midrange.com>                                         
>                     .com>                      cc:
> 
>                     Sent by:                   Subject:     Re: QSYSOPR
> message queue segregation                        
>                     owner-midrange-l@mi
> 
>                     drange.com
> 
>  
> 
>  
> 
>                     07/19/01 03:55 PM
> 
>                     Please respond to
> 
>                     MIDRANGE-L
> 
>  
> 
>  
> 
> 
> 
> 
> 
> Michael,
> 
> You could put the qsysopr msgq in *break mode and specify a break handling
> pgm to run every time a msg arrives in the queue.  Your bhp can then send
> the received msg to the queue of your choice depending on say the msgid.
> 
> To segregate depending on the prod or test env, maybe the job name and
> user
> of the msg sending job is available.
> 
> hth,
> Steve Richter
> 
> 
> 
> +---
> | 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 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 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
+---

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.