Start Archived Storage Mgmt (STRASMOND)

The Start Archived Storage Mgmt (STRASMOND) command starts the Archived Storage Management (ASM) process which manages the movement of data within the ASM defined levels. This function can be canceled with a controlled cancel option if enough time is allowed to end what it is currently processing.

STRASMOND requires that the job it runs in allow DB2 to be set into server mode. This is only a concern if the command is run interactively. If any SQL statements have been processed in the interactive job before STRASMOND is run, STRASMOND will fail with SQL errors. To avoid this problem either always submit STRASMOND to batch (the default) or signoff and sign back on before running STRASMOND interactively.

Parameters

Keyword	Description	Choices	Notes
POLICY	Policy	Character value	Optional, Positional 1
PROCESS	Process to run	ALL, MIGRATION, *EXPIRATION	Optional
INSTANCE	Instance	Name, QUSROND	Optional
SBMJOB	Submit to batch	YES, NO	Optional
JOBD	Job description	Qualified object name	Optional
	Qualifier 1: Job description	Name, QOND400
	Qualifier 2: Library	Name, QRDARS, LIBL, CURLIB

Top

Policy (POLICY)

Specifies the name of the policy that Archived Storage Management will perform the requested functions against.

Note: If you press the F4 key for this parameter while prompting the command, a list of all the valid entries is presented to you.

*ALL: All policies are used. This causes all eligible data to be managed.
policy-name: Specify the name of the policy that ASM is to process. This causes only the eligible data that is associated with the named policy to be managed.

Process to run (PROCESS)

Specifies if the Archived Storage Management (ASM) process does migration processing, expiration processing, or both. You may want to separate these functions if you are concerned with how long ASM processing takes.

*ALL: Both migration and expiration processing are done.
*MIGRATION: Only migration processing is done.
*EXPIRATION: Only expiration processing is done.

Instance (INSTANCE)

Specifies the name of the instance to use.

QUSROND: The default OnDemand instance is used.
instance-name: Specify the name of the instance that is to be used. By definition, the instance must be on the system that the command is run.

Submit to batch (SBMJOB)

Specifies if ASM should run in batch or interactively.

*YES: This command should be submitted to run in a different job.
*NO: This command should be run within the current job. If you are entering this command from a terminal, this will prevent you from doing any other work from this terminal session until this command completes.

Job description (JOBD)

Specifies the name of the job description used for the submitted job.

Qualifier 1: Job description

QOND400: The QOND400 job description is used as the job description for the submitted job.
name: Specify the name (name/name) of the job description used for the job.

Qualifier 2: Library

QRDARS: Library QRDARS is used as the job description's library.
*LIBL: All libraries in the job's library list are searched until the first match is found.
*CURLIB: The current library for the job is used to locate the job description name. If no library is specified as the current library for the job, QGPL is used.
name: Specify the name of the library where the job description name is located.

Examples

Example 1: Simple Example

STRASMOND

This command submits a job to batch that starts the OnDemand Common Server Archived Storage Management (ASM) process which manages the movement of data within the defined levels of archive media. When issued with no parameters specified, this command processes data for ALL defined storage management policies for the default QUSROND instance, and runs both migration and expiration processing.

Example 2: More Complex Example

STRASMOND POLICY(APDATAPOL) PROCESS(*MIGRATION)

This command is Similar to Example 1 but processes only data associated with the APDATAPOL policy definition and runs only migration processing.