A fix is available
APAR status
Closed as program error.
Error description
Recently, I defined a number of SYSLINK records in the CICSPlex SM repository with connection type SNA (as a replacement for the IPIC SYSLINKs we used until now). However, after restarting the CICS TS regions involved, no installation of the MRO connections takes place. Manual installation by means of the WUI services works fine. The value of AUTOINST in the CSYSDEF records is set to ALWAYS. On the restart of the MAS, the IPIC SYSLINKS are re-installed instead of the newly added MRO SYSLINKS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R1M0 Users * **************************************************************** * PROBLEM DESCRIPTION: You use CPSM SYSLINK definitions to * * manage connections between your MASes. * * When converting your existing SYSLINKs * * from IPIC to SNA (or from SNA to IPIC) * * you create a new SYSLINK for each of * * your existing connections, and then * * remove the original SYSLINKs. When * * you restart your MASes with a COLD or * * INITIAL start, connections of the ori- * * ginal type are installed, rather than * * of the new type. If you restart the * * CMAS to which they connect, the next * * time you bring the MASes up again with * * a COLD or INITIAL start, connections * * of the correct type will be installed. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes must be recycled to pick * * up the new code. Note that CMASes do not * * need to be brought down and restarted at * * the same time. * **************************************************************** When a MAS is started for which BAS is to install resources, the connection matrix is scanned for all SYSLINK resources for which the MAS is the primary or secondary system. Originally there could only be one SYSLINK for a given pair of MASes, but when IPIC SYSLINKs were added, it became possible to have two SYSLINK associations between a pair of MASes: one SNA, and one IPIC. When a SYSLINK resource is created or updated, a copy of the resource table is extracted from the data repository and passed to module EYU0BMLA (BMLA - BAS Create SYSLINK Association), but the LINKTYPE attribute (SNA or IPIC) is not saved in the BAS SYSLINK definition element (SLNK). When a SYSLINK is removed, a copy of the SYSLINK resource table must be built by BAS, be- cause the real record has been deleted. The Definition Change notification (EDEFCHG) received by BAS does not contain the link type, so this field is not initialized in the SYSLINK copy. When a SYSLINK definition is removed, module EYU0BMLR (BMLR - BAS Remove SYSLINK Association) removes the first SYSLINK assoc- iation between the primary and secondary MASes, regardless of the LINKTYPE. If the CMAS has not been restarted since a new SYSLINK was created between the MASes, the new association will be removed and when SYSLINKs are installed at MAS initialization the original SYSLINK will be processed. If the CMAS is restarted before restarting the MASes, the Association Matrix will be rebuilt from the contents of the data repository, and the correct link type will be installed.
Problem conclusion
Module EYU0BMDC (BMDC - BAS Process EDEFCHG Event) was modi- fied to determine the type of SYSLINK by examining the restype of the connection resource: if a CONNDEF resource, the LINKTYPE is set to SNA, if an IPCONDEF resource, the LINKTYPE is set to IPIC. Module EYU0BMZ2 (BMZ2 - Extended SYSLINK Association Processing) was modified to store the LINKTYPE in the BAS SLNK element when a SYSLINK is added or updated. Module EYU0BMLR was modified to compare the LINKTYPE of the SYSLINK being removed with the LINKTYPE in each SLNK element to insure that the de- sired SYSLINK association will be removed.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI04755
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
80M
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-10-24
Closed date
2013-11-18
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:
UI12627
Modules/Macros
EYU0BMDC EYU0BMLR EYU0BMZ2 EYU0BMZR EYU9BAR3 EYU9BAR4 EYU9BAR6 EYU9BARU
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R80M PSY UI12627
UP13/12/02 P F311
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