Creating copy areas on the remote system

Allocate one copy area for each distributed view. If the structure of a mapped view changes, upload the files in the view again to reflect the change.

1. Allocate the data set on the mainframe system to be used as a copy area, which is a designated storage area on the mainframe where copies of your distributed files reside.
   Allocate one copy area for each distributed view. If the structure of a mapped view changes, upload the files in the view again to reflect the change.

   Copy areas must be allocated as partitioned data sets (PDS). Allocate your copy area with a variable block record format (RECFM=VB) and 256-byte record length (LRECL=256) unless you require other allocation parameters. If you try to use a type other than PDS, an allocation error displays.

   Examples of data that requires other parameters include:

   • JCL and source code libraries (RECFM=FB, LRECL=80).
   • Object (binary) code (user-defined RECFM and LRECL).
2. Name the copy area.
   Note: When naming your copy area, do not use the following names:

   • userID.TSC.LOG
   • userID.TSC.LOG2
   • userID.TSC.CMD
   • userID.TSC.JCL

   The copy area name consists of two parts:

   • The local PDS prefix
     This is a unique identifier that precedes your copy area file name. Local PDS prefixes must contain no dashes. They can have single or multiple data set name levels (using one or more periods [.]).

     Note: Choose a PDS prefix that is not used with any other view.

     A default local PDS prefix is generated by your TSO logon ID and the last eight characters of the view name. For example, a z/OS® logon ID of RFGUSER1 and a view name with the last eight characters of DEVVIEW produces a local PDS prefix of RFGUSER1.DEVVIEW.

     Be aware that if you change the local PDS prefix, the client component of TSO Client retrieves information from the distributed system, performing an active refresh of your mainframe file list exactly as it does when you select a new environment definition or view. For more information, see Refreshing copy areas.

   • The mapped file suffix

     This is a meaningful name that describes the file being mapped on the distributed system. For example, a file that contains Assembler programs might be named SRC.ASM.

     Note: The file suffix on a distributed system (such as Windows®, UNIX®, or Linux®) must be composed of five characters or less.

   Using the examples above, an example of a complete copy area name, is RFGUSER1.DEVVIEW.SRC.ASM.

3. Map, or associate, your distributed views to a mainframe copy area.
4. Work with the files in the copy area using the client component of TSO.