LINC Programming Reference Manual - Public Support Login - Unisys

Procedure
To send an OLTP transaction:
AUTO; WRITE and AUTO; WRITE&CLEAR
1. Nominate an External Auto Ispec or an OLTP View Ispec with the AUTO.ENTRY;
command (GLB.OLTPTYPE and GLB.OLTPSUBTYPE are set automatically for OLTP
View Ispecs).
2. Set GLB.DESTHOST to GLB.OLTP.
3. Set GLB.DESTINATION to the OLTP Service you require.
4. Set GLB.OLTPSUBTYPE (if it is not an OLTP View Ispec) to the value required by the
OLTP Service specified. For a LINC Service, this will be as follows.
$ For UNIX and OS 2200 based LINC Systems:
$ For MCP based LINC Systems:
The values entered in ispec, system, andwindow refer to the destination LINC
System.
5. Use AUTO; logic commands to prepare the data items in the message.
6. Use the AUTO; WRITE logic command to send the message.
Results
If GLB.DESTHOST does not specify an OLTP transaction but your AUTO.ENTRY
command specified an OLTP View Ispec, a runtime error occurs, GLB.STATUS is set to
five asterisks (*****), and GLB.HUBSTATUS is set to an appropriate error message.
If the OLTP transaction is processed successfully, GLB.STATUS contains spaces or DATA.
A DATA value indicates that there is a response message in the Auto Entry buffer .
If the processing on the OLTP Server is aborted and the transaction is using Two-Phase
commit, the client transaction will be immediately aborted (for more details, see the
ABORT; command).
If any other processing or OLTP exception is encountered, your LINC logic execution will
continue after the AUTO; WRITE command. Note the following points regarding these
exceptions:
$ GLB.STATUS will be set to five asterisks (*****), and GLB.HUBSTATUS will contain
the error code. GLB.STATUS and GLB.HUBSTATUS settings are described later in this
subsection.
$ The buffer is not changed by the AUTO; WRITE command. The buffer is cleared to
spaces by the AUTO; WRITE&CLEAR command.
v 1-35