SYNCSORT - AN OVERVIEW

Table of Contents

1. OverView ...................................................................................................... 1 2. SYNCSORT Commands ............................................................................... 2 2.1 SORT......................................................................................................... 2 2.2 MERGE ..................................................................................................... 2 2.3 INCLUDE and OMIT................................................................................ 2 2.4 INREC and OUTREC ............................................................................... 3 2.5 SUM .......................................................................................................... 3 2.6 ALTERNATE COLLATING SEQUENCE .............................................. 4 2.7 OPTION Statement ................................................................................... 4 2.7.1 EQUALS AND NOEQUALS ............................................................. 4 2.7.2 RECORD............................................................................................. 4 2.7.3 SKIPREC............................................................................................. 4 2.7.4 STOPAFT............................................................................................ 4 2.7.5 COPY .................................................................................................. 5 2.8 OUTFIL..................................................................................................... 5 3. JCL Requirement........................................................................................... 5 SYSIN . ...................................................................................................... 5 SYSOUT ..................................................................................................... 5 SORTIN ...................................................................................................... 5 SORTIN## .................................................................................................. 5 SORTOUT .................................................................................................. 5 SORTOUT# ................................................................................................ 5 SORTOT## ................................................................................................. 5 SORTWK##................................................................................................ 5 4. PROCESSING ORDER ................................................................................ 5
1. OVERVIEW
Syncsort belongs to Syncsort IncC that can sort data, merge data, selectively process data, reformat data, create summary records from data and create extensive reports from input data. It can also perform any combination of the above mentioned functions and more. This document tries to explain in brief the various items related to processing data using Syncsort. This document describes a subset of the Syncsort functions and does not claim to be a replacement nor does the author guarantee the exactness of details or syntax.
Syncsort.doc Page 1 of 6

Syncsort. The second form of the SORT statement can be used when all the fields specified for the sort sequence are of the same type. The list of fields and their formats must be specified for this statement. irrespective of the field type.{fieldtype}.{D|A}[.. GT. The format of the MERGE statement is as follows. MERGE FIELDS=({begcol}. The length of the field must be specified in bytes.. LT. The frequently used ones are CH for character. 2.{length}. BI for binary (COMP fields of COBOL).{fieldtype} Please refer to SORT statement above for description of the statement.{begcol}. LE and GE..{length}. The MERGE statement requires the sort sequence for the data.{length}.. NE. {length}..{comp.{length}.) or MERGE FIELDS=({begcol}.{begcol}.{D|A}[. The valid comparison operators are EQ.{fieldtype}. {D|A}]. ZD for zone decimal and AQ for alternate collating sequence (refer to later section on alternate collating sequence).{begcol}. The list of fields and their formats must be specified for this statement.SYNCSORT ..{D|A}[.1 SYNCSORT COMMANDS SORT The SORT statement can be used sort a dataset or concatenated datasets.{length2}.). PD for packed decimal (COMP-3 fields of COBOL). The output records are sorted in the specified sequence. INCLUDE COND=({begcol1}. MERGE The MERGE statement can be used merge two or more pre-sorted datasets.. The SORT statement requires the sort sequence for the data.AN OVERVIEW 2.{fldtype1}.{length}. {length}. {begcol2}.{D|A}].{D|A}]. then the options specified will determine if the input order is maintained for such records. 2.. The multiple records contain the same sort sequence key.{length1}. The OMIT statement can be used to specify the conditions for exclusion of records from the input during processing. {D|A}].3 INCLUDE AND OMIT The INCLUDE statement can be used to specify the conditions for inclusion of records from the input during processing. Both statements cannot be used together. The different formats of the INCLUDE and OMIT statements are shown below.{length}. starting with 1 for the first byte.doc Page 2 of 6 . SORT FIELDS=({begcol}.{fieldtype}.2 2.) or SORT FIELDS=({begcol}. There are many field types.{fieldtype} The beginning column is specified in bytes.{fldtype2}) The above statement can be used to compare two fields within the same record.). The format of the SORT statement is as follows.{begcol}.{D|A}[.oper}.{fieldtype}.

{constant}) The above statement can be used to compare a field in the record with a character. placing the first field specified at column 1. INCLUDE COND=({cond.. In the example above. NOTE: When using INREC fields.AN OVERVIEW INCLUDE COND=({begcol}.{fldtype}.4 INREC AND OUTREC The INREC statement can be specified to reformat the input records before SYNCSORT processes them for SORT or MERGE.{fldtype}. INREC FIELDS=([{outpos}:]{begcol}. MERGE and SUM statements must reflect the output from the INREC processing. The individual numeric fields can also be reformatted from any form to zone decimal. The OUTREC statement can be specified to reformat the processed records into the required layout for the output records or the report that is generated. Constant fields can also be introduced in the record. The format for the INREC and OUTREC statements are similar. the column positions and lengths in the SORT. SUM The SUM statement can be used to summarize data based on the SORT statement.5 Syncsort. The default is to place it at the current position in the output record.EDIT=M#) or INREC FIELDS=({begcol}. the S character is for sign field.TT) Default picture clauses are provided and named M0 to M9. decimal or hexadecimal constant.[{outpos}:]{begcol}. 2.doc .) Parenthesis can be used to group conditional statements to form complex conditions. I is equivalent of Z PIC clause of COBOL and T is equivalent of 9 PIC clause. compound statements can be constructed as follows.EDIT=SIII. using SIGNS parameter. more than one record may be created.. INREC FIELDS=({begcol}. Whenever there is an overflow of a numeric field.stmt}.oper}.) The Outpos description is optional. For OMIT statements replace the INCLUDE verb by OMIT verb in the above examples.{length}.[{OR|AND}.{length} [. Conventions for the sign displayed for numeric fields can be specified after the edit parameter.{fldtype}.stmt}].{comp.{length}. spaces or zeroes can be placed in the record at specific positions.{length}.SYNCSORT . The SYNCSORT software does not guarantee unique records if numeric fields are required to be summed up. One record will be produced for each unique key present in the input. If numeric fields are specified for summation..stmt} is the part of statement between the parenthesis in either of the statements mentioned above. The syntax is as follows. SUM FIELDS=NONE or Page 3 of 6 2.{length}]. For example. Using the convention that {cond. Customized picture clauses can be specified by using appropriate syntax. This specifies the position in the output record where the field must be placed.IIT.. those fields will be summed up. An example syntax is given below.{cond.

{fldtype}].7. The valid values are RECORD=V and RECORD=F. 2. When EQUALS is used the data for the non key fields are taken from the first input record for that key value.6 ALTERNATE COLLATING SEQUENCE The alternate collating sequence can be specified using the ALTSEQ statement.{begcol}. that the user intends to sort on. 2.SYNCSORT . This will help the user in sorting records in a different sequence than the EBCDIC character set. STOPAFT The STOPAFT parameter of the OPTION statement can be used to specify the number of records to be included for processing. EQUALS AND NOEQUALS The default of NOEQUALS specifies that SYNCSORT need not retain the order of input data when duplicate record keys are found.{length}.AN OVERVIEW SUM FIELDS=({begcol}. This is required when both the input and output from the SORT or MERGE processing are VSAM files. RECORD The record option of the OPTION statement can be used to specify if the input data to be processed are Variable length records or Fixed length records. OPTION EQUALS should be used if the order of input data must be maintained during the SORT processing.7. OPTION STATEMENT The option statement can be used to control parameters during SORT.2 2. This may be required in situations where the character codes for fields..3 2.4 Syncsort.{fldtype}[. The new hex code will not replace the hex codes in the output or the reports.{length}. ALTSEQ CODE=({hexcode}{newhexcode}[. The second format is used when numeric summation is required when duplicate records exist. This parameter will affect the non-summation data in SUM processing..doc Page 4 of 6 .7. SKIPREC=20 specifies that the first 20 records of the input must be skipped. MERGE and SUM processing..1 2. SKIPREC The SKIPREC parameter of the OPTION statement can be used to specify the number of records of input to skip before any processing should begin. When NOEQUALS is specified the data for the non keyfields are unpredictable. STOPAFT=100 specifies that SYNCSORT stop taken any more input after 100 records that match the criteria are selected.7..{hexcode}{newhexcode}].) The first format is used when duplicate records need to be removed and no numeric summation is required. are not in EBCDIC collating sequence.) The new hex code will be used for the sorting or merging process only for the appropriate hex code specified for it.7 2.

When COPY is combined with INREC or OUTREC processing (INREC is more efficient in this case). like producing reports. This is where the SYNCSORT messages are placed. SORTIN## These statements should refer to the individual datasets to be merged. SORTOT## The same as SORTOUT#. One OUTFIL statement is required for each output dataset. For example. report formatting is available. including 3 levels of HEADER#. 4. Syncsort. If neither SORT processing nor MERGE processing is required this is ideal to use. SORTOUT# These datasets should point to the individual output datasets referred in the OUTFIL statements. These individual datasets are required to be in pre-sorted order. There must be a one to one correspondence between the FILES parameter in the OUTFIL statement and the list of DD statements specified. a reformatted output can be produced. summation. PROCESSING ORDER The processing order of the control statements by SYNCSORT is as follows. 3.doc Page 5 of 6 . OUTFIL The OUTFIL statement can be used to produce multiple output datasets. 3 levels of TRAILER#. The SYNCSORT manual should be referred if the OUTFIL statement is required. Each output dataset can have its own INCLUDE or OMIT condition and its own INREC and OUTREC parameters.1. 2.SYNCSORT .7. JCL REQUIREMENTS The different DD statements required for the SORT step are as follows. this statement can help create separate reports for each department into a different dataset or sysout and route them to the appropriate destination. Section processing and Section breaks. SORTIN This dataset should point to the input dataset(s) for the sort process. SYSOUT It should point to a dataset or SYSOUT.1. The parameter when combined with SKIPREC and STOPAFT helps copy selected records to output based on number of records.1 SYSIN It should point to the SYNCSORT control statements mentioned above. selected records can be copied to output based on specific conditions in field values. Further.AN OVERVIEW 2. This statement must be used if elaborate formatting is required. The FILE parameter specifies the DD name suffix to be used for the dataset output. If COPY is combined with INCLUDE or OMIT condition statements. SORTOUT This dataset should point to the dataset where the output must be placed. SORTWK## These statements should refer to temporary volumes with appropriate space parameters depending on the volume of data to be processed.8 3.5 COPY The COPY parameter can be used if a simple COPY operation is required.

SUM statement processing.doc Page 6 of 6 . MERGE or COPY processing (including alternate collating sequence processing for SORT and MERGE). 1. 4.SYNCSORT . The processing is very complex if the OUTFIL statements use different INREC statements and different INCLUDE or OMIT statements. The processing order will drastically change if OUTFIL statement is present in the SYSIN of SYNCSORT. OUTREC processing.AN OVERVIEW INCLUDE or OMIT condition statement processing. 5. 3. SORT. Syncsort. 2. INREC statement processing.