M204.2953: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add info from 7.6 rel notes) |
||
| Line 2: | Line 2: | ||
__NOTOC__ | __NOTOC__ | ||
<p> | <p> | ||
> | This informational message displays zHPF capabilities for each data set in a currently open file. The <code>Supported:</code> value in the message, <var class="term">token3</var>, shows whether [[Performance monitoring and tuning#High Performance FICON (zHPF)|zHPF type I/O]], called "transport mode I/O," can be used for the data sets. </p> | ||
</p> | <p> | ||
The message's three <var class="term">hexValue</var> bytes represent the existing zHPF capabilities as shown in the following tables: </p> | |||
<ul> | |||
<li><b>Byte 1:</b> ZHPF_FLAG1: zHPF Channel Program Information Area, Capabilities flag 1 | |||
<table> | |||
<tr class="head"><th>Value</th> <th class="head">Meaning</th></tr> | |||
<tr><td>X'80'</td> | |||
<td>all of the online paths for the device support bidirectional data for zHPF I/O requests.</td></tr> | |||
<tr><td>X'40'</td> | |||
<td>zHPF is supported for EXCPVR requests </td></tr> | |||
<tr><td>X'20'</td> | |||
<td>The incorrect length facility is supported by the processor</td></tr> | |||
<tr><td>X'10'</td> | |||
<td>zHPF is supported for EXCP virtual requests</td></tr> | |||
</table></li> | |||
<li><b>Byte 2:</b> ZHPFD_FLAG1: zHPF DASD Feature Information Area, Capabilities flag 1 | |||
<table> | |||
<tr class="head"><th>Value</th> <th class="head">Meaning</th></tr> | |||
<tr><td>X'80'</td> | |||
<td>Phase 0 zHPF features are supported</td></tr> | |||
<tr><td>X'20'</td> | |||
<td>Multi-track operations are supported</td></tr> | |||
<tr><td>X'08'</td> | |||
<td>Transfer TCA Extension (TTE) DCW supported</td></tr> | |||
<tr><td>X'04'</td> | |||
<td>Phase 1 zHPF features are supported</td></tr> | |||
<tr><td>X'02'</td> | |||
<td>Imbedded Locate Records are supported</td></tr> | |||
<tr><td>X'01'</td> | |||
<td>Format and Update writes in same chnl pgm</td></tr> | |||
</table></li> | |||
<li><b>Byte 3:</b> ZHPFD_FLAG2: zHPF DASD Feature Information Area, Capabilities flag 2 | |||
<table> | |||
<tr class="head"><th>Value</th> <th class="head">Meaning</th></tr> | |||
<tr><td>X'80'</td> | |||
<td>zHPF Format Write supported</td></tr> | |||
<tr><td>X'40'</td> | |||
<td>zHPF TCAX Pad fix</td></tr> | |||
</table></li> | |||
</ul> | |||
<p> | |||
<var class="term">token3</var> has one of the following values: </p> | |||
<table> | |||
<tr class="head"><th>Value</th> <th class="head">Meaning</th></tr> | |||
<tr><td>YES</td> | |||
<td>zHPF is supported for <var class="term">dataset_name</var> in <var class="term">filename</var></td></tr> | |||
<tr><td>NO</td> | |||
<td>hardware or z/OS support for zHPF functionality is insufficient (for example when z/OS runs under VM)</td></tr> | |||
<tr><td>N/A</td> | |||
<td>zHPF support is not available at all at the z/OS or hardware level</td></tr> | |||
</table> | |||
<p> | |||
<b>Response:</b> No response is needed. This message is for information only.</p> | |||
<p> | <p> | ||
<b>Version introduced:</b> | |||
7.6 | |||
</p> | </p> | ||
{{Template:M204.2953 footer}} | {{Template:M204.2953 footer}} | ||
Latest revision as of 17:41, 20 August 2018
M204.2953 File token token2 zHPF capabilities hexValue hexValue2 hexValue3 Supported: token3
This informational message displays zHPF capabilities for each data set in a currently open file. The Supported: value in the message, token3, shows whether zHPF type I/O, called "transport mode I/O," can be used for the data sets.
The message's three hexValue bytes represent the existing zHPF capabilities as shown in the following tables:
- Byte 1: ZHPF_FLAG1: zHPF Channel Program Information Area, Capabilities flag 1
Value Meaning X'80' all of the online paths for the device support bidirectional data for zHPF I/O requests. X'40' zHPF is supported for EXCPVR requests X'20' The incorrect length facility is supported by the processor X'10' zHPF is supported for EXCP virtual requests - Byte 2: ZHPFD_FLAG1: zHPF DASD Feature Information Area, Capabilities flag 1
Value Meaning X'80' Phase 0 zHPF features are supported X'20' Multi-track operations are supported X'08' Transfer TCA Extension (TTE) DCW supported X'04' Phase 1 zHPF features are supported X'02' Imbedded Locate Records are supported X'01' Format and Update writes in same chnl pgm - Byte 3: ZHPFD_FLAG2: zHPF DASD Feature Information Area, Capabilities flag 2
Value Meaning X'80' zHPF Format Write supported X'40' zHPF TCAX Pad fix
token3 has one of the following values:
| Value | Meaning |
|---|---|
| YES | zHPF is supported for dataset_name in filename |
| NO | hardware or z/OS support for zHPF functionality is insufficient (for example when z/OS runs under VM) |
| N/A | zHPF support is not available at all at the z/OS or hardware level |
Response: No response is needed. This message is for information only.
Version introduced: 7.6
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=0 | Sets batch (single user) return code |
| CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
| AUDITMS | Writes the message with line type MS to the audit trail |
| NOCOUNT | Does not increment the error count (ERCNT) parameter |