A fix is available
APAR status
Closed as program error.
Error description
You receive a RESPONSE( FAILED ) REASON( EXCEPTION ) ( 1038 / 1361 ) trying to update a result set. This happens either through the CICS Explorer or through a user API program. . A review of the CMAS AUX trace shows trace entries similar to the following: . XDNI XDNR XDNR DAT EXCP 1 ABM0err1 EUI COMERM CMAS hh:mm:ss MOFB XDY7 XDNR DAT EXCP 5 METHFAIL EUI COMERM CMAS hh:mm:ss XDY7 XDNR XDNR DAT EXCP 1 MOFBFAIL EUI COMERM CMAS hh:mm:ss . Additional Symptom(s) Search Keyword(s): KIXREVEPH
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: You execute a batch API program which * * invokes the UPDATE verb to apply a * * modification string to a result set * * of BAS CICS resource definitions (for * * example, PROGDEFs). The UPDATE returns * * a response and reason of TABLEERRROR / * * DATAERROR. You then execute the API * * FEEDBACK verb to retrieve FEEDBACK * * resources describing the problem. * * Either the FEEDBACK verb fails with a * * response and reason of * * FAILED / EXCEPTION * * or the returned FEEDBACK resources * * contain error codes which do not relate * * to the failed action. For example, * * UPDATE of a BAS resource might return * * an error code which is relevant to up- * * dating of resources in the CICS CSD. * * * * After receiving a response and reason * * of * * TABLEERROR / DATAERROR * * from an API UPDATE verb, you execute * * the FEEDBACK verb without passing the * * result token of the target result set. * * The thread FEEDBACK resource indicates * * that the command returned a response of * * OK. FEEDBACK against the result set * * token returns the correct response and * * reason codes in FEEDBACK resources. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and CICS regions configured * * as Single Server (SMSS) regions must be re- * * cycled to pick up the new code. Note that * * regions do not need to be brought down and * * restarted at the same time. * **************************************************************** After executing the Method Argument List (MAL) for an update module EYU0XDH7 (XDH7 - API UPDATE Command Processor) invokes EYU0MOFB (MOFB - Internal FEEDBACK Generator) to initialize the Thread FEEDBACK block. It does not pass the FEEDBACK block for the result set, so the result set FEEDBACK still points to the action definition for the GET which built the result set. When the FEEDBACK verb is invoked to retrieve Result Set FEEDBACK resources, the error status value in the MAL for the UPDATE action is interpreted using the actionerror data from the GET action definition. If no actionerror entries were defined for the GET action, or if none of the actionerror entries match the error status value, the FEEDBACK verb will return response and reason of FAILED / EXCEPTION. If the error status from the UPDATE MAL is found, FEEDBACK resources will be returned, but the FEEDBACK error code will reflect the GET action. Module EYU0XDH7 invokes module EYU0XDP1 (XDP1 - API GET Com- mand Processor) passing a queue containing resource instances for which the update failed, to build an internal result set identifying the failing resources. This internal GET causes the Thread FEEDBACK block to be updated with the response and reason for the GET (probably RESPONSE=OK). This ovewrites the original error response and reason stored for the failed UPDATE.
Problem conclusion
Module EYU0XDH7 was modified to pass addresses of both the Thread and Result Set FEEDBACK blocks to EYU0MOFB. Module EYU0XDP1 was modified to bypass copying the current response and reason codes into the Thread FEEDBACK block if invoked by another API command passing a queue of resources. Module EYU0MOFB was modified to bypass tracing the MAL work area if a MAL address is not available.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM90630
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
70M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-06-07
Closed date
2013-06-20
Last modified date
2013-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK95276 UK95277
Modules/Macros
EYU0MOFB EYU0XDH7 EYU0XDP1
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.2","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.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 July 2013