Red Alert : z/OS 2.1 DFSORT records out of sequence
Abstract:
There is a potential exposure for out of sequence records with DFSORT for users on release z/OS 2.1.
Description:
At z/OS 2.1 code levels, DFSORT is intermittently returning records out
of sequence. There is no data loss, but records may be returned out of
sequence to the DFSORT output file. If VERIFY=YES is set at the
installation level, out of sequence conditions are already being
detected. This problem only occurs in z/OS 2.1. No prior releases of
DFSORT are affected.
Please see APAR PI22817 for more details and latest information.
Please see APAR PI22817 for more details and latest information.
Users affected :
All z/OS 2.1 DFSORT (HSM1L00) users who SORT data with DFSORT using the
performance path may be affected if there is insufficient virtual
storage below the line at the time of execution. In other words the
potential for error exists for all users of DFSORT SORT function on z/OS
2.1, but not all users will experience the problem.
Recommended Actions:
Enable VERIFY=YES at the installation level to detect out of sequence
conditions. Affected jobs can be rerun with DEBUG $NOPFP$ to circumvent
the issue.
In addition, a ++APAR is available to disable the affected performance
path, as a temporary circumvention, using a new DFSORT installation
option.
See APAR PI22817 for details.
If you haven't signed up to the Red Alerts by now, you really should do it. Just go over here.
1 comment:
Intereesting thoughts
Post a Comment