A fix is available
APAR status
Closed as program error.
Error description
Customers have an MQ Process Definition that is created with the USRDATA parameter field containing blanks. But CICS is passing the USRDATA field like this: USRDATA(' , ') The comma is causing the problem and the CICS code adds the comma when (strlen(ptm->UserData) > 0) is true.This causes the follow message to be produced later on in execution: DFHMQ0705E CKBR 00063 Parameter at offset 178 in input string is invalid. We should also be getting a DFHMQ0784 message which should provide more details on the issue (bad parameter in USERDATA), but this message is not issued because there are no bad parameters. Customers are taking the defaults with no parameters. When the customer adds a parameter the problem goes away. Additional Symptom(s) Search Keyword(s): KIXREVSLY
Local fix
Specify at least one parameter in the MQ Process definition's USERDATA field, do not specify a blank USERDATA field.
Problem summary
**************************************************************** * USERS AFFECTED: All * **************************************************************** * PROBLEM DESCRIPTION: The CICS-WebSphere MQ bridge fails to * * start when its MQ process definition is * * specified with blank USERDATA and * * message DFHMQ0705E is written. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using the CICS-WebSphere MQ bridge, the bridge queue is defined to use an MQ Process definition with a blank USERDATA field. A message is sent to the bridge queue which should trigger the process to start the CICS-WebSphere MQ bridge, but instead message DFHMQ0705E is written and the CICS-WebSphere MQ bridge fails to start. DFHMQ0705 E mm/dd/yyyy hh:mm:ss IYCKZCET CKBR ttttt Parameter at offset 178 in input string is invalid.
Problem conclusion
The procedure which gets the input parameters to create the bridge start data has been amended to correctly handle a blank USERDATA field.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI21480
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-07-07
Closed date
2014-10-31
Last modified date
2015-03-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI22752 UI22753
Modules/Macros
DFHMQR0@
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 March 2015