4. Operation › 4.4 Administering CA MICS › 4.4.4 CA MICS Administrator Utilities › 4.4.4.5 Database Health Check Utility › 4.4.4.5.2 Symptom Descriptions
4.4.4.5.2 Symptom Descriptions
The following is a list of possible symptoms that the CA MICS
Database Health Check Utility may generate. The list also
includes the symptom's description and solution.
Symptom : Database Format Not at Current SAS Level
Description: Analyzed data library is at a lower level of SAS
than the SAS level running on your system.
Action : Reallocate the library under the current SAS
release and copy the contents from the old
library to the new.
Symptom : Data Library Not Optimally Blocked
Description: The blocksize of the SAS data library is not
specified for optimal performance. Half-track
blocking provides better performance than
smaller blocksizes.
Action : Reallocate data set with half-track blocksize;
then use SAS PROC COPY to copy contents. Swap
data set names.
Symptom : Defined Cycles Exceeded (Dead Cycle)
Description: The number of cycles in the database are greater
than what is defined in DBMODEL.
Action : Run the prefix.MICS.CNTL(DBHDELET) job. For more
information, see section 4.4.4.5.4.
Symptom : Unknown File
Description: File is not affiliated with a CA MICS component.
Action : Check file for applicability and delete if
necessary.
Symptom : Database Update Not Completed
Description: A CA MICS operational job (for example, the
DAILY job) has not completed successfully. The
Database Health Check utility requires that all
updates be complete.
Action : Run the prefix.MICS.CNTL(RSTATUS) job to
identify failed process and restart accordingly.
Symptom : Invalid Cycle
Description: The cycles specified are either non-numeric or
not valid for a CA MICS file.
Action : Check file for applicability and delete if
necessary.
Symptom : Incorrect File Location
Description: The component that this file is affiliated with
is not installed in this unit.
Action : Check file for applicability and delete if
necessary.
Symptom : Residual Update Files
Description: Identified files are left over from a CA MICS
database update process (for example, DAILY).
Action : Check file for applicability and delete if
necessary.
Symptom : File Not Active in Unit
Description: This file is turned off in this unit.
Action : Turn this file on in
sharedprefix.MICS.GENLIB(cccGENIN) and run
sharedprefix.MICS.CNTL(cccCGEN) to activate this
change.
Symptom : Incremental Checkpoint File for Undefined
Component
Description: The incremental checkpoint file is turned on for
a component not defined in this unit.
Action : Check file for applicability and delete if
necessary.
Symptom : Component Not Active in Unit for File
Description: The component that this file is affiliated with
is not active in this unit.
Action : Check file for applicability and delete if
necessary.
Symptom : Dummy File found
Description: This file is defined as a DUMMY file.
Action : This dummy file is needed when a database is
first created, but after at least one component
file exists in the database, the dummy file may
be deleted. Note that the space occupied by
this file is insignificant.
Symptom : Incremental Checkpoint File for Inactive
Component
Description: The incremental checkpoint file is turned on for
an inactive component.
Action : Check file for applicability and delete if
necessary.
Symptom : Files Flagged for Deletion
Description: These files are marked for deletion. Y was
specified for GENERATE DELETE when the Database
Health Check Utility was invoked.
Action : To complete the deletion process, submit
prefix.MICS.CNTL(DBHDELET). For more
information, see section 4.4.4.5.4.
Symptom : Special ledgers found but Ledger Prorating not
active
Description: Accounting and Chargeback special ledgers were
found in the months timespan. However, the
Ledger Prorating option is not active.
Action : Check file for applicability and delete if
necessary. For more information on proration
options, see section 4.8.2 in the CA MICS
Accounting and Chargeback Option User Guide.
Symptom : Special ledgers found but not requested
Description: Accounting and Chargeback special ledgers were
found in the months timespan. However, the
option to use special ledgers is not active.
Action : Check file for applicability and delete if
necessary. For more information on proration
options, see section 4.8.2 in the CA MICS
Accounting and Chargeback Option User Guide.
Symptom : No File Activity. All Cycles have zero
observation
Description: Every cycle for the named file has zero
observations.
Action : This informational message identifies files that
have no activity. A file is considered inactive
if all cycles in a timespan have zero
observations. Note that this is not necessarily
an indicator of an error in the CA MICS
database, but can be a result of one or more of
the following:
o A data source not being collected. For
example, the HARCPU file may show as inactive
if the RMF type 70 record is not being
collected.
o Missing input data. An example of this is if
the NODATA option is specified and the input
data set is empty, or contains data that has
already been processed.
Symptom : Format found in multiple catalogs of same
Library
Description: A format of the same name and entrytype resides
in multiple catalogs of the same library.
Library would either be the MCOLIB or MUOLIB.
Action : This warning message identifies a possible
duplicate format condition. This may or may not
be significant depending on the format itself
and the catalog location.
Most CA MICS processes define the format search
order as the following:
USERFMT1 MICSFMTS USERFMT2
The order of the library (complex versus unit)
may vary. For more information about format
catalog search order, see section 4.5 of the
System Modification guide.
Symptom : Format found in both the MCOLIB and MUOLIB
Description: A format of the same name and entrytype resides
in catalogs at both the complex and unit levels.
Action : This warning message identifies a possible
duplicate format condition. This may
or may not be significant depending on the
format itself and the catalog location.
Most CA MICS processes define the format search
order as the following:
USERFMT1 MICSFMTS USERFMT2
The order of the library (complex versus unit)
may vary. For more information about format
catalog search order, see section 4.5 of the
System Modification guide.
Symptom : Format Catalog Not Found
Description: Either the USERFMT1 or USERFMT2 catalog does
not exist in the format library.
Action : This warning message identifies a missing
format catalog. A typical CA MICS installation
should have a USERFMT1 MICSFMTS and USERFMT2
at the complex level (MCOLIB) as well as each
unit (MUOLIB).
