Pathway/iTS TCP and Terminal Programming Guide

Designing Your Application
Compaq NonStop™ Pathway/iTS TCP and Terminal Programming Guide—426751-001
2-23
Designing Applications for Batch Processing
server classes if you ensure that the server program’s request and reply formats are
consistent for all requesters.
After you code and compile your server program, the server object code and library code
are shared among all processes of the same server class.
For information about designing and coding Pathway servers, refer to the NonStop™
TS/MP Pathsend and Server Programming Manual.
Designing Applications for Batch Processing
If your Pathway application includes batch processing, consider the different needs of
this type of processing in your design.
For example, you might code a Pathsend program that takes its input from a file rather
than from a terminal, then sends requests to a server to make updates to a database. This
program could be configured as a server, thus operating as a nested server. Its input file
might be TMF protected, and the Pathsend program might make updates to it.
An application that does several updates to a database, with each update coded as a
separate TMF transaction, could be slow when it performs these updates as a batch job
rather than performing them online. For batch processing, it is usually faster to group a
number of updates in a single transaction. However, if your batch jobs are very large,
note that you should not try to group more than about one thousand updates in one TMF
transaction.