Sequence of requests

About this task

Each communication session must always start with an INIT request and end with a TERM request. There can be several requests between them.

When modifying the current plan, requests must be made as follows:
  1. With a series of requests, an MCP block is built containing all the necessary information required for one modification of the current plan.
  2. With an EXECUTE request, information in the MCP block is used to actually update the current plan data set.

Also, when modifying the current plan, you can make a series of requests that refer to the same occurrence. The first request identifies the occurrence, and following requests can modify data related to that occurrence without needing to specifically identify it each time. The program interface remembers what the current occurrence is. Similarly, the program interface remembers the current operation and, once identified, a series of requests can be made that refer to it.

Other requests can be made in any sequence except where specifically noted. For example, you can produce a list of records with one request, which you can follow with one or more requests that select records from the list.