Resolution:
Version 2:
----------
A system abend D78 reason code 4 (SD78-4) may occur in the target Execution Environment (EE) when a session is cancelled as a result of action taken in the Data Object Broker region or by a force canceluser request in the EE or lost terminal connection.

HDRSBOCP runs under a z/OS "Operator" TCB (HOPEnnnn) and uses a z/OS Create Interruption Request Block (CIRB) request to schedule termination of the user session. The cancel request then is dispatched to an "Interpreter" z/OS TCB (HINTnnnn) task. The abend happens when a storage freemain inside SVC3 exit processing is issued against the storage acquired under TCB HOPERnnn as part of the CIRB processing request. z/OS 1.11 then issues the SD78-4 abend.

A D78 RC4, as defined by IBM "z/OS MVS System Codes" manual means:
"A FREEMAIN request was specified for local system queue area (LSQA) virtual storage that is associated with a task. However, the virtual storage area specified is not associated with the task."

Environment:
============
* problem happens at z/OS 1.11 or later releases
* cancel must use z/OS CIRB (SVC x'2B') processing to schedule the session termination

Symptoms:
=========
Typical symptoms include EE joblog messages such as:

S6BDR002E ERROR=SD78  UNKNOWN .UNKNOWN +0300E VERSION=UNKNOWN
IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=D78  REASON CODE=00000004
    PSW AT TIME OF ERROR  070C1000   813BE7B0  ILC 2  INTC 0D
      NO ACTIVE MODULE FOUND                                  
      NAME=UNKNOWN                                            
      DATA  AT PSW  013BE7AA - 00181610  0A0D18CE  18FB180C    

Cause:
=====
There is a difference in Create Interruption Request Block (CIRB) processing behaviour under z/OS 1.11 and later z/OS releases which now results in a system SD78-4 abend.  

Resolution:
=========
In order to accomodate the new CIRB cleanup behaviour under z/OS 1.11 and later releases, TIBCO Object Service Broker for z/OS IRB processing is being revised to use the branch entry macro call to CIRB with the target TCB address set.

Customers requiring this fix should open a service request with TIBCO Support and request notification for the OSBZ-1253 fix. You may also subscribe to Late Breaking News for TIBCO Object Service Broker for z/OS to receive notification of the upcoming Hotfix containing this fix.

History:
========
Oct 15, 2010 -original solution issued
Oct 21, 2010 -revision 2 issued to remove reference to IBM apar II14548 and replace with TIBCO problem report OSBZ-1253

References:
==========
TIBCO incident:  OSBZ-1253