Ibm HOTS Manual do Utilizador

z/TPF HOTX Driver(HOTR/HOTS/HS64)User's Guide© Copyright IBM Corp. 2006

ZTEST HOTR START HOTR0009I Driver started for FACE ID: #HOTREC ordinal: 00000000+ZTEST 2 HOTR STAR

ZTEST HOTR START O-14 HOTR0002E Ordinal number too high- must be 0x0-0x13+ZTEST HOTR START FILEADD-00000000CC03A802 O-

The file-count is: 00007913 Snippets active - last was STATE: 0004 SERVICE: 0001 This rec

ReferencesFor more information about reading syntax diagrams, also referred to as railroad diagrams, seeAccessibility information in the TPF Product I

This page intentionally left blank.Last Updated 6/5/20062 HOTX Driver User's Guide © Copyright IBM Corp. 2006

ZTEST HOTR/HOTS/HS64The HOTX driver suite contains the HOTR, HOTS and HS64 drivers. The HOTR driver tests theTPF DASD supports by creating a 'hot

STOpstops the driver on the ordinal number specified.STATqueries the status of the ordinal number specified.FIleadduses the address specified as the a

HOTS/HS64 Format>>--ZTEST--+----+----- --+--HOTS-+---------------------------------------> '- i-' '--HS64-&ap

Allindicates to use all record ordinal numbers defined (i.e. 0x00-0x13). This parameter cannot bespecified with the FILEADDR parameter.FCtspecifies fu

BSOsHS64 driver segmentqht6.asmapp_drvs.makQHT6Called by QHT1 when HOTS is runningHOTS driver segmentqht3.asmapp_drvs.makQHT3HOTS driver segmentqht2.a

GETCC D7FILNC D7WAITCy STATE 6: No VFA buffery STATE 7: VFA-S lock pending, BCA queue, use D4/D5CRUSAFINDC FINDC y STATE 8: VFA-S lock pending,

SERVICE 6: FILSC VS=YES, RID=xxSERVICE 7: FILUC VS=YES, RID=xxSERVICE 8: FILUC VS=NO RID=xx SERVICE 9: UNFRC VS=NO RID=xxSERVICE 10: UNFRC VS