This option changes the amount of time that program execution history, window title update history, and other history information is retained. Specify this option to use the task to acquire program execution history and window title update history on a regular basis.

• Program execution history
  -s PDAYS=(history-information-retention-time)
  
• Window title update history
  -s WDAYS=(history-information-retention-time)
  Specify the history information retention time in units of days, in the range 0 to 1,000. If 0 is specified, history information is always deleted (never retained). If 9,999 is specified, history information is saved indefinitely (never deleted).
  If nothing is specified, history information is deleted when it becomes 32 days old.
  

Specification example

In this specification example, program execution history and window title update history that are more than 11 days old are deleted.

"C:\jp1asset\exe\jamscript.exe"

-f "C:\jp1asset\scriptbatch\TakeClientOperation.txt"

-s PDAYS=10 -s WDAYS=10

Here, C:\jp1asset refers to the Asset Information Manager installation folder.

This option collects information for a particular period of time. Specify this option to output a list of software names and file versions (ClientOperationList.txt) or to collect program execution history and window title update history for a specific time period.

If both the start and end dates are omitted, program execution history and window title update history are acquired for the period since the date when program execution history and window title update history were previously acquired (date in the modification date of SD operation history of the asset information). For a new device (no value is specified for the modification date of SD operation history), program execution history and window title update history are acquired, beginning with those with the oldest date.

Start date

Program execution history and window title update history are acquired, beginning with those with the specified date.

The start date is specified in the format -s STARTDATE=yyyymmdd. If this option is omitted, program execution history and window title update history are acquired, beginning with those with the oldest date.

End date

Program execution history and window title update history are acquired, beginning with those older than the specified date.

The end date is specified in the format -s ENDDATE=yyyymmdd. If this option is omitted, program execution history and window title update history are acquired, up to those with the latest date.

Program execution history and window title update history, including the content of the backup files (files in the operation history save directory), are collected. Specify this option to collect all program execution history and window title update history, such as when collecting new history, when changing the filtering definition file for the program execution history and window title update history, and when collecting program execution history and window title update history by specifying a specific time period.

Specify collection from files in the operation history save directory in the format -s BACKUP=YES. If this option is omitted, program execution history and window title update history are not collected from the files in the operation history save directory.

This option specifies devices for which information is to be collected. Specify this option to output a list of software names and file versions (ClientOperationList.txt) or to collect program execution history and window title update history for specific devices.

Specify the devices for which information is to be collected in the format -s ASSETNO=(asset-number). However, devices that are not registered devices in the JP1/Software Distribution inventory information (devices for which there is no Assignment key value for the asset information) are not included.

This option outputs the execution file name and the software version to the ClientOperationList.txt file. Using the content that is output to the file, you can define a program that collects (or does not collect) program execution history and window title update history in the filtering definition file (ClientOperation.ini) for program execution history and window title update history.

When this option is specified, program execution history and window title update history are not collected in the asset management database.

Specify in the format -s MAKELIST=YES. When this option is specified, the assets to be collected must be specified.

The execution results are output to Asset-Information-Manager-installation-folder\sample.

Specification example

In this specification example, program execution history and window title update history for dates between April 1 and 30, 2005 are collected.

"C:\jp1asset\exe\jamscript.exe"

-f "C:\jp1asset\scriptbatch\TakeClientOperation.txt"

-s STARTDATE=20050401 -s ENDDATE=20050430

Here, C:\jp1asset refers the Asset Information Manager installation folder.

Note

When using the Take operation history task, set the task schedule by taking into consideration the use of the software operation monitoring history of JP1/Software Distribution. For details about how to set a schedule, see 5.9.2(2) Changing a task schedule.

Most importantly, set the task execution interval so that the threshold size beyond which the collected data is deleted or the maximum size of program execution history and window title update history accumulated in one day will not be exceeded.

For details about the threshold size beyond which the collected data is deleted and the maximum size of program execution history and window title update history accumulated in one day, see the description related to software operation monitoring in the manual Job Management Partner 1/Software Distribution Administrator's Guide Volume 1, for Windows systems.

If the program execution history and window title update history to be collected have been moved to a save directory, it may not be possible to collect this information. In this case, execute the task after specifying options such as the start and end dates for the program execution history and the window title update history to be acquired and collection of from files in the operation history backup folder.

When you collect operation history from JP1/Software Distribution, you can define filtering of the information collected from the operation history.

Specify collection of only the operation history information that you want Asset Information Manager to manage (among all the JP1/Software Distribution operation history information).

To collect only the information you wish to manage using Asset Information Manager from the program execution history and window title update history, you define the content to be collected or not to be collected in the definition file for filtering (ClientOperation.ini) the program execution history and window title update history.

The storage destination and the coding method for the definition file for filtering the program execution history and window title update history are described below.

• Storage destination for the definition file for filtering the program execution history and window title update history
  Asset-Information-Manager-installation-folder\env
  
  
• Coding method for the definition file for filtering the program execution history and window title update history
  

  ; ; Filter ; [Option] Program=NOTCOLLECT Window=COLLECT WindowType=ACTIVE,CAPTION [Program] a=AAAA.exe, 0001 a=BBBB.exe, 0001 [Window] a=CCCC.exe, 0001 a=DDDD.exe, 0001

  [Option]

  Specifies whether to collect the program execution history and the window title update history.

  Specify program execution history in the format Program=(collection-type).

  Specify window title update history in the format Window=(collection-type).

  Specify one of the following as the collection type:

  COLLECT: Collect the history of the specified files

  NOTCOLLECT: Do not collect the history of the specified files

  IGNORE: Do not collect histories

  Also, specify the type of window title update history information to be collected, in the format WindowType=(event-type).

  Specify one of the following as the event type:

  ACTIVE: Collect a log of switches to an active window

  CAPTION: Collect a log of character strings displayed in window titles

  To collect both, specify both separated by a comma. The collection order will be the same as the order of specification.

  If the format is invalid, processing terminates with an error.

  [Program]

  Specify the file name and file version of software programs for which program execution history is to be collected (or not collected), in the format a=(file-name),(version). The version can be omitted, in which case you must also omit the separator comma.

  [Window]

  Specify the file name and file version of software programs for which window title update history is to be collected (or not collected), in the format a=(file-name),(version). The version can be omitted, in which case you must also omit the separator comma.

• Specification example when the program and window title update history are to be acquired from all managed clients
  To acquire the program and window title update history from all managed clients, specify the filtering definition file as follows:
  

  ; ; Filter ; [Option] Program=NOTCOLLECT Window=NOTCOLLECT [Program] [Window]

(a) Extracting the software name and version

Filtering definitions can be made more efficient by extracting and using the software name and version specified in [Program] and [Window] from the operation history of a specific device.

To extract the software name and file version that are specified in the filtering definition file for the program execution and window title update history, specify TakeClientOperation.txt. Then, a user with administrator permissions must execute the jamscript (access definition file execution) command.

For details about the options you can specify for execution of the jamscript command, see 5.9.8 Specifying the operation history acquisition range and filtering. For details about the jamscript command, see online Help for Job Management Partner 1/Asset Information Manager - Creating an Access Definition File (assetscr.chm).

By starting and stopping programs for which operation history is collected (or not collected), collecting the operation history, and then specifying the asset number of the PC executing the operation, you can output the contents of the definition file for filtering operation history that you want to set.

The PC with the specified asset number must satisfy the following conditions:

• JP1/Software Distribution Client 07-50 or later must be installed
• JP1/Software Distribution Manager must have already collected operation history

The list of software names and file versions (ClientOperationList.txt) is output to Asset-Information-Manager-installation-folder\sample.

(b) Re-collecting operation history after the definition contents have been changed

To re-collect past operation history by changing the definition of the operation history filtering definition file, specify the start date option and the option to collect operation history from files in the operation history save directory.

Execution example

Shown below is an execution example for the period from April 1 through April 10, 2005, in which the names of programs collected as the operation history of asset number 000001 are output to a file:

jamscript -f "C:\tmp\TakeClientOperation.txt"

-s STARTDATE=20050401 -s ENDDATE=20050410

-s ASSETNO=000001 -s MAKELIST=YES