IT12123: 0 BYTE FILE IS CREATED ON THE TRADING PARTNER SIDE WHEN USING THE CDCOPYTO SERVICE

si_52_build_5020500_interimfix_10
si_52_build_5020500_interimfix_10

APAR status

• Closed as program error.

Error description

• When connecting with a trading
  partner, the connection exceeded the maximum
  session remote number, since the
  FileGatewaySendMessage BP tries to reconnect automatically.
  After several attempts it succeeds. After reconnecting,
  the BP sends the file but with 0 bytes, as shown in
  the following trace:
  
  CDServerCopyToService: finished copying Database persisted
  document
  from Local Connect Direct
  [CLIENT_CDSERVER_ADAPTER_node1/tran141020150106_tv sa.in]
  to Remote Connect Direct
  [SNTDR_CD_GROUP//mailbox/Inbound/tran141020150106_tvsa.in] and
  bytes
  copied were [0]
  
  The transaction must be restarted manually to send
  the file to the trading partner.
  

Local fix

• STRRTC - 481243
  JMB / EM
  Circumvention:
  There are several possible workarounds below listed in
  preferred order:
  
  1. Disable AutoDetectTerminator feature by specifying
  AutoDetectTerminator=No in the Connect Direct CopyTo service.
  
  2. Change the transmission mode in the Connect Direct CopyTo
  service from BinaryMode=No to BinaryMode=Yes. This should ONLY
  be done if the source document is already in the text
  file format of the destination platform.
  
  3. Reconfigure Document Storage from DB to FS. This can be done
  "globally" by changing Sterling B2B Integrator's default
  document storage type; see
  defaultDocumentStorageType in jdbc.properties, or locally
  using the BP or protocol adapter setting.
  
  4. Increase the Execution Cycle for a designated queue to
  prevent processes from being preempted and requeued in the WAIT
  queue. Assign the BP to this queue.
  

Problem summary

• Users Affected:
  All
  
  Problem Description:
  During a restart of a database-backed TEXT document with
  content less than 32K, the payload is transmitted from the
  CDSA to the remote CD node as a zero-length (empty) file,
  resulting in the loss of data. When the content is greater
  than this, the destination file is missing the initial 32K of
  data.
  
  Platforms affected:
  All
  

Problem conclusion

• Resolution Summary:
  A code fix has been provided.
  
  Delivered In:
  5020500_10
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels

• R525 PSY

     UP