Dovetailed Technologies Solutions Support Contact Us

Appendix C. Dataset Name Determination

When issuing a put command to create a dataset, or get to a local dataset using the cozsftp client, the resulting dataset name is determined as follows:

put myfile //HLQ.LEVEL
get myfile //HLQ.LEVEL (using the cozsftp client)

Table C.1. Dataset Name determination

CaseConditionDataset NameNotes
1HLQ.LEVEL is a Sequential DatasetHLQ.LEVELReplaces existing SEQ dataset
2HLQ.LEVEL is a PDSHLQ.LEVEL(MYFILE)Creates or replaces member named MYFILE in PDS
3HLQ.LEVEL is not a dataset, but HLQ.LEVEL.XXX names exist in catalogHLQ.LEVEL.MYFILECreate or replace SEQ dataset
4HLQ.LEVEL is not a dataset, and no HLQ.LEVEL.XXX names exist in catalogHLQ.LEVELCreates new SEQ dataset

In most cases, this is acceptable behavior. However, there are cases where the supplied name should be treated as a dataset rather than a "directory" (as in Case 3 above). If this is the required behavior, a different dataset prefix can be supplied: //! or /-/!:

put myfile //!HLQ.LEVEL
get myfile //!HLQ.LEVEL  (using the cozsftp client)

Table C.2. Dataset Name determination

CaseConditionDataset NameNotes
1HLQ.LEVEL is a Sequential DatasetHLQ.LEVELReplaces existing SEQ dataset
2HLQ.LEVEL is a PDSHLQ.LEVEL(MYFILE)Creates or replaces member named MYFILE in PDS
3HLQ.LEVEL is not a datasetHLQ.LEVELCreates new SEQ dataset

NOTE: If you intend to always use a fully qualified dataset name, it is preferable to use the //! or /-/! syntax.

Copyright 2009 Dovetailed Technologies, LLC. All rights reserved.