RECEIVE, APPLY, ACCEPT and RESTORE
Maintenance follows a fixed path. RECEIVE stores SYSMODs and HOLDDATA in the global zone, APPLY CHECK shows what would happen, APPLY installs into the target libraries, and ACCEPT later makes the change permanent in the distribution libraries. RESTORE can back out an applied SYSMOD that has not been accepted.
The flow at a glance
RECEIVE
RECEIVE reads SYSMODs and HOLDDATA from an input source (the SMPPTFIN and SMPHOLD DD statements, or a network package from IBM's service tools) and stores the SYSMODs in the SMPPTS dataset with records in the global zone. Nothing on the running system changes. You can RECEIVE a full service order and decide later what to apply.
HOLDDATA: read it before you apply
Some SYSMODs need special attention. Vendors flag them with ++HOLD statements, either inside the SYSMOD or as separately received HOLDDATA. SMP/E will not apply a held SYSMOD unless the hold is resolved or you explicitly bypass it.
| Hold type | Meaning | What you do |
|---|---|---|
| ERROR | The PTF itself has been found to be in error (a PE PTF) | Do not install it; wait for the fixing PTF, which releases the hold |
| SYSTEM | The PTF needs a manual action, such as an IPL, a parmlib change or a dependent product update | Read the reason text and plan the action; then bypass that hold category |
| FIXCAT | The SYSMOD needs a fix (APAR) that belongs to a fix category, such as a hardware support or coexistence category; the hold is resolved when a SYSMOD that resolves that APAR is installed | Use APPLY or REPORT MISSINGFIX to find fixes needed for that category |
| USER | A hold your own site added | Follow your local process |
SYSTEM holds carry a reason ID, such as one meaning an IPL is required or one meaning documentation changed. The text explains exactly what to do. Teams usually produce a HOLDDATA report with every maintenance package and review it before the change is approved.
APPLY CHECK, then APPLY
APPLY installs SYSMODs into the target libraries and updates the target zone. Adding the CHECK operand runs everything as a simulation: SMP/E reports what would be installed, what is held, what requisites are missing and what would be regressed, without changing any library. Always run it first.
SET BOUNDARY(ZOSTGT1).APPLY PTFSGROUPEXTENDBYPASS(HOLDSYSTEM)CHECK.Read the SMPRPT and SMPOUT output, especially the SYSMOD status report and any regression warnings. A regression means a SYSMOD would replace an element that has a change from another SYSMOD not in its chain, such as a USERMOD. Regressions must be understood, never ignored.
SYSMOD STATUS REPORT SYSMOD STATUS TYPE UJ12345 APPLIED PTF (would be applied) UJ12360 HELD PTF ERROR HOLD UJ12377 NOGO PTF MISSING REQUISITE
ACCEPT and RESTORE
ACCEPT copies a SYSMOD into the distribution libraries and records it in the distribution zone. Those libraries are the base copy: they are used to rebuild target libraries and as the fallback that RESTORE relies on. Sites usually ACCEPT only after a service level has run successfully in production for a while.
RESTORE removes an applied SYSMOD from the target libraries by replacing its elements with the copies in the distribution libraries. It only works for a SYSMOD that has not been accepted, and SMP/E also removes or requires the removal of SYSMODs that depend on it. Many sites prefer to back out a bad level by IPLing from the previous set of libraries, and use RESTORE for narrower cases.
Other commands you will meet
- LIST shows what a zone holds, for example a single SYSMOD and its status.
- REPORT MISSINGFIX lists fixes missing for chosen fix categories, such as those needed before new hardware or a new release.
- REJECT removes received SYSMODs that were never applied, to tidy the global zone and SMPPTS.
- CLEANUP removes old records from a zone after SYSMODs have been superseded and accepted.
Which APPLY operand (one word) makes SMP/E report what would happen without changing any library?
Show a hint
It turns the command into a dry run.
Show the solution
CHECK. APPLY ... CHECK simulates the apply and produces the reports, without updating target libraries or the target zone.
Common mistakes
An ERROR hold means the PTF is known to be broken. Wait for the fixing PTF; bypassing it installs a known defect.
Without the dry run, held SYSMODs, missing requisites and regressions are discovered half-way through the real APPLY. Always CHECK first and review the reports.
After ACCEPT, RESTORE cannot back the SYSMOD out. Accept only after the level has proved itself in production.
What you will see at work
- A maintenance change record normally attaches the APPLY CHECK reports and the HOLDDATA review for approval.
- SYSTEM hold actions, such as parmlib changes or required IPLs, become tasks in the rollout plan.
- When IBM marks a PTF in error after you installed it, the team checks the hold text to judge the risk and plans the fixing PTF.
Key terms
Check your understanding.
Take this lesson's quiz and save your progress. Free.