Instruction for TWS (Tivoli workload Schedule)
1: what is a TWS job ?
At its simplest ,a TWS job is simplly the name of a script or command to be executed ,almost anything that can be run from the Unix or Windows sever can be run as a TWS job.
In order for the TWS schedule to create a TWS job they will need to know the name of the server where the scripts runs ,the name of the scripts (including the full path) and the user to run it as. This must be the user who has the correct envronment to run the script and the permission s to execute the scripts.
2: What is a TWS job stream?
A TWS job stream is a collection of TWS jobs that have somthing in common. There may be many job streams, For example,a Daily job stream, a weekly job stream and a monthly job stream. There will be normally job dependecies between jobs in a job stream. for example: the first job must complete (successfully) before the second job start ro run. if it ends in failure the second job will NOT run ,job steams have rules to say when they must run.
In order for the TWS schedule to create a TWS job stream they will need to know the name of the jobs( which should be previously defined ). the order and the dependencies of the jobs and the dates and times they must run. it is same for the jobs to be executed in different job streams.
3 :Return Codes:
TWS uses the return code from the script or command to determine whether that script was successful. Usually ,the return code "0" means that the script was successful and anything else means the script failed.
As stated earier TWS use the return code from a script to determine whether that script was successful.
It is possible to assign a return code to each individual job starting what return codes should be considered as a success. for instance if a job issues a command to delete a file and that file is not avaliable or present then it will generate a non-zero return code, Since this may be not a really a problem , it is possible to inform TWS to stil consider the jobs run successful and to continue to schedule any other jobs to run.
4: conditional processing:
TWS can not use a return code of a job, to make decisions on job procession ,There is no if/else functionality .if a job succeds then dependant job will continue to run, if a job abended, the dependent job will not run.
TWS have a "recovery" function. it permits some actions to be predefined for when a job bended. The standard is :STOP, in this case ,the dependect job will not run , This may be idified to "CONTINUE" , even if the job abends ,the dependent job will continue to run , The third option is "Rerun" in this case, the dependecy job will automaticlly rerun itself once. if it is successful this time the dependency job continue as nomal. if it abends again the dependent job will stop run. Note that a job will nly run itself once.
At its simplest ,a TWS job is simplly the name of a script or command to be executed ,almost anything that can be run from the Unix or Windows sever can be run as a TWS job.
In order for the TWS schedule to create a TWS job they will need to know the name of the server where the scripts runs ,the name of the scripts (including the full path) and the user to run it as. This must be the user who has the correct envronment to run the script and the permission s to execute the scripts.
2: What is a TWS job stream?
A TWS job stream is a collection of TWS jobs that have somthing in common. There may be many job streams, For example,a Daily job stream, a weekly job stream and a monthly job stream. There will be normally job dependecies between jobs in a job stream. for example: the first job must complete (successfully) before the second job start ro run. if it ends in failure the second job will NOT run ,job steams have rules to say when they must run.
In order for the TWS schedule to create a TWS job stream they will need to know the name of the jobs( which should be previously defined ). the order and the dependencies of the jobs and the dates and times they must run. it is same for the jobs to be executed in different job streams.
3 :Return Codes:
TWS uses the return code from the script or command to determine whether that script was successful. Usually ,the return code "0" means that the script was successful and anything else means the script failed.
As stated earier TWS use the return code from a script to determine whether that script was successful.
It is possible to assign a return code to each individual job starting what return codes should be considered as a success. for instance if a job issues a command to delete a file and that file is not avaliable or present then it will generate a non-zero return code, Since this may be not a really a problem , it is possible to inform TWS to stil consider the jobs run successful and to continue to schedule any other jobs to run.
4: conditional processing:
TWS can not use a return code of a job, to make decisions on job procession ,There is no if/else functionality .if a job succeds then dependant job will continue to run, if a job abended, the dependent job will not run.
TWS have a "recovery" function. it permits some actions to be predefined for when a job bended. The standard is :STOP, in this case ,the dependect job will not run , This may be idified to "CONTINUE" , even if the job abends ,the dependent job will continue to run , The third option is "Rerun" in this case, the dependecy job will automaticlly rerun itself once. if it is successful this time the dependency job continue as nomal. if it abends again the dependent job will stop run. Note that a job will nly run itself once.