History data is viewed and managed using the following commands.

Command	Description
rmhist	delete history data
cathist	type out history data

A history record is generated for every scheduling queue transition. As a job leaves a queue, an entry is recorded. Each entry is marked with the letter of that queue.

Delete history information.

The DELETE command will delete entries out of the history file.

General Format

rmhist [-options] job_name

Alternate

delete -history [-options] job_name

option summary

Selection qualifiers:

-from (or since) = date
-to (or before) = date
-queue = letter [,letter]
-set_id = number (default = all)

General qualifiers:

-[no]log
-[no]confirm
-node = target_node

Examples

 
 
 
 Schedule> rmhist test -queue=b 
 
 
      

Options

-confirm

-noconfirm

CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.

-node=target_node

The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.

-from=date

The FROM option specifies that only those history entries that are dated after the specified date are to be deleted. The date specified can be either an absolute time or a combination time. The default date is the current time.

-log

-nolog

The LOG qualifier causes each completed operation to issue a note to the user.

-queue=letter [,letter]

The QUEUE option will select entries originating from the specified scheduling queue. The default is B, E, F, G, H, I, K, L, R. Enclose multiple queue letters in parentheses.

-set_id=number

The SET_ID option points to a designated job set. If no number is specified the default implies all job sets.

-to=date

The TO option specifies that only those history entries that are dated earlier the specified time are to be deleted. The date specified can be either an absolute time or a combination time. The default date is the current time.

Type a history file.

The TYPE command will type out the various list sections that can be associated with a history file.

General Format

cathist [-options] job_name

Alternate

type -history [-options]

option summary

Selection qualifiers:

-from (or since) = date
-to (or before) = date
-queue = letter [,letter]
-set_id = number (default = all)
-node = target_node

Column section qualifiers:

-full
-step
-job
-statistics
-log_date
-submit
-event

Examples

 
 
 
 Schedule> cathist test -job 
 
 /jlee/test 
 
    may 3, 2006, 10:56   r  msg comp     0. /jlee/default (0) 
    may 3, 2006, 10:54   r  msg comp     0. /jlee/default (0) 
    may 3, 2006, 10:54   r  msg comp     0. /jlee/default (0) 
    may 3, 2006, 10:53   v  msg failed   0. /jlee/default (0) 
 
 
      

Options

-node=target_node

The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.

-event

The EVENT option adds to the display the column of event data (the letter of the event queue and the very brief event description).

-from=date

The FROM option specifies that only those history entries that are dated after the specified date are to be displayed. The date specified can be either an absolute time or a combination time. The default date is the current time.

-full

The FULL option displays all the known attributes of a history file.

-job

The JOB option displays the job_name in the history file.

-log_date

The LOG_DATE option displays the date a job was logged in.

-queue=letter [,letter]

The QUEUE option will select entries originating from the specified scheduling queue. The default is B, E, F, G, H, I, K, L, R. Enclose multiple queue letters in parentheses.

-set_tag

The SET_TAG option adds to the display the column of set tag data.

-statistics

The STATISTICS option displays the various statistics of a job, including start time, I/O, elapsed time, etc..

-step

The STEP option adds to the display the column of step data.

-submit

The SUBMIT option displays the queue on which a job was submitted and the position in the queue.

-to=date

The TO option specifies that only those history entries that are dated earlier the specified time are to be displayed. The date specified can be either an absolute time or a combination time. The default date is the current time.

The scheduling queues can be viewed and managed using the following commands.

QUEUE command	Description
rmqueue	delete an entry from the queue
chque	modify an entry in the queue
monque	monitory queue state changes
catque	display queue entries

Each queue in the SCHEDULE System represents a scheduling state. Queues are identified by a single letter. Active jobs move between these states as they progress through the system. Generally they start at the top and go to the bottom (this varies depending on the job attributes).

Each entry in the scheduling queues has a unique index entry number.

The various queues are listed below:

1. COMPUTE NEXT START Any job that is to be examined to determine when it will start again is entered here. The next start time is computed and the job proceeds on.
2. WAIT FOR NEXT START TIME Any job that has a start time set is entered into this queue and stays here until the start time occurs.
3. INITIATE WITH NO SET ID Any job that has been initiated either manually or automatically that does NOT have a SET ID assigned is entered here. The job is assigned a number and then proceeds.
4. WORKGROUP MANAGER Workgroup processing is performed in this state. Node analysis and selection is performed. Only affects jobs that are part of a workgroup.
5. WAIT FOR LOCAL PREREQUISITE Any job that has prerequisites on the local system (or cluster) is entered into this queue. Once all the prerequisite jobs have successfully completed the job proceeds.
6. REQUEST REMOTE PREREQUISITE Any job that has a prerequisite specified that is on a remote node is entered here. A request is transmitted to the remote node and then the job proceeds.
7. WAIT FOR REMOTE PREREQUISITE Once a job has requested a completion event from a remote node it then waits in this queue until the event occurs. Once all responses have been received the job proceeds on.
8. WAIT FOR A REQUIRED FILE Any job that requires a file to be present is entered into this queue. Once the file has been created the job proceeds.
9. WAIT FOR DISK SPACE REQUIREMENTS Any job that requires a certain amount of disk space to be present before proceeding will stay in this queue until the space is available.
10. READY TO SUBMIT Once a job has met all the resource and other requirements it is entered into this queue. The job is then entered into a batch execution queue and the job proceeds.
11. SUBMITTED FOR EXECUTION Once the job has been submitted for execution an entry is made into this queue.
12. EXECUTION STARTED Once the job starts to execute an entry is made into this queue.
13. JOB COMPLETED When the job completes execution it is entered into this queue.
14. INITIATE DESCENDANTS JOBS On completion the initiate list of each job is examined. Any jobs that are to be activated are entered into the B queue.
15. SEND INITIATE REQUEST TO A REMOTE NODE Any remote initiate job request is placed into this queue. The request is then transmitted over to the remote node.
16. HOLDING PREVIOUS COMPLETIONS When a job completes it is entered into this queue. Entries are held in this queue to be used to satisfy future prerequisite requirements. After a short period typically 1 day the entries are removed.
17. EVENT MESSAGES Foreground processing signal messages are entered into this queue before dispatching them.
18. JOB COMPLETION MESSAGES Foreground job completion messages containing complete history information are entered into this queue before dispatching.
19. REMOTE COMPLETION MESSAGES Remote messages requesting information when a job has completed are kept in this queue until the job completes. At that time a message is sent back to the requesting node.

23. EVALUATING VARIABLES The job is currently evaluating variables and determining the course that the job group will go depending on the resource list, initiates, prerequisites, and end action list.

Type a queue.

The catque command will show the entries from the scheduling queues.

General Format

catque [-options] queue_letter

Alternate

type -queue [-options] queue_letter

where queue letters are A through S or "*"

option summary

/FAILED
-full
-all
-entry = number
-set_id = number
-env [=prefix_string,format](Prefix default = SQ)(Format default = "export %s = \" " %s \" "" (ksh) "setenv %s = \" " %s \" "" (csh))
-node = target_node

Examples

 
 
 
 Schedule> catque * 
 
 
 
  Scheduling queue A: Identify next start time 
  
 Scheduling queue B: Waiting for start time to occur 
 
 
  200. repeat_test (0)     Holding until November 21, 2001, 19:14 
  119. /a/start (0)       Holding until November 21, 2001, 20:21 
  191. /b/start_tree (0)  Holding until November 22, 2001, 10:00 
  138. named_day_test (0)  Holding until November 26, 2001, 08:15 
 
 
 Scheduling queue C: Initiated with NO set id. 
  
 Scheduling queue D: Initiated with a set id. 
 
  Scheduling queue E: Waiting for local prerequisites 
 
  
  144. /c/rcr1 (1230) 
          80. /c/rcr1_a (1230)   not completed 
          93. /c/rcr1_b (1230)   not completed 
          67. /c/rcr1_c (1230)   not completed 
  558. /a/finished (1232) 
         181. /a/report_3 (1232)   not completed 
 
 
 Scheduling queue F: Request remote completion codes 
  
 Scheduling queue G: Waiting for remote prerequisites 
  
 Scheduling queue H: Waiting for a required file 
 
  Scheduling queue I: Waiting for disk space requirements 
 
  Scheduling queue J: Ready to submit into execution queue 
 
  Scheduling queue K: Submitted for execution 
 
 
   80. /c/rcr1_a (1230) 
   93. /c/rcr1_b (1230) 
 
  Scheduling queue L: Execution started 
 
  181. /a/report_3 (1232) 
   70. repeat_test (1362) 
 
 
 Scheduling queue M: Job completed 
  
 Scheduling queue N: Initiate descendant jobs 
  
 Scheduling queue O: Send initiation to a remote node 
 
  Scheduling queue P: Holding previous completions 
 
 
  415. repeat_test (1348)     Completed on November 21, 2001, 03:15 
  168. /a/start (1349)        Completed on November 21, 2001, 04:24 
   62. /a/update_a (1349)     Completed on November 21, 2001, 04:28 
  120. /a/update_c (1349)     Completed on November 21, 2001, 04:28 
  117. /a/report_1 (1349)     Completed on November 21, 2001, 04:31 
  184. /a/summary_a (1349)    Completed on November 21, 2001, 04:32 
  186. /a/report_3 (1349)     Completed on November 21, 2001, 04:34 
  159. /a/report_2 (1349)     Completed on November 21, 2001, 04:34 
  185. /a/finished (1349)     Completed on November 21, 2001, 04:37 
 
 
 Scheduling queue Q: Event signals 
 
 Scheduling queue R: Job completion messages 
 
 Scheduling queue S: Remote completion requests 
 
      

 
 
 
 Schedule> catque -symbol -entry=121 -out=x.x 
 $ type x.x 
 
 
   SQ_ENTERED_ON = "28-FEB-2001 10:22:46.15" 
   SQ_ENTRY = "121" 
   SQ_INITIATED_ON = "28-FEB-2001 10:21:36.38" 
 
 
   SQ_NAME = "/demo/d/a1" 
 
 
   SQ_QUEUE = "P" 
   SQ_SET_ID = "2278" 
   SQ_SET_PARAMETER = "" 
   SQ_SET_TAG = "" 
   SQ_START_ON = "28-FEB-2001 10:22:38.63" 
   SQ_STATUS = "%X00030001" 
   SQ_STEP = "0" 
      

Options

-all

The ALL option displays all entries in a queue.

-node=target_node

The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.

-entry=number

The ENTRY option selects a particular entry in a scheduling queue.

-failed

The FAILED qualifier displays only jobs that have failed. Failed jobs may only be in the M, N, O or P. In most cases, this qualifier will result in listing failed jobs in the P queue.

-full

The FULL option displays all the known attributes of a queue.

-order

Lists the current jobs in queue order rather than the default set/name order.

-set_id=number

The SET_ID option points to a designated job set. If no number is specified the default implies all job sets.

-symbol[=prefix_string,format]

The SYMBOL option causes all output to be sent to the console or a file that can be used to define a set of environment variables. (Prefix default = SQ) (Format default = "export %s = \" %s" ""(ksh) "setenv %s = \" %s" "" (csh))

Modify a queue.

The rmque command will change an entry in a queue.

General Format

chque [-options] -entry = number

Alternate

modify -queue [-options] -entry = number

option summary

-[no]confirm
-[no]log
-node = target_node
-entry = entry_number

-step = number
-set_tag = "string"
-set_parameter = "string"
-set_id = number
-restart = number

-abort
-[no]hold

Examples

 
 
 
 Schedule> chque -entry=37 -set_id=2 
 
 
      

Options

-abort

The ABORT option indicates that the job is to be aborted immediately. If the job has started execution then it is terminated.

-confirm

-noconfirm

CONFIRM requests that the user be prompted prior to any operation to verify that the selected job is the correct one.

-node=target_node

The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.

-entry=number

The ENTRY option selects a particular entry in a scheduling queue.

-hold

-nohold

The HOLD and NOHOLD option s force an executing job to be suspended and resumed. If the job has not yet been submitted for execution then at submission time it is submitted as PENDING.

-log

-nolog

The LOG option causes each completed operation to issue a note to the user.

-restart=number

The RESTART option will modify the number of allowed restarts for the specified entry in the scheduling queues.

-set_id=number

The SET_ID option points to a designated job set. If no number is specified the default implies all job sets.

-set_parameter="string"

The SET_PARAMETER option specifies information to be passed from one job to another inside a set of jobs.

-set_tag="string"

The SET_TAG option also specifies information to be passed from one job to another inside a set of jobs.

-step=number

The STEP option will set the current step number into the queue entry. If the job fails and is restarted this step number can be used to start up the job in the correct place.