WPC 2%.Bpz W"S^11>bbu"::Dg1:11bbbbbbbbbb11gggbuuuk1Xubuukuuuk111Rb:bbXbb1bb''X'bbbb:X1bXXXX;.;g:=::m:::mmmmm::::::mm:k1mubububububXubububub11111111bbbbbbbbbuXubbkbuXmmmmumububXXXXbububububbmbbbbbb:k:k::=kmmX:uXb'b:b:b:b'bmbbbb:::uXuXuXuXk:k:k:mbbbmbuXkXkXKQmmmm^b:kbbbbmbA@mmbmmbmmmmmmm:b:mmmbbmmmmmmmmmmmmXXmmmmmmmmmmmmmmmmmmcm`m`mm`m:mmmmmm}}}mjjmmmmmmmmmmmmmmm0mm}mmmmmmmmmmmmmmmmmmmmmmm}Mmmmmmmmmmmmmjmmmtmmmmmmmmm`'mmm`mmjmlWmmmmmmmmmmmmmmmmmmmW`mmmmjmM#|xaHelveticaCourierCourier Bold4PkCQMS PS Jet Plus /800 II QPJPII.PRSPl`D4PkCg2W _a.s|x-HelveticaCourierHelveticaCourierCourier BoldHelvetica BoldmQrrr r  @C2 M.IPw.@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C"S^"55U@ %8 55555555558885a@@EE@;KE0@5PEK@KE@;E@[@@;-5 55055550P5555 050E000  8 " m mmmmm mm ;m@5@5@5@5@5`UE0@5@5@5@5E5K5K5K5K5E5E5E5E5@0@5E5K;K5@0mmmmmm@5@5E0E0E0E0E5@5@5@5@5K5mmK5K5K5K5E5E5 ; ; ";mm0 @055 5 5 5E5mmE5E5K5K5`[E E E @0@0@0@0; ; ; mmE5E5E5mmE5[E@0;0;0K,mmmm45 ;5555m5$#mm5mmLL5mmmmmmm 5` mmm55Ummmmmmmmmmmm00`mmmmmmmmmmmmmmmmmm`cm5m5mm5m mmmmmJmDDDm::mdmmmmmmmmmmmmmmmmDmmmmmmmmmmmm__mmdmmmmmmmmmD*Ommmmmmmmmmmm:mmm?mmmmmmmmm5'mmm5mm:m;/mmmmmmmmmmmmmmmmmmm/H5Jmmmm:m*@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@H4': 4D4PkC"S^1:Sbb1::Dg1:11bbbbbbbbbb::gggkuk1bkuukuuuk:1:gb1bkbkb:kk11b1kkkkDb:kbbbXD1Dg:=::r:::rrrrr::::::rr:k1rbbbbbbubububub11111111kkkkkkkkkubbkkkubrrrrrbbbbbbkububububkrkkkkkk:k:k::=krrb:bk1k:k:k:k1krkkkkDDDububububk:k:k:rkkkrkubkXkXKQrrrrbb:kbbbbrbA@rrbrrbrrrrrrrXb::rrbbrrrrrrrrrrrrkkrrrrrrrrrrrrrrrrrrcr`r`rr`r:rrrrrr}}}rjjrrrrrrrrrrrrrrr0rr}rrrrrrrrrrrrrrrrrrrrrrr}Mrrrrrrrrrrrrjrrrtrrrrrrrrr`'rrr`rrjrlWrrrrrrrrrrrrrrrrrrrW`rrrrjrM2'  x@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@H4': 4D4PkC@,dK1dD4p}wC@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@H4': 4D4PkC@,dK1dD4p}wC;,>>> >  @C  X` hp x (#%'HP ,x--h.    3'3'Standard6'6'StandardC6QMS $=R- y:(  x|@   Fascicle VII.7 Rec. T.432 y:- x|@  Fascicle VII.7 Rec. T.432    9.6.1.7HCheckpoint mechanism  HThis parameter specifies the mechanism for checkpointing in DTAMPM, and the following mechanisms are defined: H1)  Mechanism 1'  H The places where to insert the checkpoints are related to a maximum size (integral number of octets) indicated by the DTAM user. A checkpoint should be set at the end of each segment and a segment should be composed of the greatest number of integral IDE (InterchangeDataElement) which is inferior or equal to the maximum size. If the document is smaller than the maximum size, then no checkpoint is required.' H2)  Mechanism 2  H The places where to insert the checkpoints are related to a number of IDEs indicated by the DTAM user. A checkpoint should be set at the end of each segment and a segment should be composed of the number of integral IDE which is indicated by the user. Only the number of IDE of the last segment is equal or inferior to the indicated number.'  H NoteSome applications may not count IDEs of Document Profile and Document Root.' 9.7HDTYPEDDATA service  HTyped data transmission is used independent of the data token and is issued from both DTAM users when required.  HThe related service structure consists of two events, as illustrated in Figure8/T.432. #FIGURE 8/T.432 *  DTYPEDDATE service events ă 9.7.1HDTYPEDDATA service parameters HThe parameters of DTYPED DATA are listed in Table 7/T.432. $TABLE 7/T.432 *  DTYPEDDATA service parameters ă   x|@ w      Parameter  DTYPED DATA request  DTYPED DATA indication     Typeddata information  M  M(=)          d#  HP ,x--h.Xp$%%p&9.7.1.1 Typeddata information XTypeddata information is chosen from the following strings: X NumericString; X PrintableString; X TeletexString; X VideotexString; X VisibleString; X OctetString; X IA5String; X GraphicString. 9.8XDUNCONFIRMEDCREATE service  XThe document create operation procedure is used by the requestor of document manipulation to add the constituents of ODA and Operational Structure to a document without any confirmation of the create manipulation.  XThe related service structure consists of two events, as illustrated in Figure 9/T.432. #FIGURE 9/T.432 *  DCREATE service events ă 9.8.1XDUNCONFIRMEDCREATE service parameters XTable 8/T.432 lists the DUNCONFIRMEDCREATE service parameters. $TABLE 8/T.432 *  DUNCONFIRMEDCREATE service parameters ă   w      Parameter  DCREATE  DCREATE     request  indication     Create information  M  M(=)             9.8.1.1 Create information  XThis parameter consists of a sequence of sequences of Parent Object or Class Identifiers and Objects which are as defined in Recommendations T.412 and T.441. 9.9XDUNCONFIRMEDDELETE service  XThe document delete operation procedure is used by the requestor of document manipulation to delete the constituents of ODA and Operational Structure of an existing document without any confirmation of the delete operation. &  XThe related service structure consists of two events, as illustrated in Figure 10/T.432. #FIGURE 10/T.432 *  DDELETE service events ă 9.9.1XDUNCONFIRMEDDELETE service parameters XTable 9/T.432 lists the DUNCONFIRMEDDELETE service parameters. $TABLE 9/T.432 *  DUNCONFIRMEDDELETE service parameters ă   w      Parameter  DDELETE  DDELETE     request  indication     Delete information  M  M(=)             9.9.1.1 Delete information  XThis parameter consists of a sequence of Object or Class of Identifiers, Content Portion Identifiers and Operational Information Identifiers which are as defined in Recommendations T.412 and T.441. 9.10XDUNCONFIRMEDMODIFY service  XThe document modify operation procedure is used by the requestor of document manipulation to modify the attributes of constituents of ODA and Operational Structure of an existing document without any confirmation of the modify operation.  XThe related service structure consists of two events, as illustrated in Figure 11/T.432. #FIGURE 11/T.432 *  DMODIFY service events ă  9.10.1 DUNCONFIRMEDMODIFY service parameters XTable 10/T.432 lists the DUNCONFIRMEDMODIFY service parameters. #TABLE 10/T.432 *  DUNCONFIRMEDMODIFY service parameters ă   w      Parameter  DMODIFY  DMODIFY     request  indication     Modify information  M  M(=)             9.10.1.1 Modify information  XThis parameter is a sequence of sequences of Current Object or Class Identifiers and Objects which are as defined in Recommendations T.412 and T.441. 9.11XDUNCONFIRMEDCALL service  XThis procedure is used to address or to read an object of Operational Structure which contains a sequence of DTAM protocol data units (with some restrictions, i.e. that only DCREATE, DDELETE and DMODIFY can appear in this sequence). These protocol data units are applicable to the existing document.  XThe related service structure consists of two events, as illustrated in Figure 12/T.432. #FIGURE 12/T.432 *  DCALL service events ă 9.11.1 DUNCONFIRMEDCALL service parameters XTable 11/T.432 lists the DUNCONFIRMEDMODIFY service parameters. #TABLE 11/T.432 *  DUNCONFIRMEDCALL service parameters ă   w      Parameter  DCALL  DCALL     request  indication     Call information  M  M(=)          &   9.11.1.1 Call information  XThis parameter is a sequence of choices of Current Object Identifier which are defined in Recommendation T.441. 9.12XDUNCONFIRMEDREBUILD service  XThis procedure is used to delete an object of ODA and/or the Operational Structure (and all the subordinates of this object, if any) and create an object immediately after this particular object, updating the attributes of the object with the values carried by the DREBUILD operation. XThis service is for further study. 9.13XDTOKENGIVE service  XThe tokengive procedure is used by a sender (requestor) to give the data token to the receiver (responder), when the sender wants to give the right to manipulate documents.  XThe requestor becomes the receiver and the responder becomes the sender. The related service structure consists of two events, as illustrated in Figure 13/T.432. #FIGURE 13/T.432 *  DTOKENGIVE service events ă 9.13.1 DTOKENGIVE service parameters XDTOKENGIVE service has no parameters. 9.14XDCONTROLGIVE service  XThe controlgive procedure is used by a sender (requestor) to give all the tokens to the receiver (responder). This service can only be requested when the document bulk transfer functional unit has been selected and the requestor owns all the tokens.  XThe related service structure consists of two events, as illustrated in Figure 14/T.432. #FIGURE 14/T.432 *  DCONTROLGIVE service events ă  9.14.1 DCONTROLGIVE service parameters XDCONTROLGIVE service has no parameters. 9.15XDTOKENPLEASE service  XThe tokenplease procedure is used by a receiver (requestor) to request the data token from  the sender (responder), when the receiver wants to request the right to transfer or manipulate documents.  XThe related service structure consists of two events, as illustrated in Figure 15/T.432. #FIGURE 15/T.432 *  DTOKENPLEASE service events ă 9.15.1 DTOKENPLEASE service parameters XTable 12/T.432 lists the DTOKENPLEASE service parameters. #TABLE 12/T.432 *  DTOKENPLEASE service parameters ă   w      Parameter  DTOKENPLEASE  DTOKENPLEASE     request  indication     Tokens priority  U  C(=)              XNoteIn the case of using Session service as a lower layer service, this parameter may not be mapped into the session service in Recommendation X.215 applied. 9.15.1.1 Tokens priority  XThis parameter defines the priority of the action, governed by the data token, that the requestor of the DTOKENPLEASE service wishes to carry out. This parameter has to be supplied by the requestor of the DTOKENPLEASE service. 9.16XDPEXCEPTIONREPORT service  XThe providerexception reporting service permits DTAM users to be notified of unanticipated situations not covered by other services. If a service cannot be completed due to DTAMservice provider protocol errors or malfunctions, the providerexception reporting service is used to indicate this to both DTAM users.  XIf used with the document bulk transfer service, the providerexception reporting service is only permitted while a DTRANSFER service is in progress or waiting for the DCAPABILITY confirm primitive. &  XFollowing a DPEXCEPTIONREPORT indication, and until the error condition is cleared:  Xa) typeddata information (DTYPEDDATA service), document informations (DTRANSFER service) will be discarded by the DTAMserviceprovider;'  Xb) synchronization point indications will not be given to the DTAMserviceprovider.'  XOn receipt of a DPEXCEPTIONREPORT indication, either DTAM user initiates one of the following services to clear the error: Xc) abort; Xd) retry of the transmission of the document information; Xe) give the data token.  XDTAM users are not permitted to initiate any other services until the error is cleared.  XThe related service structure consists of two events, as illustrated in Figure 16/T.432. #FIGURE 16/T.432 *  DPEXCEPTIONREPORT service events ă 9.16.1 DPEXCEPTIONREPORT service XTable 13/T.432 lists the DPEXCEPTIONREPORT service. #TABLE 13/T.432 *  DPEXCEPTIONREPORT service parameters ă   w      Parameter  DPEXCEPTIONREPORT     indication     Reason  M(=)        9.16.1.1 Reason  XReason is a parameter specifying the reason for the exception report. Its value is one of: Xa) protocol error; Xb) not sufficient storage capacity for transmission at the receiver; Xc) nonspecific error. N*  XIn a Normal Mode, the storage capacity parameter is optionally used by each of two DTAM protocol machines to indicate its own capacity to the peer. After the negotiation, if the storage capacity of the receiving DTAMPM is smaller than the largest segment of document information (see6.6) according to the checkpoint rule, the sending DTAMPM shall not transfer the document and DPEXCEPTION indication should be issued to the sending DTAM user. 9.17XDUEXCEPTIONREPORT service  XThe userexception reporting service permits a DTAM user to report an exception condition. XThe detailed definition of this service is for further study. 9.18XReliable transfer support service  XReliable transfer support service provides the communication secured as DTAM functionalities. XTwo types of Reliable Transfer Mode are defined as follows: X1) Reliable transfer mode 1'  X In this mode, the DTAMServiceprovider performs the reliable transfer of a document but, in case of problem, it will interrupt the transfer and indicate to the user that the transfer has not been completed. The user will then have the responsibility to start a new transmission by using the DTRANSFER request primitive with the appropriate parameters.' X2) Reliable transfer mode 2  X In this mode, the DTAMServiceprovider performs the complete reliable transfer of a document. If the transfer is interrupted, the recovery is under the responsibility of the DTAMPM. If the document is not transferred within the transfertime, this will be indicated to the user.'