The use of the MVS CANCEL command on Restore, Auto-restore, Recover and FMS Recover jobs has occasionally resulted in partial data sets being left. To prevent this, Restore type jobs will set the job noncancelable during the restore process. Instead of using the CANCEL command to terminate the job, it will be necessary to use the MVS STOP command. When the STOP command is issued to the Restore type job the restore function will be terminated and the data set in the process of being restored will be cleaned up according to normal CA Disk disposition rules for restore failures. Data sets that were cataloged to the pseudo-volume will be deleted and recataloged to the pseudo-volume. Data sets that were uncataloged at the start of the restore will be deleted and uncataloged. Predefined data set disposition will depend on the data set organization. Partitioned data sets (PDS) and partitioned data sets/extended (PDSE) that were being restored with the ERASE parameter specified will be deleted and uncataloged. PDS and PDSE data sets that were being restored without the ERASE parameter will be kept. Generation data sets (GDG) will be kept. All other predefined data sets will be deleted and uncataloged.
The format of the MVS STOP command, which can be abbreviated as P, is:
STOP jobname [.taskid][,A=asid]
Or:
STOP taskid[,A=asid]
If batch job DMSREST1 was running in ASID x'105' it can be stopped by:
P DMSREST1
Or:
P DMSREST1,A=105
Note: The ASID is in undelimited hexadecimal notation.
If a DMSAR started task was started with the command S DMSAR.DMSREST2 and was running in ASID x'107' it can be stopped by:
P DMSAR.DMSREST2
Or:
P DMSAR,A=107
Or:
P DMSREST2,A=107
Or if there were only one DMSAR active in the system:
P DMSAR
The ASID can be determined from a MVS display active of the job, which can be done by issuing the command:
D A,jobname
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|