Automatic breakpoint Invalid machine instruction when monitoring a COBOL program with CA Intertest for CICS VSE r 6.0 on a static call to MQSETENV?

book

Article ID: 7851

calendar_today

Updated On:

Products

CA InterTest - CICS CA InterTest - Batch CA InterTest VSE - CICS

Issue/Introduction

We are in the process of converting all of our MQ Cobol programs to connect to a MQ Server on Linux instead of the MQ Server on VSE. The MQ Server on VSE has been dropped from support. This was working fine until we try to use break points with CA INTERTEST for CICS r 6.0. It gets an 0C1 invalid machine instruction on the first of three static calls to MQSETENV.

A ==> CALL 'MQSETENV' USING MQSERVER-NAME
==> an invalid machine instruction code.
==>
==> Press PF1 for a detailed description.  

Environment

VSECICS

Resolution

The client created a IN25UEXI copybook with the signature below which resolved the problem. The IN25UEXI is use by CA Intertest for CICS VSE to drop monitoring on static calls to programs the user does not want to monitor.

*------------------------------------------------------------*
* CA-INTERTEST UEXI FOR VSE MQ CLIENT                      
*------------------------------------------------------------*
    IN25UEX CALL=MQSETENV,LENGTH=8
    MQSETENV CSECT
    DC   X'47F0F02814CEA106' 

 

MQPUT Calls are listed below
CALL 'MQSETENV' USING MQSERVER-NAME
CALL 'MQSETENV' USING MQ-USER-ID-NAME
CALL 'MQSETENV' USING MQ-PASSWORD-NAME

CALL 'MQCONN'
CALL 'MQOPEN'
CALL 'MQCLOSE'
CALL 'MQDISC'
CALL 'MQPUT'
CALL 'MQPUT'