- Mais recentes
- Mais votos
- Mais comentários
The most likely reason you are only getting one record from the Systran(0) file instead of 50 is that the sort key value for those records may not be unique.
When SORT operation is performed, it orders the records lexicographically based on the sort key value. If multiple records have the same sort key value, only one of those duplicates will be returned.
A few things you can check:
Verify that the sort key field contains a unique value for each record in the Systran(0) file. If any records have the same sort key, only one of the duplicates will be returned.
Check if the sort key type is appropriate - dates/numbers stored as strings may not sort correctly. The sort key should be of a type that provides unique ordering like a number or date.
Try running the SORT without the "recordSize=350" parameter to see if it returns more records from Systran(0) file. That parameter could be influencing the number of records returned.
Check AWS documentation for latest limits or behaviors of SORT operation that could impact the number of returned records.
Conteúdo relevante
- AWS OFICIALAtualizada há 7 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
Verified SYSTRAN(0) records and all 50 are unique transaction ids yyyymmdd000000xx where xx is number 01 to 50. So duplicate is not an issue. However I think Normal JCL SORT many not remove duplicates without explicitly specifying SUM FILEDS= NONE. On recordSize parameter. You mentioned remove but as per bluAge workshop documents, explicityly mentioned to include recordSize. Prior to this jobs are having recordSize parameters. So any other possibilities to get only one record in SORTOUT?