Summary
This procedure documents one method to extract schedule data from DPX. This data is only needed when an administrator wants to make a visual check of scheduled jobs and/or keep a record of what their current job schedule looks like. Note: The syncui utility should only be used under the direction of technical support; in this case, specifically to spot-check the list of scheduled jobs prior to master server maintenance.
Resolution
Dumping the schedule in this way does not give all of the details of your scheduled environment, any exceptions, holidays, etc. will not appear in the output. This procedure simply dumps out what DPX has scheduled for a given range of time. This information is generally useful for reviewing your expected schedule.
You will need to invoke a command line on your master server to run the 'syncui' program. If you are unfamiliar with this please refer to Setting Up an Interactive Command Line Interface for SYNCUI.
Once you have the appropriate command line interface set up, run the following command:
syncui
The syncui program will start and wait for interactive input. You will need to know the master server host name or IP address. Replace MSERVER below with the master server host name or IP address. The schedule list requires a date range. This is represented by two groups of yyyy mm dd which represent the start and end dates in 4-digit year, 2-digit month, and 2-digit day format. Enter the following syncui commands:
c s MSERVER sssched
sched list yyyy mm dd yyyy mm dd
quit
By way of example, if the master server name is "DPX32ms" and you are interested in displaying the schedule for Sept 1st 2010 through Sept 10th 2010, you would use the following command sequence:
syncui
c s DPX32ms sssched
sched list 2010 09 01 2010 09 10
quit
For larger enterprises, you may want to directly send the 'sched list' output to a file for review. You can use the -f parameter followed immediately by a file name (no space before) to capture this. So given the example above, if you needed to capture this to a file you can use:
sched list -fschedule.txt 2010 09 01 2010 09 10
Output will print to the screen, and it will also be saved to a file called 'schedule.txt'.
Example output is shown below:
--------------------------------------------------------------------------------
SID JOB NAME MM/DD HH:MM RET SUBTYPE STATUS MM/DD HH:MM JOBID
--------------------------------------------------------------------------------
0 migtest2-BASE 09/01 13:00 7 0 WAITING
0 migtest-BASE 09/01 14:00 7 0 WAITING
0 6mo_job-INCR 09/01 17:38 45 0 WAITING
0 migtest2-BASE 09/02 13:00 7 0 WAITING
0 migtest-BASE 09/02 14:00 7 0 WAITING
0 6mo_job-INCR 09/02 17:38 45 0 WAITING
0 migtest2-BASE 09/03 13:00 7 0 WAITING
0 migtest-BASE 09/03 14:00 7 0 WAITING
0 6mo_job-INCR 09/03 17:38 45 0 WAITING
0 migtest2-BASE 09/04 13:00 7 0 WAITING
0 migtest-BASE 09/04 14:00 7 0 WAITING
0 migtest2-BASE 09/05 13:00 7 0 WAITING
0 migtest-BASE 09/05 14:00 7 0 WAITING
0 6mo_job-BASE 09/05 17:37 45 0 WAITING
0 migtest2-BASE 09/06 13:00 7 0 WAITING
0 migtest-BASE 09/06 14:00 7 0 WAITING
0 6mo_job-INCR 09/06 17:39 45 0 WAITING
0 migtest2-BASE 09/07 13:00 7 0 WAITING
0 migtest-BASE 09/07 14:00 7 0 WAITING
0 6mo_job-INCR 09/07 17:39 45 0 WAITING
0 migtest2-BASE 09/08 13:00 7 0 WAITING
0 migtest-BASE 09/08 14:00 7 0 WAITING
0 6mo_job-INCR 09/08 17:39 45 0 WAITING
0 migtest2-BASE 09/09 13:00 7 0 WAITING
0 migtest-BASE 09/09 14:00 7 0 WAITING
0 6mo_job-INCR 09/09 17:39 45 0 WAITING
0 migtest2-BASE 09/10 13:00 7 0 WAITING
0 migtest-BASE 09/10 14:00 7 0 WAITING
0 6mo_job-INCR 09/10 17:39 45 0 WAITING