To schedule a job use kitchen and to schedule a transformation use pan. The executable pan.bat and kitchen.bat (resp. pan.sh and kitchen.bat for linux) were shipped with your PDI and sits in the same directory as your spoon.bat (resp. spoon.sh).
Write a new mySchedule.bat file (resp a .sh on linux) with one instruction:
pdi-path\pan.bat /file=myPath\myTransfo.ktr /log=pdi-path\logs\myTransfo.log
or
pdi-path\kitchen.sh /file=myPath\myJob.kjb /log=pdi-path\logs\myTransfo.log
In the above pdi-path is the folder containing your spoon.bat, which also contains pan.bat and a sub-folder called logs where pan will write the logs. Care also that myPath\myTransfo.ktr is the absolute path to be executed.
You can check the above if typing in a commad line window: absolute-path\mySchedule.bat (mind the path of your bat file). If you do not see anything, it is normal: the logs are written
in the log file. You can nevertheless follow the progression of the
transformation from sql-server and type (or edit) the log file when
the run is finished.
Then open the Windows Task Scheduler, select the cycle, and when it comes to define the action, put the absolute path of your mySchedule.bat.
Check (and clean) the logs for a week or so. By that time you'll have certainly learned how to include a date in the log file name.
I also recommend to enable the logging on the transformation, which will give you the number of input/output lines and other precious information. To know how to do that, ask an other question.