tpcc_current (Дополнительные методические материалы), страница 10

The d isp lay field s are d ivid ed in tw ogrou p s as follow s:• One non-rep eating grou p of field s: W_ID, D_ID, C_ID, C_FIRST, C_MIDDLE, C_LAST, C_BALAN CE, O_ID,O_EN TRY_D, and O_CARRIER_ID;• One rep eating grou p of field s: OL_SUPPLY_W_ID, OL_I_ID, OL_QUANTITY, OL_AMOUN T, andOL_DELIVERY_D. The grou p is rep eated O_OL_CN T tim es (once p er item in the ord er).Comment 1: The ord er of item s show n on the Ord er -Statu s screen d oes not need to m atch the ord er in w hich theitem s w ere entered in its corresp ond ing N ew -Ord er screen.Comment 2: If OL_DELIVERY_D is nu ll (i.e., the ord er has not been d elivered ), the term inal m u st d isp lay anim p lem entation sp ecific nu ll d ate rep resentation (e.g., blanks, 99-99-9999, etc.).

The chosen nu ll d ate rep resentationm u st not change d u ring the test.2.6.3.4The follow ing table su m m arizes the term inal I/ O requirem ents for the Ord er-Statu s transaction :EnterN on-rep eating Grou pD_IDC_ID 1C_LAST 2Rep eating Grou pDisp layRow / Colu m nCoord inatesW_IDD_IDC_IDC_FIRSTC_MIDDLEC_LASTC_BALAN CEO_IDO_EN TRY_DO_CARRIER_IDOL_SUPPLY_W_IDOL_I_IDOL_QUAN TITYOL_AMOUN TOL_DELIVERY_D2/2/3/3/3/3/4/6/6/6/8-22/ 38-22/ 148-22/ 258-22/ 338-22/ 471 Enter only for qu ery by cu stom er nu m ber.Enter only for qu ery by cu stom er last nam e.2.6.3.512291124414416153876For general term inal I/ O requ irem ents, see Clau se 2.2.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 39 of 13022.7The D elivery TransactionThe Delivery bu siness tran saction consists of p rocessing a batch of 10 new (not yet d elivered ) ord ers. Each ord er isp rocessed (d elivered ) in full w ithin the scop e of a read -w rite d atabase transaction .

The nu m ber of ord ers d eliveredas a grou p (or batched ) w ithin the sam e d atabase transaction is im p lem entation sp ecific. The bu siness transaction,com p rised of one or m ore (u p to 10) d atabase transactions, has a low frequ ency of execu tion and m u st com p letew ithin a relaxed resp onse tim e requ irem ent.The Delivery transaction is intend ed to be execu ted in d eferred m od e throu gh a qu eu ing m echanism , rather thaninteractively, w ith term inal resp onse ind icating transaction com p letion.

The resu lt of the d eferred execu tion isrecord ed into a resu lt file.2.7.1Input D ata Generation2.7.1.1interval.For any given term inal, the hom e w arehou se nu m ber (W_ID) is constant over the w hole m easu rem ent2.7.1.2The carrier nu m ber (O_CARRIER_ID) is rand om ly selected w ithin [1 .. 10].2.7.1.3and tim e.The d elivery d ate (OL_DELIVERY_D) is generated within the SUT by u sing the cu rrent system d ate2.7.2D eferred Execution2.7.2.1Unlike the other transactions in this benchm ark, the Delivery transaction m u st be execu ted in d eferredm od e.

This m od e of execu tion is p rim arily characterized by qu eu ing the transaction for d efe rred execu tion,retu rning control to the originating term inal ind ep end ently from the com p letion of the transaction, and record ingexecu tion inform ation into a resu lt file.2.7.2.2Deferred execu tion of the Delivery transaction m u st ad here to the follow ing ru les:1. The bu siness transaction is qu eu ed for d eferred execu tion as a resu lt of entering the last inp u t character.2.

The d eferred execu tion of the bu siness transaction m u st follow the p rofile d efined in Clau se 2.7.4 w ith theinp u t d ata d efined in Clau se 2.7.1 as entered throu gh the inp u t/ ou tp u t screen and com m unicated to thed eferred execu tion qu eu e.3. At least 90% of the bu siness transaction s m u st com p lete w ithin 80 second s of their being qu eu ed forexecu tion.4. Up on com p letion of the bu siness transaction , the follow ing inform ation m u st have been record ed into a resu ltfile:•The tim e at w hich the bu siness transaction w as qu eu ed .•The w arehou se nu m ber (W_ID) and the carried nu m ber (O_CARRIER_ID) associated w ith the bu sinesstransaction.•The d istrict nu m ber (D_ID) and the ord er nu m ber (O_ID) of each ord er d elivered by the bu sinesstransaction.•The tim e at w hich the bu siness transaction com p leted .TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 40 of 1302.7.2.3The result file associated w ith the d eferred execu tion of the Delivery b u siness transaction is only forthe p u rp ose of record ing inform ation abou t that transaction and is not relevant to the bu siness fu nction beingp erform ed .

The resu lt file m u st ad here to the follow in g ru les:1.All events m u st be com p leted before the related inform ation is record ed (e.g., the record ing of a d istrictand ord er nu m ber m u st be d one after the d atabase transaction , w ithin w hich this ord er w as d elivered , hasbeen com m itted );2.N o ACID p rop erty is requ ired (e.g., the record ing of a d istrict and ord er nu m ber is not requ ired to beatom ic w ith the actu al d elivery of that ord er) as the resu lt file is u sed for benchm arking p u rp oses only.3.Du ring the m easu rem ent interval the resu lt file m u st be located either on a d u rable m ed iu m (see clau se3.5.1) or in the internal m em ory of the SUT. In this last case, the resu lt file m u st be transferred onto ad u rable m ed iu m after the last m easu rem ent interval of the test ru n (see Clau se 5.5).2.7.3Terminal I/O2.7.3.1For each transaction the originating term inal m u st d isp lay the follow ing inp u t/ ou tp u t screen w ith allinp u t and ou tp u t field s cleared (w ith either sp aces or zeros) excep t for the Warehou se field w hich has not changedand m u st d isp lay the fixed W_ID valu e associated w ith that term inal.123451234567890123456789012345678901234567890123456789012345671Delivery2 Warehouse: 999934 Carrier Number: 9956 Execution Status: XXXXXXXXXXXXXXXXXXXXXXXXX7891011121314151617181920212223242.7.3.2The em u lated u ser m u st enter, in the ap p rop riate inp u t field of the inp u t/ ou tp u t screen, the requ iredinp u t d ata w hich is organized as one d istinct field : O_CARRIER_ID.2.7.3.3The em u lated term inal m ust d isp lay, in the ap p rop riate ou tp u t field of the inp u t/ ou tp u t screen, allinp u t d ata and the ou tp u t d ata w hich resu lts from t he qu eu ing of the transaction.

The follow ing field s are d isp layed :W_ID, O_CARRIER_ID, and the statu s m essage "Delivery has been qu eu ed ".TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 41 of 1302.7.3.4The follow ing table su m m arizes the term inal I/ O requirem ents for the Delivery transaction :EnterN on-rep eating Grou pO_CARRIER_ID2.7.3.52.7.4Disp layRow / Colu m nCoord inatesW_IDO_CARRIER_ID"Delivery has been qu eu ed "2/ 124/ 176/ 19For general term inal I/ O requ irem ents, see Clau se 2.2.Transaction Profile2.7.4.1The d eferred execu tion of the Delivery transaction d elivers one ou tstand ing ord er (average item s-p erord er = 10) for each one of the 10 d istricts of the selected w arehou se u sing one or m ore (u p to 10) d atabasetransaction s.

Delivering each ord er is d one in the follow ing step s:1.Process the ord er, com p rised of:1 row selection w ith d ata retrieval,(1 + item s-p er-ord er) row selections w ith d ata retrieval and u p d ate.2.Up d ate the cu stom er's balance, com p rised of:1 row selections w ith d ata u p d ate.3.Rem ove the ord er from the new -ord er list, com p rised of:1 row d eletion.Comment: This bu siness transaction can be d one w ithin a single d atabase tr ansaction or broken d ow n into u p to 10d atabase transactions to allow the test sp onsor the flexibility to im p lem ent the bu siness transaction w ith th e m ostefficient nu m ber of d atabase transactions.N ote: The above su m m ary is p rovid ed for inform ation only.