In certain cases z/OS automation software is not catching messages produced by OSB.

In certain cases z/OS automation software is not catching messages produced by OSB.

book

Article ID: KB0090114

calendar_today

Updated On:

Products Versions
TIBCO Object Service Broker for z/OS -
Not Applicable -

Description

Resolution:
Description:
============
OSB messages all begin with a 10 character message identifier.
In the past this was followed by a dash, in R5.2 it is followed by a blank.
Automation that relies on the dash may no longer trap messages correctly.

Environment:
============
o OSB systems running on the z/OS platform

Symptoms:
=========
Messages may not be trapped by automation after upgrade to R5.2.

Cause:
======
OSB messages all begin with 10 character message identifier. In the past this was followed by a dash, in R5.2 it is followed by a blank.

This change was made to allow message ids to be more easily processed by z/OS SLIP processing.
In SLIP processing the message id is terminated by the first blank in the message.

Resolution:
===========
Modify z/OS automation rules to use only the first 10 characters of the message as the message id.

Issue/Introduction

In certain cases z/OS automation software is not catching messages produced by OSB.