Sysval QMLTTHDACN

[bvining@xxxxxxxxxxxx]

Neil,

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.

Bruce

>
>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
+---