Change Policy Level Date (CHGPLDOND)
| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Change Policy Level Date (CHGPLDOND) command changes the next level date to the new date for objects that are at the named level in the named migration policy. Only objects in the specified date range are changed.
| Top |
Parameters
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| POLICY | Policy | Character value | Required, Positional 1 |
| OPTION | Processing option | *DATE, *RPTID | Optional |
| RPTID | Report ID | Character value | Optional |
| LEVEL | Level | Character value | Required, Positional 2 |
| NEWDATE | New date | Date, *CURRENT | Required, Positional 3 |
| LVLDATE | Level date range | Element list | Optional |
| Element 1: From date | Date, *BEGIN, *CURRENT | ||
| Element 2: To date | Date, *END, *CURRENT | ||
| INSTANCE | Instance | Name, *DFT | Optional |
| Top |
Policy (POLICY)
Specifies the migration policy that contains the level to change.
This is a required parameter.
Note: Position the cursor in the policy parameter entry and use the prompt (F4) key to view the list of policy values that are available for the default (*DFT) instance.
The default instance is specified in the QDFTINST data area. The QDFTINST data area can exist in multiple libraries. A search for the QDFTINST data area is performed using the library list. The first data area found will be used. If the QDFTINST data area is not found using the library list, the QUSRRDARS library will be searched for the data area. If the data area exists in the QUSRRDARS library it will be used. If the QDFTINST data area is not found, instance QUSROND is used.
- name
- Specify the name of the migration policy.
| Top |
Database files CCSID (OPTION)
Specifies the type of processing to perform.
- *DATE
- Documents within the specified date range are processed.
- *RPTID
- Documents with the specified report ID are processed.
| Top |
Report ID (RPTID)
Specifies the report ID of the report to be processed.
The report ID is also known as the load ID and can be found in the Content Manager OnDemand System Load folder or the System Log folder in the message text for message number 87, both generated when an input file is successfully loaded into the system. The report ID contains the value that Content Manager OnDemand generates to uniquely identify an input file, such as 5547-4-0-2FAA-20130313000000-20130313000000-5548. The report ID contains the following parts:
agid-pri_nid-sec_nid-docid-start_date-stop_date-aid
- agid
- Application group identifier.
- pri_nid
- Primary storage node.
- sec_nid
- Secondary storage node.
- docid
- Document identifier.
- start_date
- First date in the report. The format of the date is YYYYMMDDHHMMSS. Loads created with versions of Content Manager OnDemand prior to server version 9.0 use an older, internal date format for this part.
Note: If you do not know the start date, the value of this part can also be specified as 0.
- stop_date
- Last date in the report. The format of the date is YYYYMMDDHHMMSS. Loads created with versions of Content Manager OnDemand prior to server version 9.0 use an older, internal date format for this part.
Note: If you do not know the stop date, the value of this part can also be specified as 0.
- aid
- Application identifier. This part is optional.
| Top |
Level (LEVEL)
Specifies the level that contains the objects to change.
This is a required parameter.
- name
- Specify the name of the level.
| Top |
New date (NEWDATE)
Specifies the new date that objects can move from the level.
This is a required parameter.
- date
- Specify the new date in job date format. If date separator characters are specified, enclose the date value between single quotation marks.
| Top |
Level date range (LVLDATE)
Specifies the earliest and latest dates of the level that should be changed to the new date.
Element 1: From date
- *BEGIN
- Start with the earliest available date.
- *CURRENT
- Today's date is used.
- date
- Specifies the starting date in job date format. If date separator characters are specified, enclose the date value between single quotation marks.
Element 2: To date
- *END
- End with the latest available date.
- *CURRENT
- Today's date is used.
- date
- Specifies the ending date in job date format. If date separator characters are specified, enclose the date value between single quotation marks.
| Top |
Instance (INSTANCE)
Specifies the name of the OnDemand instance to use.
- *DFT
- The default OnDemand instance is used. The default instance is specified in the QDFTINST data area. The QDFTINST data area can exist in multiple libraries. A search for the QDFTINST data area is performed using the library list. The first data area found will be used. If the QDFTINST data area is not found using the library list, the QUSRRDARS library will be searched for the data area. If the data area exists in the QUSRRDARS library it will be used. If the QDFTINST data area is not found, instance QUSROND is used.
- instance-name
- Specify the name of the instance that is to be used. By definition, the instance must be on the system where the command is run.
| Top |
Examples
Example 1: Changing Next Level Date for Level OPT
CHGPLDOND POLICY(TESTPOLICY) LEVEL(OPT) NEWDATE(*CURRENT)
This command will change the next level date of all objects in the migration policy named TESTPOLICY at level OPT for the default instance to today's date, allowing them to move to the next level the next time the Start Archived Storage Management (STRASMOND) command is run.
Example 2: Changing Next Level Date with Date Range
CHGPLDOND POLICY(TESTPOLICY) LEVEL(OPT) NEWDATE(*CURRENT)
LVLDATE(*BEGIN '05/10/07') INSTANCE(TEST)
This command will change the next level date of those objects in the migration policy TESTPOLICY at level OPT for the instance TEST that have a date less than or equal to 05/10/07. The date for those objects will be changed to today's date.
| Top |
| Top |