A fix is available
APAR status
Closed as program error.
Error description
A failure will occur when creating the EVALDEF if using the MNRIOWT attribute as the field to evaluate. You would like the event message CPSM issues to include the task ID, filename and terminal ID. As the event messages only contain the key fields associated with the record, you can create an EVALDEF against the TASKFILE resource table to include the task ID and filename in the event message. The message will be similar to the following: EYUPN0007W cmasname Notify created for RTADEF TASKFILE by MRM, Context=plexname, Target=masname, Sev=VHS, Resource=TASKFILE, Key=48,EYUHISTA, Text=taskfile start. Additional Symptom(s) Search Keyword(s): KIXREVCTC
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: The CREATE or UPDATE of an EVALDEF will * * fail if the EVALCOL attribute (Field * * being evaluated) is set to an eight * * byte attribute of type INT16US (for * * example, the MLOCTRAN CPUTIME * * attribute) or of type SCLOCK (for * * example, the TASKFILE MNRIOWT * * attribute). * * * * If the EVALDEF is associated with an * * RTADEF, the install of that RTADEF will * * fail also. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes must be restarted. Note * * that the restarts do not need to occur at * * the same time. * **************************************************************** When an EVALDEF is created or updated, method EYU0PAEC (PAEC) calls method EYU0MOFS (MOFS) to validate the EVALDATA (Evaluation data value) for the EVALCOL from external to internal format. A logic error in MOFS causes the validation to fail if the EVALCOL specifies an attribute which is an eight byte field of type INT16US or SCLOCK. The failure is propagated back to PAEC, resulting in the failure of the create or update. Note that this processing occurs in the maintenance point (MP) CMAS for the CICSplex that the EVALDEF is associated with. When an RTADEF associated with an EVALDEF that specifies an EVALCOL attribute that is of type INT16US or SCLOCK is installed, method EYU0PECD (PECD) calls MOFS to convert the data to internal format. The same logic error that fails validation will fail the conversion, which results in the failure of the install of the RTADEF. Note that for MRM, this will take place in the CMAS to which the MAS is connected, and for APM, this will take place in the analysis point CMAS.
Problem conclusion
MOFS has been updated to properly validate and convert eight byte fields of type INT16US or SCLOCK from external to internal format.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI08426
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
60M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-18
Closed date
2014-02-18
Last modified date
2014-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI08510 UI15222 UI15223
Modules/Macros
EYU0MOFS
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 March 2014