A fix is available
APAR status
Closed as program error.
Error description
MSGKO21107E has incorrect field name for some fields in ZATRD panel Additional keywords STARTDATE STDATE STARTTIME STTIME ENDDATE ENDTIME CICSTRAN will not accept an all numeric value or when the CICSTRAN value starts with a number / digit Screen ZATQM ZATRQ
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2 PM * * ATF - Application Trace Facility * **************************************************************** * PROBLEM DESCRIPTION: Application Trace Facility INCORROUT * * corrections. * * MSGKO2O1107E Specifies incorrect field * * name when invalid start Date or Time * * entered. * * MSGKO2O1107E not issued when ROUTINE1 * * and ROUTINE2 both specify a routine * * name, but no schema, allowing trace to * * proceed with no routine filtering. * * MSGKO2O1144E issued on first panel of * * Application Trace Specification, * * blocking the ability to schedule a * * trace to a dataset currently in use. * * Incorrect format in ATVW command when * * Yes/No fields set to non-default value. * * MSGKO201107E Issued when CICSTRAN * * starts with a numeric, which should be * * valid. * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** When an invalid date was entered for the START DATE on the Trace Specification, MSGKO2O1107E mis-identified the invalid field as START TIME, and invalid START TIME was mis-identified as START DATE. If data was entered in just the two Routine name fields, or the first Routine name only and second line had Schema only, MSGKO2O1107E was bypassed and routine filtering was ignored. If a Trace is currently executing writing to the requested dataset, MSGKO2O1144E is entered on first panel, blocking the ability to schedule a trace to a dataset currently in use. When a YES/NO value pair was specified with a non-default value, the first such field would be on the same line as the prior name/value pair on the ATVW screen. When a CICSTRAN field is entered with a numeric in the first position, the field was incorrectly identified as invalid, and MSGKO2O1107E was issued.
Problem conclusion
MSGKO2O1107E will specify the correct field name when reporting on invalid specification of start date or time. MSGKO2O1107E will be issued if both schema and name are not specified for routine filtering. Issuance of MSGKO2O1144E indicating dataset in use will be deferred until the second specification panel, and only if request is for immediate trace execution. ATVW report has been modified to put each keyword/value pair on its own line. CICSTRAN field has been changed to accept transaction ID's which start with a numeric character.
Temporary fix
Comments
APAR Information
APAR number
PH12223
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
540
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-05-17
Closed date
2019-06-27
Last modified date
2019-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI63924
Modules/Macros
KO2ATRCB KO2ATRDB KO2ATVWB
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R540 PSY UI63924
UP19/06/28 P F906 ¢
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
01 July 2019