Filter
Top Products
19.3 Additional DFSORT/VSE Migration Considerations
DFSORT/VSE is based on and replaces Sort/Merge. It offers additional features
not available in Sort/Merge. All of the migration considerations discussed
previously for Sort/Merge apply to DFSORT/VSE as well. Migration
considerations for additional features of DFSORT/VSE are discussed below.
19.3.1 Control Statements
OPTION: DFSORT/VSE has additional OPTION statement operands not found in
Sort/Merge. Here are the actions, if any, you should consider taking for each
such OPTION operand:
•
DSPSIZE: Can be used with no changes. However, since the OS/390
environment is considerably different from the VSE environment, you should
determine if the DSPSIZE value specified is still appropriate as the maximum
amount of data space to be used for dataspace sorting.
•
EQUALS: Can be used with no changes.
•
NOEQUALS: Can be used with no changes.
•
GVSIZE: Must be removed. DFSORT terminates if this operand is specified.
GVSIZE has no meaning for DFSORT since OS/390 does not support GETVIS
areas. By default, DFSORT uses virtual storage (above and below 16M
virtual), dataspace sorting, hipersorting and work data sets, as appropriate.
•
GVSRANY: Must be removed. DFSORT terminates if this operand is
specified. GVSRANY has no meaning for DFSORT since OS/390 does not
support GETVIS areas.
•
GVSRLOW: Must be removed. DFSORT terminates if this operand is
specified. GVSRLOW has no meaning for DFSORT since OS/390 does not
support GETVIS areas.
•
LOCALE: Can be used with no changes.
•
SKIPREC: Can be used with no changes.
•
STOPAFT: Can be used with no changes.
•
STXIT: Must be removed. DFSORT terminates if this operand is specified. By
default, DFSORT uses an ESTAE routine for abend recovery.
•
NOSTXIT: Must be removed. DFSORT terminates if this operand is specified.
Use the NOESTAE operand of the DEBUG control statement to suppress
DFSORT′s ESTAE routine for abend recovery.
•
WRKSEC: Must be removed. DFSORT terminates if this operand is specified.
By default, DFSORT uses automatic secondary allocation for temporary JCL
SORTWKnn data sets for which a secondary allocation amount is not
specified.
•
NOWRKSEC: Can be used with no changes. However, since NOWRKSEC
applies to SAM ESDS work files for Sort/Merge, but to temporary work files
for DFSORT, you should determine if this operand should be kept or
removed.
•
Y2PAST: Can be used with no changes.
OUTREC: DFSORT/VSE has additional OUTREC statement operands not found in
Sort/Merge. Here are the actions, if any, you should consider taking for each
such OUTREC operand:
Chapter 19. SORT 379