General Page
Enhanced HOLDDATA for z/OS replaced the HOLDDATA previously delivered on ESOs, Corrective Service orders, and PDOs.
Note: See FLASH10820 for important changes to z/OS preventive service ordering which occurred in 3Q 2014.
z/OS Version 1 Release 10 and SMP/E Release 3.5 in 2008 introduced FIXCAT HOLDDATA to simplify identifying required service from PSP buckets and other fix categories such as Coexistence. The new FIXCAT statements are available only in the full.txt and full.bin files.
Check the IBM Fix Category Values and Descriptions to learn more about FIXCAT HOLDDATA.
Enhanced HOLDDATA for z/OS is a single source of ERROR and FIXCAT HOLDDATA, and provides several advantages over previous sources of ERROR HOLDDATA to simplify identification and management of critical service (PEs and HIPERs).
- Enhanced HOLDDATA includes ERROR ++HOLDs not only for PE APARs, but also for HIPER (High Impact) APARs. Thus the SMP/E REPORT ERRSYSMODS identifies not only missing PE fixes but also missing HIPER fixes, and the report is specific to the target system. The additional ++HOLDs for HIPER require a procedure change for the installation of FMIDs.
- Enhanced HOLDDATA includes the fixing PTF number in the comment field when the PTF is available for either corrective service (COR closed) or preventive service (PER closed). The two date fields in the ++HOLD statement represent the date that the ++HOLD was updated, and not necessarily the original date of the APAR flag.
- Any reason flags for HIPER APARs are included in the comment field (IPL, data loss, major function loss, performance, and pervasive). These flags aid prioritizing review of uninstalled HIPER fixes. HIPER reason flags are listed here.
- The SMP/E REPORT ERRSYSMODS is a summary of missing critical service, identifies whether any fixing PTFs are in RECEIVE status (available for installation), and if the chain of PTFs to resolve the error has outstanding PEs.
- The Enhanced HOLDDATA file is available using SMP/E RECEIVE ORDER, in ShopzSeries deliverables, and in this downloadable HOLDDATA file.
- The entire z/OS platform of SMP/E managed products is covered with a single set of holddata that is cumulative and complete. There is no need to collect and compile holddata from multiple sources for different systems at differing times. Enhanced HOLDDATA serves as a single source of holddata for any system. SMP/E ignores holddata for FMIDs not on the system (unless specified otherwise on the RECEIVE command), so Enhanced HOLDDATA can serve any system. Installations with many programmers receiving Enhanced HOLDDATA might need to use caution to ensure that only the latest Enhanced HOLDDATA is received. One way to ensure that latest Enhanced HOLDDATA is used is to get electronic updates by using SMP/E RECEIVE ORDER or the Internet to acquire the daily updates to Enhanced HOLDDATA (next two items).
- SMP/E RECEIVE ORDER, which is available on SMP/E 3.4 and later releases, is the recommended method to acquire all z/OS stack PTFs and HOLDDATA, as it is tailored on every request based on what you need. It can be automated in a Batch JOB to run daily so that you never have to separately retrieve anything before you install because the daily automation already did. Basically, once set up, it is “hands off” with zero human work necessary, and other software vendors follow similar processes. More information on setting up SMP/E RECEIVE ORDER can be found at SMP/E Internet Service Retrieval.
- Daily updates to Enhanced HOLDDATA are also available by using FTPS, and up to 3 years of history is available. Customers that use Enhanced HOLDDATA need to ensure only the time span of the latest Enhanced HOLDDATA to be received overlaps any previously received holddata. If available, SMP/E RECEIVE ORDER is more robust method to acquire HOLDDATA and PTFs. More information on the RECEIVE ORDER command can be found in the SMP/E Commands manual. You can find the manual corresponding to your system level at SMP/E Commands. Note: plain FTP for download was removed on 12 February 2023, so FTPS must be used instead. See Disablement of unsecure connection methods.
HOLDDATA for Security-Integrity fixes is available through the IBM Z and LinuxONE Security Portal. Information on registration and accessing the IBM Z and LinuxONE Security Portal is available at the z System integrity page. If you are already registered, you can link directly to the IBM Resource Link Security Alerts.
The HOLDDATA available from the IBM Z and LinuxONE Security Portal adds a new HOLD CLASS, SECINT, and the HOLD SYMPTOMS contains the CVSS Base and Temporal scores. Further information about CVSS and a guide to scoring can be found on the FIRST (Forum of Incident Response and Security Teams) website http://www.first.org/cvss/ . Additional information is available in the IBM Z and LinuxONE Security Portal frequently asked questions (FAQs) page.
If not using SMP/E RECEIVE ORDER with CONTENT(HOLDDATA) to acquire HOLDDATA, download the file that overlaps the time from your last update of Enhanced HOLDDATA. Receiving the same HOLDDATA again causes no problems, but missing HOLDDATA can result in installation of a known PE and thus impact system availability. Always select a time period long enough to overlap your last update. Normally use one of the 'full' files to get the previous 2 year's ERROR and FIXCAT holddata.
Use any of the following methods to identify your last update of Enhanced HOLDDATA,
- The production date of your last service deliverable that included Enhanced HOLDDATA,
- The date of your last electronic Enhanced HOLDDATA update,
- The comments in the header of your last Enhanced HOLDDATA file, or
- List your already-received HOLDDATA.
Use the SMP/E RECEIVE command to receive Enhanced HOLDDATA into your global CSI.
All files are updated daily.
To download the plain text files by using the browser, click the name in the Download Now column to download the file to your workstation. Most browsers use a cached copy of previously displayed pages, so you might need to use the reload or refresh button of the browser to retrieve the latest copy from the server.
- Use "file/save-as" to save the data to the specified file on the workstation. (This command varies depending upon the web browser you are using).
- Upload to the z/OS Host system by using any file transfer facility, note the resultant data set on the Host must be FB80.
- The .bin files must upload to the z/OS Host system as binary data by using any file transfer facility. Note the resultant data set on the Host must be RECFM=FB LRECL=1024.
- Use AMATERSE to unpack the packed (.bin) file into a data set.
|
Name |
Time Span |
Plain text |
Packed Data |
FIXCATs |
||
|
Size |
Download |
Size |
Download |
|||
|
Month |
Last 30 days |
~ 100 Kb |
~ 24 Kb |
No |
||
|
Quarter |
Last 90 days |
~ 300 Kb |
~ 47 Kb |
No |
||
|
Year |
Last 365 days |
~1200 Kb |
~ 200 Kb |
No |
||
|
Full |
Last 730 days |
~2250 Kb |
~ 400 Kb |
YES |
||
|
YRS3 |
Last 3 years |
n/a * |
n/a * |
~600 Kb |
No |
|
* The 3-year file is only available in compressed (TRSMAIN) format.
Note: SMP/E requires the data set containing HOLDDATA to be recfm=FB and lrecl=80. FTP and emulator program uploads usually default to a data set format of VB. Pre-allocate the target data set as FB-80 or specify parameters on upload to the z/OS Host so the target data set is FB-80.
Downloading of Enhanced HOLDDATA can be more easily accomplished by using the SMP/E RECEIVE ORDER CONTENT(HOLDDATA) command.
FTPS Download to Host Instructions
If not using SMP/E RECEIVE ORDER, FTPS can be used to download Enhanced HOLDDATA. Plain FTP for download was removed on 12 February 2023, so FTPS must be used instead. See Disablement of unsecure connection methods.
FTPS anonymously to "public.dhe.ibm.com". Change directories to "/s390/holddata". Preferably get the Full file, "full.txt".
Note: SMP/E requires the data set containing HOLDDATA to be recfm=FB and lrecl=80. FTP normally defaults to a data set format of VB. Pre-allocate the target data set as FB-80 or specify FTP parameters so the target data set is FB-80.
Enhanced HOLDDATA is processed the same way previous HOLDDATA was processed. Use SMP/E's RECEIVE HOLDDATA command to receive Enhanced HOLDDATA into the Global zone.
Enhanced HOLDDATA introduced ERROR holds against product FMIDs for HIPER APARs. Thus, customers can easily check that all PE and HIPER service is installed when the FMID is being APPLYed. Furthermore, it enables the SMP/E REPORT ERRSYSMODS to identify any HIPER fixes that are missing. To ensure all recommended service for a PSP bucket is installed, receive the latest Enhanced HOLDDATA and install FIXCAT(ProductInstall-RequiredService).
Therefore, installing an FMID from a CBPDO might need a change to the parameters specified on the APPLY. ServerPac delivers a system with the FMIDs already installed.
There are two methods to complete a CBPDO FMID installation:
- To ensure that all critical service is installed with the FMID, add the SOURCEIDs of PRP, HIPER to the APPLY command. There can be some HIPER APARs that do not have resolving PTFs available yet. You need to analyze the symptom flags to determine whether you want to BYPASS the specific ERROR HOLDs and continue the FMID installation.
APPLY S(fmid,fmid,...)
FORFMID(fmid,fmid,...)
SOURCEID(PRP,HIPER,...)
GROUPEXTEND.
This method requires more initial research but provides resolution for all HIPERs that have fixes available and are not in a PE chain.
- To install the FMID as it would have before Enhanced HOLDDATA, you can add a BYPASS(HOLDCLASS(HIPER)) operand to the APPLY command. This method allows the FMID to install even though there might be HIPER ERROR HOLDs against it. Note not all ERROR HOLDs were bypassed, only the HIPER ERROR HOLDs. After one or more FMIDs are installed, run the SMP/E REPORT ERRSYSMODS command to identify any missing HIPER maintenance.
APPLY S(fmid,fmid,...)
BYPASS(HOLDCLASS(HIPER))
...any other parameters documented in the program directory...
This method is the quicker of the two but requires subsequent work to investigate any HIPERs.
One other procedural point about Enhanced HOLDDATA. Since it is likely (and advantageous) to receive Enhanced HOLDDATA updates between the APPLY and ACCEPT steps, it is possible to encounter ++HOLDs on ACCEPT that were not identified at the time of APPLY. Review the REPORT ERRSYSMODS before ACCEPT to identify any outstanding PEs or HIPERs on the target system.
Current HIPER flags and meanings.
|
Flag |
Keyword |
Description |
|
DAL |
DATALOSS |
Customer data destruction, contamination or both. |
|
FUL |
FUNCTIONLOSS |
Causes a major loss of function on the customer's system. |
|
IPL |
SYSTEMOUTAGE |
Causes the customer to re-IPL, reboot, recycle, or restart one or more systems or subsystems. |
|
PRF |
PERFORMANCE |
Causes severe impact to system performance or throughput. |
|
PRV |
PERVASIVE |
Problem can affect many customers. |
|
YR2000 |
Year 2000 |
Identifies APARs that provide Year 2000 function, or fix a Year 2000-related problem. |
|
SYSPLXDS |
SYSPLEXDS |
Identifies HIPER fixes needed to support and implement SYSPLEX data sharing. |
|
XSYS |
XSYSTEM |
Identifies HIPER fixes that provide cross-system, migration, compatibility, or toleration support. |
|
MSYSPLX |
MSYS-PLEX |
Identifies HIPER fixes that affect multiple systems of the entire sysplex. The problem causes a severe customer impact to more than one system in the sysplex or to the entire sysplex. |
|
D/Tnnnn |
D/Tnnnn |
Identifies HIPER fixes that pertain to the Hardware device number nnnn. |
|
CST |
CST |
Indicates a fix that was installed in CST outside the normal schedule for installing maintenance in CST (such as to fix a problem in CST or to add new function such as hardware). |
|
DST2007 |
DST2007 |
Identifies HIPER fixes that support a provision of the Energy Policy Act of 2005, extending Daylight Saving Time (DST) by four weeks, beginning in 2007. |
|
EURO99 |
EURO99 |
Identifies HIPER fixes that support the EURO currency symbol introduced in 1999. |
|
Bx.x |
BASE |
The CVSS Base score. See IIBM Z and LinuxONE Security Portal frequently asked questions (FAQs) page. |
|
Tx.x |
TEMPORAL |
The CVSS Temporal score. See IBM Z and LinuxONE Security Portal frequently asked questions (FAQs) page. |
Reporting Errors on Enhanced HOLDDATA
Suspected errors in Enhanced HOLDDATA can be reported by sending an email or opening a case to SMP/E support.
If you have ++HOLDs in your global zone containing an incorrect APAR (SYSMODID) prefix that was introduced by Enhanced HOLDDATA, send an email or open a case to report the problem. For example, the correct ++HOLD for APAR OW12345 is AW12345, but the ++HOLD contains OW12345. Thus the ++HOLD statement is not satisfied when the fixing PTF is installed because the PTF supersedes AW12345 while the ++HOLD was for OW12345.
Any incorrect prefix introduced by Enhanced HOLDDATA is resolved with subsequent updates to Enhanced HOLDDATA providing the appropriate ++RELEASE and ++HOLD statements. In addition, for errors not introduced by Enhanced HOLDDATA, there is a sample REXX utility available to create appropriate ++RELEASE and ++HOLD statements based on output from your system. The REXX utility was written for the specific format of ++HOLDs created by Enhanced HOLDDATA, but it can be modified to scan and correct ++HOLDs from sources other than Enhanced HOLDDATA.
To receive the REXX utility with the instructions, click the following to download:
Sample Report
PAGE 0001 - NOW SET TO GLOBAL ZONE DATE 12/01/11 TIME 17:09:57 SMP/E 36.09
EXCEPTION SYSMOD REPORT FOR ZONE TGT113
HOLD SYSMOD APAR ---RESOLVING SYSMOD---- HOLD HOLD
FMID NAME NUMBER NAME STATUS RECEIVED CLASS SYMPTOMS
--------------------------------------------------------------------------------------
HBB7780 HBB7780 AA35954 UA62955 GOOD YES HIPER IPL
AA36906 UA63106 GOOD YES HIPER FUL
AA37264 UA62997 GOOD YES HIPER IPL,FUL,XSYS,SYSPLXDS
AA37287 UA62566 GOOD YES HIPER FUL
AA37312 UA62801 GOOD YES HIPER FUL
AA37341 UA63229 GOOD YES HIPER FUL
AA37420 UA63185 GOOD YES HIPER DAL
AA37467 UA63002 GOOD YES HIPER FUL,XSYS,SYSPLXDS
AA37646 UA62885 GOOD YES HIPER IPL,PRV,SYSPLXDS
AA37743 UA62909 GOOD YES HIPER IPL,FUL
AA37832 UA62686 GOOD YES HIPER IPL
AA37893 UA63069 GOOD YES HIPER FUL,SYSPLXDS
AA37905 ***NONE HIPER FUL
AA98765 UA12345 GOOD YES SECINT B6.9,T6.0
AA37985 UA63165 GOOD YES HIPER IPL
AA38058 ***NONE HIPER FUL,XSYS,SYSPLXDS
AA38061 UA63180 GOOD YES HIPER IPL,FUL
AA38087 ***NONE HIPER IPL
AA38094 ***NONE HIPER IPL
UA60368 AA37940 ***NONE PE
UA62375 AA38061 UA63180 GOOD YES PE
HCR7780 HCR7780 AA37708 UA62975 GOOD YES HIPER FUL
HDZ1D1N HDZ1D1N AA36568 UA62316 GOOD YES HIPER FUL
AA37513 UA62912 GOOD YES HIPER DAL
AA37964 UA62316 GOOD YES HIPER FUL
HDZ1D10 HDZ1D10 AA35877 UA62482 GOOD YES HIPER FUL,PRV
AA36920 ***NONE HIPER IPL
AA37293 UA62923 GOOD YES HIPER FUL
AA37313 UA62129 GOOD NO HIPER PRF,PRV
AA37360 ***NONE HIPER DAL
AA37396 UA61969 GOOD YES HIPER IPL
AA37423 ***NONE HIPER DAL
AA37456 ***NONE HIPER FUL,PRV
AA37503 UA62933 GOOD YES HIPER DAL
AA37639 UA62703 GOOD YES HIPER FUL
AA37640 UA63211 GOOD YES HIPER DAL,PRV
AA37750 ***NONE HIPER FUL,PRF
AA37954 ***NONE HIPER DAL,PRV
AA38047 ***NONE HIPER FUL
AA87654 UA23456 GOOD YES SECINT B7.2,T6.3
UA60512 AA37956 ***NONE PE
UA60543 AA38119 ***NONE PE
UA60559 AA38073 ***NONE PE
HIP61D0 HIP61D0 AM48616 UK72410 GOOD YES HIPER FUL
AM48924 UK72621 GOOD YES HIPER IPL
AM49510 UK72808 GOOD YES HIPER FUL
AM49829 ***NONE HIPER IPL
HJE7780 HJE7780 GA37654 UA62711 GOOD YES HIPER FUL
GA37835 UA62866 GOOD YES HIPER DAL
HJS7780 HJS7780 WA37432 UA62720 GOOD YES HIPER FUL
HVT61D0 HVT61D0 AA37473 ***NONE HIPER IPL
AA37606 UA62442 GOOD YES HIPER FUL
AA37978 ***NONE HIPER IPL,FUL
AA37994 ***NONE HIPER IPL
HZFS3D0 HZFS3D0 AA37623 ***NONE HIPER FUL
AA37710 ***NONE HIPER FUL
AA37744 ***NONE HIPER FUL,XSYS
AA37950 ***NONE HIPER PRF
PAGE 0002 - NOW SET TO GLOBAL ZONE DATE 12/01/11 TIME 17:09:57 SMP/E 36.09
EXCEPTION SYSMOD REPORT SUMMARY
ZONE FMID TOTAL APARS TOTAL RESOLVING
AGAINST FMID SYSMODS AGAINST FMID
--------------------------------------------------------------------------------------
TGT113 HBB7780 20 15
HCR7780 1 1
HDZ1D1N 3 2
HDZ1D10 18 8
HIP61D0 4 3
HJE7780 2 2
HJS7780 1 1
HVT61D0 4 1
HZFS3D0 4 0
REPORT ERRSYSMODS APAR SYSMOD ID to RETAIN APAR Number mapping
The APAR NUMBER column in the SMP/E EXCEPTION SYSMOD REPORT is similar to but not the same as the APAR number in RETAIN.
The APAR SYSMOD ID has the same second through seventh characters as the APAR number in RETAIN. The first character of the APAR SYSMOD ID is used to differentiate the release or fix level of an APAR.
The naming convention for IBM APAR SYSMOD IDs is tannnnn where:
t = Type of SYSMOD.
a = Any alphabetic character.
nnnnn = any additional identifier.
An APAR SYSMOD ID from the EXCEPTION SYSMOD REPORT can be mapped to the RETAIN APAR number by using the second character of the SYSMOD ID to determine the first character for the RETAIN APAR number as shown in the following table:
|
2nd |
RETAIN |
|
A |
OA |
|
H |
PH |
|
I |
PI |
|
K |
PK |
|
L |
PL |
|
M |
PM |
|
N |
PN |
|
O |
IO |
|
P |
PP |
|
Q |
PQ |
|
R |
IR |
|
W |
OW |
|
Y |
OY |
|
Z |
OZ |
For example, APAR number AI12345 in the report corresponds to PI12345 in RETAIN, and APAR number AO98765 in the report corresponds to IO98765 in RETAIN.
In the sample report, AA35954 corresponds to OA35954 in RETAIN, WA37432 to OA37432, and AM48616 to PM48616.
Links to other Service sites
- ShopzSeries
- zSeries Support
- z/OS Preventive Maintenance Strategy to Maintain System Availability
- CST and RSU
Was this topic helpful?
Document Information
Modified date:
22 March 2024
UID
ibm16572419