IBM Support

PTF service orders from 4 December 2020 to 10 December 2020 need to be reviewed

Notification


Risk classification

Red Alert

Affected Domain

All clients who placed service orders from 4 December 2020 to 10 December 2020 and received PTFs for z/OS and other software products on the z/OS platform as documented in this list PTFList.zip.

Abstract

An error in the PTF supply chain inadvertently added extraneous data to the parts shipped in the PTF list PTFList.zip.  This process was corrected and all affected PTFs were reloaded on 10 December 2020.

In December, clients known to be affected were informed.  Now, IBM® determined that additional clients might be affected.  IBM® recommends that all clients review the list of PTFs by taking the Recommended Action to determine whether any damaged PTFs were received during the affected dates. 

Description

If a PTF in the list PTFList.zip was received in a service order from 4 December 2020 to 10 December 2020, then there was extraneous data added to the parts.  
If the part contains ++MOD, the APPLY can fail with messages such as:
  • IEW2690E 3530 ONE OR MORE FIELD DESCRIPTORS IN GOFF RECORD rrr WITHIN MEMBER xxxxxx NOT VALID. ERRORID =  12.
  • IEW2307E 1032 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA.
  • IGW01513T RECFM INCOMPATIBLE -- INPUT RECFM = FB OUTPUT RECFM = U
If the part contains files other than ++MOD, the APPLY can succeed.  In such cases, the incomplete or extraneous data can lead to unpredictable results within the respective product.   

Recommended Action

  1. Run the following JCL provided via PTFList.zip against each of your global and target zones.  The JCL contains all of the PTFs that were affected from 4 December 2020 to 10 December 2020.    
  2. Review and sort the resulting output to verify whether any PTFs show a DATE/TIME REC between the dates from 4 December 2020 to 10 December 2020.  Note: If a PTF does not reside in the zones that the job was run against, then you can observe a RC04 and "NOT FOUND" entry.  The PTF does not need to be considered further for those zones. 
  3. If no PTFs fall within the date range, then no further action is required.
  4. If a PTF shows a DATE/TIME REC between the dates "20.339" (4 December 2020) and "20.345" (10 December 2020), then review steps 5, 6, and 7. 
  5. If the PTF is in RECEIVE status, then REJECT the PTF, reorder the PTF, and RECEIVE the new PTF:
    SET BDY(GLOBAL).
    REJECT S(OldAffectedPTF) BYPASS(APPLYCHECK,ACCEPTCHECK).
  6. If the PTF is in APPLY status, then REJECT the PTF, reorder the PTF, and RECEIVE the new PTF:
    SET BDY(GLOBAL).
    REJECT S(OldAffectedPTF) BYPASS(APPLYCHECK,ACCEPTCHECK).
    Then, APPLY the PTF again with REDO parameter:
    SET BDY(tzone).
    APPLY S(NewAffectedPTF) REDO.
    Follow your normal product procedures to ensure that NewAffectedPTF is activated on your system.
  7. If the PTF is in ACCEPT status, follow the instructions in step 6.  Additionally, ACCEPT the new PTF:
    SET BDY(dzone).
    ACCEPT S(NewAffectedPTF) REDO.
PTFList.zip  is available for download:
ftp://public.dhe.ibm.com/eserver/zseries/zos/alert/PTFList.zip
https://testcase.boulder.ibm.com/fromibm/mvs/PTFList.zip

Date first published

13 April 2021

[{"Risk Classification":"Red Alert","Line of Business":{"code":"LOB56","label":"Z HW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG90","label":"z\/OS"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
14 April 2021

UID

ibm16441973

Page Feedback