RP/TMA 8.1 (SNA/CRM) - CRM RC should not = 0 when CRM is stopped due to an error.

(Doc ID 777637.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo Mainframe Adapter for SNA - Version: 8.1 to 8.1
Information in this document applies to any platform.
Information in this document applies to any platform

Goal

DESCRIPTION:
When CRM is stopped due to run time mistakes like:

+ERROR: Attempt to connect as second master refused!

Or

ERROR: Attempt to connect with incorrect CRM name (EAM812) refused!

Etc

The return code value is RC=0 as you can see:

started 2006-12-15 15:42:56.584 UTC
 [CRM] CRM 81.x, Jun  9 2004 03:52 Build TMACRM
0Statistics for Remote Link EAM812
   Input conversations =     0, messages =       0, bytes =                        0
  Output conversations =     0, messages =       0, bytes =                        0
-BEA Tuxedo Mainframe Adapter for SNA Resource Manager
 ended 2006-12-15 15:57:46.273 UTC, rc=0

When CRM is stopped due to critical task failure the return code value is RC=1

Customer would like the following behavior:

00  normal stopped by calling CRMDOWN
01  error during stopping by calling CRMDOWN
------------------------------------------------------------------------------------------
02  errors due to run-time mistakes like "second master refused" and so on

03  could be used for other errors during run-time of CRM

But in the first step they want to fix the wrong return code RC=0 for run-time mistake:
Replacing it by RC = 02. If it is just RC=01, it could be acceptable too.

Environment: TMA SNA 8.1 RP5 for CRM and gateway - CRM runs on Z/OS 1.4 and CICS TS 2.2, Gateway on HP UX 11.23

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms