PTF metadata and audit details for Datacom maintenance

Products

• Datacom

Issue/Introduction

When updating Datacom maintenance, audit departments often require detailed information regarding the PTFs being applied. This includes Component identification, Priority, Impact, and Risk. Use the following procedures to extract this metadata from the mainframe environment or the Broadcom Support Portal.

Environment

Z/OS

Datacom 15.1 

Resolution

Method 1: Generating an SMP/E LIST Report

To identify installed PTFs, their associated FMIDs (Components), and their HIPER status (Priority), run the following JCL against the relevant Target zone:

//SMPE     EXEC PGM=GIMSMP,REGION=6M,PARM='DATE=U'
//SMPCSI   DD DSN=####.####.CSI,DISP=SHR
//SMPCNTL  DD *
  SET BDY(CAIT0) .
  LIST PTF .
/*

How to Interpret the Report for Audit Fields:

• Component Name: Cross-reference the FMID from the report (e.g., CAVEF10) with the official Datacom FMID list.
• Priority: PTFs containing the HIPER (High Impact Pervasive) tag should be classified as High Priority.
• PTF Type: The report will specify if the solution is a PTF (Error/Fix) or an APAR.
• Description: The DESCRIPTION field in the report provides a summary of what the PTF addresses.

Method 2: Broadcom Support Portal Lookup

For detailed Impact and Risk analysis, use the online Solution Search:

1. Log in to the Broadcom Support Portal.
2. Enter the PTF ID (e.g., LU02879) in the search bar.
3. Review the following sections:
   • Problem Description: Use for the "Description" field.
   • Symptom: Defines the "Impact" on the service.
   • Risk: The "Risk of not applying" is typically the occurrence of the described symptom (e.g., MUF Abend, Incorrect Results).
   • HOLDDATA: Check this section to determine if the PTF requires an IPL.

Additional Information

For a complete list of Datacom component FMIDs, refer to Datacom FMIDs