Creating a PDS or PDSE - mkdir dsntype(pds), dsntype(library)

To create a PDS or PDSE, perform the following steps:

Create a local directory on your client to be used as a mount point. For example (with UNIX), enter this command:
```
$ mkdir /u/smith/mnt
```
Mount the MVS file system (accessing files that begin with the high-level qualifier of smith).
```
# mount mvshost1:"smith,mgmtclas(normal)"
/u/smith/mnt
```
If creating a PDSE, use the mkdir (make directory) UNIX command, specifying the dsntype(library) attribute to create a PDSE named smith.datalib.
```
$ mkdir /u/smith/mnt/"datalib,dsntype(library)"
```
If creating a PDS, use the mkdir (make directory) UNIX command, specifying the following dsntype(pds) attribute.
```
$ mkdir /u/smith/mnt/"datalib,dsntype(pds),dir(20)"
```
Omitting dsntype(pds): You can omit specifying the dsntype(pds) attribute if pds has been specified for the dsntype attribute either in your site attribute data set or in your mount point.
You can use the vi UNIX command to create a PDS or PDSE member named smith.datalib(member1).
```
$ vi "/u/smith/mnt/datalib/member1,text"
```
Type your text, save it, and quit.

You have now created a PDS or PDSE member, which is processed in text processing mode. You can use the cat UNIX command to view the contents of your PDS or PDSE member.

Note: z/OS NFS server supports a maximum of 14,562 members in a PDS or PDSE data set. When a NFS read-directory request on a PDS or PDSE is processed, the z/OS NFS server will return up to 14,562 member names. Other requests, such as read and write, to individual members are not affected.