Table of Contents
Advertisement
v The command is different from mirror_create_snapshot whereas it is applied to
v The event is triggered for all pertinent couplings at the same time.
v A Warning message is presented to the user, requiring a confirmation.
Access Control:
Completion Codes:
v SCHEDULE_DOES_NOT_EXIST
v SCHEDULE_IS_NOT_MANUAL
Deletes a Schedule Object
Deletes a schedule for replication.
Parameters:
This command deletes a schedule definition.
The command can be issued successfully only if the schedule specified is not
referenced by a mirror coupling, or if it is not a pre-defined schedule
(min_interval).
Outcome:
v Command will delete the schedule specified
Example:
234
IBM XIV Storage System User Manual
schedule (and only whenever the schedule is of a non-interval type) which is
equivalent to the 'new-interval-arrived' event triggered automatically by the
system for a mirror (with a schedule of type interval).
mirrors that do not have an interval-based schedule. Thus, even though an event
is triggered immediately (as with mirror_create snapshot), no sync job is created
for a pertinent mirror with the specified schedule (in a case that such mirror has
an outstanding sync job, as one might expect for mirrors with an interval-based
schedule if a new interval arrives during an outstanding job).
User Category
Storage administrator
Storage integration administrator
Application administrator
Security administrator
Read-only users
Technicians
Specified Schedule does not exist
Specified Schedule does not allow external trigger
schedule_delete schedule=Schedule
Name
Type
schedule
Object name
Permission
Allowed
Disallowed
Disallowed
Disallowed
Disallowed
Disallowed
Description
Mandatory
The name of the
Y
schedule to be deleted.
Hide quick links:
Advertisement
Chapters
Table of Contents
