|
View previous topic :: View next topic
|
| Author |
Message |
akhi007
New User
.jpg)
Joined: 30 Jan 2006
Posts: 35
Location: Richmond
|
|
|
|
hi,
Is there any way to get the details of the submitted job though Assembler.
I will explain in detail below.
I have one job, first step will be an assembler routine, next steps will be programs i need to run. Assembler routine should validate the job for jcl errors. Is it possible through assembler
Thanks,
@khi |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| ...Assembler routine should validate the job for jcl errors... |
certainly yes,
if You have the skill,
if You have the time
if Your organization provides You with the proper budget
... to rewrite the mvs/jes jcl components
please, please, please, please,
review Your understanding of job flow thru the system,
when Your steps start excuting all the jcl validation has been already made,
and,guess what? the jcl was error free! wonderful isn't it |
|
| Back to top |
|
|
akhi007
New User
Joined: 30 Jan 2006
Posts: 35
Location: Richmond
|
|
|
|
hi enrico,
without touching JES components, Is there any possibility?
I mean, when the assembler routine executes (first step of the job), it should verify the dataset errors and file allocations etc. Suppose, if output files already exists, it should delete it...
Is this possible? Simply saying, i need to get the all lines of job got submitted into assembler routine which is inside that job. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| it should verify the dataset errors and file allocations etc. Suppose, if output files already exists, it should delete it... |
if the procedure writing standards have been well defined there is no need to write such a tool
the general approach to procedure writing is...
- define the unit of work ( job, series of jobs )
- define the restartable unit ( job, series of jobs that can be resubmitted as is )
- define the preprocessing actions for each restartable unit
( for example to delete up all the new datasets allocation made by a previous run,
and iDCAMS delete will allways work, and it will not recall migrated datasets )
- define the postprocessing to be done
( for example take backups )
again... in a properly planned environment no need to write anything ,
apart good standards and directives |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
Have DD cards for all files in the first step with an IEFBR14 pgm. If any are missing, you'll get an error right away.
You could also include 2 DD cards for all the output files, one with (OLD,UNCATLG) and one with (OLD,DELETE) with the VOL=SER coded. This would handle clean up. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| I have one job, first step will be an assembler routine, next steps will be programs i need to run. Assembler routine should validate the job for jcl errors. |
A better investment (imho) would be to ensure all jcl is properly tested before being promoted to production.
If production jobs abend enough to justify even considering the creation of such a "tool", there are porbably major issues with the testing & turnover procedures. If (some of) these abends are due to files that may or may not exist at run-time, this can be provided for with proper design/implementaton and still not need this "safety valve". |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
This is a good example of fixing the results and ignoring the cause.
(fixing the symtoms without correcting the cause of the errors) |
|
| Back to top |
|
|
|
|
