MXDSK
Codes | Description |
|---|---|
MXDSK0000E Socket Header Data RETRIEVE Failed, EIBRESP(xxxxxxxxx) EIBRESP2(nnn). | Explanation: DBUGSOCK, the Code Debug CICS API child listener, was unable to retrieve the socket header record that is passed by the CICS Sockets listener assigned to the port reserved for use by the Code Debug CICS API. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer and have them verify that the TYPE=LISTENER parameter CSSTTYPE=KC was specified. The values of EIBRESP and EIBRESP2 are displayed. If the problem persists after the TYPE=LISTENER parameters have been verified and/or modified, then contact BMC Support. Module: DBUGSOCK |
MXDSK0001E TAKESOCKET call failed, Retcode=nnnn Errno=nnnn. | Explanation: DBUGSOCK, the Code Debug CICS API child listener, was unable to retrieve the socket header record that is passed by the CICS Sockets listener assigned to the port reserved for use by the Code Debug CICS API. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer and have them verify that the TYPE=LISTENER parameter CSSTTYPE=KC was specified. Retcode is the return code from the TAKESOCKET call and Errno is the error number from the TAKESOCKET call. If the problem persists after the TYPE=LISTENER parameters have been verified and/or modified, then contact BMC Support. Module: DBUGSOCK |
MXDSK0002E Listener Definition Error, refer to the Installation Guide. | Explanation: DBUGSOCK, the Code Debug CICS API child listener, has determined that the IP CICS Sockets Listener definition did not specify FORMAT=ENHANCED. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer and have them refer to the Code Debug CICS Installation and Configuration Guide and pay special attention to the ENHANCED Listener parameters CSTRANID=, MSGLEN=, and PEEKDAT= parameters. These parameters must be set to:
Module: DBUGSOCK |
MXDSK0003E Access Denied, uuuuuuuu Not Authorized For EXEC CICS SYSTEM SECURITYMGR. | Explanation: A NOTAUTH response was received by a CICS SYSTEM SECURITYMGR call in DBUGSOCK, the Code Debug CICS API child listener. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, you should ensure that any user attempting to access the Code Debug CICS API has sufficient authority to execute the EXEC CICS SYSTEM SECURITYMGR command. Module: DBUGSOCK |
MXDSK0004E Socket SEND failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket SEND call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the SEND call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0005E Socket READ failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket READ call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the READ call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0006E Socket SHUTDOWN failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket SHUTDOWN call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the SHUTDOWN call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0007E Socket CLOSE failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket CLOSE call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the CLOSE call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0008I CICS in shutdown, socket session (task nnnnn) is being terminated. | Explanation: CICS is in shutdown. The socket session associated with the DBUGSOCK, the Code Debug CICS API child listener, task displayed in the message is being terminated. System Action: The socket connection is closed and the child listener task ends. User Response: None. Module: DBUGSOCK |
MXDSK0009E Length of initial contact data for ENHANCED Listener Must Be 61. | Explanation: DBUGSOCK, the Code Debug CICS API child listener, has determined that the IP CICS Sockets Listener definition has specified FORMAT=ENHANCED. The length of the initial contact data must be 61 bytes. This normally indicates an unauthorized attempt to use the Code Debug CICS API. System Action: The socket connection is closed and the child listener task ends. User Response: A non-BMC client may be attempting to connect to the Code Debug CICS API using the transaction specified in the CSTRANID parameter. If the problem persists with a valid BMC client, contact BMC Support. Module: DBUGSOCK |
MXDSK0010E Invalid initial contact data detected, Reason=nn:mmmm | Explanation: DBUGSOCK, the Code Debug CICS API child listener, has determined that the initial contact data expected is incorrect. This normally indicates an unauthorized attempt to use the Code Debug CICS API. System Action: The socket connection is closed and the child listener task ends. User Response: A non-BMC client may be attempting to connect to the Code Debug CICS API using the transaction specified in the CSTRANID parameter. Contact your Code Debug CICS installer. If the problem persists, contact BMC Support and ensure you have the value of the Reason=nn:mmmm available. Module: DBUGSOCK |
MXDSK0011E Current support is limited to IPv4 addresses only. | Explanation: This version of DBUGSOCK, the Code Debug CICS API child listener, only supports IPv4 socket descriptors. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer. Make sure that the socket listener being used has been defined with AF=INET. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0012I Socket has been closed by partner, socket session (task nnnnn) ending. | Explanation: The partner communicating with DBUGSOCK, the Code Debug CICS API child listener, has closed the socket prematurely. System Action: The child listener task ends. User Response: None. Module: DBUGSOCK |
MXDSK0013E Socket SELECTEX failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket SELECTEX call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the SELECTEX call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0014E Socket CONNECT failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket CONNECT call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the CONNECT call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0015E Socket INITAPI failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket INITAPI call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the CONNECT call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0016E Socket SOCKET failed, Retcode=nnnn Errno=nnnn. | Explanation: A socket SOCKET call failed in DBUGSOCK, the Code Debug CICS API child listener. System Action: The socket connection is closed and the child listener task ends. User Response: Contact your Code Debug CICS installer to investigate the IP CICS Sockets return code and errno from the CONNECT call. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0017I Code Debug shutdown, socket session (task nnnnn) is being terminated. | Explanation: Code Debug CICS is being shut down. The socket session associated with the DBUGSOCK, the Code Debug CICS API child listener, task displayed in the message is being terminated. System Action: The socket connection is closed and the child listener task ends. User Response: None. Module: DBUGSOCK |
MXDSK0018E Access Denied, uuuuuuuu Not Authorized For EXEC CICS INQUIRE TRANSACTION. | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. DBUGSOCK, the Code Debug CICS API child listener, has attempted to validate this transaction. The EXEC CICS INQUIRE for the transaction failed, most probably caused by the user not having sufficient authority to execute this command. Program DBUGSOCK should not be secured and the userID associated with this socket task must have sufficient authority to issue EXEC CICS INQUIRE and EXEC CICS VERIFY commands. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: If the installer has elected to not secure access to the services on this port, then the user they establish for transactions on this port must have sufficient authority to access this transaction and program XDPIMIRS. This user must also have authority to execute all EXEC CICS commands that are normally issued by Code Debug CICS. Authority for this transaction and programs DBUGSOCK and XDPIMIRS should be the same as for the XPED or XPRT transactions. Module: DBUGSOCK |
MXDSK0019E Access Denied, Transaction tttt Has Not Been Defined. | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. The settings must be set to specific values. If the transaction has not been defined, this is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0020E Access Denied, Transaction tttt Is Not Associated With Program XDPIMIRS. | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. The transaction must be associated with program XDPIMIRS. If the transaction has not been associated with program XDPIMIRS, this is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0021E Access Denied, CICS INQUIRE TRANSACTION(tttt) Failed. | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. The EXEC CICS INQUIRE TRANSACTION call failed for a reason other than NOTAUTH or NOTDEFINED. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0022E Access Denied, Transaction tttt Must Be Enabled. | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. The transaction must be defined and enabled. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0023E Access Denied, Transaction tttt Must Run In TASKDATAKEY(CICS). | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. The transaction must be defined and TASKDATAKEY (CICS) specified. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0024E Access Denied, Transaction tttt Must Run In TASKDATALOC(ANY). | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. The transaction must be defined and TASKDATALOC(ANY) specified. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0025E Access Denied, QUERY SECURITY Failed EIBRESP(xxxxxxx) EIBRESP2(nnn). | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. This transaction must be defined and secured for READONLY access. Any user of the Code Debug CICS API must have the ability to perform an EXEC CICS QUERY TRANSACTION. The EXEC CICS QUERY SECURITY call failed. The CICS EIBRESP and EIBRESP2 fields are displayed. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: Review the EIBRESP and EIBRESP2 values to determine the cause of failure. This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, you should ensure that any user attempting to access the Code Debug CICS API has sufficient authority to execute the EXEC CICS QUERY SECURITY command. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0026E Access Denied, uuuuuuuu Is Not Authorized To Use thisXDSK0060E API. | Explanation: If you wish to use Code Debug Eclipse, the Code Debug CICS Debugging API is required. You can use the default of XPGD, or use a global override (operand XPGDTXNM) to specify a transaction identifier of your own choice. This transaction must be defined and secured for READONLY access. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message indicates that an unauthorized user was attempting to access the Code Debug CICS component of Code Debug Eclipse. Module: DBUGSOCK |
MXDSK0027E Access Denied, Program XDPIMIRS Has Not Been Defined. | Explanation: The Code Debug CICS program XDPIMIRS must be defined to CICS. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0028E Access Denied, INQUIRE PROGRAM Failed EIBRESP(xxxxxxx), EIBRESP2(nnn). | Explanation: The EXEC CICS INQUIRE PROGRAM (XDPIMIRS) call failed for a reason other than PGMIDERR. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. If you are in the process of installing and testing Code Debug Eclipse, you should ensure that any user attempting to access the Code Debug CICS API has sufficient authority to execute the EXEC CICS QUERY SECURITY command. If the problem persists, contact BMC Support. Module: DBUGSOCK |
MXDSK0029E Access Denied, Program XDPIMIRS Must Be Enabled. | Explanation: The Code Debug CICS Sockets programs must be defined and STATUS(ENABLED) specified. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0030E Access Denied, Program XDPIMIRS Must Be Defined As Assembler. | Explanation: The Code Debug CICS program XDPIMIRS must be defined and LANGUAGE(ASSEMBLER) specified. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The transaction is rejected. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0031E Access Denied, Program XDPIMIRS Must Run In EXECKEY(CICS). | Explanation: The Code Debug CICS program XDPIMIRS must be defined and EXECKEY(CICS) specified. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0032E Access Denied, Program XDPIMIRS Must Run In DATALOC(ANY). | Explanation: The Code Debug CICS program XDPIMIRS must be defined and DATALOC(ANY) specified. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: DBUGSOCK |
MXDSK0033E Access Denied, uuuuuuuu Not Authorized For EXEC CICS INQUIRE PROGRAM. | Explanation: A NOTAUTH response was received by a CICS INQUIRE PROGRAM call in DBUGSOCK, the Code Debug CICS API child listener. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed and the child listener task ends. User Response: This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, you should ensure that any user attempting to access the Code Debug CICS API has sufficient authority to execute the EXEC CICS INQUIRE PROGRAM command. Module: DBUGSOCK |
MXDSK0034E CSS Conv Serv Err RC=xxxxxxxx, RS=yyyyyyyy, CUNB RC=rrrrrrrr, ssssssss. | Explanation: During the initialization process of DBUGSOCK, the BMC AMI Common Shared Services call to IBM Conversion Services failed. The CSS return code is xxxxxxxx and the reason code is yyyyyyyy. The Conversion Services return and reason codes are rrrrrrrr, ssssssss. System Action: The Code Debug Eclipse or Topaz Workbench debugging session will be terminated. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0035E TAKESOCKET HCI call failed........... Retcode=xxxxxxxx Errno=yyyyyyyy. | Explanation: During the initialization process of DBUGSOCK, the TAKESOCKET call to CICS TCP/IP Sockets interface failed. The return code is xxxxxxxx and the error number is yyyyyyyy. System Action: The Code Debug Eclipse or Topaz Workbench debugging session will be terminated. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0036E GETCLIENTID call failed, Retcode=xxxxxxxx Errno=yyyyyyyy. | Explanation: During the initialization process of DBUGSOCK, the GETCLIENTID call to CICS TCP/IP Sockets interface failed. The return code is xxxxxxxx and the error number is yyyyyyyy. System Action: The Code Debug Eclipse or Topaz Workbench debugging session will be terminated. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0037E UNIX Conversion Services Retry Failed RC=xxxxxxxx, Reason=yyyyyyyy. | Explanation: During the initialization process of DBUGSOCK, the call to IBM Conversion Services failed. The return code is xxxxxxxx and the reason code is yyyyyyyy. System Action: The Code Debug Eclipse or Topaz Workbench debugging session will be terminated. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0038I Trans ID cannot be entered from a terminal. | Explanation: Transactions XSOC and XSRE are not intended to be run from a terminal. If run from a terminal, the above message will be displayed. System Action: None. User Response: Do not attempt to run this transaction from a terminal. Module: DBUGSOCK, DBUGREMS |
MXDSK0039E DBUGSOCK cannot run in a region defined as a CPSM Routing region. | Explanation: While attempting to route transaction XSOC to a region (an AOR) in the same LPAR in which the TOR is running, no region could be detected that had Code Debug CICS active. This would mean that XSOC (DBUGSOCK) would have to run in the TOR, which is not a desirable situation. System Action: The DBUGWRAM (EYU9WRAM) task is terminated to cause the socket to close. User Response: Contact your Code Debug CICS support group to ensure at least one region (an AOR) in the LPAR in which the TOR is running has Code Debug CICS installed and active. Module: DBUGWRAM |
MXDSK0040E XDPCICSE Proc Bypassed, Commarea Length Error. | Explanation: The Commarea being passed to the Code Debug CICS Sockets security exit program (XDPCICSE) is not the correct length. To prevent corruption of the data passed, XDPCICSE will simply return to the caller without performing additional processing. System Action: None Taken. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). The first indication of unauthorized access is that the common area length is not what the exit expects. The initial request for services is requested by the BMC AMI Common Shared Services Server, which sends an initial contact message to the port defined by the installer. This length is fixed and should be specified in the MSGLEN parameter of the Listener definition. If you are in the process of installing and testing Code Debug Eclipse, make sure that you have specified the correct value for MSGLEN and you have defined the CICS Listener as ENHANCED. Module: XDPCICSE |
MXDSK0041E XDPCICSE Access Denied, Initial Contact Data Is Invalid. | Explanation: The Commarea being passed to the Code Debug CICS Sockets security exit program (XDPCICSE) has failed the first level syntax check. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). An indication of unauthorized access is that the initial contact data does not pass an initial syntax check. The initial request for services is requested by the BMC AMI Common Shared Services Server, which sends an initial contact message to the port defined by the installer. This message has a fixed format, and the initial syntax check of the message has failed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you have specified the correct port in your HCIxx PARMLIB member. If you have, then this is an indication of an unauthorized user attempting to connect to this port. Module: XDPCICSE |
MXDSK0042E XDPCICSE Access Denied, Transaction Mismatch, CSTRAN=tttt, CSS Server=xxxx. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction associated with the socket against the transaction sent in the initial contact message. The transactions do not match, the socket definition CSTRAN= parameter setting is tttt, and the initial contact message transaction is xxxx. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). An indication of unauthorized access is that the initial contact transaction identifier does not match the CSTRAN= parameter of the socket definition. The initial request for services is requested by the BMC AMI Common Shared Services Server Configuration File. This should match the transaction id specified in the CSTRAN= parameter of the Socket Listener definition. If the definitions are correct, then this is an indication of an unauthorized user attempting to connect to this port. BMC AMI Common Shared Services Server, which sends an initial contact message to the port defined by the installer. If you are in the process of installing and testing Code Debug Eclipse, make sure that you have specified the correct transaction id in your Module: XDPCICSE |
MXDSK0043E XDPCICSE Access Denied, Transaction tttt Is Not Defined To CICS. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The transaction tttt has not been defined to this CICS region. In order to use Code Debug Eclipse, this transaction must be defined, and the settings must be set to specific values. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this transaction for this region and that any additional parameters are correctly specified. Module: XDPCICSE |
MXDSK0044E XDPCICSE Access Denied, Inquire for Transaction tttt Failed. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for transaction tttt failed, most probably caused by the user not having sufficient authority to execute this command. Program XDPCICSE should NOT be secured and the default user associated with this socket (we suggest using the USERID= parameter of the Socket listener definition) should have sufficient authority to issue EXEC CICS INQUIRE and EXEC CICS VERIFY commands. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that any users attempting to use Code Debug Eclipse have sufficient authority to issue EXEC CICS commands in general. You should also make sure that the default userID that will be active when XDPCICSE is accessed has at least authority to execute EXEC CICS INQUIRE and EXEC CICS VERIFY commands. Module: XDPCICSE |
MXDSK0045E XDPCICSE Access Denied, Transaction tttt, Program pppppppp Mismatch. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for transaction tttt indicates that it is associated with program pppppppp. This indicates an error in the transaction definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the transaction definition for transaction tttt is associated with program DBUGSOCK, not program pppppppp. Module: XDPCICSE |
MXDSK0046E XDPCICSE Access Denied, Transaction tttt is NOT Enabled. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for transaction tttt indicates that it is not enabled. This indicates an error in the transaction definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the transaction definition for transaction tttt specifies STATUS (ENABLED). Module: XDPCICSE |
MXDSK0047E XDPCICSE Access Denied, Transaction tttt Must Run In TASKDATAKEY(CICS). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for transaction tttt indicates that it is not defined to run in TASKDATAKEY(CICS). This indicates an error in the transaction definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the transaction definition for transaction tttt specifies TASKDATAKEY(CICS). Module: XDPCICSE |
MXDSK0048E XDPCICSE Access Denied, Transaction tttt Must Run In TASKDATALOC(ANY). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for transaction tttt indicates that it is not defined to run in TASKDATALOC(ANY). This indicates an error in the transaction definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The transaction is rejected. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the transaction definition for transaction tttt specifies TASKDATALOC(ANY). Module: XDPCICSE |
MXDSK0049E XDPCICSE Access Denied, Transaction tttt Is Secured. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for transaction tttt indicates that it is secured [RESSEC(YES)]. This indicates an error in the transaction definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the transaction definition for transaction tttt specifies RESSEC(NO). Module: XDPCICSE |
MXDSK0050E XDPCICSE Access Denied, Program DBUGSOCK Is Not Defined To CICS. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate program DBUGSOCK. The program has not been defined to this CICS region. In order to use Code Debug Eclipse, this program must be defined, and the settings must be set to specific values. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that you define this program for this region and that any additional parameters are correctly specified. Module: XDPCICSE |
MXDSK0051E XDPCICSE Access Denied, Inquire for Program DBUGSOCK Failed. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate program DBUGSOCK. The EXEC CICS INQUIRE for it failed, most probably caused by the user not having sufficient authority to execute this command. Program XDPCICSE should NOT be secured and the default user associated with this socket (we suggest using the USERID= parameter of the Socket listener definition) should have sufficient authority to issue EXEC CICS INQUIRE and EXEC CICS VERIFY commands. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that any users attempting to use Code Debug Eclipse have sufficient authority to issue EXEC CICS commands in general. You should also make sure that the default userID that will be active when XDPCICSE is accessed has at least authority to execute EXEC CICS INQUIRE and EXEC CICS VERIFY commands. Module: XDPCICSE |
MXDSK0052E XDPCICSE Access Denied, Program DBUGSOCK Is Not Defined As Assembler. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate program DBUGSOCK. The EXEC CICS INQUIRE for DBUGSOCK indicates that it has not been defined as Assembler. This indicates an error in the program definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the program definition for DBUGSOCK has LANGUAGE(ASSEMBLER) specified. Module: XDPCICSE |
MXDSK0053E XDPCICSE Access Denied, Program DBUGSOCK Is Not Enabled. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate program DBUGSOCK. The EXEC CICS INQUIRE for program DBUGSOCK indicates that it is not enabled. This indicates an error in the program definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the API has yet to be completed. Ensure that the program definition DBUGSOCK specifies STATUS (ENABLED). Module: XDPCICSE |
MXDSK0054E XDPCICSE Access Denied, Program DBUGSOCK Must Run In EXECKEY(CICS). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate program DBUGSOCK. The EXEC CICS INQUIRE for program DBUGSOCK indicates that it is not defined to run in EXECKEY(CICS). This indicates an error in the program definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the program definition for program DBUGSOCK specifies EXECKEY(CICS). Module: XDPCICSE |
MXDSK0055E XDPCICSE Access Denied, Program DBUGSOCK Must Run In DATALOC(ANY). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate the transaction to be started. The EXEC CICS INQUIRE for program DBUGSOCK indicates that it is not defined to run in DATALOC(ANY). This indicates an error in the program definition. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that the program definition for program DBUSOCK specifies DATALOC(ANY). Module: XDPCICSE |
MXDSK0056E XDPCICSE Access Denied, Verify Password For uuuuuuuu, CICS=dfhresp** Resp2=nn. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify the userID/password passed by Code Debug Eclipse. The EXEC CICS VERIFY call failed. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the user of Code Debug Eclipse has entered an invalid userID/password combination. The values of EIBRESP and EIBRESP2 are formatted and displayed. This message will be followed by message MXDSK0057E, which will display the response and reason codes returned by the External Security Manager (ESM). Module: XDPCICSE |
MXDSK0057E XDPCICSE Access Denied, Verify Password For uuuuuuuu, Resp=(nnnn) Reas=(mmm). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify the userID/password passed by Code Debug Eclipse. The EXEC CICS VERIFY call failed. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the user of Code Debug Eclipse has entered an invalid userID/password combination. The values of the response and reason codes returned by the External Security Manager (ESM) are shown. This message will be preceded by message MXDSK0056E that will display the EIBRESP and EIBRESP2 values. Module: XDPCICSE |
MXDSK0058E XDPCICSE Proc Bypassed, Commarea Format Does Not Conform To Listener Sec Exit. | Explanation: The Commarea being passed to the Code DebugCICS Sockets security exit program (XDPCICSE) does not appear to conform to the format passed by a CICS Sockets Listener when performing a Security Exit call. To prevent corruption of the data passed, XDPCICSE will simply return to the caller without performing additional processing. System Action: None taken. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Sockets security exit (XDPCICSE). The Code Debug CICS API requires the default listener, program EZACIC02, to be used. If you have written a custom listener for other processing, it should not be used for traffic on this port. Ensure you are using the default listener. Module: XDPCICSE |
MXDSK0059E XDPCICSE Proc Bypassed, Cannot Be Executed By A Terminal Related Task. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) cannot be executed by a terminal related task. To prevent corruption of the data passed, XDPCICSE will simply return to the caller without performing additional processing. System Action: None taken. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). The Code Debug CICS API cannot run as part of a terminal related task. Module: XDPCICSE |
MXDSK0060E XDPCICSE Access Denied, Code Debug API Requires CICS Enhanced Listener. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate selected Sockets Listener parameters. It has detected that the CICS Listener who is invoking XDPCICSE indicates that it is not an Enhanced Listener. This indicates a Socket Listener Definition error. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that FORMAT=ENHANCED is specified in the Listener definition. Module: XDPCICSE |
MXDSK0061E XDPCICSE Access Denied, Code Debug API Must Be KC (Task Control) Started. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate selected Sockets Listener parameters. It has detected that the CICS Listener who is invoking XDPCICSE indicates that the transaction to be started will not be started via a Task Control (KC) Start. This indicates a Socket Listener Definition error. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that CSSTTYP=KD is specified in the Listener definition. Module: XDPCICSE |
MXDSK0062E XDPCICSE Access Denied, Code Debug API Currently Only Supports Sockets IPv4 | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to validate selected Sockets Listener parameters. It has detected that the CICS Listener who is invoking XDPCICSE indicates that it is not an Address Family INET (IPv4) listener. At this time, the Code Debug CICS API only supports IPv4 sockets. This indicates a Socket Listener Definition error. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that the setup necessary for the Code Debug CICS API has yet to be completed. Ensure that AF=INET is specified in the Listener definition. Module: XDPCICSE |
MXDSK0063E XDPCICSE Access Denied, Verify Auth to region - uuuuuuuu, CICS=NORMAL-check ESM. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify the userID/password passed by Code Debug Eclipse. The EXEC CICS VERIFY call has returned a normal response, but the ESM response code was NOTAUTH. This indicates that the user of Code Debug Eclipse does not have authority to access the CICS region. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the user of Code Debug Eclipse does not have authority to access the CICS region. This message will be followed by message MXDSK0064E, which will display the response and reason codes returned by the ESM (External Security Manager). Module: XDPCICSE |
MXDSK0064E XDPCICSE Access Denied, esm message NOT AUTHORIZED PARTNER ESM Resp=(nnnn) Reas=(mmmm). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify the userID/password passed by Code Debug Eclipse. The EXEC CICS VERIFY call has returned a normal response, but the ESM response code was NOTAUTH. This message indicates that the user of Code Debug Eclipse does not have authority to access the CICS region. This is flagged as a security error and access to the TCP/IP Port is denied The ESM reason code is also displayed in case additional information may be obtained from that. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the user of Code Debug Eclipse does not have authority to access the CICS region. This message will be preceded by message MXDSK0063E that will display the Workbench userID that is trying to connect to CICS. Module: XDPCICSE |
MXDSK0065E XDPCICSE Access Denied for uuuuuuuu, UNKNOWN ESM codes, Resp=(nnnn) Reas=(mmmm). | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify the userID/password passed by Code Debug Eclipse. The EXEC CICS VERIFY call has returned a normal response, but received abnormal response and reason codes, returned by the External Security Manager (ESM). This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the user of Code Debug Eclipse has had access denied for an unfamiliar reason. The values of the ESM RESPONSE and REASON are formatted and displayed to help you resolve the issue. Module: XDPCICSE |
MXDSK0066E XDPCICSE Listener luuuuuuu no access- Query Sec response(xxxxxxx) RESP2 - nnnn. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify that the listener’s userID (luuuuuuu) has the authority to start transactions for the workbench userID (displayed in the following MXDSK0069E message), which is passed by Code Debug Eclipse. The EXEC CICS QUERY SECURITY RESCLASS ('SURROGAT') call failed. This message indicates that the listener does not have authority to start transactions for the user of Code Debug Eclipse. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the listener’s userID (luuuuuuu) does not have the authority to start transactions for the workbench userID (wuuuuuuu) passed by Code Debug Eclipse. This message will be followed by message MXDSK0069E that will display the workbench userID. You should investigate your External Security Manager rules for the DFHSTART surrogate class profile. Module: XDPCICSE |
MXDSK0067E XDPCICSE Listener luuuuuuu needs wuuuuuuu.DFHSTART to be READABLE-was nnnnnnuu. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify that the listener’s userID (luuuuuuu) has the authority to start transactions for the workbench userID (wuuuuuuu) passed by Code Debug Eclipse. The EXEC CICS QUERY SECURITY RESCLASS ('SURROGAT') call has found a matching ESM rule, but returned a value (nnnnnnnn) other than READABLE. It must be READABLE to be able to continue. This is flagged as a security error, and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the listener’s userID (luuuuuuu) does not have the authority to start transactions for the workbench userID (wuuuuuuu) passed by Code Debug Eclipse. The unacceptable value (nnnnnnnn) returned by the External Security Manager (ESM) is shown. Investigate your ESM SURROGAT profile for DFHSTART. Module: XDPCICSE |
MXDSK0068E XDPCICSE Access Denied for luuuuuuu - Inquire System RESP - nnnn RESP2 - mmmm. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to determine if security is in effect. The EXEC CICS INQUIRE SECURITYMGR failed, most probably caused by the user not having sufficient authority to execute this command. Program XDPCICSE should NOT be secured, and the default user associated with this socket (BMC suggests using the USERID= parameter of the Socket listener definition) should have sufficient authority to issue EXEC CICS INQUIRE and EXEC CICS VERIFY commands. This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message is an indication that all of the setup necessary for the Code Debug CICS API has yet to be completed. If you are in the process of installing and testing Code Debug Eclipse, make sure that the Code Debug listener’s userID (luuuuuuu) that will be active when XDPCICSE is accessed has sufficient authority to execute EXEC CICS INQUIRE and EXEC CICS VERIFY commands. Module: XDPCICSE |
MXDSK0069E XDPCICSE, XUSER=YES requires def for wuuuuuuu.DFHSTART in SURROGAT resclass. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify that the listener’s userID (displayed in the previous MXDSK0066E message) has the authority to start transactions for the workbench userID (wuuuuuuu) passed by Code Debug Eclipse. The EXEC CICS QUERY SECURITY RESCLASS ('SURROGAT') call has received an abnormal response code (displayed in the previous MXDSK0066E message). This is flagged as a security error and access to the TCP/IP Port is denied. System Action: The socket connection is closed. User Response: If the installer has elected to secure access to the services on this port, several additional checks are made in the Code Debug CICS Sockets security exit (XDPCICSE). This message indicates that the listener’s userID does not have the authority to start transactions for the workbench userID (wuuuuuuu) passed by Code Debug Eclipse. This message will be preceded by message MXDSK0066E that will display the RESP and RESP2 values. The most common error response will be NOTFOUND, and you should investigate your External Security Manager rules for the DFHSTART surrogate class profile. Module: XDPCICSE |
MXDSK0070E XDPCICSE Access Denied - cant use AES-128 decryption, XD code - n. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has attempted to verify the userID/password passed by Code Debug Eclipse using AES-128 decryption. If the XD code is 1, your hardware does not support KM instruction used during the decryption process. If the XD code is 2, AES-128 decryption has not been enabled at your site. System Action: The socket connection is closed. User Response: A second attempt will be made to validate your userID/password using a less secure method of encryption/decryption. Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: XDPCICSE |
MXDSK0071E XDPCICSE Proc Bypassed, Minimum listener message length is 61. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) has determined that the MSGLENGTH parameter in the sockets listener definition is less than 61. The minimum length is 61 if password validation is being used and 512 if pass phrase validation is being used. System Action: The socket connection is closed. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: XDPCICSE |
MXDSK0072E XDPCICSE Proc Bypassed, Syntax error in contact message, no slash (/) found. | Explanation: The Code Debug CICS Sockets security exit program (XDPCICSE) initial contact message contains a syntax error. A slash (/) was expected in the string and was not found. System Action: The socket connection is closed. User Response: This is most likely an error in the Topaz Workbench (Code Debug Eclipse) component. Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: XDPCICSE |
MXDSK0073I XDPCICSE Test Response, returning message length nnnn. | Explanation: This message will be displayed by the Code Debug CICS Sockets security exit program (XDPCICSE) when a user connects to a CICS region to begin a debugging session. The value nnnn displayed is the MSGLENGTH setting associated with the sockets listener being used to connect Topaz Workbench (Code Debug Eclipse) to the CICS region. System Action: None. User Response: None. This message will be followed by CICS IP Sockets message EZY1311E which can be ignored. Due to the limited message handling capabilities of the CICS IP Sockets Security Exit, this message cannot be suppressed, and it should be ignored when preceded by message MXDSK0073I. The following is an example of the sequence you will see: MXDSK0073I 15 Mar 2017 15:02:35 A01TS024 XDPCICSE Test Response, returning message length 61. EZY1311E 03/15/17 15:02:35 CICS TRANID XSOC NOT AUTHORIZED PARTNER INET ADDR=10.101.14.221 PORT= 52419 Module: XDPCICSE |
MXDSK0100I Forcing Code Debug session into this region. DBUGGBL load failed. | Explanation: DBUGSOCK (the socket handler) and DBUGWRAM (the Dynamic Transaction Routing interface running in the TOR) use an internal routing table utilizing storage acquired by the Code Debug CICS Service Provider. During processing, the Code Debug CICS global table (DBUGGBL) could not be loaded. The product will be unable to determine where XDPIMIRS (the debugging interface) will run, so it will force the LINK to XDPIMIRS to occur in the local region. System Action: None. User Response: The product may not have been properly installed. Ensure the product has been properly installed in the region. You should execute the XIVP transaction in this region to see if any initialization errors have been detected. If you are unable to determine why DBUGGBL could not be loaded, contact BMC Support. Module: DBUGSOCK |
MXDSK0101I Forcing Code Debug session into this region. No Service Provider Functbl. | Explanation: DBUGSOCK (the socket handler) and DBUGWRAM (the Dynamic Transaction Routing interface running in the TOR) use an internal routing table utilizing storage acquired by the Code Debug CICS Service Provider. During processing, the function table used to connect to the Code Debug CICS Service Provider was not available. The product will be unable to determine where XDPIMIRS (the debugging interface) will run, so it will force the LINK to XDPIMIRS to occur in the local region. System Action: None. User Response: A restart of the Code Debug CICS Service Provider may be necessary if this message is issued multiple times. If a restart of the Service Provider does not resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0102I Forcing Code Debug session into this region. No Service Provider ALET. | Explanation: DBUGSOCK (the socket handler) and DBUGWRAM (the Dynamic Transaction Routing interface running in the TOR) use an internal routing table utilizing storage acquired by the Code Debug CICS Service Provider. During processing, the ALET used to connect to the Code Debug CICS Service Provider was not available. The product will be unable to determine where XDPIMIRS (the debugging interface) will run, so it will force the LINK to XDPIMIRS to occur in the local region. System Action: None. User Response: A restart of the Code Debug CICS Service Provider may be necessary if this message is issued multiple times. If a restart of the Service Provider does not resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0103I Forcing Code Debug session into this region. Unable to getmain route table. | Explanation: DBUGSOCK (the socket handler) and DBUGWRAM (the Dynamic Transaction Routing interface running in the TOR) use an internal routing table utilizing storage acquired by the Code Debug CICS Service Provider. During processing, the storage could not be acquired. The product will be unable to determine where XDPIMIRS (the debugging interface) will run, so it will force the LINK to XDPIMIRS to occur in the local region. System Action: None. User Response: A restart of the Code Debug CICS Service Provider may be necessary if this message is issued multiple times. If a restart of the Service Provider does not resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0104I Forcing Code Debug session into this region. Unable to add route table ID. | Explanation: DBUGSOCK (the socket handler) and DBUGWRAM (the Dynamic Transaction Routing interface running in the TOR) use an internal routing table utilizing storage acquired by the Code Debug CICS Service Provider. During processing, the storage has been acquired, but the product received an error while trying to add the storage to a named list using the Service Provider NAMADD function. The product will be unable to determine where XDPIMIRS (the debugging interface) will run, so it will force the LINK to XDPIMIRS to occur in the local region. System Action: None. User Response: A restart of the Code Debug CICS Service Provider may be necessary if this message is issued multiple times. If a restart of the Service Provider does not resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0105E LINK to XDPIMIRS failed, EIBRESP(xxxxxxxx) EIBRESP2(yyyyyyyy). | Explanation: DBUGSOCK (the socket handler) and XDPIMIRS (the debugging interface) communicate via Channel/Containers. While trying to send a request from DBUGSOCK to XDPIMIRS for debugging services, the CICS LINK from DBUGSOCK to XDPIMIRS failed. The EIBRESP value is xxxxxxxx and the corresponding EIBRESP2 value is yyyyyyyy. The request for debugging services cannot be completed. System Action: None. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0106E GET for container MIRSRESP failed, EIBRESP(xxxxxxxx) EIBRESP2(yyyyyyyy). | Explanation: DBUGSOCK (the socket handler) and XDPIMIRS (the debugging interface) communicate via Channel/Containers. While trying to send a request from DBUGSOCK to XDPIMIRS for debugging services, DBUGSOCK was unable to GET data from container MIRSRESP. The EIBRESP value is xxxxxxxx and the corresponding EIBRESP2 value is yyyyyyyy. The request for debugging services cannot be completed. System Action: None. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0107E GET for container MIRSBTCB failed, EIBRESP(xxxxxxxx) EIBRESP2(yyyyyyyy). | Explanation: DBUGSOCK (the socket handler) and XDPIMIRS (the debugging interface) communicate via Channel/Containers. While trying to send a request from DBUGSOCK to XDPIMIRS for debugging services, DBUGSOCK was unable to GET data from container MIRSBTCB. The EIBRESP value is xxxxxxxx and the corresponding EIBRESP2 value is yyyyyyyy. The request for debugging services cannot be completed. System Action: None. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0108E Unable to acquire Code Debug for CICS BTCB for DBUGSOCK use. | Explanation: DBUGSOCK (the socket handler) and XDPIMIRS (the debugging interface) may be running on separate LPARs. During initial communication, DBUGSOCK was attempting to create an internal control block (BTCB), but received an error when attempting to do so. This is an internal product error. System Action: None. User Response: Contact BMC Support. Module: DBUGSOCK |
MXDSK0109E PUT for container XMLREQRESP failed EIBRESP(xxxxxxxx) EIBRESP2(yyyyyyyy). | Explanation: DBUGSOCK (the socket handler) and XDPIMIRS (the debugging interface) communicate via Channel/Containers. While trying to send a request from DBUGSOCK to XDPIMIRS for debugging services, DBUGSOCK was unable to PUT data to container XMLREQRESP. The EIBRESP value is xxxxxxxx and the corresponding EIBRESP2 value is yyyyyyyy. The request for debugging services cannot be completed. System Action: None. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |
MXDSK0110E PUT for container XMLREQDATA failed EIBRESP(xxxxxxxx) EIBRESP2(yyyyyyyy). | Explanation: DBUGSOCK (the socket handler) and XDPIMIRS (the debugging interface) communicate via Channel/Containers. While trying to send a request from DBUGSOCK to XDPIMIRS for debugging services, DBUGSOCK was unable to PUT data to container XMLREQDATA. The EIBRESP value is xxxxxxxx and the corresponding EIBRESP2 value is yyyyyyyy. The request for debugging services cannot be completed. System Action: None. User Response: Contact your Code Debug CICS administrator to resolve the issue. If unable to resolve the issue, contact BMC Support. Module: DBUGSOCK |