Deploying Products › Change Deployments › Methodologies › Edit a Methodology

Edit a Methodology

You can edit a methodology by updating or modifying any of the fields on the Edit Methodology window.

Follow these steps:

1. Click the Deployments tab, and in the Actions section click the Maintain Methodologies link.
2. Select the methodology that you want to edit, click the Actions drop-down list, and then click Edit.

   The Edit Methodologies dialog appears.

   Note: The asterisk indicates that the field is mandatory.

   As with Add a Methodology, all fields are available to be edited and the details for each field are listed.

3. Enter the methodology name.

   Limits: 64 characters

   Note: Each methodology name must be unique and it is not case-sensitive. For example, Meth1 and meth1 are the same methodology name.

4. Enter the Description of this Methodology.

   Limits: 255 characters

5. Enter the data set name mask, click the file icon, and select a symbolic name.

   Data Set Name Mask

   This is the mask that will be used to name the data sets that are deployed. They can contain symbolic qualifiers.

   Example: CAPRODS.&SYSID. - in this case the &SYSID. will be replaced by its values. If the SYSID that is being deployed to is XX16 the DSN mask will be: CAPRODS.XX16

   Limits: Maximum 64 characters.

   Note: Each deployed target data set is named using the resolved content of the data set name mask followed by the low-level qualifier of the source data set. Appending the low-level qualifier from the source data set helps ensure uniqueness of the final data set name. Verify that the mask that you entered does not exceed 35 characters when it is translated.

   The mask consists of one or more qualifiers that are separated by periods. The maximum number of characters is 64, including the periods. While you are entering the mask, CA CSM validates the mask by replacing symbolics with the minimum possible values first, and then with the maximum values. If the validation with the minimum possible values fails, an error message appears at the top of the dialog, and you cannot proceed. If the validation with the maximum values fails, a warning message appears, and you can proceed.

   When the mask is translated, it has a maximum length of 44 characters including the periods and the low-level qualifier from the source data set. The low-level qualifier from the source data set has a maximum length of nine characters including a period.

6. Select a style of the deployment.

   Create Only

   Creates new data sets.

   Note: Prior to creating any data sets on the remote system, a check is made, to see if the data sets already exist. The deployment is not allowed to continue if this occurs.

   Create or Update

   If you select Create or Update and the target data sets do not exist, they will be created. If the target data sets exist, Create or Update indicates that data in the existing data set, file or directory will be replaced.

   Partitioned data set

   Create or Update indicates that existing members in a partitioned data set will be replaced by members with the same name from the source file. Any currently existing member that is not in the source file will remain in the PDS. Any member from the source that does not already exist in the target PDS will be added to the target PDS.

   The amount of free space in the PDS will need to be sufficient to hold the additional content, since no automatic compress will be done.

   Directory in a UNIX file system

   Create or Update indicates files in a directory will be replace by files with same name from the source. Any currently existing directory in a UNIX file system that is not in the source will remain in the UNIX file system.

   Sequential data set or a file in the UNIX file system

   Create or Update indicates the existing data set or file and its attributes will be replaced with the data from the source file.

   For a VSAM data set (cluster)

   Create or Update indicates that an existing VSAM cluster should be populated with the data from the source file.

   Note: The existing VSAM cluster must be of the same type as the source cluster (ESDS, KSDS, LDS, or RRDS), and it must have characteristics that are compatible with the source cluster (such as, record size, key size, and key offset). Replace does not verify the compatibility of these characteristics!

   To replace the contents of an existing cluster, the cluster is altered to a reusable state by using an IDCAMS ALTER command, if necessary, before the data from the VSAM source is copied into the cluster by using an IDCAMS REPRO command. The REPRO command will use both the REPLACE and REUSE operands. Following the REPRO operation, the cluster is altered back to a non-reusable state if that was its state to begin with.

   Replace

   Removes any existing deployment data sets and creates new ones.

   Prior to creating any data sets on the remote system, all existing data sets are removed: the system first allocates all target data sets and then deletes them. If any data set is used by another user or application, the data set cannot be deleted, and the whole deployment fails. In this case, no data sets are deleted.

7. Click Save.

   Your changes are saved.

   Note: Click Cancel to close this dialog without saving your changes.