|
Option P on either the
SuperCE Utility panel or the Search-ForE Utility panel provides one
or more panels from which you can select process options. For SuperCE,
the options displayed are compatible with the compare type (File,
Line, Word, or Byte) that you specified in the Compare Type field.
The compare type that you select determines the available process
options (Table 1).
Table 1. Summary of process
optionsProcess
option |
Valid for compare type |
Valid for Search |
---|
Keyword |
Description |
FILE |
LINE |
WORD |
BYTE |
---|
ALLMEMS |
All members |
X |
X |
X |
X |
X |
ANYC |
Any case |
|
X |
X |
|
X |
APNDLST |
Append listing output |
X |
X |
X |
X |
X |
APNDUPD |
Append update |
|
X |
X |
X |
X |
ASCII |
Convert input file data from EBCDIC to ASCII |
X |
X |
X |
X |
X |
CKPACKL |
Check for packed format |
|
X |
X |
|
|
CNPML 1 |
Count non-paired member/file lines |
|
X |
|
|
|
COBOL 2 |
For COBOL source files |
|
X |
X |
|
X |
COVSUM |
Conditional summary |
X |
X |
X |
X |
|
CPnnnnn |
EBCDIC code page used with ASCII option |
X |
X |
X |
X |
X |
DLMDUP |
Do not list matching duplicate lines |
|
X |
|
|
|
DLREFM |
Do not list reformatted lines |
|
X |
|
|
|
DPACMT |
Do not process asterisk (*) comment lines |
|
X |
X |
|
X |
DPADCMT |
Do not process ADA-type comments |
|
X |
X |
|
X |
DPBLKCL |
Do not process blank comparison lines |
|
X |
X |
|
X |
DPCBCMT |
Do not process COBOL-type comment lines |
|
X |
X |
|
X |
DPCPCMT |
Do not process C++ -type comment
lines |
|
X |
X |
|
X |
DPFTCMT |
Do not process FORTRAN-type comment lines |
|
X |
X |
|
X |
DPMACMT |
Do not process PC Assembly-type comment lines |
|
X |
X |
|
X |
DPPLCMT |
Do not process PL/I-type comments |
|
X |
X |
|
X |
DPPSCMT |
Do not process Pascal-type comments |
|
X |
X |
|
X |
FINDALL |
Require all strings found for return code 1 |
|
|
|
|
X |
FMSTOP |
Stop immediately a difference found |
X |
|
|
|
|
FMVLNS |
Flag moved lines |
|
X |
|
|
|
GWCBL |
Generate WORD/LINE comparison change bar listing |
|
X |
X |
|
|
IDPFX |
Identifier-prefixed listing lines |
|
|
|
|
X |
LMCSFC 3 |
Load module CSECT file compare |
X |
|
|
|
|
LMTO 4 |
List group member totals |
|
|
|
|
X |
LNFMTO 4 |
List not-found member totals only |
|
|
|
|
X |
LOCS |
List only changed entries in summary |
X |
X |
X |
X |
|
LONGLN 5 |
Long lines |
|
X |
|
|
X |
LPSF 4 |
List previous-search-following lines |
|
|
|
|
X |
LTO 4 |
List totals only |
|
|
|
|
X |
MIXED |
Mixed input (single/double byte) text |
|
X |
X |
|
|
NARROW 5 |
Narrow (side-by-side) listing |
|
X |
|
|
|
NOPRTCC |
No printer control columns |
X |
X |
X |
X |
X |
NOSEQ 2 |
No sequence numbers |
|
X |
X |
|
X |
NOSUMS |
No summary section |
|
X |
X |
X |
X |
REFMOVR |
Reformat override |
|
X |
|
|
|
SDUPM |
Search duplicate members |
|
|
|
|
X |
SEQ 2 |
Ignore standard sequence number columns |
|
X |
X |
|
X |
SYSIN |
Provide alternative DD name for process statements. |
X |
X |
X |
X |
X |
UPDCMS8 6 |
Update CMS8 format |
|
X |
|
|
|
UPDCNTL 6 |
Update control |
|
X |
X |
X |
|
UPDLDEL 6 |
Update long control |
|
X |
|
|
|
UPDMVS8 6 |
Update MVS8 format |
|
X |
|
|
|
UPDPDEL 6 |
Update prefixed delta lines |
|
X |
|
|
|
UPDREV 6 |
Update revision |
|
X |
X |
|
|
UPDREV2 6 |
Update revision (2) |
|
X |
X |
|
|
UPDSEQ0 6 |
Update sequence 0 |
|
X |
|
|
|
UPDSUMO 6 |
Update summary only |
|
X |
X |
X |
|
VTITLE |
Print data set volume serial |
|
X |
X |
X |
|
WIDE 5 |
Wide (side-by-side) listing |
|
X |
|
|
|
XREF |
Cross reference strings |
|
|
|
|
X |
XWDCMP |
Extended word comparison |
|
|
X |
|
|
Y2DTONLY 7 |
Compare Dates Only |
|
X |
|
|
|
Note:
- Valid for group LINE comparisons only.
- COBOL, SEQ, and NOSEQ are mutually exclusive.
- Not supported for PDSE data sets.
- LMTO, LNFMTO, LPSF, and LTO are
mutually exclusive.
- LONGLN, NARROW, and WIDE are mutually exclusive.
- All update (UPD) process options are mutually exclusive.
Also, they cannot be used with the process option Y2DTONLY.
- Y2DTONLY is not supported for change bar listing (process
option GWCBL).
|
Here are the SuperC process options, listed alphabetically: - ALLMEMS
- Process
all members in a PDS including ALIAS members. Without this process
option, when performing a PDS compare, SuperC does not include members
with the ALIAS attribute unless explicitly specified by a SELECT process
statement. The ALLMEMS process option indicates that all directory
entries including those with the ALIAS attribute are to be processed.
Valid
for FILE, LINE, WORD, and BYTE compare types and Search.
- ANYC
- Any case. Lowercase
alphabetic characters (a to z) in source files are translated to uppercase
(A to Z) before comparison processing. (The actual input files are
not modified.)
Use this option to cause strings such as "ABC", "Abc", "ABc",
to compare equally.
Valid for LINE and WORD compare types
and Search.
- APNDLST
- The APNDLST
process option appends the listing output to the specified or default
listing file. If the file does not exist, it is created.
APNDLST
allows you to collect updates from multiple comparisons into one listing
file.
Valid for FILE, LINE, WORD, and BYTE compare types and
Search. Note: - You can also do this by using the SELECT process statement (and,
on CMS, SELECTF) that identifies different files/members and produces
a single listing.
- APNDUPD
- The
APNDUPD process option appends the update output to the specified
or default update file. If the file does not exist, it is created.
APNDUPD allows you to collect updates from multiple comparisons
into one update file.
Valid for LINE, WORD, and BYTE compare
types and Search. Note: - You can also do this by using the SELECT process statement (and,
on CMS, SELECTF) that identifies different files/members and produces
a single listing.
- ASCII
- Process ASCII
input files. For LINE or WORD compare and for Search the input data
is translated from ASCII to EBCDIC. For BYTE compare, character data
in the listing is translated from ASCII to EBCDIC. For FILE compare,
this option is accepted but has no effect. Any search string given
in hexadecimal notation is assumed to be in ASCII, matching the original
input data.
The ASCII code page is assumed to be ISO 8859-1 (CCSID
819). The EBCDIC code page may be specified using the Cpnnnnn option.
Valid
for FILE, LINE, WORD, and BYTE compare types, and Search.
- CKPACKL
- Check
for packed format. This option determines if the member or sequential
data set has the standard ISPF/PDF packed header format. If required,
SuperC unpacks the input data set or member during the comparison.
Valid for LINE and WORD compare types.
- CNPML
- Count
non-paired member/file lines for the group summary list. Use this
option to inventory the total number of processed and not-processed
lines. Otherwise, only the paired entries are listed with line counts.
Valid for LINE compare type.
Note: CNPML is only used when
comparing a group of files.
- COBOL
- Ignore columns
1 to 6 in both COBOL source files. Data in columns 1 to 6 is assumed
to be sequence numbers.
Valid for LINE and WORD compare types
and Search.
- COVSUM
- Conditional
summary section. List the final summary section or the update file
for the option UPDSUMO only if there are differences. This is useful
when used in combination with APNDLST or APNDUPD.
Valid for FILE,
LINE, WORD, and BYTE compare types.
- CPnnnnn
- Use the
specified EBCDIC code page number (up to 5 digits) when translating
data using the ASCII option. If not specified ISPF uses the terminal
code page. If the terminal code page cannot be determined or is not
supported SuperC uses CP1047. All CECP and Euro Latin-1 code pages
are supported. Therefore nnnnn can be any of the following values:
- Default: 1047 (Open Systems Latin-1 EBCDIC)
- CECP: 37, 273, 277, 278, 280, 284, 285, 297, 500, 871
- ECECP (Euro): 1140 to 1149
Valid for FILE, LINE, WORD, and BYTE compare types, and Search.
- DLMDUP
- Do
not list matching duplicate lines. Old file source lines that
match new file source lines are omitted from the side-by-side
output listing.
Valid for LINE compare type.
- DLREFM
- Do
not list reformatted lines. Old file source lines that have
the same data content (that is, all data is the same except the position
and number of space characters) as the new file lines are omitted
from the listing. Only the new file reformatted lines are included
in the output.
Valid for LINE compare type.
- DPACMT
- Do not process
asterisk (*) comment lines. Lines with an "*" in
column 1 are excluded from the comparison set. Other forms of assembler
comments are unaffected.
Valid for LINE and WORD compare types
and Search.
- DPADCMT
- Do not process
ADA type comments. ADA comments are whole or partial lines that appear
after the special "--" sequence. Blank lines are also considered
part of the comment set. This option produces a comparison listing
with comments removed and part comments blanked.
Valid for LINE
and WORD compare types and Search.
- DPBLKCL
- Do not process
blank comparison lines. Source lines in which all the comparison columns
are blank are excluded from the comparison set.
Note: It is redundant
to use this option with DPADCMT, DPPLCMT, or DPPSCMT as these process
options also bypass blank comparison lines.
Valid for LINE
and WORD compare types and Search.
- DPCBCMT
- Do not process
COBOL-type comment lines. COBOL source lines with an "*" in
column 7 are excluded from the comparison set
Valid for LINE and
WORD compare types and Search.
- DPCPCMT
- Do not process C++ end-of-line type
compiler comments. These are "//" delimited comments. DPPLCMT
may also be used with DPCPCMT when the source file contains "/* … */" comments
delimiters.
Valid for LINE and WORD compare types and Search.
- DPFTCMT
- Do not process
FORTRAN-type comment lines. FORTRAN source lines with a "C" in
column 1 are excluded from the comparison set.
Valid for LINE
and WORD compare types and Search.
- DPMACMT
- Do not process
PC Assembly-type comments. This uses the IBM® PC
definition for assembler comments: comments begin with either the
COMMENT assembler directive or a semi-colon (;).
Valid for LINE
and WORD compare types and Search.
- DPPLCMT
- Do not process
PL/I-type comments. PL/I, C++, C, REXX comments
(/* … */) and blank lines are excluded
from the comparison set. This option produces a listing with all comments
removed and blanked.
Valid for LINE and WORD compare types and
Search.
- DPPSCMT
- Do not process
Pascal-type comments. Comments of the type (* … *)
and blank lines are excluded from the comparison. DPPSCMT and DPPLCMT
may be required for some Pascal compiler comments. This option produces
a comparison listing with comments removed and part comments blanked.
Valid for LINE and WORD compare types and Search.
- FINDALL
- All strings
must be satisfied for the search to be considered successful, whereupon
the return code is set to one.
Note: - If all searches are not satisfied, there is NO message to indicate
this, other than RC=0. To find which searches failed, specify the
XREF process option.
- If the FMSTOP option is specified, the search will stop once it
has satisfied all search strings.
- FMSTOP
- Immediately
a difference is found between files, stops the compare with a return
code of 1. This option provides a quicker way of telling if two files
are different.
Valid for FILE compare type.
- FMVLNS
- Flag
moved lines. Identify inserted lines from the new file that
match deleted lines from the old file. Inserted-moved lines
are noted with "IM" and deleted-moved lines are noted with "DM" in
the listing.
Valid for LINE compare type. Note: - Maximum length for lines is 256 characters.
- Maximum length for a contiguous block of moved lines is 32K.
- GWCBL
- Generates
WORD/LINE comparison change bar listings. SuperC lists new file
lines with change bars ("|") in column 1 for lines that differ
between the new and old files. Deleted lines are indicated
by flagging the lines following the deletion.
Valid for LINE and
WORD compare types. Note: - LINE comparison and WORD comparison may give slightly different
results due to their sensitivity to word and line boundaries. For
further details, see Reasons for differing comparison results.
- GWCBL cannot be used with the process option Y2DTONLY.
- IDPFX
- Identifier
prefixed. File ID or member name is prefixed to the search string
lines of the listing. See Figure 1 for
an example of a IDPFX listing.
Valid for Search.
- LMCSFC
- Load
module CSECT file compare list. Lists the name, number of bytes,
and hash sum for each load module CSECT. Unchanged paired CSECTs
are omitted when you specify the LOCS process option.
Note: - LMCSFC is not supported for PDSE.
Valid for FILE compare type.
- LMTO
- List
group member totals. Lists the member summary totals and the overall
summary totals for the entire file/group. See Figure 1 for an example of
an LMTO listing.
Valid for Search.
- LNFMTO
- List "not
found" member totals only. Lists the members that have no strings
found for the entire file/group.
Valid for Search.
- LOCS
- List
only changed entries in summary. Normally, for groups of files/members
being compared, SuperC lists all paired entries in the Member Summary
Listing section of the listing file. Preceding the names of these
pairs is a CHNG field to indicate whether the comparison found any
differences or not. Figure 6 shows
a FILE comparison without LOCS. Figure 7 shows
a FILE comparison with LOCS.
When LOCS is specified, only those
pairs which have changes are listed in the summary section.
Valid
for group FILE, LINE, WORD, and BYTE compare types.
- LONGLN
- Long lines.
LONGLN causes SuperC to create a listing with 203 columns, reflecting
up to 176 columns from the source files. This file may exceed the
maximum number of columns handled by many printers.
Valid for
LINE compare type and Search.
- LPSF
- List
previous-search-following lines. Lists the matched string line and
up to 6 preceding and 6 following lines for context. The preceding
and following count may be changed by using the LPSFV process statement.
This allows a count range of 1 to 50 lines. A value of 0 is invalid,
since this produces a normal search without any options.
Valid
for Search.
- LTO
- List
totals only. List the overall summary totals for the entire file/member
group. See Figure 1 for
an example of an LTO listing.
Valid for Search.
- MIXED
- Mixed
input. Indicates that the input text may be a mixture of both single-byte
and double-byte (DBCS) text. Double-byte strings are recognized and
handled differently than if MIXED were not specified. For instance,
single byte characters are not valid within double-byte strings. Special
terminal devices (for example, 5520) allow entry of DBCS characters.
Valid for LINE and WORD compare types.
- NARROW
- Narrow
side-by-side listing. Creates
a 132/133 variable listing file with only 55 columns from each source
file. Insertions and deletions are flagged and appear side-by-side
in the listing output. Refer to Figure 3 and Figure 4 for examples of NARROW listings.
Valid for LINE comparison.
- NOPRTCC
- No printer
control columns. SuperC generates "normal" or NARROW listing
files with record lengths of 133 columns, or WIDE or LONGLN listing
with 203 columns. These listings contain printer control columns and
page separators. NOPRTCC eliminates both the page separators and page
header line. With NOPRTCC, "normal" and NARROW listings are 132
columns, and WIDE and LONGLN listings are 202. Section separators
and title lines are still generated. This file may be preferred for
on-line "browsing".
Valid for FILE, LINE, WORD, and BYTE
compare types and Search.
- NOSEQ
- No Sequence
numbers. Process fixed-length 80-byte record standard sequence number
columns (73 to 80) as data. This option is extraneous for any record
size other than 80.
Valid for LINE and WORD compare types and
Search.
- NOSUMS
- No Summary
Section. Eliminates the group and final summary section from the output
listing. This allows the user to generate a better "clean" copy
for program inspection. Conversely, it eliminates the all-problem
information in case of errors and option identification.
Valid
for LINE, WORD, and BYTE compare types and Search.
- REFMOVR
- Reformat
override. Reformatted lines are not flagged in the output listing.
They are, however, counted for the overall summary statistics and
influence the return code since they are a special case of an insert/delete
pair.
Valid for LINE compare type.
- SDUPM
- Search
duplicate members. Searches all members found in concatenated PDS
data sets, even if more than one member is found to have the same
name. Searches duplicate names even if the search is for a single
member or if members are specified using the SELECT process statement.
Valid for Search.
- SEQ
- Sequence numbers.
Ignore fixed-length 80-byte record standard sequence number columns.
Sequence numbers are assumed in columns 73 to 80 for such records.
This option is invalid for any record size other than 80.
Valid
for LINE and WORD compare types and Search.
- SYSIN
- Provide
alternate DD name for process statements. Syntax is SYSIN(DDNAME).
The default ddname is SYSIN. If this option is used, SuperC only accesses
process statements via the supplied ddname. It does not attempt to
access additional process statements via the SYSIN2 DD card.
Valid
for FILE, LINE, WORD, and BYTE compare types and Search.
- UPDCMS8
- Update
CMS 8 format. UPDCMS8 produces an update file that contains both
control records and source lines from the new input file. UPDCMS8
requires that the old file has fixed-length 80-byte records
with sequence numbers. The new file may have a variable or
fixed length format with an LRECL ≤ 80.
SuperC may change the
status of match lines to insert/delete pairs, enlarging the sequence
number gaps of the old file. The update file (when properly
named) can be used as input to CMS XEDIT. For information and an example
of this update file, see Update CMS sequenced 8 file.
Valid
for LINE compare type.
- UPDCNTL
- Update
Control. Produces a control file which relates matches, insertions,
deletions, and reformattings using relative line numbers (for LINE
compare type), relative word positions (for WORD compare type), or
relative byte offsets (for BYTE compare type) within the new and old file.
No source or data from either input file is included in the output
file. "Do not" process options/statements are compatible selections
for the LINE compare type. For information and an example of this
update file, see Update control files.
Valid
for LINE, WORD, and BYTE compare types.
- UPDLDEL
- Update
Long Control with all matches and delta changes. This reflects the
comparison's matches, inserts, and deletes. You can edit this update
file accepting, rejecting, or modifying the changes.
There are
control records preceding each change and matching section. After
the changes have been audited, optionally modified, and the control
records removed, you should be able to reuse this control file as
a composite new file.
Valid for LINE compare type.
- UPDMVS8
- Update
MVS8 format. Produces a file that contains both control and new file
source lines. Sequence numbers from columns 73 to 80 of the new file
are used (when possible) as insert references, while deletes use sequence
numbers from columns 73 to 80 of the old file. Both files must
have fixed-length 80-byte records. The format of the generated data
may be suitable as z/OS® IEBUPDTE
input. For information and an example of this update file, see Update MVS sequenced 8 file.
Valid for LINE compare type.
- UPDPDEL
- Update
prefixed delta lines. Produces a control data set containing header
records and complete (up to 32K line length limit) delta lines from
the input source files. Each output record is prefixed with identification
and information. The update data set is a variable-length data set
reflecting the input source files' characteristics.
Valid for
LINE compare type.
- UPDREV
- Update
Revision. UPDREV produces a copy of the new file with SCRIPT/VS .rc
on/off or BookMaster® :rev/:erev revision
codes delimiting most script lines that contain changes.
You may
wish to contrast the source lines delimited by the UPDREV option and
a similar flagging of the lines with changes from the output listing
file as produced by the GWCBL process.
Note: The revision character
used is controlled by using the REVREF process statement. For details,
see Revision code reference.
A REVREF process
statement (for example, REVREF REFID=ABC or REVREF
RCVAL=1) defines the revision level (SCRIPT/VS tags) or reference
ID (BookMaster tags).
Alternatively, SCRIPT/VS .rc delimiters may be controlled by the first
record in the new file. (For example, .rc 2 | as
the first record causes level 2 to be used).
Note: BookMaster requires the REFID value to
be defined with a :revision tag and "RUN=YES" attribute
to have the change character inserted in the processed document.
For
information and an example of this update file, see Revision file.
Valid for LINE and WORD
compare types.
- UPDREV2
- Update
Revision (2). UPDREV2 is identical to UPDREV with the exception that
data between the following BookMaster tags
are not deleted in the update file:
:cgraphic.
:ecgraphic.
:fig.
:efig.
:lblbox.
:elblbox.
:nt.
:ent.
:screen.
:escreen.
:table.
:etable.
:xmp.
:exmp.
Valid for LINE and WORD compare types.
- UPDSEQ0
- Update
Sequence 0 (zero). UPDSEQ0 produces a control file that relates insertions
and deletions to the relative line numbers of the old file.
Both control records and new file source lines are included
in the output file. This option is like UPDCMS8 except that it uses
relative line numbers (starting with zero) instead of the sequence
numbers from columns 73 to 80. The control field after a "$" designates
the number of new source lines that follow in the update file.
Both
fixed and variable record length lines are allowed. Fixed-length records
shorter than 80 bytes are padded with spaces to 80. Insertion lines
are full fixed or variable length copies of the new input data set
lines. For information and an example of this update file, see Update sequenced 0 file.
Valid for LINE compare
type.
- UPDSUMO
- Update
Summary only. UPDSUMO produces an update file of 4 lines (new file
ID, old file ID, totals header, single summary line). The summary
line is tagged with a "T" in column 1 and the summary statistics
are located at fixed offsets in the output line. The file has a record
length of 132. For information and an example of this update file,
see Update summary only files.
Valid for LINE,
WORD, and BYTE compare types.
- VTITLE
- Volume
title. VTITLE modifies the compare listing so that the data set volume
serial is printed below the data set name.
For a multi-volume
data set only the VOLSER of the first volume is displayed.
VTITLE
is ignored if the NTITLE or OTITLE process option is specified.
Valid
for LINE, WORD, and BYTE compare types.
- WIDE
- Wide
side-by-side listing. Creates a 202/203 variable-length listing file
with 80 columns from each source file. Inserts and deletes are flagged
and appear side-by-side in the listing output. For an example of a
WIDE side-by-side listing, see Figure 5.
Valid for LINE compare type.
- XREF
- Cross
reference strings. Creates a cross reference listing by search string.
Can be used with IDPFX, LMTO LNFMTO, and LTO.
Not implemented for LPSF.
The XREF option can be useful when
more than one search string (or search condition) is specified. The
XREF listing is implemented using a multiple pass operation for listing
the "lines found" for each individual string. Be aware that XREF
adds some additional processing overhead to the normal search process.
For an example of a search XREF listing, see Figure 1.
Valid for Search.
- XWDCMP
- Extended
WORD comparison. The word delimiter set is extended to include non-alphanumeric
characters (including spaces). For example, "ABCD(EFGH) JKL" is
2 words using normal WORD compare type, but 5 (3 words and 2 pseudo-words)
with the XWDCMP process option.
Valid for WORD compare type.
- Y2DTONLY
- Compare
Dates Only. Indicates that the comparison process is to be performed
only on the dates defined by the Date Definition process statements.
That is, all data in the input files is ignored in the comparison
process apart from that defined by NY2C, NY2Z, NY2D, NY2P, OY2C, OY2Z,
OY2D, and OY2P process statements. For further details on these process
statements, see Date definitions.
Note: - Y2DTONLY causes a "record-for-record" comparison to be performed
between the two input files, whereby dates are checked for being equal
or unequal. (The "high/low" comparison logic that SuperC normally
uses is not applied in the case of Y2DTONLY and, as such, the relative values of
the dates have no bearing on the result of the comparison.)
- Y2DTONLY is not supported for the process option GWCBL (change
bar listing).
Valid for LINE compare type.
|