Bill,

this is Just what I needed.

thank you

Bill,

if you are interested this is what I am doing with that. I have a PowerShell script that build a csv file and automatically generates the dates I need this to run  based off of separation from the second Tuesday each month.

The  CSV Looks like this.

BATCH_JOB_NAME,BATCH_JOB_GROUP,COMMIT_DATE,COMMIT_TIME

batchjobname,/batch/job/path,2016-01-15,22:00:00

here is the NSH.

#!/bin/nsh

HOST=
INPUT_CSV=

# Process the command line
while getopts :h:i: Option
do
       case $Option in
              h) HOST=$OPTARG;;
              i) INPUT_CSV=$OPTARG;;
              \?) echo "Incorrect command line option."
                     exit 1;;
       esac
done

assert ()
{
  if test $1 -eq 11 ; then
       return 0
  elif test $1 -ne 0 ; then
    echo "####### ERROR: $2; RC=$1" >&2
    exit 1
  fi
}

# Check INPUT_CSV exists
if [ ! -f $INPUT_CSV ];then
  echo "Input CSV [$INPUT_CSV] not found."
  exit 1
fi

INPUT_CSV_NUM_LINES=`cat $INPUT_CSV | wc -l`
LINE_CNT=2

while [ $LINE_CNT -le $INPUT_CSV_NUM_LINES ]
do
input_csv_line=`sed -n "${LINE_CNT}p" $INPUT_CSV`

BATCHJOB=`echo $input_csv_line | cut -f1 -d,`
BATCHGROUP=`echo $input_csv_line | cut -f2 -d,`

# Get the Batch Job DBKey using the above information. 
BATCHJOB_DBKEY=`blcli_execute BatchJob getDBKeyByGroupAndName "${BATCHGROUP}" "${BATCHJOB}"`

# Set the job schedule

DATE_STRING="2016-01-01 23:35:00"

BATCHJOB_KEY=`blcli_execute Job addOneTimeSchedule "${BATCHJOB_DBKEY}" "${DATE_STRING}"`

LINE_CNT=`expr $LINE_CNT + 1`
done

I have around 30 batch jobs that I need to set schedules on. I use a powershell script to generate a csv file that has the name and path to the jobs. Then it calculates the cate based on patch Tuesday + xx days. Once the csv file has been created I can run the nsh script to set the schedule on all 30 jobs. Doing it this way takes 2-3 mintues vs and hour or so to set them manaually.

I use the same process to set the schedules on all of my windows patch jobs.

Bill,

Thanks. No these jobs are not time critical. I will normally set the schedules a week or so ahead of time. They need to run once a month. Just trying to avoid the tedious task of setting 30 schedules manually, along with the possibility of getting a date \ time wrong on one.

Martin Gomez

Lead Systems Administrator

816 435-6067

816 564-8876 (cell)

Bill,

Another thing worth noting. When the job runs and the format of the time is not correct. The target job executes NOW, instead of the set schedule just failing. I corrected my PowerShell script to ensure the time was 04:00:00 and it works as expected.