Troubleshooting › Cross-System Command Processing Problems › Cross-system Command Responses Not Returned to the Local System

Cross-system Command Responses Not Returned to the Local System

Try these possible solutions:

• If CA MIC is using extended MCS (EMCS) consoles, then verify that the product on the target system supports EMCS consoles. For example, earlier releases of CICS, JES2, and CA Look may not support this.

  Change GCMINIT EXTCON=NONE. This forces CA MIC to use subsystem consoles. Try the command again.

• Verify that CA MIC is synchronized on all systems. For example:

  F MIM,D SYS
  

  • Look in the syslog on the target system. Is the command reissued on the target system?
  • Look for any CA MIC error messages on the local or target system, for example, messages MIM3167, MIM3169, and MIM3066.

    If the MIM3066 message was issued, then this indicates that a target console was not available. You may have run out of available target consoles. Check GCMINIT CONSLIST and SETOPT MAXCONS and MINCONS values. Do a D C,L or D C,SS if you are using subsystem consoles. Check to see that the consoles specified in CONSLIST are available to CA MIC. If MAXCONS or MINCONS is used, then check to see if any subsystem consoles are available. Also, look for error messages indicating that there may be problems allocating consoles.

  • Verify the source of the cross-system commands. Some sources do not receive responses to cross-system commands. For example, batch jobs and internal sources do not “receive” responses to cross-system commands. In these cases, the command executes on the target system and the response is returned to the original systembut not to the issuing source. In most cases, the response returns to the log of the originating system.
  • Check for CA MIC exits.

    Issue the following command on all systems to verify whether any CA MIC exits are active:

    F MIM,D EXIT