A deprecated feature in DFSORT is one that still works in the current version but is planned for removal in a future release. Vendors deprecate features when they want to steer users toward a better or more maintainable alternative. If you keep using a deprecated option, a future upgrade may break your job when the option is removed. This page explains what deprecated means, where to find the list of deprecated DFSORT features, how to find and use the replacement, and why you should avoid deprecated options in new jobs and plan to migrate existing jobs before the removal.
When a feature is deprecated, the vendor is saying: "This still works today, but we plan to remove it in a future release. Please stop using it and use the replacement instead." So deprecated is a warning, not an immediate error. The feature continues to function until the release in which it is actually removed. Once removed, control statements that use it may be rejected (syntax error) or ignored, and the job may fail or produce unexpected results. So the right approach is to treat deprecation as a signal to migrate soon, not to ignore it.
| Term | Meaning |
|---|---|
| Deprecated | Still supported but planned for removal; use replacement |
| Removed | No longer accepted; job will fail if used |
| Replacement | Documented alternative that will remain supported |
The list of deprecated features is published in the product documentation for each DFSORT (and z/OS) level. Look for sections such as "Deprecated features," "What's new and changed," "Migration," or "Compatibility." Release notes for each version typically call out what is deprecated in that release and what the replacement is. The list can grow from version to version: an option deprecated in one release may be removed in the next. So you need to check the documentation that matches the level you are running (or the level you are upgrading to).
When a feature is deprecated, the documentation usually states the replacement. It might be a new keyword that does the same thing, or a different way to achieve the same result (e.g. a different combination of statements). If the replacement is a new keyword, you update the control card to use it. If the replacement is a different approach (e.g. "use INREC with BUILD instead of OUTREC FIELDS=..."), you rewrite the step accordingly. If you cannot find a replacement in the manual, check migration guides or contact support. Do not assume there is no replacement—sometimes it is in a different section (e.g. under a new feature name).
When writing new DFSORT jobs, use only options that are currently supported and not deprecated. That way the job is future-proof: when the deprecated option is eventually removed, your job is unaffected. It also keeps the job aligned with the vendor's recommended practice. If you are copying an old job as a template, check that the template does not use deprecated options and update it if it does.
For jobs that already use a deprecated option, plan to migrate them before the option is removed. The deprecation notice may state a target release for removal (e.g. "will be removed in the next major release"). Use that to prioritize: jobs using options that will be removed sooner should be updated first. Test each updated job with representative data and compare output to ensure the replacement produces the same results. Document the change so that future maintainers know why the control statements were updated.
Occasionally a deprecated feature has no one-to-one replacement. The documentation might recommend achieving the same result with a different approach—for example, using a user exit (MODS) or a different set of control statements. In that case you need to redesign the step. If the documentation is unclear, use support or migration services to get a concrete recommendation. Do not assume you can keep using the deprecated option indefinitely.
"Deprecated" is like when the teacher says: "This old way still works for now, but we are going to stop using it next year. Use the new way from now on." If you keep using the old way, next year it will not work. So you learn the new way now and change your work so you are ready.
1. What does "deprecated" mean for a DFSORT option?
2. Where do you find which DFSORT features are deprecated?
3. Why should you avoid using deprecated options in new jobs?
4. What if there is no direct replacement for a deprecated option?
5. Can a deprecated option be removed in a PTF or minor release?