Exporting the job list

When the JobList type is exported, an overview of the jobs and their results will be created.

The export can be produced either as a CSV or JSON file (see section Parameter file).

In addition to the keys described in the Parameter file section, the parameter file can also contain the following keys specifically for this export.

Key Value
Dir

Relative path of the part of the Project tree that you want to be exported.

  • If this key is empty (default value), the whole Project tree will be exported. (With the exception of the directories and components, to which the user carrying the export has no access to)
  • If this key is not empty, there has to be a backslash ("\) at the front of the entry.
  • It is also possible to enter the path of a component (with its name).

This key will be disregarded if a value is entered for "ComponentID".

IncludeAllComponents

Determines whether components are listed for which no jobs have been configured. This makes it possible, for example, to see at a glance whether two jobs have been set up for all Sinumerik components

The following values are possible:

  • Y: Components without jobs are listed
  • N: Components without jobs are not listed (Standard value)

Example call:

VDogAutoExport.exe "/rd:D:\vdClientArchive" "/CFile:D:\Test\exportJobList.ini"

Parameterdatei CiCoLog.ini:

[Common]
ReportType=JobList
ExportFile=D:\Test\myJobList.csv
Dir=\SmartShopFloor

[User]
Account=versiondog
Password={Password}

The following table provides an overview of the columns that appear in the resulting file:

Column

Description
Component Name of the component (including its path in the project tree)
ComponentID ID of the component (in GUID format)
ComponentTypeID ID of the component type (in the GUID format)
ComponentTypeName Name of the component type
JobID ID of the job (in GUID format)
JobName Name of the job
UploadClass Upload type of the Job
WhoToNotify List of users to be notified about the job execution
WhoToNotifyNames

Names of versiondog users to be notified about job executions

Multiple names are separated by commas.

This column is displayed only if sending emails about job executions is configured. For more information, see the tutorial AdminClient, section Jobs.

WhoToNotifyEMails

Email addresses of versiondog users who should be notified about job executions

Multiple email addresses are separated by commas.

This column is displayed only if sending emails about job executions is configured. For more information, see the tutorial AdminClient, section Jobs.

WhoToNotifyAdditional

Email addresses of users who do not have a versiondog account but should still be notified about job executions

Multiple email addresses are separated by commas.

This column is displayed only if sending emails about job executions is configured. For more information, see the tutorial AdminClient, section Jobs.

Execution

Execution status of the job

The following values are possible:

0: Not according to a schedule

1: According to a schedule

2: Using the versiondog BackupClient

IpOrComputername

IP address or computer name

The value is issued dependent on the upload class

UploadAgent

Computer name or IP address of Agent

This value is only issued when an upload agent is assigned to the job.

CompareAgent

Computer name or IP address of Agent

This value is only issued when an upload agent is assigned to the job.

LastCheck (local) Date of last planned job execution (local time)
LastCheck (UTC) Date of last planned job execution (UTC)
NextStart (local) Starting time of next planned job execution (local time)
NextStart (UTC) Starting time of next planned job execution (UTC)
JobStart (local) Actual start time of the last job execution (manual or scheduled) (local time)
JobStart (UTC) Actual start time of the last job execution (manual or scheduled) (UTC)
JobFinish (local)

End time of the last job execution (manual or scheduled) (local time)

JobFinish (UTC) End date of the last job execution (manual or planned) (UTC)
ResultVersionVsBackup

Result of the comparison between the version on the server and the version on the Backup.

A list of issued status codes and their descriptions can be found in the AdminClient tutorial under the section Job results.

ErrorVersionVsBackup The column contains only a value if an error has occured when comparing Server version <-> Backup.
WarningVersionVsBackup The column contains only a value if an error has occured when comparing Server version <-> Backup.
ResultBackupVsPreBackup

The result of the comparison between the current and previous backup.

A list of issued status codes and their descriptions can be found in the AdminClient tutorial under the section Job results.

WarningBackupVsPreBackup The column contains only a value if an error arose when comparing previous backup <-> backup.
ErrorBackupVsPreBackup The column contains only a value if an error arose when comparing the previous backup <-> backup.
DirBackup

The relative path of the directory in the server archive where the current backup of the job (file Backup.zip) was stored.

TimeStampBackup (local) Timestamp of the file Backup.zip (local time)
TimeStampBackup (UTC) Timestamp of the file Backup.zip (UTC)
DirPreBackup The relative path of the directory in the server archive where the previous backup of the job (file Backup.zip) was stored.
TimeStampBackup (local) Timestamp of the file Backup.zip of the previous backup (in UTC time)
TimeStampPreBackup (UTC) Timestamp of the file Backup.zip of the previous backup (UTC)

OutOfDate

Shows whether the period since the last backup is longer than the set value

The following values are possible:

Y: The backup is out of date

N: The backup is not out-of-date

?: The job has never been executed or no backup was yet created.

VersionVsBackupVersionNumber

Version number of the data that was used for the version/backup comparison

DeactivatedComment

Text entered when a job was deactivated