Previous Topic

Next Topic

Book Contents

Book Index

Looking at history data

Each job as it progresses through the Schedule System, it makes a series of queue changes (e.g. `Ready to submit', `Completed', etc.). Each queue change is recorded in the historical data file.

To view historical data about a particular job use a command of the following format.

C:\> schedule type/history job_name

For example:

C:\> schedule type/history \demo.a\start/queue=(r,u)

\demo\a\start

December 4, 2002, 16:07 R Msg comp

December 4, 2002, 16:05 U Msg started

December 4, 2002, 16:03 U Msg started

December 4, 2002, 16:01 U Msg started

November 29, 2002, 11:28 R Msg comp

November 29, 2002, 11:26 U Msg started

November 29, 2002, 09:50 R Msg comp

November 29, 2002, 09:42 U Msg started

November 29, 2002, 09:41 U Msg started

November 27, 2002, 12:11 R Msg comp

November 27, 2002, 12:03 U Msg started

November 27, 2002, 09:22 R Msg comp

November 27, 2002, 09:08 U Msg started

November 27, 2002, 08:39 R Msg comp

C:\> schedule type/history \demo\a\start /full/queue=r

\demo\a\start

February 3, 2002, 10:44 R Msg comp 86. \DEMO\A\START (2026)

step:0 tag:"" param:""

node:MWS queue:MWSBATCH entry:133

strt:February 3, 2002, 10:41 Sts:00030001

CPU:3 Elps:134 IO:257 Flts:1877 Ppg:4733

February 3, 2002, 10:36 R Msg comp 89. \DEMO\ASTART (2025)

step:0 tag:"" param:""

node:MWS queue:MWSBATCH entry:127

strt:February 3, 2002, 10:34 Sts:00030001

CPU:3 Elps:136 IO:277 Flts:1822 Ppg:4733

January 30, 2002, 17:01 R Msg comp 695. \DEMO\A\START (1989)

step:0 tag:"" param:""

node:MWS queue:MWSBATCH entry:996

strt:January 30, 2002, 16:59 Sts:00030001

CPU:3 Elps:137 IO:272 Flts:1680 Ppg:4735

January 27, 2002, 11:51 R Msg comp 125. \DEMO\A\START (1957)

step:0 tag:"" param:""

node:MWS queue:MWSBATCH entry:666

strt:January 27, 2002, 11:48 Sts:00030001

CPU:3 Elps:149 IO:283 Flts:1691 Ppg:4731

The U (Job started event) and the R (Job completed event) are the most useful. All transistions are recorded and they can be used to identified exactly what order and at what time a certain event took place.

See Also

SCHEDULE command overview

Command mode vs. prompt mode

Creating a job

Creating a directory

Creating a calendar

Modifying jobs

Looking at jobs

Looking at calendars

Looking at directories

Monitoring activity

Other Schedule commands