PK17787: POSSIBLE INVALID REMOTESYSTEM FOR BAS TRANDEF/PROGDEF INSTALL.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The REMOTESYSTEM name used for a BAS install of a PROGDEF or
  TRANDEF resource in a target system may be incorrect when the
  target system starts up, if the install is associated with a
  RASGNDEF that specifies a USAGE of REMOTE and a MODE of STAT.
  
  In this situation, the REMOTESYSTEM name used should be the
  SYSIDNT of the related system.  Instead, it will be the
  REMOTESYSTEM name specified in the PROGDEF/TRANDEF, or in the
  RASGNDEF override, if either is non-blank.
  
  Note that this error does not occur with ad-hoc installs of
  PROGDEFs and TRANDEFs through the PROGDEF, TRANDEF, or RESGROUP
  views.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex/SM V3R1M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: The REMOTESYSTEM name used for a BAS    *
  *                      install of a PROGDEF or TRANDEF         *
  *                      resource in a target system may be      *
  *                      incorrect when the target system starts *
  *                      up, if the install is associated with a *
  *                      RASGNDEF that specifies a USAGE of      *
  *                      REMOTE and a MODE of STAT.              *
  *                                                              *
  *                      In this situation, the REMOTESYSTEM     *
  *                      name used should be the SYSIDNT of the  *
  *                      related system.  Instead, it will be    *
  *                      the REMOTESYSTEM name specified in the  *
  *                      PROGDEF/TRANDEF, or in the RASGNDEF     *
  *                      override, if either is non-blank.       *
  *                                                              *
  *                      Note that this error does not occur     *
  *                      with ad-hoc installs of PROGDEFs and    *
  *                      TRANDEFs through the PROGDEF, TRANDEF,  *
  *                      or RESGROUP views.                      *
  ****************************************************************
  * RECOMMENDATION: The changes implemented by the PTF that      *
  *                 resolves this APAR could change the way      *
  *                 PROGDEFs and TRANDEFs are installed through  *
  *                 BAS.  If a PROGDEF or TRANDEF is             *
  *                 automatically installed through a RASGNDEF   *
  *                 that specifies a USAGE of REMOTE and a MODE  *
  *                 of STAT, then with the PTF in place, the     *
  *                 REMOTESYSTEM used when the PROGDEF or        *
  *                 TRANDEF is installed in the TARGET system    *
  *                 will be the SYSIDNT of the RELATED system.   *
  *                 Previously, if the PROGDEF or TRANDEF        *
  *                 specified a REMOTESYSTEM or the RASGNDEF     *
  *                 override specified a REMOTESYSTEM, this      *
  *                 would be used.  Please ensure that all BAS   *
  *                 definitions are updated to tolerate this     *
  *                 change before applying the PTF.  For more    *
  *                 information about this change, including a   *
  *                 table illustrating the differences, please   *
  *                 refer to the ACTion HOLD associated with the *
  *                 PTF.                                         *
  *                                                              *
  *                 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 a MAS starts, method EYU0BMES (BMES) is called to build the
  definitions for the BAS resources that should be installed in
  the MAS.  If the MAS is defined as the target system for a
  PROGDEF or TRANDEF that is installed via a RASGNDEF that
  specifies a USAGE of REMOTE and a MODE of STAT, BMES checks if
  the REMOTESYSTEM name in the definition or RASGNDEF override is
  non-null.  If it is, BMES will set the REMOTESYSTEM in the
  resource installed in the target system to this non-null value.
  If the value is null, then BMES will set the REMOTESYSTEM in the
  resource installed in the target system to the related system's
  SYSIDNT.  BMES should always be using the related system's
  SYSIDNT, regardless of the REMOTESYSTEM value in the definition
  or RASGNDEF override.
  

Problem conclusion

• BMES has been updated to always use the related system's SYSID
  as the REMOTESYSTEM when a PROGDEF or TRANDEF is installed in a
  target system at target system startup, if the install is
  associated with a RASGNDEF that indicates a USAGE of REMOTE and
  a MODE of STAT.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK15477

• APAR is sysrouted TO one or more of the following:

  UK10937

Modules/Macros

•    EYU0BMES EYU0BMRB
  

Fix information

• Fixed component name

  CPSM CICS 3.1

• Fixed component ID

  5655M1501

Applicable component levels

• R100 PSY UK10937

     UP06/01/24 P F601

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.