Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Standard ISPF naming conventions z/OS ISPF User's Guide Vol I SC19-3627-00 |
|
Each component of the library name can be up to 8 alphanumeric or national characters; the first one must be alphabetic. This conforms to standard TSO data set naming conventions. For convenience, any cataloged data set (sequential or partitioned) with a three-level name can be entered in the Project, Group, and Type fields, with one level of the name in each field. If a cataloged data set with four or more levels is to be entered, multiple levels of the name may be entered in each field, with each level being separated by a period. If both a library and a data set name are specified on the same panel, the data set name takes priority. Therefore, to specify a library, leave the Data Set Name field blank. When the library identification appears in a title line or message,
the project name, group name, and type name are separated with periods.
A member name, if applicable, is enclosed in parentheses. For example:
On most data entry panels that allow a library name to be specified,
a Member field is available:
The ISPF library's project, group, and type must always accompany the member name, if entered. If you try to edit a member that does not exist, ISPF provides an Edit display screen with a blank data area. Member names entered in the Member field or those enclosed in parentheses and entered in the Data Set Name field must follow standard ISPF naming conventions. If you have a partitioned data set with members whose names do
not follow ISPF naming conventions, ISPF allows limited processing,
as follows:
ISPF cannot process member names that begin with a blank or have embedded blanks which can cause unpredictable results. Also, ISPF cannot process member names that include special characters, such as an ampersand (&). CLIST processing in both Foreground (option 4) and Batch (option 5) can result in a runtime error. |
Copyright IBM Corporation 1990, 2014
|