Title: 3270 MQBridge

We are using the 3270 Bridge in CICS with the MQSeries bridge exit.  The user application abends ASP7 in CICS which points to a syncpointing error.  My initial investigation points to the BRXA_CALL_FOR_SYNC parameter in the BRXA area, but I fail to see how these parameters are changed as it is built into the Bridge Exit Area.  From the system dump:

BRXA.00088 1BCB20A8 Bridge Exit Area                           
                                                               
   0000  6EC2D9C1 D9C5C140 00000038 00000130  *>BRAREA ........*
   0010  1BCB20E0 000000B4 1BCB2194 00000051  *...\.......m....*
   0020  1BE70008 0000075B 00000000 00000000  *.X.....$........*
   0030  00000000 00000000 6EC2D9E3 D9C1D5C1  *........>BRTRANA*
   0040  C3D2C2D9 C9D4C9F5 C9D4C9F5 40404040  *CKBRIMI5IMI5    *
   0050  C6C9C9D4 C9F5F0F2 C5F0F2F0 F5F0F140  *FIIMI502E020501 *
   0060  00000000 00000000 E3C4D5D5 C6E9F2C4  *........TDNNFZ2D*
   0070  000001F4 D0C1C1C3 0000C003 00180050  *...4}AAC..{....&*
   0080  00200050 C3E2D840 D9C2C1C4 40404040  *...&CSQ RBAD    *
   0090  40404040 B7C9344D A726CC81 40404040  *    .I.(x..a    *
   00A0  40404040 40404040 40404040 40404040  *                *
   00B0  40404040 40404040 40404040 E8C20000  *            YB..*
   00C0  00000000 00000000 00000000 1BCB0040  *............... *
   00D0  0000003C 00000000 00000000 00000000  *................*
   00E0  00000000 00000000 00000000 6EC2D9C3  *............>BRC*
   00F0  D6D4D4C1 F0F0F0F4 D4C2D9C7 0018ECF8  *OMMA0004MBRG...8*
   0100  0000060F 00000000 00000000 00000000  *................*
   0110  00017DC5 D5D50000 00000000 C9D4C9F5  *..'ENN......IMI5*
   0120  C5D54000 C6C9C9D4 C9F5C100 00000000  *EN .FIIMI5A.....*
   0130  FFFE0000 0000D5D5 E8D5D5E8 00        *......NNYNNY.   *

Any suggestions?



***************************************************************************
* This email and any files transmitted with it are
* confidential and intended solely for the use of the
* individual or entity to whom they are addressed.
* Please note that any views or opinions presented in this
* email are solely those of the author and do not
* necessarily represent those of Riyad Bank.
* Finally, the recipient should check this email and any
* attachments for the presence of any viruses.
* Riyad Bank accepts no liability for any damage caused
* by any virus / error transmitted by this email." *
***************************************************************************

Reply via email to