jssitemstore (stores Items)
- Organization of this page
Description
This command stores the Items (registered in the Item management database) whose status is Close during the specified period, as stored Items in an active storage area in the Item storage database. The Items stored in the Item storage database can be viewed in windows in the same way as the Items registered in the Item management database. However, they cannot be edited or deleted. Also, the Items stored as stored Items in the Item storage database cannot be changed back to the managed Items stored in the Item management database.
Format
jssitemstore -ct start-date-end-date [-ch] [-q]
Required execution permission
Administrator permissions
Storage folder
JP1/SS-path\bin\
Arguments
-ct start-date-end-date
Specify the range for the registration dates with a character string in YYYY/MM/DD format in order to store the Items whose status is Close among the Items registered in the Item management database during the specified period. Connect start-date and end-date with a hyphen (-).
For start-date and end-date, you can specify values from 1970/01/01 to 2107/01/01. Specify the values so that start-date is earlier than end-date.
The following explains start-date and end-date:
- start-date
-
Stores the Items whose status is Close in the Item storage database among the Items registered after the date specified with this value. If the specified date is in the specified range but does not exist as a date, an error occurs.
- end-date
-
Stores the Items whose status is Close in the item storage database among the Items registered before the date specified with this value. If the specified date is in the specified range but does not exist as a date, an error occurs.
For example, if 2013/01/01-2013/12/31 is specified, the Items whose registration date is in the range from 2013/01/01 00:00:00(.000) to 2013/12/31 23:59:59(.999) can be stored in the Item storage database.
-ch
Checks whether the Items registered during the specified period can be stored in the Item storage database.
-q
Continues storing Items without displaying a confirmation message. If you do not specify the -q option, the system displays a message to ask whether to continue storing Items.
Return values
|
Return value |
Meaning |
|---|---|
|
0 |
Normal end |
|
1 |
Abnormal end |
Conditions for storing Items
When you store Items in the Item storage database, the Items whose status is Waiting to be deleted or is not Close among the Items registered during the specified period cannot be stored in the Item storage database. Also, in some cases, Items cannot be stored in the Item storage database depending on the status of the system or process work board in which the Items are registered. The following table describes the status of the Items and whether they can be stored in the item storage database.
|
No. |
Status of the system in which the Item is registered |
Status of the process work board in which the Item is registered |
State of the Item |
Status of the Item |
Whether the Item can be stored in the Item storage database |
|---|---|---|---|---|---|
|
1 |
Waiting to be deleted |
Waiting to be deleted |
-- |
-- |
N#1 |
|
2 |
Operating |
Waiting to be deleted |
-- |
-- |
N#1 |
|
3 |
In process |
-- |
-- |
N#2 |
|
|
4 |
Under suspension |
Waiting to be deleted |
-- |
N#1 |
|
|
5 |
-- |
Other than Close |
N#1 |
||
|
6 |
Other than Waiting to be deleted |
Close |
Y#3 |
||
|
7 |
Operating |
Waiting to be deleted |
-- |
N#1 |
|
|
8 |
-- |
Other than Close |
N#1 |
||
|
9 |
Other than Waiting to be deleted |
Close |
Y#3 |
- Legend:
-
Y: Stored in the Item storage database.
N: Not stored in the Item storage database.
--: Does not depend on the status.
- #1
-
The jssitemstore command terminates with an error.
- #2
-
The Item cannot be stored because it has not been registered.
- #3
-
The Item is stored in the Item database regardless of the editing status of the Item. If the Item is stored in the Item storage database, the Item will not be edited.
Prerequisites for executing the command
-
For details about the status of services when commands are executed, see Status of services when commands are executed in Chapter 12. Commands.
-
Before executing the jssitemstore command, set up the Item storage database. For details about how to set up the Item storage database, see 11.2.10 Setting up the Item storage database.
Remarks
-
Make a backup before the jssitemstore command is executed. For details about backup, see 11.2.13 Storing Items in the Item storage database.
-
The Items stored in the Item storage database cannot be moved back to the managed Items. Therefore, store the Items for which editing is completed. If you want to edit a stored Item, copy the relevant Item and create a new Item.
-
If the jssitemstore command is executed, the relevant Items are deleted from the Item management database, and free space of the Item management database is fragmented. For this reason, we recommend that you reorganize the Item management database. For details about how to reorganize the Item management database, see jssdbrorg.bat (reorganizes the Item management database) in Chapter 12. Commands.
-
When the jssitemstore command is executed, if error message KNAB24002-E (detailed code: -756) is output and the command terminates abnormally due to insufficient database capacity, expand the Item storage database, and then re-execute the command with the same arguments specified. If the Item storage database is expanded to the upper limit, rotate the storage areas of the Item storage database.
For details about how to expand the Item storage database, see 11.2.12 Expanding the Item storage database. For details about how to rotate the storage areas of the Item storage database, see 11.2.11 Rotating the storage locations in the Item storage database.
-
If the jssitemstore command fails, the history information and latest information of the failed Items are stored separately. Then, if the stored Items are deleted in a batch, only the history information might be deleted. If this happens, we recommend that you re-execute the jssitemstore command with the same arguments specified.
-
Execute the jssitemstore command and jssdbbackup.bat command without overlapping each other. If their execution overlaps, the command executed later terminates with an error.
-
If you use Ctrl+C to cancel the jssitemstore command while it is being executed, processing of the command might fail. For this reason, do not cancel the command during execution by using Ctrl+C.
-
While the jssitemstore command is executed, do not change the status of the Items to be stored and the status of the system or process work board in which the Items to be stored are registered. If you change an Item so that it cannot be stored, the command terminates with an error.
-
Do not operate the JP1/Service Support service while the jssitemstore command is being executed. If you happen to do so, command processing might fail.
-
Two or more jssitemstore commands cannot be executed at the same time.
-
You can output the result of executing the jssitemstore command to a log file and check the result. For details, see User log definition file (jp1itemstore.conf) in Chapter 13. Definition Files.
Examples
- Example 1
-
When you store the Items whose registration dates fall on 2013/01/01 to 2013/12/31 into the Item storage database:
jssitemstore -ct 2013/01/01-2013/12/31
- Example 2
-
When you check whether Items whose registration dates fall on 2013/01/01 to 2013/12/31 can be stored in the Item storage database:
jssitemstore -ct 2013/01/01-2013/12/31 -ch