OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-14
API Troubleshooting Example
The screen shows that the APS_ATTACH_ call did send a register request to the OSI
manager process to establish a connection. That request failed; the reason given is
“Loc(al) Name Not Found.”
You can also see that $OMGR is configured for four APPL object entries. The next step
is to look at those entries.
The SCF command
names entry $omgr.#appl.*
displays the following:
Notice that there is no application name configured for LOCALZ, but there is a name
configured for LOCALX. Look back at the Inspect log. Notice that the application name
(LOCAL1.ZAPPL-NAME) that the APS_ATTACH_ call was posted against is specified
as LOCALZ.
Step 4: Correct the Problem
The application name in either the application code or the configuration needs to be
corrected. The solution for this example is to modify the application name
LOCAL1.ZAPPL-NAME to LOCALX in the application code.
Step 5: Return to the Inspect Session Log
Now run the application again with the change, using Inspect. Before the following
typical line of code (remember that when the service_id is omitted, it defaults to a value
of 5 for the Session Layer):
status := APS_ASSOC_ATTACH_ ( cepi_1
, api_environment
, local_appl_1
);
the Inspect command
L5HALDO-d local_appl_1.zappl^name
displays the following:
Notice that now the application structure for local1.zappl^name has been changed to
LOCALX.
OSIAS Names ENTRY \MARS.$OMGR.#APPL.*
ENTRY
$OMGR.#APPL.LOCALL $OMGR.#APPL.REMOTEL $OMGR.#APPL.REMOTEX
$OMGR.#APPL.LOCALX
LOCAL1.ZAPPL^NAME=
ZLEN= 6
ZC=
BYTE[0]= "LOCALX"