Summary of the content on the page No. 1
z/TPF HOTX Driver
(HOTR/HOTS/HS64)
User's Guide
© Copyright IBM Corp. 2006
Summary of the content on the page No. 2
Last Updated 6/5/2006 This page intentionally left blank. 2 HOTX Driver User's Guide © Copyright IBM Corp. 2006
Summary of the content on the page No. 3
ZTEST HOTX ZTEST HOTR/HOTS/HS64 The HOTX driver suite contains the HOTR, HOTS and HS64 drivers. The HOTR driver tests the TPF DASD supports by creating a 'hot record' (default using #HOTREC) to blast channels and test cache. The instances created by the HOTR driver stresses the DASD system by repeatedly finding and filing the ‘hot record’. The first time it runs, it allocates a 4K frame on the system heap for the subsystem to store the information (8 bytes for each entry containing the flags (r
Summary of the content on the page No. 4
Last Updated 6/5/2006 STOp stops the driver on the ordinal number specified. STAT queries the status of the ordinal number specified. FIleadd uses the address specified as the address of the ‘hot record’. Note: The FILEADDR parameter overrides the FACID parameter. FAcid uses the FACE ID specified as the FACE ID of the ‘hot record’. Ordinal specifies number in Hex 0x00-0x13. If not specified, the default is 0. All runs the action with all 20 ordinals 0x00-0x13. Note: The ALL parameter overrides
Summary of the content on the page No. 5
ZTEST HOTX HOTS/HS64 Format >>--ZTEST--+----+----- --+--HOTS-+---------------------------------------> '- i-' '--HS64-' .-Ordinal-0-. >-+- -Set-+-----------+ -+------------+ -+-----------+ -+--------+---+--->< | +- -FIleadd-+ +-Normal-----+ +-Ordinal-n-+ +-FCt----+ | | '- -FAcid---' +-SNippets---+ '-All-------' '-NOFCt--' | | +-NOSNippets-+ | |
Summary of the content on the page No. 6
Last Updated 6/5/2006 All indicates to use all record ordinal numbers defined (i.e. 0x00-0x13). This parameter cannot be specified with the FILEADDR parameter. FCt specifies functional test mode. NOFCt specifies system test mode. Help displays the correct syntax of the command. Examples The following example will set the flag to run the snippets with ordinal 0 on I-stream two: ZTEST 2 HOTS SET SNIPPETS The following example will set the flags for not running the snippets with all ordinals on
Summary of the content on the page No. 7
ZTEST HOTX BSOs Module Makefile Segment Description QHT0 app_drvs.mak qht0.asm HOTR driver segment QHT1 app_drvs.mak qht1.asm HOTR driver segment QHT2 app_drvs.mak qht2.asm HOTS driver segment QHT3 app_drvs.mak qht3.asm Called by QHT1 when HOTS is running HOTS driver segment QHT6 app_drvs.mak qht6.asm HS64 driver segment CSOs None. Additional information Macro Usage (HOTR): Macro Usage BPKDC Standardized parameter parser. Also uses BPPSC. CINFC Get the protection key. CRUSA Test if data level(s
Summary of the content on the page No. 8
Last Updated 6/5/2006 GETCC D7 FILNC D7 WAITC STATE 6: No VFA buffer STATE 7: VFA-S lock pending, BCA queue, use D4/D5 CRUSA FINDC FINDC STATE 8: VFA-S lock pending, no BCA queue, use D5 CRUSA FINDC STATE 9: VFA buffer, VFA-s lock CRUSA FINDC WAITC STATE 10: VFA buffer, VFA-s lock, RHT in BCA FINHC WAITC UNFRC STATE 11: VFA buffer, VFA-X lock, RHT in BCA STATE 12: VFA buffer, VFA-X lock, delay file pending FINHC WAITC FILNC WAITC UNFRC STATE 13: VFA
Summary of the content on the page No. 9
ZTEST HOTX SERVICE 6: FILSC VS=YES, RID=xx SERVICE 7: FILUC VS=YES, RID=xx SERVICE 8: FILUC VS=NO RID=xx SERVICE 9: UNFRC VS=NO RID=xx SERVICE 10: UNFRC VS=YES RID=xx SERVICE 11: FINHC VS=YES RID=0 SERVICE 12: FINHC VS=YES RID=correct SERVICE 13: FINHC VS=YES, RID=incorrect SERVICE 14: FINHC VS=YES RID=incorrect vs=no SERVICE 15: FINHC VS=NO, RID=0 SERVICE 16: FINHC VS=NO, RID=correct SERVICE 17: FINHC VS=NO RID=inc VS=yes SERVICE 18: FINHC VS=NO, RID=inc VS=no SERVI
Summary of the content on the page No. 10
Last Updated 6/5/2006 ZTEST HOTR START HOTR0009I Driver started for FACE ID: #HOTREC ordinal: 00000000+ ZTEST 2 HOTR START HOTR0009I Driver started for FACE ID: #HOTREC ordinal: 00000000+ ZTEST HOTR START O-4 HOTR0009I Driver started for FACE ID: #HOTREC ordinal: 00000004+ ZTEST HOTR STAT O-4 HOTR
Summary of the content on the page No. 11
ZTEST HOTX ZTEST HOTR START O-14 HOTR0002E Ordinal number too high- must be 0x0-0x13+ ZTEST HOTR START FILEADD-00000000CC03A802 O-1 BPKD0061E 07.33.16 ZHOTR, TOO MANY CHARACTERS IN FILEADD PARAMETER+ Normal Cases: (HOTS/HS64) ZTEST HOTS HELP CSMP0099I 09.28.09 010000-B ZTEST HOTS HELP+ CSMP0097I 09.28.09 CPU-B SS-BSS SSU-HPN IS-01 HOTS0001I Valid HOTS parameters are:
Summary of the content on the page No. 12
Last Updated 6/5/2006 The file-count is: 00007913 Snippets active - last was STATE: 0004 SERVICE: 0001 This record is not running EHT This record is running SVT Mode+ ZTEST HOTR STAT HOTR0030I STATUS was requested for FACE ID #HOTREC Ordinal 00000000+ CSMP0097I 16.53.01 CPU-B SS-BSS SSU-HPN IS-01 HOTR0016I Driver running on F
Summary of the content on the page No. 13
ZTEST HOTX References For more information about reading syntax diagrams, also referred to as railroad diagrams, see Accessibility information in the TPF Product Information Center. © Copyright IBM Corp. 2006 HOTX Driver User's Guide 13
