English dropdown-ico

IBM HS64 manual

1
2
3
4
5
6
7
8
9
10
11
12
13

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of IBM HS64, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of IBM HS64 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of IBM HS64. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of IBM HS64 should contain:
- informations concerning technical data of IBM HS64
- name of the manufacturer and a year of construction of the IBM HS64 item
- rules of operation, control and maintenance of the IBM HS64 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of IBM HS64 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of IBM HS64, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the IBM service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of IBM HS64.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the IBM HS64 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

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

  • Page 2

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

  • Page 3

    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 [...]

  • Page 4

    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 pa rameter. FAcid uses the FACE ID specified as the FACE ID of the ‘hot record’. Ordinal specifies number in H[...]

  • Page 5

    HOTS/HS64 Format >>--ZTEST--+----+----- --+--HOT S-+---------------------------------------> ' - i -' ' --HS64-' .- Ordinal-0-. >-+- -Set-+-----------+ -+------------+ -+-----------+ -+--------+---+--->< | +- -FIleadd-+ +- Normal-----+ +-Ordinal- n -+ +-FCt----+ | | '- -FAcid--- ' +-SNippets---+ &apos[...]

  • Page 6

    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-str[...]

  • Page 7

    BSOs HS64 driver segment qht6.asm app_drvs.mak QHT6 Called by QHT1 when HOTS is running HOTS driver segment qht3.asm app_drvs.mak QHT3 HOTS driver segment qht2.asm app_drvs.mak QHT2 HOTR driver segment qht1.asm app_drvs.mak QHT1 HOTR driver segment qht0.asm app_drvs.mak QHT0 Description Segment Makefile Module CSOs None. Additional information Macr[...]

  • Page 8

    GETCC D7 FILNC D7 WAITC y STATE 6: No VFA buffer y STATE 7: VFA-S lock pending, BCA queue, use D4/D5 CRUSA FINDC FINDC y STATE 8: VFA-S lock pending, no BCA queue, use D5 CRUSA FINDC y STATE 9: VFA buffer, VFA-s lock CRUSA FINDC WAITC y STATE 10: VFA buffer, VFA-s lock, RHT in BCA FINHC WAITC UNFRC y STATE 11: VFA buffer, VFA-X lock, RHT in BCA y S[...]

  • Page 9

    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[...]

  • Page 10

    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 HOTR0030I STATUS was requested for FACE ID #HOTREC Ordinal 00000004+ CSMP0097I[...]

  • Page 11

    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 paramet[...]

  • Page 12

    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 FACE ID #HOTREC Ordinal 00000000 The file-coun[...]

  • Page 13

    References For more information about reading syntax diagrams, also referred to as railroad diagrams, see Accessibility information in the TPF Product Information Center. ZTEST HOTX © Copyright IBM Corp. 2006 HOTX Driver User's Guide 13[...]