Condition codes
Value | Meaning |
|---|---|
0 | Normal completion |
4 | Warning condition; not necessarily an error |
8 | Exceptional condition |
12 | Error condition; operation not complete Possible reasons are
|
16 | Error condition |
20 | Severe error condition |
The IMFCC variable can be tested by commands in the EXEC that follow the IMFEXEC command. However, the IMFCC condition code is different for services that are dependent or services that are independent of CICS.
For services that are CICS-dependent (where CICS performs the task), the request is routed to the respective CICS system for processing. If the request is successfully scheduled, IMFCC is set to 0; if the request fails, IMFCC is set to 8. Either message FT037I or FT038W is written to the Journal log at this time. The final status of the service is written to the Journal log by messages FT401 through FT414. These messages are accompanied with explanatory text. CEMT is an exception; CEMT returns the actual CICS response to the log instead of issuing FTxxxx messages.
For services that not CICS-independent (services that do not require CICS to perform the task), a Service Request Block (SRB) is scheduled to the target CICS system to perform the processing. If the request is successfully scheduled, IMFCC is set to 0; if the request fails, IMFCC is set to 8. Either message FT037I or FT038W is written to the Journal log at this time. The final status of the service is written to the Journal log by messages FT401 or FT414. These messages are accompanied with explanatory text.
For more information about which services are CICS dependent and which are not, see BMC-AMI-Ops-Automation-for-CICS-functions-with-BBI-SS-PAS-to-CICS-communication and BMC-AMI-Ops-Automation-for-CICS-functions-without-BBI-SS-PAS-to-CICS-communication.