A fix is available
APAR status
Closed as program error.
Error description
You are trying to use CPSM BATCHREP to add resources to your CICSplex. You specify option DUPREC SKIP so that if you need to rerun the job you won't have to delete records first, and can simply use the same control cards as input on successive BATCHREP runs. With DUPREC SKIP, CPSM is supposed to continue processing when it tries to add a record to the EYUDREP repository and finds one already exists. That isn't however working for LNKSxSCS Records (LNKSMSCS, LNKSRSCS, LNKSWSCS). With those resources, you are instead receiving Status(LNKASSOC_EXISTS). Additional Symptom(s) Search Keyword(s): KIXREVSVR
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R1M0 Users * **************************************************************** * PROBLEM DESCRIPTION: - When the BATCHREP or EYU9XDBT * * facilities are used to create * * linkage records between CICS groups * * or systems, and Monitor, RTA or WLM * * specifications, invalid results can * * occur when using the option that * * allows duplicate records to be * * skipped. * * * * The linkage records affected are: * * * * - LNKSMSCG - CSYSGRP to MONSPEC * * - LNKSMSCS - CSYSDEF to MONSPEC * * - LNKSRSCG - CSYSGRP to RTASPEC * * - LNKSRSCS - CSYSDEF to RTASPEC * * - LNKSWSCG - CSYSGRP to WLMSPEC * * - LNKSWSCS - CSYSDEF to WLMSPEC * * * * For BATCHREP, duplicate records are * * not recognized. This can result in * * the BATCHREP run being terminated * * abnormally with message EYUXU0218I * * when OPTION DUPREC SKIP is * * specified. * * * * For EYU9XDBT, links to different * * xxxSPECs are invalidly recognized as * * duplicate records. This can result * * in the run not being terminated * * correctly when OPTION DUPREC SKIP is * * specified. Instead, message * * EYUXU1447I is issued and the job * * ends with a return code of 0. * * * * - When the LNKSxSCx CHGSPEC action is * * used to change the link between a * * CICS group or system from one * * xxxSPEC to a different xxxSPEC, * * invalid results may occur: * * * * - If a link to the xxxSPEC already * * exists, either the record is * * updated and a response of OK is * * returned or a response of * * FAILED_EXCEPTION is returned, * * instead of an indication that the * * link already exists. * * * * - If a link already exists to a * * xxxSPEC that is not the same as * * the OLD_SPECNAME provided, a * * response of FAILED_EXCEPTION is * * returned instead of an indication * * that a different association * * already exists. * * * * - When the xxxSPEC ADDSYSDEF or * * ADDSYSGRP action is used to * * associate a CICS group or system to * * a xxxSPEC, and the link already * * exists, an invalid error code is * * returned, instead of the proper * * error code of 4 (REC_EXISTS): * * * * - for MONSPEC, an error code of 8 * * (LNKASSOC_EXISTS) is returned. * * * * - for RTASPEC, an error code of 9 * * (LNKASSOC_EXISTS) is returned. * * * * - for WLMSPEC, an error code of 23 * * (LNKASSOC_EXISTS) is returned. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes must be recycled * * to pick up the new code. Note that regions * * do not need to be brought down and restarted * * at the same time. * **************************************************************** - BATCHREP and EYU9XDBT use different methods to determine if a duplicate record exists when a CREATE is requested: - For BATCHREP, method EYU0XDBR (XDBR) examines the status returned from the CREATE method to determine if it is 'RECORD_EXISTS'. The CREATE method for LNKSxSCx records, EYU0TAAS (TAAS), returns 'LNKASSOC_EXISTS' when a duplicate record exists. As a result, BATCHREP does not recognize when a duplicate record is being created. This will cause the BATCHREP run to be aborted invalidly when OPTION DUPREC SKIP has been specified. - For EYU9XDBT, program EYU9XDBT examines the API FEEDBACK record error code (FEEDBACK_ERROR_CODE) to determine if it is a 4. For the LNKSxSCX records, an error code of 4 is returned when the create method, TAAS, returns a status of 'LNKASSOC_EXISTS'. Since TAAS returns this status for when either a duplicate record exists or when an existing link to another xxxSPEC exists, both cases are recognized as duplicate record conditions. This will cause the EYU9XDBT run to not be aborted when the OPTION DUPREC SKIP is used and a there is an existing LNKSxSCx record to a different xxxSPEC. - When the LNKSxSCx CHGSPEC action is issued, method EYU0TAUS (TAUS) is passed the name of the CICS group or system, along with the name of the existing xxxSPEC (OLD_SPECNAME) and the xxxSPEC to be changed to (NEW_SPECNAME). - If the NEW_SPECNAME is the same as the existing xxxSPEC, TAUS either allows the record to be updated and returns a response of OK, or returns a response of FAILED_EXCEPTION. - If the OLD_SPECNAME is not the same as the existing xxxSPEC, TAUS returns a response of FAILED_EXCEPTION. - When the xxxSPEC ADDSYSDEF or ADDSYSGRP action is issued, and the link requested already exists, method BARH (BARH) returns a status of 'LNKASSOC_EXISTS' instead of a status of 'RECORD_EXISTS'.
Problem conclusion
To resolve the problems described above, the following changes have been made: - TAAS and TAUS have been updated to return a response of OK and a status of 'RECORD_EXISTS' if a link already exists to the requested xxxSPEC. - TAAS and TAUS have been updated to return a response of OK and a status of 'LNKASSOC_EXISTS' if a link already exists to a different xxxSPEC. - The LNKSxSCx tables have been updated so that if a CREATE or CHGSPEC action returns a status of 'RECORD_EXISTS', an error code of 4 (REC_EXISTS) will be set. - The LNKSxSCx tables have been updated so that if a CREATE or CHGSPEC action returns a status of 'LNKASSOC_EXISTS', an error code of 13 (LNKASSOC_EXISTS) will be set. - BARH has been updated to return a status of 'RECORD_EXISTS' when the association it is asked to create for the xxxSPEC ADDSYSDEF or ADDSYSGRP actions already exists.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI14972
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
80M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-01
Closed date
2014-05-01
Last modified date
2015-03-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI17586
Modules/Macros
EYU0BARH EYU0TAAS EYU0TAUS EYU0XDGS EYU0XDSS EYU9TSP3 EYU9TSP4 EYU9TSPU EYU9XDP3 EYU9XDP4 EYU9XDP6 EYU9XDPU EYUA5633 EYUA5634 EYUA5635 EYUA5636 EYUA5637 EYUA5638 EYUC5633 EYUC5634 EYUC5635 EYUC5636 EYUC5637 EYUC5638 EYUE5633 EYUE5634 EYUE5635 EYUE5636 EYUE5637 EYUE5638 EYUK5633 EYUK5634 EYUK5635 EYUK5636 EYUK5637 EYUK5638 EYUL5633 EYUL5634 EYUL5635 EYUL5636 EYUL5637 EYUL5638 EYUP5633 EYUP5634 EYUP5635 EYUP5636 EYUP5637 EYUP5638 EYUS5633 EYUS5634 EYUS5635 EYUS5636 EYUS5637 EYUS5638 EYUT5633 EYUT5634 EYUT5635 EYUT5636 EYUT5637 EYUT5638 EYUY5633 EYUY5634 EYUY5635 EYUY5636 EYUY5637 EYUY5638
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R80M PSY UI17586
UP14/05/08 P F405
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":"5.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":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 March 2015