PJ40768: RCAT AND IMAGE FALLBACK

APAR status

• Closed as program error.

Error description

• See Problem Summary.
  

Local fix

• PUNCH '* '
  
  .CRASTD   ANOP
  
  PUNCH '         DC    XL1''00''           COHA IMAGE NUMBER'
  
  PUNCH '         DC    XL1''00''           COHA PROGRAM AREA
  NUMBER'
  
  rather than:
  
  PUNCH '         DC    XL1''00''           COHA IMAGE NUMBER'
  
  PUNCH '         DC    XL1''00''           COHA PROGRAM AREA
  NUMBER'
  
  PUNCH '* '
  
  .CRASTD   ANOP
  
  The branch to  CRASTD is being taken during the build of sip and
  the two new fields are not being generated in the resulting
  ctkc.
  

Problem summary

• APAR NUMBER:  PJ40768
  PRODUCT:  z/TPF
  FUNCTIONAL AREA:  MESSAGE ROUTER
  SHIPPED IN PUT:  10
  
  ABSTRACT:
  With PJ40442 applied, the RCIT may be built from RCAT records
  on every IPL.
  
  PACKAGE CONTENTS:
  Source Segments:
  (C) base/macro/sip/skctkc.mac
  
  Object Only Binaries:
  None.
  
  Configuration Independent Binaries:
  None.
  
  Support Files:
  None.
  
  OTHER BINARIES TO BUILD: YES
  (C) <sys>/obj/ctkc.o
  (C) <sys>/load/CTKC.kpt
  
  COMMENTS:
  APAR PJ40442 involved making a design change to rebuild RCIT
  records from the RCAT when an IPL occurs and both the image
  number and program area number selected are different than the
  previous IPL. This involved adding new fields to the CTKC
  keypoint and requires a new keypoint be loaded. However, if the
  keypoint is generated through z/TPF SIP, the keypoint is
  generated with an incorrect length and this can cause the RCIT
  to be rebuilt from file on every IPL of the z/TPF system.
  
  The skctkc.mac macro has been modified to create ctkc.asm with
  the correct length. Customers may still use the manual method
  of updating the length field in CTKC on their systems, as
  described in the migration considerations section of APAR
  PJ40442.
  

Problem conclusion

• SOLUTION:
  The skctkc.mac macro has been modified to punch the correct
  length computation, so that when ctkc.asm is created using the
  SIP generation process that ctkc will have the correct length
  value when it is assembled. Customers may still use the manual
  method of updating the length field in CTKC on their systems,
  as described in the migration considerations section of APAR
  PJ40442.
  
  COREQS: NO
  None.
  
  MIGRATION CONSIDERATIONS: YES
  System generation process (SIP) changes:
  In order for conn.asm to properly save the current image number
  and program area number during an IPL, CTKC must be reassembled
  and reloaded in order for the keypoint size to be updated in
  the keypoint record on file. If the keypoint is not reloaded,
  then conn.asm will not properly recognize if the image number
  and program area number match the values from the previous IPL,
  as such will force a reload of the RCIT records from the RCAT
  saved on file during each IPL. In addition, the first time an
  IPL is done after installing this APAR, the processor load mask
  will be reset in COHA, which will therefore cause each
  processor in the loosely-coupled complex to rebuild its RCIT
  from the RCAT the next time they are IPLed.
  
  
  
  BUILD COMMANDS AND INSTRUCTIONS: YES
  #maketpf commands for linux
  maketpf -f CTKC ctkc.o
  maketpf CTKC link
  
  UPDATED INFORMATION UNITS: NO
  None.
  
  See your IBM representative if you need additional information.
  
  DOWNLOAD INSTRUCTIONS:
  http://www.ibm.com/software/htp/tpf/maint/maintztpf.html
  
  APAR URL:
  http://www.ibm.com/software/htp/tpf/ztpfmaint/put10/PJ40768.htm
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  Z/TPF

• Fixed component ID

  5748T1501

Applicable component levels

• R110 PSY

     UP