• Subject: Sysval QMLTTHDACN
  • From: "Neil Palmer" <neilp@xxxxxxxxxxx>
  • Date: Sat, 20 Jan 2001 13:41:55 -0500

Reading through the help text for sysval QMLTTHDACN, wouldn't you ask 
yourself  - Why is the default 2 ?
Does Rochester assume that data integrity isn't important for the average 
user of the 400 ?


                             Change System Value  
  
System value . . . . . :   QMLTTHDACN  
Description  . . . . . :   Multithreaded job action  
  
  
Type choice, press Enter.  
  
  Multithreaded job  
    action . . . . . . .   2          1=Perform the function that is not  
                                        threadsafe without sending a 
message
                                      2=Perform the function that is not  
                                        threadsafe and send an 
informational
                                        message  
                                      3=Do not perform the function that 
is 
                                        not threadsafe  

                    Multithreaded job action - Help 
 
1           Perform the function that is not threadsafe without sending
            a message. 
 
            This value should not be used on systems running 
            multithreaded jobs in production mode or on any system for 
            which data integrity is important. 
 
2           Perform the function that is not threadsafe and send an 
            informational message. This value is the default. 
 
            This value may be used for investigating thread safety of 
            applications.  It should not be used on systems running 
            multithreaded jobs in production mode or on any system for 
            which data integrity is important. 

3           Do not perform the function that is not threadsafe. 
 
            This value should be used on systems running multithreaded
            jobs in production mode or on any system for which data 
            integrity is important. 



...Neil 
+---
| 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-Ups:

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