|
View previous topic :: View next topic
|
| Author |
Message |
mano
New User
Joined: 23 Mar 2006
Posts: 17
Location: chennai
|
|
|
|
I have a same sort step in two different LPAR regions in mainframe. Sort step has the same input files(i.e. data is same in both the files) but the output file is giving the difference. Sort fields are same in both the SORT step.
Difference is the placement of records if there is duplicates in the sort field.
I would like to know whether the SORT behaves differently in different LPAR regions. If not, why the difference is coming in the Output file even if the input file & sort fields are same in both the regions? |
|
| Back to top |
|
 |
Alain Benveniste
New User
Joined: 14 Feb 2005
Posts: 88
|
|
|
|
Could you post your JCL and how your records look like ?
Alain |
|
| Back to top |
|
|
mano
New User
Joined: 23 Mar 2006
Posts: 17
Location: chennai
|
|
|
|
JCL:
| Code: |
//STEP1 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SORTIN DD DISP=SHR,DSN=INFILE
//SORTOUT DD DSN=OUTFILE,
// DISP=(,CATLG,DELETE),
// UNIT=DASD,SPACE=(CYL,(50,50),RLSE)
//SYSIN DD *
SORT FIELDS=(51,20,CH,A)
/* |
For Example:
Record # 12 in outfile of LPAR1 region is placed as record # 13 in outfile of LPAR2 region and viceversa. This misplacement of records happens randomly when there is duplicates in the sort fields. |
|
| Back to top |
|
|
Alain Benveniste
New User
Joined: 14 Feb 2005
Posts: 88
|
|
|
|
Ok,
I think your problem comes from the EQUALS=YES option which is coded in one of the LPAR and not in the other.
Alain |
|
| Back to top |
|
|
mano
New User
Joined: 23 Mar 2006
Posts: 17
Location: chennai
|
|
|
|
The sort step is same in both the LPAR regions.
could you please tell me where to find the "EQUAL=YES" option located. |
|
| Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005
Posts: 7129
Location: San Jose, CA
|
|
|
|
When your System Programmers installed DFSORT, they specified (or defaulted) a set of installation options. EQUALS is one of these options and can be set to YES or NO.
I would guess that Alain is right that one of your LPARs has EQUALS=YES as the installation option and the other has EQUALS=NO. You can ensure that the job runs the same in both LPARS by adding the EQUALS run-time option to the job:
| Code: |
//DFSPARM DD *
OPTION EQUALS
/*
|
You can read all about DFSORT's installation options in "z/OS DFSORT Installation and Customization" which you can access, along with all of the other DFSORT books, from:
Use [URL] BBCode for External Links |
|
| Back to top |
|
|
mano
New User
Joined: 23 Mar 2006
Posts: 17
Location: chennai
|
|
|
|
No,
the EQUALS option is NO in both the regions. |
|
| Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005
Posts: 7129
Location: San Jose, CA
|
|
|
|
NOEQUALS in both regions can do it too.
With NOEQUALS, the order of duplicate records is unpredictable (NOEQUALS says that the duplicate records can be in any order) so they can be ordered in one way in one region and in another way in another region. If you want to guarantee that the duplicate records always come out in the same order, you need to use EQUALS in both regions (EQUALS says that the duplicate records must be in their original order).
As I said, you can add the following to the job wherever it runs:
| Code: |
//DFSPARM DD *
OPTION EQUALS
/*
|
|
|
| Back to top |
|
|
|
|
