The Start Report Management Cycle (STRRMCRDAR) command starts the Report Management Cycle (RMC) which manages the movement of report data between disk and optical or tape. This function can be canceled with a controlled cancel option if enough time is allowed to end what it is currently processing.

Parameters

Keyword	Description	Choices	Notes
PROCESS	Process to run	*ALL, *MIGRATION, *EXPIRATION	Optional, Positional 1
RPTCOL	Report policy	Generic name, name, *ALL	Optional
LOGSTS	Log migration status	*NO, *YES	Optional
SNDFAILMSG	Send failure message	*NO, *YES	Optional
USER	User to send failure message	Name, QSYSOPR	Optional
SBMJOB	Submit to batch	*YES, *NO	Optional
JOBD	Job description	Qualified object name	Optional
	Qualifier 1: Job description	Name, QRDARS400
	Qualifier 2: Library	Name, *LIBL, *CURLIB

Top

Process to run (PROCESS)

Specifies if the Report Management Cycle (RMC) does migration processing, expiration processing, or both. You may want to separate these functions if you are concerned with how long RMC processing takes. Migration processing only looks at reports or indexes that are on DASD, while expiration processing looks at all reports and indexes. By separating these processes, you can run the expiration process less frequently than the migration process.

*ALL

Both migration and expiration processing is done.

*MIGRATION

Only migration processing is done.

*EXPIRATION

Only expiration processing is done.

Report policy (RPTCOL)

Specifies the name of the Report Policy to use when the Report Management Cycle is run.

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 report policies are used. This causes all eligible reports to be managed.

generic*-policy-name

Specify the generic name of the report policies that RMC should process.

policy-name

Specify the name of the report policy that RMC is to process. This causes only the eligible reports that specify the named policy to be managed.

Log migration status (LOGSTS)

Specifies if RMC should log the status of processes that it is performing.

*NO

Log only failures in the job log.

*YES

Log the start and the final status of each process performed in the job log.

Send failure message (SNDFAILMSG)

Specifies if RMC should send a message to notify someone that a migration failure has occurred during RMC processing. This message is only sent on the first failure during the run. Processing does not stop but continues on to the next report. If RMC needs to be ended because of this message, issue a controlled cancel on the RMC job allowing at least 30 minutes. This gives RMC time to finish the report it is migrating before it ends.

*NO

Do not send a message.

*YES

Send a message to the user named in the USER parameter when there is a migration or expiration failure.

User to send failure message (USER)

Specifies the user who should be notified when SNDFAILMSG is *YES.

QSYSOPR

Send the message to the system operator.

name

Specify the name of the user that should receive the message.

Submit to batch (SBMJOB)

Specifies if RMC 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

QRDARS400

The QRDARS400 job description is used as the job description for the submitted job.

name

Specify the name of the job description used for the job.

Qualifier 2: 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

STRRMCRDAR

This command submits a job to batch that starts the Report Management Cycle (RMC), which manages the movement of OnDemand Spool File Archive and AnyStore data between disk and optical or tape. This command example runs both migration and expiration processing for all report migration policies. It logs only failures in the job log and sends no failure messages to any message queues.

Example 2: More Complex Example

STRRMCRDAR PROCESS(*MIGRATION) LOGSTS(*YES) SNDFAILMSG(*YES)
             USER(QSYSOPR)

This command submits a job to batch that starts Report Management Cycle (RMC) migration processing only. No expiration processing will occur. Both successful and failure status messages will be written to the job log, and if any failure occurs, a failure message will be sent to the QSYSOPR message queue.

Error messages

None