Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for IMS Offline 5.6.

Return codes

The Log Edit program (IMFLEDIT) produces the following return codes:

Code

Explanation

032

An invalid parameter was specified in the BMC AMI Ops Monitor for IMS Offline parameter library member IMFLEP00.

Log Edit prints the MVIMS Parameter File Error Report and stops.

036

Requested storage was not available during the allocation of internal tables.

Increase the region size or correct the table size parameters in IMFLEP00.

040

The number of defined LTERMs exceeded the LTERM table capacity.

041

(BMC.AMIOPS.SPE2204) This code indicates one of the following problems:

  • The IMSLEVEL you have specified does not match the IMS release level recorded in the X'FA', X'F9', or X'45' record.
  • No X'FA', X'F9', or X'45' records were found in the input log.

042

The IMS release level of the input log data set could not be determined.

Specify the IMSLEVEL parameter explicitly.

043

The input data set referenced by LOGFILE DD contains records that are not supported by this release of BMC AMI Ops Monitor for IMS Offline.

044

LOGFILE contains data sets that are concatenated out of chronological order, or it contains logs from different IMS systems.

If RSPOPT=YES (see Log-Edit-input-parameters), the chronological log record sequence check is performed to prevent incorrect response times from being reported by the Performance Reporter. If RSPOPT=NO, IMFLEDIT does not calculate response time data and the check is not performed.

045

SMQ=YES was specified in IMFLEP00, but the log being processed is from an unsupported IMS version.

046

SMQ=YES was specified in IMFLEP00, but the X'FA' records do not have SMQ data.

Either this log is not from a shared message queues system or the Event Collector running on that system was MainView for IMS Offline 3.2.00 or earlier.

047

SMQ=NO was specified in IMFLEP00, but the X'FA' records have SMQ data.

048

No records were written to the IRUF, which results from an invalid parameter specification.

050

SMQ=YES was specified in IMFLEP00, but IMFLEDIT encountered an error calling DFSORT.

Add //SORTDIAG DD DUMMY to the IMFLEDIT job step and inspect the messages written to SYSPRINT DD.

051

SMQ=YES was specified in IMFLEP00, but all of the X'FA' records in the LOGFILE DD are not from IMS systems in the same shared queues group.

To correct the problem, concatenate to the LOGFILE DD only IMS logs from the same shared queues group.

052

The SELREC option was specified, but the RTAUDIT file could not be opened.

053

The FAUTIL=YES option was specified, but the FAUTIL file could not be opened.

Log Edit might continue to run when it encounters nonfatal abnormal conditions. The following return codes indicate such conditions:

Code

Explanation

064

A response table overflow caused loss of response data.

Check the processing statistics in the Log Edit Audit Report for the number of occurrences. If necessary, either decrease the purge time (RSPPURGE) or increase the size of the response table (RSPTBL).

068

A message switch table overflow caused loss of message switch arrival times.

Check the processing statistics in the Log Edit Audit Report for the number of occurrences. If necessary, increase the size of the message switch table (MSGSWTBL).

072

A multiple systems coupling table (MSCTBL) overflow caused a loss of MSC transaction arrival times.

Check the processing statistics in the Log Edit Audit Report for the number of occurrences. If necessary, increase the size of MSCTBL.

084

More storage was requested by subroutine PRSFPLED than was available in the region.

Response fields in some transaction accounting records could be lost. Increase the region size for IMFLEDIT. The number of times this error occurred during IMFLEDIT processing is provided in the Log Edit Audit Report.

088

No log records of type X'33' were found in the IMS logs.

Response processing requires X'33' log records. If you provided an extract of the IMS log, make sure that the X'33' log records are included. Refer to the BBSAMP member ARCHCTL2.

092

More storage was requested by subroutine PRSRSPED than was available in the region.

Response fields in some transaction accounting records could be lost. Increase the region size for IMFLEDIT. The number of times this error occurred during IMFLEDIT processing is provided in the Log Edit Audit Report.

1xxx

LOGFILE DD OPEN failed (where xxx represents the return code from the open failure).

2xxx

LOGFILE DD CLOSE failed (where xxx represents the return code from the close failure).

Note

The high-water marks (maximum measured value) reached in the response table (RSPTBL), the message switch table (MSGSWTBL), and the multiple systems coupling table (MSCTBL) and the number of purges that occurred in RSPTBL are monitored and presented in the Log Edit Audit Report when Log Edit ends. Check the high-water marks occasionally to avoid loss of data.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*