Log Edit (IMFLEDIT) input parameters

The IMFLEDIT program processes input data according to parameters specified in BBPARM member IMFLEP00. The following table describes the Log Edit input parameters and lists them in alphabetical order.

Important

Leading zeros are required for the parameter values.

Related topic

Log-Edit-input-data

Parameter	Valid values	Description
CPUTIME	TRUNC (the default) ROUND	Specifies how millisecond CPU time fields are handled: TRUNC truncates millisecond CPU time fields. ROUND rounds millisecond CPU time fields to the nearest millisecond.
CTLBFR	05 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) as the percentage when calculating: CTL_BUFF_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
CTLDLI	06 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) as the percentage when calculating: CTL_DLI_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
CTLOC	01 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) when calculating: CTL_OPEN_CLOSE_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
DAY	ALL FIRST SECOND DATE	Specifies whether BMC AMI Ops Monitor for IMS Offline is to process a portion of the IMS log file using the program and transaction record start timestamps ALL processes all records encountered in IMS log file. FIRST limits IMS log file data processing to data for the first date encountered. SECOND limits IMS log file data processing to data for the second date encountered. DATE limits IMS log file data processing to data for the date specified in the SELDATE parameter. If DATE is specified, the next parameter must be SELDATE=yyddd.
FAPURGE	120 (the default) 000-999	Specifies how long an FA record can stay queued in the FA chain Any queued FA record that is older than the specified time is written to the IRUF.
FAUTIL	NO (the default) YES	Specifies whether transaction records (X'FA') encountered on the LOGFILE file will be written to the FAUTIL file NO does not write transaction records from the LOGFILE file to the FAUTIL file. YES writes all transaction records encountered in the LOGFILE file to the FAUTIL file. Before writing the transaction records, IMFLEDIT adjusts the timestamps in the transaction records so that they remain consistent with the corresponding timestamps in the transaction accounting records (TARs) written to the IRUF (including the timestamp related to MSGSWIQT).
IMSLEVEL	0000 (the default) 1510 (IMS 15.1) 1520 (IMS 15.2)	Identifies the IMS release level of the input log data sets. Although Log Edit can process log data sets for different releases of IMS, it can process only one level at a time If Log Edit does not find either a transaction (X'FA'), a program (X'F9'), or an IMS statistics (X'45') log record in the records of the log data set and if the value of IMSLEVEL is not the correct release level of the log data set, Log Edit stops with an 0Cx abend.
LTERMREC	ACTIVE (the default) ALL	Specifies for which terminals the IRUF terminal accounting records (LARs) are created ACTIVE creates IRUF LARs for only those terminals with activity against them. ALL creates IRUF LARs for all terminals defined to IMS.
LTERMTBL	001500 (the default) 000001 - 999999	Specifies the number of 102-byte entries for the logical terminal table This parameter should be adjusted to a number larger than the number of logical terminals defined to IMS.
MAXINQ	00000 (the default) 00000 - 99999	Optional ceiling value in seconds for TAR INPUT Q. If the ceiling is nonzero, all TAR INPUT Q values that exceed the ceiling are replaced by the ceiling value. If the value is 00000, no ceiling is set or checked.
MAXRINQ	00000 (the default) 00000 - 99999	Optional ceiling value in seconds for TAR R INPUT Q. If the ceiling is nonzero, all TAR R INPUT Q values that exceed the ceiling are replaced by the ceiling value. If the value is 00000, no ceiling is set or checked.
MAXRRESP	00000 (the default) 00000 - 99999	Optional ceiling value in seconds for TAR R RESPONSE. If the ceiling is nonzero, all TAR R RESPONSE values that exceed the ceiling are replaced by the ceiling value. If the value is 00000, no ceiling is set or checked.
MAXSEGS	228 (the default) 000 - 228	Specifies the maximum number of DBT segments to be included in the TAR DBT section The PCB segment is not included in this value; it resides in the fixed portion of the TAR record. The ALLDBS, Db2, and OTHER segments are in addition to the number of segments specified with MAXSEGS.
MESSAGES	NO (the default) YES	Specifies whether log edit error reporting is enabled Each exception counted on the audit report is listed when MESSAGES=YES.
MSCPURGE	120 (the default) 000 - 999	Important Used only if parameter RSPOPT=YES. Specifies the maximum time in seconds that a multiple-systems-coupling (MSC) entry will be held in the MSC table waiting for either the first attempt to transmit or the GET UNIQUE of the output message If the maximum time is exceeded, the missing timestamps are set using this interval and the entry is purged. If MSCPURGE is increased, you may need to increase the required size of the MSC table.
MSCTBL	00000 (the default) 00000 - 999999	Specifies the number of 44-byte entries for the multiple systems coupling (MSC) table If a nonzero value is specified for MSCTBL, IMFLEDIT collects the transaction arrival timestamp in the processing system to calculate the input queue time and the response time. The default is 00000 (no MSC handling). If you have MSC processing transactions in your system and the overflow value in the IMFLEDIT Audit Report is not zero, increase the MSCTBL value by the overflow value. In BMC AMI Ops Monitor for IMS Offline log records created for MSC transactions, the transaction arrival timestamp is set to the transaction start time, which results in zero input queue time. This processing is done because the arrival timestamp set by IMS is from the originating system, not from the processing system. Since the clocks on the two systems may not be synchronized, the timestamp might be invalid and could lead to anomalies such as a negative input queue time.
MSGBFR	10 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) as the percentage when calculating: MSG_BUFF_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
MSGCPU	30 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) as the percentage when calculating: MSG_REGION_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
MSGDB2	18 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) as the percentage when calculating: MSG_DB2_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
MSGDLI	18 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) as the percentage when calculating: MSG_DLI_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
MSGOC	01 (the default) 01 - 99 REJECT	Indicates to Log Edit what to do when an invalid CPU timing field is encountered Use the specified numeric value (01 - 99) when calculating: MSG_OPEN_CLOSE_CPU_TIME = Transaction_Elapsed_Time × Percentage REJECT the input log record. Important IMFLEDIT automatically adjusts invalid CPU timing fields by using the specified numeric value and multiplying it by transaction elapsed time. For example, if the numerical value for MSGCPU is 30 and the transaction elapsed time is 1 second, IMFLEDIT automatically adjusts it to 0.3 seconds: MSG_REGION_CPU_TIME = (1 × 0.30)
MSGSWIQT	NO (the default) YES	Specifies whether to use the input queue time of the originating message or the input queue time of the most recent message switch, which is the time when the message is enqueued to the scheduler message block (SMB) NO uses the input queue time of the originating message. YES uses the input queue time of the most recent message switch.
MSGSWTBL	01000 (the default) 00001 - 999999	Specifies the number of 36-byte entries for the message switch table. If the overflow value in the IMFLEDIT Audit Report is not zero, increase the MSGSWTBL value by the overflow value.
MSWPURGE	120 (the default) 000 - 999	Important Used only if parameter RSPOPT=YES. Specifies the maximum time in seconds that a response entry will be held in the message switch table waiting for either the first attempt to transmit or the GET UNIQUE of the output message If the maximum time is exceeded, the missing timestamps are set using this interval and the entry is purged. If MSWPURGE is increased, you may need to increase the required size of the message switch table.
PSTNUM	031 (the default) 001 - 999	Specifies the maximum number of PSTs
ROLB	NO (the default) YES	When a transaction issues ROLB calls, whether to create a transaction accounting record (TAR) record for each FA record or one TAR for all FA records belonging to the same message NO creates a TAR for each FA record even if the transaction issued ROLB calls. YES creates a single TAR for all FA records belonging to the same message.
RSPOPT	YES (the default) NO	Specifies whether output response time is to be calculated The NO option requires less processing but limits the response reports that are available. YES indicates that all response report timings are available. NO indicates that the following response report timings are not available: Arrival time to message sent time (RESPONSE) Arrival time to message free time (RSP TO DEQ) Message insert time to message sent time (OUTPUT Q) Message sent time to message free time (DEQUEUE) Message insert time to message free time (OUT TO DEQ) NO also indicates that the following response report timings are the only timings that are available: Arrival time to start time (INPUT Q) Start time to stop time (ELAPSED) Arrival time to start time (ARIV START) Arrival time to stop time (ARIV STOP)
RSPPURGE	120 (the default) 000 - 999	Important Used only if parameter RSPOPT=YES. Specifies the maximum time in seconds that a response entry will be held in the response table waiting for either the first attempt to transmit or the final dequeue of the message If the maximum time is exceeded, the missing timestamps are set using this interval and the entry is purged. If RSPPURGE is increased, you may need to increase the required size of the response table.
RSPTBL	00500 (the default) 00001 - 999999	Specifies the number of 120-byte entries for the response table If the overflow value in the IMFLEDIT Audit Report is not zero, increase the RSPTBL value by the overflow value. If you specify the maximum value (999999) for this parameter and for LTERMTBL, MSGSWTBL, and MSCTBL, you will allocate approximately 272 MB of storage. If that results in an 878 abend, increase the region size for the job or reduce the specifications.
SELDATE	yyddd	Specifies the Julian date for IRUF record selection This date is required if DAY=DATE is specified. If not required, this parameter should be commented out, deleted, or left with an unused but valid date to prevent syntax errors. An error will also occur if a nonnumeric value is entered (NULL or blanks, for example).
SELREC	01 - FF	Optionally identifies the type of log record to be written to the RTAUDIT file If SELREC is not used, no records are written to RTAUDIT. Only one type per run can be selected. The SELREC function is not available if SMQ=YES and RSPOPT=YES are specified. If you need to write records from a shared queues group of log data sets to the RTAUDIT file, set SMQ=YES and RSPOPT=NO. Keep in mind, however, that the generated IRUF TARs will not be valid.
SMQ	NO (the default) YES	Specifies whether special IMFLEDIT processing will be done for shared queues groups NO does no special IMFLEDIT processing for shared queues groups. YES processes the logs from all IMS systems participating in a shared queues group must be concatenated to the LOGFILE DD, and the resulting IRUF will have TARs, LARs, and PARs for all participating IMS systems. The SELREC function is not available if SMQ=YES and RSPOPT=YES are specified. If you need to write records from a shared queues group of log data sets to the RTAUDIT file, set SMQ=YES and RSPOPT=NO. Keep in mind, however, that the generated IRUF TARs will not be valid. If SMQ=NO, the SMQ GRP NM field in the IMFLEDIT Audit Report will be blank. If SMQ=YES, the SMQ GRP NM field will contain the name of the shared message queue group.
SYSID	Blank	Not used.
TIMSTAMP	ACCEPT (the default) REJECT	Indicates to Log Edit what to do when input records with invalid arrival, start, or stop timestamps are encountered ACCEPT accepts the record but uses default timestamps. REJECT rejects the record and lists it in the Log Edit Error Report.
ZIIPSORT	YES NO	Specifies whether to use the BMC ZIIPSORT program to sort the IMS log records when the SMQ parameter is set to YES The use of this option might reduce overall CPU use during IMFLEDIT processing. YES uses the ZIIPSORT program for sorting. NO uses the standard sort program for sorting.

Log Edit (IMFLEDIT) input parameters

On this page