TRANSFER Programming Manual
How to Use INSPECT with the Agent Tester
A Sample TRANSFER Program
40970 Tandem Computers Incorporated 11–5
Step 7: Display the Agent Linkage Information screen and accept linkage information.
The Agent Linkage Information screen is:
T R A N S F E R A G E N T T E S T D R I V E R
-------------------------------------------------------------------------------
AGENT LINKAGE INFORMATION
Sender: BLOW_JOE
Sender application ID 0000 Agent selector 0000 CERTIFIED flag N
Recipient:
ROE_JANE @PRUNE
Subject string:
test message #1
Agent name: sample-agent
Agent data: gato_tina
Error return value 00000
Error message:
F1: call the agent F2: return to previous screen
The Agent Linkage Information screen shows the recipient name and the subject of the
message. The user fills in the name of the agent to be called and any additional data to
be sent to the agent (in this case, the agent being called is the sample agent, so the
agent data is the name of the person to whom the sample agent will forward the
message).
Step 8: Call the agent.
If the user presses F1 and there are no errors, the agent tester calls the agent and passes
it the linkage information.
How to Install the
Agent Tester
The source code for the agent tester is distributed on your SUT tape in the file
AGENTEST. The GCOB and GLNK copy libraries required by the agent tester are also
included.
Compile the AGENTEST source into the same SCREEN COBOL object library where
the agent to be tested resides. Then enter the appropriate PATHCOM commands to
configure the program into your TRANSFER system. If you are using a test system,
you can put the PATHCOM commands into the CUSTCNFG file before running
XCNFG. For more information, see the TRANSFER Installation and Management Guide.
How to Use INSPECT with
the Agent Tester
Enter the commands shown in Figure 11-1 to establish an INSPECT session with the
agent tester and your agent. In this example, the TCP is named test-TCP.
These instructions assume that you have two terminals named $MYTERM1 and
$MYTERM2, that your PATHMON process is named $MYPM, and that the terminal