The TCHECK function may be executed by the API (OPTCD=SYNC) or the transport user (OPTCD=ASYN). Completion and Error EventsĬompletion and error events occur when a TCHECK control function is executed. However, in asynchronous mode, the service function is generally issued in response to the event. In synchronous mode, the time relationship between the occurrence of an event (for example, the arrival of some data) and invocation of the corresponding service function (for example, TRECV) is unimportant. This mode requires use of exit routines, and requests are often issued under control of the IRB that runs the exit routine. Asynchronous mode applies when service requests are issued asynchronous with normal processing.Generally, the application program is running under control of a PRB.
Synchronous mode applies when service requests are issued synchronous with normal application program processing. Some sequences are shown in synchronous and asynchronous mode: An asynchronous event that causes an exit routine to be scheduled is labeled an indication. On the contrary with Visio you can manage as you like every UML diagram using the drag&drop feature it provides. An abnormal completion is indicated by error. Its successful completion is simply labeled a completion. The invocation of a function is labeled a request. The vertical lines delineating the transport interface represent the endpoint from the perspective of the transport user and transport provider.Īll interactions between the local transport user and the API are shown in terms of the service functions executed, and their normal or abnormal completions: The vertical lines delineating the transport provider represent the Transport Service Access Points (TSAPs) for the local and remote transport user. Also, the transport interface between the remote transport provider and the peer transport user (Remote TU) is not shown. The transport provider is shown as a single entity, although, in actuality, there is a local and remote entity between which the protocol exchanges take place. OverviewĮach time-sequence diagram shows a local transport user (Local TU) issuing requests and responding to events at the local transport interface (API), and a transport provider (TP) receiving request and response primitives, and issuing indication and confirm primitives. It includes these sections:ĭescribes the labelling and illustration techniques used in the diagrams. Founded in 2014 with the purpose to improve the efficiency when creating and working with sequence diagrams by combining text notation scripting and drawing by clicking and dragging in the same model. #Sequence diagram visio software#
This appendix contains sequence diagrams showing the relationship between the API service requests issued at an endpoint and service primitives issued to or by the transport provider. is an online tool / software for creating UML sequence diagrams. Local Endpoint Management (Initialization)
0 kommentar(er)
