关于在tws 后台修改job 的试验:
Step1:
su - mdm
composer
先list 一下job:
-list job=time001
Workstation Job Definition Name Updated On Locked By
---------------- ---------------------------------------- ---------- ----------------
WEN TIME001 08/26/2009 -
AWSBIA291I Total objects: 1
-
在列一下详细:
-display job=time001
Workstation Job Definition Name Updated On Locked By
---------------- ---------------------------------------- ---------- ----------------
WEN TIME001 08/26/2009 -
WEN#TIME001
DOCOMMAND "cp -p /opt/IBM/test.data /opt/"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
AWSBIA291I Total objects: 1
Step3:
先产生一个文件:
-cr file01.txt from job=@#time00?
AWSBIA289I Total objects extracted: 5
上面@#time00? 表示文件: file01.txt 中包含了: 以time00开头的所有的job.
下面来看一下:
su - mdm
ls -l *.txt
-rw-rw-r-- 1 mdm mdm 908 Oct 1 14:46 file01.txt
看到就在默认路径下面生成了刚才的文件。
看一下文件:
[mdm@wen ~]$ more file01.txt
$JOBS
WEN#TIME001
DOCOMMAND "cp -p /opt/IBM/test.data /opt/"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
WEN#TIME002
DOCOMMAND "cp -p /opt/IBM/test.data /opt/"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
WEN#TIME003
DOCOMMAND "cp -p /opt/IBM/test.data /opt/"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
WEN#TIME004
SCRIPTNAME "/opt/IBM/TT/find.sh p"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
WEN#TIME005
SCRIPTNAME "/opt/IBM/TT/test.sh"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
-----------------
下面我进行修改操作:
su - mdm
composer
-edit file01.txt
WEN#TIME001
DOCOMMAND "cp -p /opt/IBM/test.data /tmp/data/"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
把job的script 修改了一下。
修改好以后: ":wq!" 保存。
-add file01.txt
在这个时候,系统会提醒已经有 WEN#TIME001 :
AWSJCL015W The object "jd=WEN#TIME001" already exists.
AWSJCL016I Do you want to replace the object (enter "y" for yes, "n" for no)?
y
AWSJCL003I The command "update" relating to object "jd=WEN#TIME001" has completed successfully.
这时,我们看一下系统里的job details:
-display job=time001
Workstation Job Definition Name Updated On Locked By
---------------- ---------------------------------------- ---------- ----------------
WEN TIME001 10/01/2012 -
WEN#TIME001
DOCOMMAND "cp -p /opt/IBM/test.data /tmp/data/"
STREAMLOGON root
DESCRIPTION "this job is test for the scheduel testing"
TASKTYPE UNIX
RCCONDSUCC "RC = 0"
RECOVERY STOP
AWSBIA291I Total objects: 1
-exit
但是系统中没有体现:
我进入图形化界面:
refresh "All schedule jobs".
发现: job=time001 还没有改变:
后来发现原因,是原来的job schedule 没有提交到系统中:
-----------
好,下面进入命令界面:
-exit
[mdm@wen ~]$ conman
提交一下刚才的shedule:
%sbs sched=wen#time
Submitted WEN#TIME to batchman as WEN#TIME[(1515 10/01/12),(0AAAAAAAAAAAAD65)]
上面的sbs 是: submit schedule 的意思。
提交后,我就在图形化界面中看到,我要的脚本了。
-----------
提醒一下,一般要修改的话,是要统一修改一个jobstream 中的job,
可以用下面的command:
su - mdm
composer
-cr file.txt from s=@#jobstream_name
然后再edit.
呵呵,今天收获很大,很高兴。