Messages › GDIF and ECMF Messages › MIM1200W

MIM1200W

DASD Data Integrity Health Check - GDIINIT PROCESS=SELECT detected

Reason:

During CA MII initialization, it was determined that GDIINIT PROCESS=SELECT was coded in the MIMINIT parmlib member or that the PROCESS parameter is defaulting to SELECT. Customers running CA MII in SELECT mode typically have many DASD data integrity exposures in their DASD data-sharing MIIplex. These exposures occur because system programmers rarely maintain accurate CA MII ENQ management definitions in the MIMQNAME parmlib member. This oversight causes many SCOPE=SYSTEMS ENQs to not be propagated across all MIIplex systems - each of which are a data integrity exposure. These DASD data integrity exposures can result in corrupted DASD data. Because of the critical nature of DASD data loss, CA MII issues this warning message to alert systems programmers that DASD data integrity exposures are likely to exist in their DASD sharing MIIplex. CA MII initialization continues.

Action:

We recommend that you set GDIINIT PROCESS=ALLSYSTEMS rather than PROCESS=SELECT. Running CA MII in ALLSYSTEMS mode causes GDIF to propagate all SCOPE=SYSTEMS ENQs across all MIIplex systems. This mode eliminates DASD data integrity exposures, and eliminates the need to constantly maintain ENQ management definitions in the MIMQNAME parmlib member.

Note: For more information on how to implement ALLSYSTEMS mode, see the chapter “Advanced Topics” in the CA MII Programming Guide. Note that due to the complexities involved in converting CA MII from SELECT to ALLSYSTEMS mode, we recommend contacting CA MIM Technical Support for assistance in converting to ALLSYSTEMS mode.

MIM1812

ddmmmyy ddd hh:mm:ss.th NQPB: NQPREFRONTEND (ISGNQXITPREBATCH) exit parameter list

Reason:

CA MII issues this message when trace information is requested for NQPREFRONTENDEXIT event activity. A formatted dump of the ISGYNQPB control block follows this message.The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1813

ddmmmyy ddd hh:mm:ss.th XERP: EQXER (Evaluate Resource) Input/Output parameter list

Reason:

CA MII issues this message when trace information is requested for NQPREFRONTENDEXIT event activity. A formatted dump of the XERP control block follows this message. The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1814

ddmmmyy ddd hh:mm:ss.th NQBP: NQFRONTENTEXIT (ISGNQXITBATCH/CND) exit parm list

Reason:

CA MII issues this message when trace information is requested for NQFRONTENDEXIT event activity. A formatted dump of the NQBP control block (mapped by ISGYNQBP) follows this message. The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1815

ddmmmyy ddd hh:mm:ss.th NQBPRSC_ENTRY: (ISGNQXITBATCH/CND) resource entry

Reason:

CA MII issues this message when trace information is requested for NQFRONTENDEXIT event activity. A formatted dump of the NQBPRSC_ENTRY control block (mapped by ISGYNQBP) follows this message. The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1816

ddmmmyy ddd hh:mm:ss.th ENF 51 Signal Data Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the IEFENFSG control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1817

ddmmmyy ddd hh:mm:ss.th ENF 51 Signal – Contention Data

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the ISGE51CN control block follows this message.

This information is for use by CA Technical Support only. The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1818

ddmmmyy ddd hh:mm:ss.th ENF 51 Signal – Resource Name

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the ISGRIB control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1819

ddmmmyy ddd hh:mm:ss.th ENF 51 Signal – Requestor

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the ISGRIBE control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed

Action:

This information is for use by CA Technical Support only.

MIM1820

ddmmmyy ddd hh:mm:ss.th Conflict Event Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the CA MII CEN control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1821

ddmmmyy ddd hh:mm:ss.th Resource Conflict Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the CA MII RCN control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1822

ddmmmyy ddd hh:mm:ss.th Requestor Conflict Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the CA MII RQC control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1823

ddmmmyy ddd hh:mm:ss.th RIB (fixed segment) Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the ISGRIB control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1824

ddmmmyy ddd hh:mm:ss.th RIBE Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the ISGRIBE control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1825

ddmmmyy ddd hh:mm:ss.th CIR Block

Reason:

CA MII issues this message when trace information is requested for CONFLICT event activity. A formatted dump of the CIR control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1826

ddmmmyy ddd hh:mm:ss.th CIHB Block

Reason:

CA MII issues this message when trace information is requested for CONFLICT event activity. A formatted dump of the CIBH control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIM1827

ddmmmyy ddd hh:mm:ss.th CQP Block

Reason:

CA MII issues this message when trace information is requested for ENF 51 event activity. A formatted dump of the CQP control block follows this message.

The date and time are the date and time when the request was issued. This message is written to the MIMTRACE data set if the TRACE feature is active. Otherwise, this message is suppressed.

Action:

This information is for use by CA Technical Support only.

MIMES001E

NAME/TOKEN service error

Reason:

An error has occurred during initialization of the early startup ENQ/RESERVE monitor. The current task is terminated with ABEND U123.

Action:

Contact CA Technical Support.

MIMES002E

Failed to create CAMIMGR address space

Reason:

An error has occurred while starting the CAMIMGR address space. The current task is terminated with ABEND U124.

Action:

Contact CA Technical Support.

MIMES002E

ENQ monitoring active

Reason:

The early startup ENQ/RESERVE monitor has completed initialization.

MIMES004I

taskname waiting on qname

Reason:

Task taskname has been suspended by the early start ENQ/RESERVE monitor, because it issued a RESERVE for QNAME qname. The task will be resumed when CA MIM initialization/synchronization has completed.