Managing resources
Search resources are available on the upper right of any page.
Use a full name or a pattern:
Wildcard Symbol | Description |
% | Replacing one character, e.g. M9RES% |
* | Replacing zero or more characters |
A search can be invoked for a data set, volume or unix object by using the full name or a pattern. Partial matches are returned.
When searching for a data set, the search displays available backup copies from incremental backup, full dumps, archived data sets and cloud data sets.
The search results page is divided into tabs:
- 1.The first tab displays data sets
- 2.The second tab displays full volumes
- 3.The third tab displays z/OS UNIX objects
By default, the results are displayed in ascending name order. Each column can be used for sorting, the sort icon is visible when clicking the column name. Additionally, the table contains column filters to allow further filtering of the results.
It is possible to perform immediate actions on the displayed items. Actions can be performed on an individual item using the 3-dot menu, or on multiple items using the actions listed on the upper right side of the page.
Column “complex”
This value indicates the resource complex and can be used to distinguish between data sets or volumes with the same name in different complexes. The resource complex is defined in the
agent.yml, with a default of the group-&SYSPLEX. An agent can be associated with one resource complex, several agents can be associated with the same resource complex. Agents sharing the same resource complex can all interact with the same resources, actions such as backup/archive/recall/restore/list are all dependent on the resource complex parameter.View resource details by selecting the “More details” option from the 3-dot menu:
A popup window showing the data set’s details is displayed.
View the resource activity log by selecting the “View backup log” option from the 3-dot menu:
A popup window showing the resource backup log is displayed.
Select the “Restore” option from the 3-dot menu:
Field | Description |
Target data set name | The operation can allocate the restored data set using a different name than the original backed up data set name. Whether the original name is changed or not, the user must have SAF alter access permission for this data set name in the target system, in addition to Model9 permission to perform the UI restore action. |
Restore volume name | The VOLSER name to use for the allocated data set name. The VOLSER can be different from the original VOLSER. |
Overwrite target data set? | Whether or not to replace the target data set if it already exists. |
Catalog restored data set | Whether or not to catalog the restored data set. SMS-managed data sets will be cataloged, regardless of this parameter setting. |
Execution agent | When restoring a data set backup which originated from a the CLI BACKDSN command, the agent on which to execute the restore operation must be specified. This field is not visible when restoring a data set backup done which was created by a policy - in which case the same agent that performed the backup will be responsible for the restore operation. |
Use the “Advanced SMS parameters” tab to set the SMS attributes of the restored data set. These parameters will be passed to the ACS routines, unless “Bypass ACS routines” is specified. For more information, see the IBM DFSMS documentation.
The parameters are:
Parameters | Description |
Storage class | Specify the storage class to be assigned. |
Management class | Specify the management class to be assigned. |
Null storage class | Set the storage class to null. |
Null management class | Set the management class to null. |
Bypass ACS routines | Whether or not to give control to the SMS ACS routines during data set allocation. Using this option requires SAF permission to M9.UI.RESTDSN.BYPASSACS. |
When done, click “Restore” to restore the data set.
Restoring a full dump disk requires both admin and a restore permission:
Field | Description |
Target volume name | The target online VOLSER on which the full dump volume will be restored. The restore will erase all previous data on the VOLSER. When restoring a disk, only the data on the disk changes, the restore does not update the catalog. |
Overwrite target volume name? | Whether or not to copy the original VOLSER to the target volume. If there is another disk with the same name as the original VOLSER, the other disk will be offlined by the system, as 2 disks cannot exist with the same name. |
When done, click “Restore” to restore the volume.
Field | Description |
Target file | Target file name |
Overwrite target file? | Whether or not to override the target file if it already exists. |
When done, click “Restore” to restore the file.
Select the “Recall” option from the 3-dot menu:
A popup window with recall parameters is displayed.
Field | Description |
Recall volume name | The operation can allocate the restored data set in a different name than the original backed-up data set. Whether the original name is changed or not, the user must have SAF permissions for this data set name in the target system, in addition to Model9 permissions to perform the UI restore action. |
Use the “Advanced SMS parameters” tab to set the SMS attributes of the recalled data set. These parameters will be passed to the ACS routines, unless specified “Bypass ACS routines”. For more information, see the IBM DFSMS documentation.
The parameters are:
Parameters | Description |
Storage class | Specify the storage class to be assigned. |
Management class | Specify the management class to be assigned. |
Null storage class | Set the storage class to null. |
Null management class | Set the management class to null. |
Bypass ACS routines | Whether or not to give control to the SMS ACS routines during data set allocation. Using this option requires SAF permission to M9.UI.RESTDSN.BYPASSACS. |
When done, click “Recall” to recall the data set.
A cloud data set is a data set that was imported from tape to cloud by the DATA SET IMPORT policy. The “Export” option provides several methods for exporting the data set for use by z/OS applications. Select the “Export” option from the 3-dot menu:
Since tapes work differently than DASD, data sets that were originally allocated on tapes can have attributes that are not always applicable for DASD allocation.
Also, data sets on tape do not have the associated space attributes required for DASD allocation, meaning that the allocation parameters that would be used are the ones specified during the “Export” action.
Specify the following parameters:
Parameters | Description |
Data Set Name | The name of the data set to be allocated in z/OS. By default, the UI displays the cloud data set name. Mandatory field. |
Target Data Set Name | The name of the data set to be allocated in z/OS. By default, the UI displays the cloud data set name. Mandatory field. |
Export Volume Name | The name of the VOLSER on which the data set is to be allocated in z/OS. Specifying this parameter means the data set will be allocated on a single volume (The “Volume Count” parameter of the “allocation parameters” will be ignored). For SMS-managed data sets, the target VOLSER will be determined by the ACS routines. |
Export to z/OS in format DATA SET | This option will create a z/OS data set. |
Export to z/OS in format AWS TAPE | This option will create a z/OS data set, containing the exported tape data in an AWS virtual tape format that can be read by distributed platforms. AWS TAPE format is suitable for data sets with a block size not applicable for DASD allocation. |
By default, the exported data set will be allocated in a DATA SET in z/OS format, on DASD, with size as automatically calculated based on the cloud data set size. The UI provides additional parameters to set the allocation parameters and overwrite SMS parameters.
When choosing the parameters, consider the following:
Property | Description |
Size | Many tape data sets are very large in size and may require allocation as large, extended or multi volume data sets on DASD. When exporting a large data set:
|
Original block size | Cloud storage can accommodate any block size, however, tape data sets can have a block size larger than 32760, that is not eligible for DASD allocation. In this case, allocate the exported data set using one of the following options:
|
Use the “Allocation parameters” tab to provide the allocation attributes of the exported data set:
Field | Description |
Unit | Any applicable z/OS value. Default: 3390 |
Space in CYLs | By default, the UI will display an estimated size, as automatically calculated based on the cloud data set size. |
DSNTYPE | Default: NONE. |
Volume Count | Default: 5. This parameter is relevant for SMS-managed data sets only, and is ignored if specifying a value in “Export Volume Name”. |
Use the “Advanced SMS parameters” tab to set the SMS attributes of the exported data set:
Field | Description |
Storage class | Specify the storage class to be assigned. |
Management class | Specify the management class to be assigned. |
Data class | Specify the data class to be assigned. |
When done, click “Export” to export the data set.
Select the "Delete" option from the 3-dot menu:
Confirm:
Click "Delete" to delete the data set.
Select the resources to be deleted and click “Delete” button above the table, next to the page size selector. Check the checkbox next to NAME in the heading bar to select all the resources that are currently displayed on the screen.
The “Prepare Stand-Alone Copy” option in the 3-dot menu is part of the stand-alone restore process. The action is available only to Model9 administrators and will not be visible to non-admin users. If the original full dump was created using DFDSS_GZIP, it will not be possible to create a stand-alone copy of it.
After the user confirms the action, an asynchronous activity is created in the management server.
Once the stand-alone copy is created, select the “View Log” option from the 3-dot menu to display information pertaining to the stand-alone copy, including:
- Source volume, backup date and size
- Output directory path, name and size of each dump section
- Restore command required for restoring data from the Stand-Alone copy
Document the restore command in a place that will be accessible during a stand-alone process. See Performing stand-alone restore (bare-metal recovery) for more details.
The activity run of "Data Set Cleanup" policy type will scan all SMS resource eligible for deletion according to the SMS Management Class settings or by the catalog entry. Data sets that were created with an expiration value of 0 will be eligible for deletion the day after they are created in order to prevent unintended data removal.
Last modified 3mo ago