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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful