please help me to put make 200 jobs in exec no by batch. if you have any sample batch please share and help me.
BTI format to update a job record setting it non-executable:
You will have to do the above for each job individually (the UPD line)
If you have the jobs listed in a pds, you could use REXX to automatically create your UPD statements. But you need to know some REXX programming or have someone that does. I use REXX in cases like this one. I hope this helps.
You can use database transportability to make changes to a mass of jobs.
I have used the CA-7 Batch interface to list the job or job range and then fed that into SAS to generate the BTI commands Marysue mentioned. I have some SAS programs that do various things like this. The key is to get all the information into a single record from which you can generate the commands. You can also use SYNCSORT to parse the output of the list command.
Here is the SYNCSORT control statements that will give you what you need(no programming needed). It takes the output from BTI - LJOB,JOB=XXXX*
JOB=XXXX* DATE=16.211 P
JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LA
NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DA
XXXXBAT1 005 XXXXBAT1 TEST 000 ALL *NONE* *NONE* 001 006 0380 162
XXXXBAT2 005 XXXXBAT2 TEST 000 ALL *NONE* *NONE* 001 011 0042 153
SYNCSORT CONTROL CARDS
//SYSIN DD *
INCLUDE COND=(33,3,CH,EQ,C'000') *INCLUDE RECS WITH 000 - COL 33
OUTFIL HEADER1=(1:'DBM',/,1:'JOB'),REMOVECC *PUT OUT DBM,JOB RECS 1ST
OUTREC FIELDS=(1:C'UPD,',2,8,C',EXEC=N',80:X) *PUT OUT UPDS
***************************** Top of Data
That worked great! Thanks.
One warning: Since //SORTOUT is FBA (even with REMOVECC specified, unfortunately), if you look at the output under SDSF, it appears the 1st character is missing.
Thanks Don for the feedback - Since you would need to feed a dataset into a CA7 BTI job to actually do the updates(EXEC=N), you wouldn't put SORTOUT to SYSOUT=*, you would specify the DCB for SORTOUT and RECFM=FB does not put a carriage control character so the warning wouldn't apply here.
I have some REXX code that will process a list of job names and uses the ADDRESS CA7 function to issue UPD,jobname commands for each entry in the job list. Settings in the REXX code specify the field name and value to be updated (e.g. "EXEC=N") and the dataset name containing the list of jobs to be processed.
Retrieving data ...