z/OS MVS Planning: APPC/MVS Management
|
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Deciding Which TP Message Log Values to Use z/OS MVS Planning: APPC/MVS Management SA23-1388-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The default values for TP message log parameters tell APPC/MVS to create a new message log for each TP instance that ends on error. Depending on the environment in which the TP will run, and the type of TP, you might specify different values for the TP message log. For example, the defaults might be appropriate for a TP running in a production system; however, you could bypass the message log completely, to reduce I/O and storage use. If the TP encounters a problem, you can change the parameter values only when you attempt to re-create the problem and collect diagnostic information. In contrast, when the TP is running in a test environment, you can use the values that allow you to collect all messages for all instances of the TP, whether or not each instance ends successfully. Table 1 lists the results of
each possible combination of TP message log parameters. As
you read through them to determine which combination best suits your
needs, keep these facts in mind:
|
Copyright IBM Corporation 1990, 2014 |