Resolution:
Description:
============
In the TIBCO Adapter(TM) for IBM AS/400, a publish service is configured. When there is a message published from the AS/400, in the adapter log there are TAS400-0351 warning messages and the output message includes some unwanted header information.

Environment:
==========
All adapter versions
  
Symptoms:
========
The adapter log looks like following:

Info [OutMsg] TAS400-0351 Received message from data queue ACSCUPPLMA in library TIBCODTA.                                                                      
Info [Publish] TAS400-0451 Publisher UpdatePlayerMaster received message. tracking=#qikcOV7LzoMO2kKxu4/UrtW-2l2#                                                
Warn [Marshall] TAS400-0907 Variable ACCTCN was set to default value due to error Low-order nibble of the byte at array offset 4 is not valid.  Byte value: A3..
Warn [Marshall] TAS400-0907 Variable AHGTCN was set to default value due to error Low-order nibble of the byte at array offset 1 is not valid.  Byte value: A2..
Warn [Marshall] TAS400-0907 Variable AWTCN was set to default value due to error Low-order nibble of the byte at array offset 1 is not valid.  Byte value: D5..  
Warn [Marshall] TAS400-0907 Variable X51CN was set to default value due to error Low-order nibble of the byte at array offset 5 is not valid.  Byte value: 40..  
Warn [Marshall] TAS400-0907 Variable X52CN was set to default value due to error Low-order nibble of the byte at array offset 5 is not valid.  Byte value: 40..  
Warn [Marshall] TAS400-0907 Variable JNBRCN was set to default value due to error High-order nibble of the byte at array offset 5 is not valid.  Byte value: 0F.
Warn [Marshall] TAS400-0907 Variable TMCTCN was set to default value due to error Unparseable date: "MU      ".                                                  
Warn [Marshall] TAS400-0907 Variable TMLDCN was set to default value due to error Unparseable date: "

In the TIBCO ActiveMatrix BusinessWorks Adapter Subscriber activity, the output XML message includes some header information such as job user, version and job name which isn’t expected and thus causes the confusion.

Cause:
=====
This issue will happen in following scenario:

1). Select the “Shared Data Queue” when creating the Pub Service.
2). Uncheck the option in Designer without refreshing the AS400 server.
3). Publish the message to the Data Queue with the TIBCO PUBLISHER program from the AS400. We can see the same issue on the BW side and the same warning messages in the adapter log.

The root cause of the issue is the inconsistent configuration between the TIBCO project and the AS400 data queue.

Resolution:
========
Reconfigure the TIBCO project and make sure that the “Shared Data Queue” is checked. Alternatively, refresh the data queue configuration on the AS400 side with the new project.