Uploading files to a copy area on z/OS

The Upload function is for setup operations where a large number of files are needed to populate a partitioned data set. This function uploads files of all states (checked in, etc.).

Before you begin

Attention: If you want to upload files via panel 4, you must make sure ENABLE_CHECKCOUPD is not specified in profile, or specify ENABLE_CHECKCOUPD as FALSE. If you specify ENABLE_CHECKCOUPD as TRUE, the upload command u will be blocked on panel 4.

About this task

The Upload option is intended to be used during setup. If a view-private file exists only on the mainframe and if you choose option 4, the data in the view-private member is cleared. If you previously uploaded files and if you chose option 4, the data that exists on the distributed system replaces the data in the corresponding members. You do not have to upload all files to a partitioned data set (PDS) to use TSO Client. You can use option 4, View File List from the main menu to upload specific files.
If you perform any of the following actions, be sure that you check in all your files before the action. After performing the action, be sure to upload the files of interest. The upload can be done with option 4. This sequence of actions ensures that the TSO Client remains synchronized with the distributed system config spec.
  • Change a config spec on your distributed system.
  • Rebase a UCM stream.

Procedure

To upload distributed DevOps Code ClearCase files to the mainframe for use with TSO Client, do these steps:
  1. On the TSO Client Main Menu, verify that the local PDS prefix contains the prefix name of the copy area to which you want to upload distributed files. If it does not contain the prefix name, change it.
    Note: Choose a local PDS prefix that is not used with any other view.
  2. On the option line of the TSO Client Main Menu, type 4.
    Attention: Option 4 is intended to use as part of a setup operation. If you create new members in your PDS as part of your development process and then choose option 4, the text in your new members is deleted. Likewise, any changed text is replaced with the original text.
  3. On the Dataset Action panel, verify that all listed data sets exist and are ready to be uploaded to the mainframe system.
  4. To select data sets to upload, do one of these actions.
    • Type u next to the data sets you want to upload and press Enter.
    • Type SELECT followed by a data set search criterion on the option line. The search criterion cannot be a complex search such as *TSC*CTS*, but can contain a period ( . ), such as *TSC.CTS*. The following list shows valid search criteria:
      • TSC and TSC*: Uploads data sets staring with TSC
      • *TSC*: Uploads data sets containing the string TSC
      Data sets that match the criterion are uploaded.
    Note: When file names (not including file type extension) are greater than 8 characters long, the first 8 characters must be unique. Otherwise, they will be overlaid when uploaded into the same copy area PDS. This requirement is due to the MVS™ 8-character restriction for member names. Likewise, because of the ambiguity, the download of the member might not update the proper file.