II08695: CORRECT WAY TO CHANGE CFRM POLICY FOR XCF XES

APAR status

• Closed as canceled.

Error description

• SEARCH ARGUMENT = SYSPLEXINFO  DB2INFO
  
  This APAR describes the procedures for all types of
  COUPLE datasets that use IXCMIAPU to format the policy
  data, including CFRM, SFM,ARM.
  
  The proper procedure is to run IXCMIAPU against the
  "live" CFRM couple datasets to define the desired new
  policy.  This is done by omitting the DSN keyword from the
  IXCMIAPU job.  Use SETXCF START,POLICY to activate the
  modified policy.  It is not necessary to STOP the old policy
  first.
    -
  See >>EXAMPLE below to step by step instructions.
  -
  
  The policy change process works this way because the active
  CDS(es) contains 2 distinct areas:  an "active policy" area
  and an "administrative policy" area.  The active policy area
  contains the customer's in-effect active policy definition
  (say POLICY1) plus much real-time status info on
  connectors/structures/etc.  The administrative policy
  contains the administrative policy definition information
  only (no real-time info) for ALL policies that were defined
  by the utility.  This includes both the administrative data
  for the currently-active policy (POLICY1) and any other
  defined policies (POLICY2,  POLICY3, etc).  These two areas
  are quite separate.
    -
  You do not need to worry about the policy utility updating
  (and overlaying) your ACTIVE policy, thereby harming your
  sysplex.  This cannot happen.  The policy utility NEVER
  UPDATES THE ACTIVE POLICY AREA -- it only updates the
  administrative definition area of the dataset with new
  information.  So, after you run the policy utility and
  define new or changed administrative policies, NOTHING HAS
  CHANGED RELATIVE TO THE ACTIVE POLICY.  The same active
  policy definitions are in effect after the utility runs as
  before the utility ran.
    -
  The next step,  of course,  is to activate a new policy
  definition via SETXCF START,POLICY.  At the time this
  command is processed, the admin statements for the new
  policy are copied into the active policy area (this is the
  ONLY process that crosses the line between the admin and
  active areas of the CDS).  This is where the rubber hits the
  road and new policy definitions have the ability to start
  affecting (for better or worse) the operation of the
  sysplex.  Note that not all policy changes take effect
  immediately -- some may become pending, in accordance with
  some fairly detailed rules for pending policy changes
  which are well-documented in Setting Up a Sysplex Chapter 4.
    -
  It is very easy to back out a policy change.  Let's say you
  start with one and only one policy (for simplicity),
  POLICY1.  It starts by being the only admin policy defined,
  and also the active policy.  Then you want to make some
  policy change, but you want it to be easy to back out.
  What you do is define a new admin policy, POLICY2, which
  is identical to POLICY1 except in the area that you intended
  to change.  Then you activate POLICY2.  If you subsequently
  become unhappy with the POLICY2 definitions and need to back
  them out, you can activate POLICY1 again and go back to the
  old definitions.
  Note:'Backing out' a policy change is, in effect, a separate
  policy change, and is still subject to the rules for pending
  policy changes, mentioned above.
  
  See related APAR OW26432 for additional information
  about couple data sets and policies.
  
   -
  >>EXAMPLE
  The steps to add a new CFRM policy and to make it active are:
  1) Run the Policy Utility (IXCM1APU) to update the current
     CFRM couple data sets. This is done by omitting the DSN
     keyword. This is an example to define policy NEWPOL.  It
     must be run on a system in the sysplex to be updated.
     Notice, the DSN keyword is not specified.
  //IXCCFRMP JOB
  //STEP20   EXEC PGM=IXCMIAPU
  //SYSPRINT DD   SYSOUT=A
  //SYSABEND DD   SYSOUT=A
  //SYSIN    DD   *
  
       DATA TYPE(CFRM) REPORT(YES)
  
       DEFINE POLICY NAME(NEWPOL) REPLACE(YES)
  
          CF NAME(FACIL01)
                 TYPE(009674)
                 MFG(IBM)
                 PLANT(02)
                 SEQUENCE(000000040102)
                 PARTITION(1)
                 CPCID(00)
                 DUMPSPACE(2000)
  
          STRUCTURE NAME(IXCSTR1)
                 SIZE(10000)
                 INITSIZE(1000)
                 PREFLIST(FACIL01)
  /*
  2) Start the policy. Issue:
     SETXCF START,POLICY,TYPE=CFRM,POLNAME=NEWPOL
  
  3) The sysplex should now be using the new policy. Issue:
     D XCF,POLICY,TYPE=CFRM to be sure.
   -
  ADDITIONAL SYMPTOMS:
  IXC276I CC12
  

Local fix

• SYMPTOMS:  msgixc276i rc4 rsn02100000 RC04  RC02100000
  SEARCH ARGS: CFRM SFM POLICY COUPLE DATASET DATA SET
  FUNCTION
  

Problem summary

Problem conclusion

Temporary fix

Comments

• close for internet view
  

APAR Information

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

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

Fix information

Applicable component levels