• Subject: Re: Sysval QMLTTHDACN
  • From: "Neil Palmer" <neilp@xxxxxxxxxxx>
  • Date: Mon, 22 Jan 2001 17:10:11 -0500


Maybe the help text for option 2 could have been worded a little 
differently than it was. 
It seems to unnecessarily cause alarm or concern.


Sent by: owner-midrange-l@midrange.com
2001/01/22 11:10
Please respond to MIDRANGE-L

        To:     MIDRANGE-L@midrange.com
        Subject:        Sysval QMLTTHDACN


Data integrity is very important to Rochester.  What you are seeing here
is that threads were added in V4R2 but this system value wasn't
introduced until V4R4.  So users had two releases where the system could
have been performing various functions (successfully we would assume)
and to use '1' would have meant no warning in the past or the future
and '3' would mean possibly failing functions that had been working (when
all the user had done was install V4R4) which is something Rochester
tries very hard to avoid.

'2' was selected as functions running prior to V4R4 would continue to
run and at least operators would be warned to look at the function.
'2' appeared to represent the lesser of possible evils given that
threaded capability was already available.


>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

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