9 Database Region Messages

This chapter documents the messages that are issued by the database instance management component of Oracle Database for z/OS. These messages are generally written to the system console.

The messages begin with the prefix "MIR" followed by a 4-digit decimal number followed by a letter to identify the action and severity associated with each message. The final letter indicates one of the following:

Table 9-1 Database Region Message Letter Codes

Letter	Definition
E	Error. Action is required
I	Information. Action is not required
W	Warning. Action may be required
D	Debug. Action is not required.

The following messages are described in this chapter:

9.1 Messages MIR0001I to MIR0622I

MIR0001I Starting control region for ssssssss service in subsystem ssss: Cause: Region initialization for the first address space of the indicated service is beginning. This is normally the first message issued by the database service after it is started.; Action: No action is required.

MIR0002I ssssssss service address space ready: Cause: Region initialization for the indicated database service address space has completed successfully. Connection to the service to perform an Oracle startup is now possible.; Action: No action is required.

MIR0003I Quiescing ssssssss service address spaces: Cause: A z/OS or OSDI STOP (P) command has been issued to the indicated database service, and termination of its address space (or spaces) and tasks is beginning.; Action: No action is required.

MIR0004I ssssssss service terminated: Cause: Termination processing for the indicated service has completed. All address spaces of the service should end execution shortly after this message is received.; Action: No action is required.

MIR0005E ssssssss service failed to signon to ssss subsystem: Cause: During database service initialization, an attempt to register the service as "active" in the subsystem failed. The service address space terminates. This message should be accompanied by one or more subsystem (MIS) messages describing the error.; Action: This message and the accompanying MIS messages should be reported to Oracle Support Services.

MIR0006E nnnn macro error. Comp code = cccc; reason code rrrr: Cause: During database service initialization, one of the macros that was issued to set up cross-memory access has failed. The service address space terminates.; Action: This message and the included macro name and error codes should be reported to Oracle Support Services.

MIR0007E Environment check failed: reason: Cause: Database service address space initialization cannot proceed due to one of the following environmental conditions [reason]:
Reason: APF-authorization: The database service program is not executing APF-authorized.; Action: Ensure that ORARASC is being fetched from an APF-authorized library and that no non-authorized libraries are concatenated in the service JCL STEPLIB DD statement.
Reason: Protection key 7: The database service program is not running in protection key 7.; Action: Ensure that ORARASC has been added to the z/OS Program Properties Table (PPT) with an entry that specifies KEY(7), and make sure that the PPT has been refreshed or that the system has been IPLed.
Reason: Non-swappable: The database service address space is not marked non-swappable.; Action: Ensure that ORARASC has been added to the z/OS Program Properties Table (PPT) with an entry that specifies NOSWAP, and make sure that the PPT has been refreshed or that the system has been IPLed.; Action: The database service address space is terminated. Correct the indicated condition and restart the service.

MIR0009I Starting system subtasks: Cause: Database service initialization has reached the point at which internal service tasks are attached. This is a normal progress message during service address space initialization.; Action: No action is required.

MIR0010I Stopping system subtasks: Cause: Database service termination has reached the point at which internal service tasks are detached. This is a normal progress message during service STOP (P) processing.; Action: No action is required.

MIR0011I Stop command received: Cause: The database service acknowledges receiving a z/OS or OSDI STOP (or P) command.; Action: No action is required.

MIR0012I Starting auxiliary region nnn for ssssssss in subsystem ssss: Cause: During database service initialization, the region INIT_ADR_SPACES parameter specified a number greater than one. The first server address space has therefore starting an auxiliary address space. One message of this type is issued from each auxiliary address space that is started.; Action: No action is required.

MIR0013E Failed to allocate parameter data set dsname: Cause: During database service initialization, the region parameters data set (supplied via the service PARM string on DEFINE or ALTER SERVICE) could not be dynamically allocated. Service initialization fails, and the address space terminates. The usual cause of this is a misspelled data set name in the service PARM.; Action: This can be corrected with an OSDI ALTER command.

MIR0014E Failed to open parameter data set dsname: Cause: During database service initialization, the region parameters data set (supplied via the service PARM string on DEFINE or ALTER SERVICE) could not be opened. Service initialization fails, and the address space terminates.; Action: This message is normally accompanied by messages from open/close/EOV (IECxxx messages) indicating the nature of the error. Refer to the appropriate message.

MIR0016W Syntax error in option; ignored: Cause: During service initialization, an invalid or unknown parameter was specified in the server region parameter file.; Action: The parameter is ignored, and service initialization continues. The parameter file should be examined and corrected.

MIR0017W Invalid option value; option ignored: Cause: During service initialization, an unacceptable parameter value was specified in the server region parameter file.; Action: The parameter is ignored, and service initialization continues. The parameter file should be examined and corrected.

MIR0018W Unrecognized option; ignored: Cause: During service initialization, an invalid or unknown parameter was specified in the server region parameter file.; Action: The parameter is ignored, and service initialization continues. The parameter file should be examined and corrected.

MIR0020W I/O error reading option file: Cause: During service initialization, an I/O error occurred while reading the server region parameter file.; Action: Region parameter processing stops, and service initialization continues. The parameter file should be examined and corrected.

MIR0021E Unable to load nnnnnnnn - cccc-rr: Cause: During service initialization, a required module could not be loaded. The module name and the LOAD macro completion and return codes are given in the message. Service initialization fails, and the service address space terminates.; Action: Two likely causes of this error are a misspelled Oracle kernel module name in the region initialization parameters or a missing data set in the region JCL STEPLIB concatenation. If the module name begins with "CEE", then it is an IBM LE/370 module. Make sure that you have included the LE/370 runtime library in STEPLIB.

MIR0022E Fatal error - terminating: Cause: An error has caused database service address space initialization to fail. The error is described in earlier MIR messages. The service address space terminates.; Action: Correct the error(s) indicated in prior message(s) and then restart the service.

MIR0023I Starting nnn auxiliary address spaces: Cause: During database service initialization, the region INIT_ADR_SPACES parameter specified a number greater than one.; Action: The first server address space is therefore starting auxiliary address spaces.

MIR0024I Terminating all auxiliary address spaces: Cause: During database service STOP (P) processing, the auxiliary address spaces that have been started are about to be terminated.; Action: This is a normal progress message during service termination.

MIR0025W Unable to open file management input file - SMS assumed: Cause: During database region initialization processing of the file management parameters, the ORA$FPS file could not be opened. The usual cause of this is that the DD is not included in the region JCL. Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations.; Action: No action is required.

MIR0027E Unable to retrieve OSDI command: Cause: An OSDI subsystem command that was forwarded to the database service could not be retrieved.; Action: This error should be reported to Oracle Support Services.

MIR0029E nnnnn lines not displayed: Cause: A DISPLAY command that was issued via the z/OS MODIFY (F) interface produced more lines of output than would fit in the response buffer.; Action: Reissue the command with finer criteria to get a complete display.

MIR0030E Fatal error - terminating: Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), a severe error has halted processing of the parameters.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Report this error to Oracle Support Services.

MIR0036W Dump request for service ssssssss failed, Return code=nn, Reason=nn: Cause: The service attempted to perform an SVC dump, but was unsuccessful. The Return code and Reason values are from the SDUMPX macro. This message commonly appears if dumps are suppressed by DAE, SLIP or other system configuration options.; Action: If the dump was suppressed by DAE, a previous dump should exist. If the previous dump was lost, it may be necessary to disable DAE or to modify it so the suppressed dump can be generated. Consult your system programmer for assistance. Refer to the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 2 for further information on macro SDUMPX.

MIR0075E FT2 dddddddd unallocation error eeeeeeee: Cause: During close/free processing for a non VSAM file (such as a trace or parameter file), a dynamic unallocation request received an unexpected error.; Action: This message and the accompanying error code should be reported to Oracle Support Services.

MIR0110W Service ssssssss UNIX services unavailable: Cause: During database service initialization, an attempt to dub the service address space as a z/OS UNIX System Services process has failed. Service initialization continues, and the database can be started up as usual. However, database functions that interact with z/OS UNIX System Services will not be available.; Action: Usually this message results from not having a default OE segment defined for the z/OS userid associated with the service address space.

MIR0111W Service ssssssss gethostbyname service unavilable: Cause: During database service initialization, an attempt to initialize the sockets macro interface has failed.; Action: Service initialization continues, and the database can be started up as usual. However, database functions that depend on z/OS UNIX System Services sockets will not be available.

MIR0112E Service ssssssss UNIX resource cleanup failed, Session=sess, func=fn, resource=resid, errno=e, reason=r: Cause: During resource cleanup processing for a terminating database session, an attempt to release a z/OS UNIX System Services resource allocated by the session has failed.; Action: The service continues execution normally. This message should be reported to Oracle Support Services.

MIR0113E Service ssssssss async request (xxxxxxxx) post error: Cause: Internal error.; Action: Service continues execution normally, but some sessions may hang. This message should be reported to Oracle Support Services.

MIR0130I FPS refresh completed successfully: Cause: The FPS refresh completed successfully.; Action: None required.

MIR0131W FPS syntax error; record nnnnnn: Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), a syntax error (such as missing punctuation) was encountered.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Correct the syntax error. For more information on file management parameter syntax, refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390).

MIR0132W FPS value error; keyword: text; record nnnnnn: Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), the value that was specified for a file management parameter keyword was not valid.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Specify a valid value for the keyword. For more information, refer to the list of file management parameter keywords in the Oracle Database System Administration Guide for IBM z/OS (OS/390).

MIR0133W FPS invalid GROUP: group; record nnnnnn: Cause: The group name specified in the FILE_GROUP parameter is not a valid group.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Choose a valid group name. For more information, refer to the list of valid file management parameter file group names in Oracle Database System Administration Guide for IBM z/OS (OS/390).

FPS unknown keyword: text; record nnnnnn: Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), an invalid or misspelled keyword was encountered.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Specify a valid keyword. For more information, refer to the list of file management parameter keywords in Oracle Database System Administration Guide for IBM z/OS (OS/390).

MIR0135W FPS I/O error reading file: Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), an I/O error occurred on a request to read the parameter file. The file is closed, and no further parameters are processed.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. This message should be reported to Oracle Support Services.

MIR0136E Unable to open ORA$FPS DD, refresh cancelled: Cause: During execution of the REFRESH FPS command, the ORA$FPS file could not be opened. The usual cause of this is that the DD is not included in the region JCL.; Action: The refresh operation is terminated and the previous configuration, if any, remains in place. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Verify that the ORA$FPS DD is included in the region JCL. If it is and the problem persists, report this error to Oracle Support Services.

MIR0137E Errors encountered reading FPS input, refresh cancelled: Cause: During execution of the REFRESH FPS command, one or more errors prevented completion of FPS processing.; Action: The refresh operation is terminated, and the previous configuration, if any, remains in place. Correct the problem with ORA$FPS and rerun the REFRESH FPS command. If the problem persists, report this error to Oracle Support Services.

MIR0138W No FPS input found, refresh cancelled: Cause: During execution of the REFRESH FPS command, the ORA$FPS was found to have no definitions.; Action: The refresh operation is terminated and the previous configuration, if any, remains in place. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Add FPS definitions and rerun the REFRESH FPS command. If the problem persists, report this error to Oracle Support Services.

MIR0139E FPS fatal error, terminating: Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), a severe error has halted processing of the parameters.; Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Report this error to Oracle Support Services.

MIR0140E FPS fatal error, insufficient memory: Cause: FPS was unable to obtain storage for the FPS definitions.; Action: FPS processing is terminated. Ensure adequate storage is available for the FPS definitions.

MIR0141E FPS fatal error, file inconsistency: Cause: New errors appeared during the second pass over the ORA$FPS data set.; Action: FPS processing is terminated. File processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Report this error to Oracle Support Services.

MIR0142E FPS fatal error, ABEND Snnn-rrrrrrrr, during oooo: Cause: The processing of the ORA$FPS DD has resulted in a z/OS ABEND. The variable nnn is the system ABEND code (hex) and rrrrrrrr is the associated reason code (hex). The ABEND occurred while performing operation oooo - the name of a system service or macro. This error can be preceded by system messages with IEC prefixes. These IEC messages will have additional detail about the problem.; Action: FPS processing is terminated. If the error occurred during server initialization, initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. If the error occurred during a REFRESH FPS command, then the refresh operation is terminated and the previous configuration, if any, remains in place. Using the ABEND code, reason code, and z/OS system-issued messages, correct the condition that resulted in the ABEND. If the problem persists, report this error to Oracle Support Services. If an SVC dump is generated, save it for problem diagnosis.

MIR0380E Failed to load ORADIE module: Cause: During database service initialization, a LOAD macro (for the timer-disabled interrupt exit) failed. Service initialization fails, and the service terminates. This message will usually be accompanied by one or more CSVxxx messages from Contents Management indicating the nature of the error.; Action: Make sure that ORADIE is in one of the server region STEPLIB data sets and that sufficient ECSA memory is available to load it. If sufficient ECSA memory is available, then report this message to Oracle Support Services.

MIR0381E Failed to obtain SQA for timer structure: Cause: During database service initialization, approximately 500 bytes of ESQA memory could not be obtained for a time interval control structure. Service initialization fails, and the service terminates.; Action: If your system does not have 500 bytes of available ESQA, you can expect other problems to be reported. If problems other than Oracle database server problems are not reported, then report this error to Oracle Support Services.

MIR0382E Initial timer request enqueue failed: Cause: During database service initialization, an attempt to enqueue a timer request (TQE) failed.; Action: Service initialization fails, and the service terminates. This error should be reported to Oracle Support Services.

MIR0400I Oracle for OS/390 External Data Mover ready: Cause: EDM startup has completed. This is normally the first message issued by the EDM after it has successfully started.; Action: No action is required.

The EDM will write high-level debug messages to the log file (SYSPRINT DD).MIR0401E ESTAEX macro failed: R15=r15,R0=r0: Cause: During EDM startup, a macro that was issued to set up a recovery environment has failed. The EDM address space terminates.; Action: This message and the register values should be reported to Oracle Support Services.

MIR0402E Environment check failed: APF-authorization: Cause: During startup, the EDM detected that it was not executing APF-authorized. The EDM address space terminates.; Action: Ensure that ORAEDM is being fetched from an APF-authorized library and that no non-authorized libraries are concatenated in the EDM JCL STEPLIB DD statement.

MIR0403E ASTX macro failed: R15=r15,R0=r0: Cause: During EDM startup, a macro that was issued to retrieve startup parameters has failed. The EDM address space terminates.; Action: This message and the register values should be reported to Oracle Support Services.

MIR0404E ASPARM length invalid: actual=x, expected=y: Cause: During EDM startup, the startup parameters length was not as expected. The EDM address space terminates.; Action: This message and the error values should be reported to Oracle Support Services.

MIR0405E Client post failed: R15=r15,R0=r0,R1=r1: Cause: An attempt by the EDM to post function completion information back to the client has failed. This could happen if the client unexpectedly terminates, as well as for other reasons. The EDM address space terminates.; Action: If the client did not unexpectedly terminate, this message and the register values should be reported to Oracle Support Services.

MIR0406D Debug mode enabled: Cause: The EDM will write high-level debug messages to the log file (SYSPRINT DD).; Action: None required.

MIR0407D Ultra debug mode enabled: Cause: The EDM will write high-level and low-level debug messages to the log file (SYSPRINT DD).; Action: None required.

MIR0408E Unable to initialize File Management Parameters handler: Cause: During startup, the EDM was unable to initialize File Management Parameters processing. The EDM address space terminates.; Action: This message should be reported to Oracle Support Services.

MIR0409E Unsupported request received; function code=fc: Cause: The EDM received a request containing an unexpected function code. This could happen if the EDM program is down-level. The request is failed.; Action: If the EDM program is not down-level, this message and the function code should be reported to Oracle Support Services.

MIR04010E SYNAD entered; message text . : text: Cause: An attempt by the EDM to write a message to the log file (SYSPRINT DD) resulted in an I/O error. The text value is the error information passed to the SYNAD exit. The EDM suspends logging.; Action: Interpret text to diagnose and correct the error. If the error persists, contact Oracle Support Services.

MIR0500I Command processed: Cause: A command that was issued using the z/OS MODIFY (F) interface has been processed.; Action: No action is required.

MIR0501E Command not processed: Cause: A command that was issued using the z/OS MODIFY (F) interface could not be processed.; Action: This message should be preceded by other messages indicating the specific error.

MIR0502I No matching sessions found: Cause: A DISPLAY SESSION command that was issued via the z/OS MODIFY (F) interface could not find any server sessions matching the criteria specified in the command.; Action: No action is required.

MIR0503I Server session display

Cause: Information is displayed in response to the server DISPLAY SESSION command when it finds one or more sessions matching the criteria, as described below:

Session ID – OSDI session identifier in hexadecimal.
AS# – Server address space number to which the session is assigned.
Jobname – Jobname for the address space that bound the session, or internal identifier for Oracle background processes
TCB-Addr – z/OS TCB address currently associated with the session (may be blank)
UserID – Oracle userid for the session, if one is known

Action: None required.

MIR0504W Results may be inaccurate; enter command again: Cause: A DISPLAY SESSION command that was issued via the z/OS MODIFY (F) interface encountered a change in server session state structures while the structures were being examined.; Action: The result of the command may not be complete. The command should be reissued to get a current display.

MIR0505W Results have been truncated: Cause: A DISPLAY SESSION command that was issued via the z/OS MODIFY (F) interface produced more lines of output than would fit in the response buffer.; Action: Reissue the command with finer criteria to get a complete display.

MIR0506E Error encountered during command processing: Cause: An error occurred during processing of an IEATDUMP request for a DUMP SESSION command that was issued via the z/OS MODIFY (F) interface.; Action: Report this problem to Oracle Support Services.

MIR0507I Session not found: Cause: The session that was specified in a DUMP SESSION command that was issued via the z/OS MODIFY (F) interface could not be found.; Action: Either the session process ID was entered incorrectly, or the session has ended in the server.

MIR0611I Service ssssssss alert log closed: Cause: The instance alert log for the indicated service has been closed due to an error condition. An attempt will be made to allocate and open a SYSOUT data set for the alert log.; Action: If that attempt fails, then the alert log will be written to the system log.

MIR0612I Alert log for service ssssssss allocated to dddddddd: Cause: The instance alert log for the indicated service has been dynamically allocated as a SYSOUT data set to the DD name shown.; Action: This message is normally received during service startup when no SYSPRINT DD statement is supplied in the service procedure.

MIR0613E Service ssssssss alert log I/O error: synad-message: Cause: An I/O error occurred when the indicated service wrote to the alert log. The error description is in the form of message text that is generated by a SYNADAF macro.; Action: The alert log is closed, and an attempt is made to dynamically allocate a SYSOUT data set for the log. This message is usually followed, therefore, by messages MIR0611I and MIR0612I.

MIR0614E Service ssssssss alert log open failed, reason code n

Cause: An attempt to create a new alert log failed. The cause of the failure is indicated by the following reason codes:

1 – Data set or spool allocation failed

2 – OPEN failed

3 – Storage for BSAM buffers not available

4 – Storage for internal structures not available

With reason codes 1 and 2, additional messages will have appeared in the system log immediately before this message. For reason code 1, look for message MIR0619E containing the return and reason codes from a z/OS DYNALLOC request. For reason code 2, look for z/OS OPEN messages beginning with IEC, in your IBM message documentation.

Action: Some instances of reason code 1 or 2 can be corrected by changing things in the environment (such as available disk space) or by changing and refreshing ORA$FPS parameters in the DBAT group, which influence alert log dynamic allocation. Reason codes 3 and 4 are unlikely unless memory is nearly exhausted in the service address space, in which case this error is the least of your worries. If the error does not seem to be due to an environment or ORA$FPS problem, report this error to Oracle Support Services.

MIR0615W Service ssssssss alert log default SYSOUT=* assumed: Cause: No non-default alert log specification was provided, or an attempt to use a non-default alert log specification (from the ALERT_DSNAME region parameter) has failed, so an attempt will be made to allocate a default alert log.; Action: Normal operation continues with the default alert log or, if that fails, using the z/OS system log for alert messages. If you can correct the cause of the original failure (for example, by increasing available disk space or by changing and refreshing ORA$FPS), issue a LOGSWITCH database service command to cause the corrected alert log to be retried.

MIR0616E Service ssssssss ALERT_DSNAME syntax or content error: Cause: During service initialization or during processing of a LOGSWITCH command, the value specified for the ALERT_DSNAME parameter was not a usable filespec.; Action: Processing continues with a default (SYSOUT=*) alert log. Correct the problem with the ALERT_DSNAME value and stop and restart the service to use a non-default alert log.

MIR0617E Service ssssssss ALERT_DSNAME symbol substitution error (nnn): Cause: During service initialization, an attempt to resolve system symbols in a data set filespec supplied for ALERT_DSNAME failed. The nnn value is the return code from the z/OS ASASYMBM service in decimal. These are described in the IBM manual Assembler Services Reference, under "ASASYMBM".; Action: Processing continues with a default (SYSOUT=*) alert log. Correct the problem with the ALERT_DSNAME value and stop and restart the service to use a non-default alert log.

MIR0618I DSN=dsn: Cause: This message accompanies message MIR0612I when the alert log is allocated as a disk data set. It provides the data set name used for the new log after symbol substitutions have been done.; Action: None required.

MIR0619E Service ssssssss alert log dynalloc error, RC=nnn, Reason=xrrrr, Info=xiiii: Cause: During service initialization or during processing of a LOGSWITCH command, dynamic allocation of a new alert log failed. The nnn is the return code from DYNALLOC in decimal and rrrr and iiii are the reason and information codes, respectively, in hexadecimal. These are described in the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 1.; Action: Processing continues with a default (SYSOUT=*) alert log. If the dynamic allocation error results from an external cause such as lack of disk space, correct the problem as necessary. If it is caused by an error in the ORA$FPS parameters used for the alert log, correct the ORA$FPS data and refresh it using the REFRESH FPS database service command. In these cases you can issue a LOGSWITCH command to cause a new attempt at alert log allocation. If the problem is caused by the value in ALERT_DSNAME, such as a syntax error, you must stop and restart the service to effect a correction.

MIR0620E Service SSSSSSSS alert log dsname symbol error, RC=nnn: Cause: During LOGSWITCH command processing, an attempt to resolve system symbols in a data set filespec supplied for ALERT_DSNAME failed. The nnn value is the return code from the z/OS ASASYMBM in decimal. These are described in the IBM manual Assembler Services Reference, under "ASASYMBM".; Action: Processing continues with a default (SYSOUT=*) alert log. Correct the problem with the ALERT_DSNAME value and stop and restart the service to use a non-default alert log.

MIR0621I Alert log switch for service ssssssss ignored, not over ALERT_MIN: Cause: A LOGSWITCH command was issued without the FORCE option, but the accumulated size of the current alert log is less than the value specified for the ALERT_MIN region parameter.; Action: The LOGSWITCH command is ignored and processing continues with the current alert log. If you want to force the log switch without regard for ALERT_MIN, reissue LOGSWITCH with the FORCE option.

MIR0622I Service ssssssss alert log switching due to ALERT_MAX: Cause: The alert log has reached the threshold size specified by the ALERT_MAX region parameter, causing an automatic alert log switch.; Action: The current alert log is closed and deallocated and a new one allocated and opened. Processing continues normally with the new alert log.