Hi all, we're having problems with the Allocate verb when opening a connection.

Current setup is Windows 2008 Server R2 / HIS 2013

We're accesing via APPC from a 32 bits application.

We create an ALLOCATE message, send it through APPC() which returns primary_rc != AP_OK

Then we call GetAppcReturnCode() and get the following message: "Allocate verb has completed with primary return code Unsuccessful"

Is there any way to get further info on that? or some documentation? I've been searching online but can't seem to find anything related, looks like it's a problem with this client's specific installation.

Thanks!

Hi,

In order to get very deep information, please activate the HIS Traces.

1. Start --> All Programs --> Host Integration Server 2013 --> Trace Utility

2. Activate the traces

The traces are very technical, but they might help you.

MSDN Documentation : https://msdn.microsoft.com/en-us/library/dn192144.aspx

If you need more assistance, please let me know.

Best Regards,

Hi,

as Steve already said APPC API traces would show what the issue is.

The primary return code AP_UNSUCESSFUL for an ALLOCATE verb is pointing to a spefic error as described in our online documentation.

AP_UNSUCCESSFUL

Primary return code; the supplied parameter rtn_ctl specified
immediate (AP_IMMEDIATE) return of control to the TP, and the local LU did not
have an available contention-winner session.
With this parameter specified the ALLOCATE only completes successfully if the session is already bound and never enforces a session to be established.

Hope that helps

Manfred Mittermller

- MSFT -

• Proposed as answer by Manfred MittermüllerModerator 18 hours 30 minutes ago

Hi,

as Steve already said APPC API traces would show what the issue is.

The primary return code AP_UNSUCESSFUL for an ALLOCATE verb is pointing to a spefic error as described in our online documentation.

AP_UNSUCCESSFUL

Primary return code; the supplied parameter rtn_ctl specified
immediate (AP_IMMEDIATE) return of control to the TP, and the local LU did not
have an available contention-winner session.
With this parameter specified the ALLOCATE only completes successfully if the session is already bound and never enforces a session to be established.

Hope that helps

Manfred Mittermller

- MSFT -

• Proposed as answer by Manfred MittermüllerModerator Thursday, July 16, 2015 12:34 PM

Hi,

as Steve already said APPC API traces would show what the issue is.

The primary return code AP_UNSUCESSFUL for an ALLOCATE verb is pointing to a spefic error as described in our online documentation.

AP_UNSUCCESSFUL

Primary return code; the supplied parameter rtn_ctl specified
immediate (AP_IMMEDIATE) return of control to the TP, and the local LU did not
have an available contention-winner session.
With this parameter specified the ALLOCATE only completes successfully if the session is already bound and never enforces a session to be established.

Hope that helps

Manfred Mittermller

- MSFT -

• Proposed as answer by Manfred MittermüllerModerator Thursday, July 16, 2015 12:34 PM