 |
- data_set_name
- specifies the name of the data set that you want to create or
edit.
If you enter the name of a sequential data set, but the data
set is actually found to be a partitioned data set, the member name
TEMPNAME is assumed. See also the description of the OLD operand below.
- password
- specifies the password associated with the data_set_name.
If the password is omitted and the data set is password protected,
you are prompted for the data set's password. Read protected partitioned
data sets prompt for the password twice, provided it is not entered
on the EDIT command, or is not the same password as your LOGON user
ID password.
- EMODE | IMODE
- EMODE
- specifies the initial mode of entry is edit mode. This is the
default for OLD data sets. See z/OS TSO/E User's Guide,
for more information about using edit mode.
- IMODE
- specifies the initial mode of entry is input mode. This is the
default for NEW or empty data sets. See z/OS TSO/E User's Guide,
for more information about using input mode.
- RECOVER | NORECOVER
- RECOVER
- specifies that you intend to recover an EDIT work file containing
the data set named on the EDIT command as the data set to be edited.
You are placed in edit mode. This operand is valid only when your
profile has the RECOVER attribute. See z/OS TSO/E User's Guide,
for more information.
- NORECOVER
- specifies that you do not want to recover a work file, even if
a recoverable work file exists. Any existing work files will be reused
to hold data set information for the current edit session. As a result,
any recovery information from a previous session will be lost.
- NEW | OLD
- NEW
- specifies the data set named by the first operand does not exist.
If an existing cataloged data set already has the data set name that
you specified, the system notifies you when you try to save it. Otherwise,
the system allocates your data set when you save it. If you specify
NEW without specifying a member name, a sequential data set is allocated
for you when you save it. If you specify NEW and include a member
name, the system allocates a partitioned data set and creates the
indicated member when you try to save it.
- OLD
- specifies the data set named on the EDIT command already exists.
When you specify OLD and the system is unable to locate the data set,
you are notified and you have to reenter the EDIT command. If you
specify OLD without specifying a member name, the system assumes that
your data set is sequential. If the data set is, in fact, a partitioned
data set, the system assumes that the member name is TEMPNAME. If
you specify OLD and include a member name, the system notifies you
if your data set is not partitioned.
Note: Specifying OLD will not prevent other users
from using EDIT to update the same member in the same partitioned
data set (PDS) at the same time. OLD informs the EDIT command that
the data set already exists - it does not provide protection equivalent
to specifying DISP=OLD for the data set.
If you do not specify
OLD or NEW, the system uses a tentative default of OLD. If the data
set name or member name that you specified cannot be located, the
system defaults to NEW.
Any user-defined data set type is also
a valid data set type operand and can have subfield parameters defined
by your installation (see Table 1, note
4).
- PLI
- specifies the data identified by the first operand is for PL/I
statements that are to be held as V-format records with a maximum
length of 104 bytes. The statements can be for the PL/I Optimizing
compiler or the PL/I Checkout compiler.
- PLIF
- specifies the data set identified by the first operand is for
PL/I statements that are to be held as fixed format records 80 bytes
long. The statements can be for the PL/I Optimizing compiler or the
PL/I Checkout compiler.
- integer_1 and integer_2
- specify the column boundaries for your input statements. These
values are applicable only when you request syntax checking of a data
set for which the PLIF operand has been specified. The position of
the first character of a line, as determined by the left margin adjustment
on your terminal, is column 1. The value for integer_1
specifies the column where each input statement is to begin. The
statement can extend from the column specified by integer_1 up
to and including the column specified as a value for integer_2.
If you omit integer_1, you must omit integer_2.
The default values are columns 2 and 72. However, you can omit integer_2 without
omitting integer_1.
- CHAR48 | CHAR60
- CHAR48
- specifies the PL/I source statements are written using the character
set that consists of 48 characters.
- CHAR60
- specifies the source statements are written using the character
set that consists of 60 characters.
If no value is entered, the default value is
CHAR60.
- ASM
- specifies the data set identified by the first operand is for
assembler language statements.
- COBOL
- specifies the data set identified by the first operand is for
COBOL statements.
- CLIST
- specifies the data set identified by the first operand is for
a CLIST and contains TSO/E commands, subcommands, and CLIST statements
as statements or records in the data set. The data set is assigned
line numbers.
- CNTL
- specifies the data set identified by the first operand is for
job control language (JCL) statements and SYSIN data to be used with
the SUBMIT command or subcommand.
- TEXT
- specifies the data set identified by the first operand is for
text that can consist of both uppercase and lowercase characters.
- DATA
- specifies the data set identified by the first operand is for
data that can be subsequently retrieved or used as input data for
processing by an application program.
- FORTGE
- specifies the data set identified by the first operand is for
FORTRAN IV (E) statements.
- FORTG
- specifies the data set identified by the first operand is for
FORTRAN IV (G) statements.
- FORTGI
- specifies the data set identified by the first operand is for
FORTRAN IV (G1) statements.
- FORTH
- specifies the data set identified by the first operand is for
FORTRAN IV (H) EXTCOMP statements.
- GOFORT(FREE | FIXED)
- specifies the data set identified by the first operand is for
statements that are suitable for processing by the Code and Go FORTRAN
licensed program. If you enter the descriptive qualifier without
a data set type, the data set type default is GOFORT(FREE). If you
do not specify a FORTRAN language level, GOFORT is the default value.
FREE specifies the statements are of variable-lengths and do not
conform to set column requirements. If you do not specify FREE or
FIXED, FREE is the default. FIXED specifies statements adhere to
standard FORTRAN column requirements and are 80 bytes long.
- VSBASIC
- specifies the data set identified by the first operand is for
VSBASIC statements.
The ASM, CLIST, CNTL, COBOL, DATA, FORTGI,
FORTH, GOFORT, PLI, PLIF, TEXT, and VSBASIC operands specify the type
of data set you want to edit or create. You must specify one of these
whenever: - The data_set_name operand does not follow data
set naming conventions (that is, it is enclosed in quotation marks).
- The data_set_name operand is a member name
only (that is, it is enclosed in parentheses).
- The data_set_name operand does not include
a descriptive qualifier or the descriptive qualifier is such that
EDIT cannot determine the data set type.
The system prompts you for data set type whenever the
type cannot be determined from the descriptive qualifier (as in the
3 cases above), or whenever you forget to specify a descriptive qualifier
on the EDIT command.
Note: If PLI is the descriptive qualifier,
the data set type default is PLI. To use data set types GOFORT, FORTGI,
or FORTH, you must enter the data set type operand to save it.
- SCAN | NOSCAN
- SCAN
- specifies each line of data you enter in input mode is to be checked,
statement by statement, for proper syntax. Syntax checking is available
only for statements written in FORTGI or FORTH.
If your installation
specified a syntax checker after system generation, user-defined data
set types can also use the SCAN operand.
- NOSCAN
- specifies syntax checking is not to be performed. NOSCAN is the
default.
- NUM(integer_1 integer_2)
| NONUM
- NUM(integer_1 integer_2)
- specifies lines of the data set records are numbered. You can
specify integer_1 and integer_2 for
ASM type data sets only. integer_1 specifies,
in decimal, the starting column (73-80) of the line number. integer_2 specifies,
in decimal, the length (8 or less) of the line number. integer_1 plus integer_2 cannot
exceed 81. If integer_1 and integer_2 are
not specified, the line numbers assume appropriate default values.
NUM
is the default.
- NONUM
- specifies your data set records do not contain line numbers. Do
not specify this operand for the VSBASIC and CLIST data set types
because they must always have line numbers.
- BLOCK(integer) | BLKSIZE(integer)
- specifies the maximum length, in bytes, for blocks of records
of a new data set. Specify this operand only when creating a new
data set or editing an empty old data set. You cannot change the
block size of an existing data set except if the data set is empty.
If you omit this operand, it defaults according to the type of data
set being created. The IBM-supplied default values for the block sizes
are described in Table 1. To modify
those default values, see z/OS TSO/E Customization.
The block size (BLOCK or BLKSIZE), for data sets that contain fixed-length
records must be a multiple of the record length (LINE or LRECL).
For variable-length records, the block size must be a multiple of
the record length plus 4.
If BLKSIZE (80) is coded with RECFM(U),
then the line is truncated by 1 character. This byte (the last one)
is reserved for an attribute character.
- LINE(integer) | LRECL(integer)
- specifies the length of the records to be created for a new data
set. Specify this operand only when creating a new data set or editing
an empty old data set. The new data set is composed of fixed-length
records with a logical record length equal to the specified integer.
You cannot change the logical record size of an existing data set
unless the data set is empty. If you specify this operand and the
data set type is ASM, FORTGI, FORTH, COBOL, or CNTL, the integer must
be 80. If this operand is omitted, the length defaults according
to the type of data set being created. The IBM-supplied default values
are described in Table 1. To modify
those default values, see z/OS TSO/E Customization.
Use this operand with the BLOCK or BLKSIZE operand.
- CAPS | ASIS
-
- CAPS
- specifies all input data and data on modified lines is to be converted
to uppercase characters. If you omit both CAPS and ASIS, CAPS is
the default unless the data set type is TEXT.
- ASIS
- specifies input and output data are to retain the same form (uppercase
and lowercase) as entered. ASIS is the default for TEXT only.
Table 1. EDIT command:
default values for LINE or LRECL and BLOCK or BLKSIZE operands| Data set type |
DSORG |
LRECL |
Block
size |
Line numbers |
|
|---|
| LINE(n) |
BLOCK(n) |
NUM(n,m) |
CAPS/ASIS |
|---|
| Default |
Specif. |
Default |
Specif. (Note 1) |
Default(n,m) Specif. |
Default |
CAPS Required |
|---|
| ASM |
PS/PO |
80 |
=80 |
3120 |
<=default |
Last 8 73<=n<=80 |
CAPS |
Yes |
| CLIST |
PS/PO |
255 |
(Note 2) |
3120 |
<=default |
(Note 3) |
CAPS |
Yes |
| CNTL |
PS/PO |
80 |
=80 |
3120 |
<=default |
Last 8 |
CAPS |
Yes |
| COBOL |
PS/PO |
80 |
=80 |
400 |
<=default |
First 6 |
CAPS |
Yes |
| DATA |
PS/PO |
80 |
<=255 |
3120 |
<=default |
Last 8 |
CAPS |
No |
| FORTE |
PS/PO |
80 |
<=255 |
3120 |
<=default |
Last 8 |
CAPS |
Yes |
| FORTG |
PS/PO |
80 |
<=255 |
3120 |
<=default |
Last 8 |
CAPS |
Yes |
| FORTGI |
PS/PO |
255 |
=80 |
400 |
<=default |
Last 8 |
CAPS |
Yes |
| FORTH |
PS/PO |
255 |
=80 |
400 |
<=default |
Last 8 |
CAPS |
Yes |
| GOFORT |
PS/PO |
255 |
|
3120 |
<=default |
First 8 |
CAPS |
Yes |
| (Or
user supplied data set type - see Note 4) |
|
|
|
|
|
| PLI |
PS/PO |
104 |
<=100 |
400 |
<=default |
(Note 3) |
CAPS |
No |
| PLIF |
PS/PO |
80 |
<=100 |
400 |
<=default |
Last 8 |
CAPS |
Yes |
| TEXT |
PS/PO |
255 |
(Note 2) |
3120 |
<=default |
(Note 3) |
ASIS |
No |
| VSBASIC |
PS/PO |
255 |
=80 |
3120 |
<=32,760 |
First 5 |
CAPS |
Yes |
| |
|
|
|
|
|
|
|
|
Notes
- IBM® supplies the default
values. For information about how to modify the default values, see z/OS TSO/E Customization.
- Specifying a LINE value results in fixed-length records with a
LRECL equal to the specified value. The specified value must always
be equal to or less than the default. If the LINE operand is omitted,
variable-length records are created.
- The line numbers are contained in the last eight bytes of all
fixed-length records and in the first eight bytes of all variable-length
records.
- A user can have additional data set types recognized by the EDIT command processor. You can
modify the user-defined data set types along with any of the data
sets shown above after system generation time by using the
EDIT macro. The EDIT macro causes a table of constants to be built,
which describes the data set attributes. For more information about
how to modify the EDIT macro, see z/OS TSO/E Customization.
When
you edit a data set type you defined yourself, the system uses the
data set type as the descriptor (right-most) qualifier. You cannot
override any data set types that have been defined by IBM. The EDIT command processor supports
data sets that have the following attributes: - Data Set Organization:
- Must be either sequential or partitioned
- Record Format:
- Fixed or variable
- Logical Record Size:
- Less than or equal to 255 characters
- Block Size:
- User specified-must be less than or equal to track length
- Sequence Number:
- V type--First 8 characters
- F type--Last 8 characters
-
|
|
z/OS TSO/E Command Reference
Copyright IBM Corporation 1990, 2014