PJ40442: RCAT AND IMAGE FALLBACK

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • See Problem Summary.
    

Local fix

  • na
    

Problem summary

  • APAR NUMBER:  PJ40442
    PRODUCT:  z/TPF
    FUNCTIONAL AREA:  MESSAGE ROUTER
    SHIPPED IN PUT:  10
    
    ABSTRACT:
    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.
    
    PACKAGE CONTENTS:
    Source Segments:
    (C) base/rt/conn.asm
    (C) base/macro/ck8ke.mac
    
    Object Only Binaries:
    None.
    
    Configuration Independent Binaries:
    None.
    
    Support Files:
    None.
    
    OTHER BINARIES TO BUILD: YES
    (C) <sys>/obj/conn.o
    (C) <sys>/load/CONN.so
    (C) <sys>/load/CTKC.kpt
    (C) <sys>/obj/ctkc.o
    
    COMMENTS:
    A customer came across a situation in which they IPLed an image
    which had a new ANT table, and this caused restart segment CONN
    to rebuild the RCAT records. The customer later decided to fall
    back to the previous image. During the IPL of the fallback
    image, CONN made the incorrect determination (based on the
    settings in the fallback image's version of COHA) that the RCIT
    records did not need to be rebuilt. As a result, the Prime CRAS
    terminal was no longer able to be used, since the ANT index for
    SMP was no longer correct for the fallback image. A design
    change has been made to the z/TPF system restart scheduler to
    have realtime segment CONN.ASM rebuild the RCIT from RCAT
    records any time a TPF system is IPLed with both a new image
    number and program area number from the previous IPL.
    

Problem conclusion

  • SOLUTION:
    A design change has been made to the z/TPF system restart
    schedule which involves having realtime segment CONN.ASM check
    two new fields in keypoint c, in order to determine if the
    current IPL is on a different image number and program area
    number than the last system to IPL. If either the image number
    or the program area number (or both) are the same as the
    previous IPL, then the code continues processing as it
    originally did. However, if both the image number and program
    area number are different from the previous IPL, then the new
    image number and program area number are filed out to keypoint
    C, the image load mask in COHA mask is all zeroed out, and we
    force a rebuild of the RCIT from the RCAT records. By resetting
    the image load mask in COHA, any other z/TPF processors in the
    loosely-coupled complex will rebuild the RCIT from the RCAT
    saved on file during their next IPL.
    
    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.
    
    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 CONN conn.o
    maketpf -f CTKC
    maketpf CONN 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/PJ40442.htm
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ40442

  • Reported component name

    Z/TPF

  • Reported component ID

    5748T1501

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-06

  • Closed date

    2012-11-15

  • Last modified date

    2012-11-15

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

TPF
z/TPF

Software version:

110

Reference #:

PJ40442

Modified date:

2012-11-15

Translate my page

Machine Translation

Content navigation