Delete paging file from disk
Component: | BS2000 |
Functional area: | System control and optimization |
Domain: | SYSTEM-MANAGEMENT |
Privileges: | OPERATING |
Routing code: | R |
Function
System support can use the DELETE-PAGING-FILE command to delete the paging file on a magnetic disk or on any volume of an SF pubset.
When the paging file is deleted, the space it was occupying is overwritten with binary zeros.
Format
DELETE-PAGING-FILE |
Operands
VOLUME = *PUBSET(...)
Specifies one or more SD pubsets. The paging file is to be deleted on each volume of the specified SF pubsets.
PUBSET = list-poss(256): <cat-id 1..4>
Specifies the SF pubsets on which the paging files are to be deleted by their catalog ID.
VOLUME = list-poss(256): <vsn 1..6>
Identifies the disk from which the paging file is to be deleted by its volume serial number (VSN).
Up to 256 disks can be listed.
FORCE = *NO / *YES
Specifies whether the deletion of paging files on the home pubset or on volumes specified in the PAGING parameter service of the current system run should be forced. Other paging files are deleted irrespective of the specification made via the FORCE operand.
The default *NO causes the command to be rejected for the paging files mentioned above if the startup paging area is smaller than 200 MB.
FORCE = *YES
This setting should be selected only in exceptional circumstances.
Paging files on the home pubset or on volumes specified on the PAGING parameter service of the current system run are deleted irrespective of the minimum size of the paging area.
Return codes
(SC2) | SC1 | Maincode | Meaning/Guaranteed messages |
|---|---|---|---|
0 | CMD0001 | Command processing start without error | |
32 | EMM2800 | Internal error | |
64 | EMM2802 | The specified pubset is unkown and cannot be identified in the given configuration. | |
64 | EMM2805 | Possible errors:
Guaranteed messages: EMM2820, EMM2824, EMM2838 | |
128 | EMM2807 | Operation cannot be performed due to lack of resources |
When lists are specified, command processing is aborted in the event of an error with a return code of EMM2800 or EMM2807.
Notes
- The pubset the disk belongs to must have been imported.
- Processing of the command may take a number of minutes. For that reason it is not executed in the calling task, but is delegated to a server task created specially for the purpose. The job completion message is delivered to the calling task asynchronously. If the calling task terminates before the completion message is delivered, the message is sent to the console instead.
If more than one volume is specified (explicitly or by specifying a pubset) when the command is issued, a separate job is started for each volume.
The deletion of paging files on the home pubset or on volumes specified in the PAGING parameter service of the current system run is critical in those cases, where the total size of the startup paging area is below 200 MB. This can happen if, during ongoing operation, paging files that are not used during startup are added with the EXTEND-PAGING-AREA command and if other paging files are deleted.
If the startup paging area is smaller than 200 MB, system startup is only possible in DIALOG mode. The paging volumes have to be entered individually. To avoid this, the home pubset should have paging files of sufficient size (>200 MB) or, in the case of the PAGING parameter service, the volume specification in the parameter file should get changed to still existing paging files.
Example
Deleting the paging file from a disk with the volume serial number 2OSW.0:
/DELETE-PAGING-FILE VOLUME=2OSW.0