| View previous topic :: View next topic |
| Author |
Message |
ANDY
Beginner
Joined: 07 Feb 2004
Posts: 127
Topics: 67
|
 Posted: Sat Feb 21, 2004 6:28 pm Post subject: Why we submit JCL from COBOL or CICS ? |
 |
|
Hi :
Can someone tell me what's the reason we submit JCL from COBOL or CICS sometimes ?
Thanks
Andy |
|
| Back to top |
|
 |
shiv_swami
Beginner
Joined: 29 Nov 2003
Posts: 68
Topics: 14
|
| Posted: Sat Feb 21, 2004 6:50 pm Post subject: |
|
|
Andy,
Do a simple search for INTRDR in the SEARCH on this site ,..you would get most of the reasons why you required to submit jobs from COBOL program.
_________________
Regards,
Shivprakash |
|
| Back to top |
|
|
ANDY
Beginner
Joined: 07 Feb 2004
Posts: 127
Topics: 67
|
| Posted: Sat Feb 21, 2004 9:14 pm Post subject: |
|
|
Hi Shivprakash :
Thank you for your remind. But my question is why we do this way not how to do it, can you give me some ideas.
Thanks
Andy
_________________
cheers,
Andy |
|
| Back to top |
|
|
shiv_swami
Beginner
Joined: 29 Nov 2003
Posts: 68
Topics: 14
|
| Posted: Sun Feb 22, 2004 2:00 am Post subject: |
|
|
Andy,
Consider following situations.
1 You are preparing a database extract into a file and sending across the file to another server by FTP.The file name required is in the format 'DB_EXT_YYYYMMDD.DAT'.
To be able get the date every day in the file name,we must creat the FTP sysin cards everyday at runtime. This is where you can submit the jobs itself to FTP the file.
2. The other oftenly used option is to submit the jobs from frontend screens i.e. ADSO or CICS.Screens might be used to generate AD HOC reports.The screen would internally construct JCL bases on the screen input.The JCL will be submitted and report would be written to a file or printed to a printer given at the screen or default for a user.
_________________
Regards,
Shivprakash |
|
| Back to top |
|
|
ANDY
Beginner
Joined: 07 Feb 2004
Posts: 127
Topics: 67
|
| Posted: Mon Feb 23, 2004 12:45 am Post subject: |
|
|
Hi Shivprakash :
Thank you. It is helpful.
Regards,
Andy
_________________
cheers,
Andy |
|
| Back to top |
|
|
neilxt
Beginner
Joined: 01 Mar 2004
Posts: 23
Topics: 1
|
| Posted: Wed May 12, 2004 4:14 pm Post subject: |
|
|
| Quote: |
Hi :
Can someone tell me what's the reason we submit JCL from COBOL or CICS sometimes ?
Thanks
|
If you want to create dynamically variable JCL based on your input data perhaps.
For instance I had one project where print output options were selected by the customer and stored on a paramter file. Some customers were getting their own copies sent direct to their printers others required different numbers of copies.
The program created the print output on a PDS with each account as a different member then generated JCL to print it to the require output queue and required copies. |
|
| Back to top |
|
|
superk
Advanced
Joined: 19 Dec 2002
Posts: 684
Topics: 5
|
| Posted: Wed May 12, 2004 7:08 pm Post subject: |
|
|
| As an automation specialist and former QA Analyst, I cannot think of one good acceptable reason for any application to create or submit jobs, nor can I imagine any modern IT shop that would allow this practice to occur. |
|
| Back to top |
|
|
Dibakar
Advanced
Joined: 02 Dec 2002
Posts: 699
Topics: 63
Location: USA
|
| Posted: Thu May 13, 2004 12:30 am Post subject: |
|
|
| I don't have much exposure to CICS but I guess you need to fire a job if you wan't to print a report, or letter, etc. |
|
| Back to top |
|
|
Cogito-Ergo-Sum
Advanced
Joined: 15 Dec 2002
Posts: 637
Topics: 43
Location: Bengaluru, INDIA
|
| Posted: Thu May 13, 2004 3:06 am Post subject: |
|
|
| Quote: | | don't have much exposure to CICS but I guess you need to fire a job if you wan't to print a report, or letter, etc. |
Dibakar,
I have been there. With what I have seen, you might have two situations. One, where customer breathing down your neck and demanding the report NOW. In such a case, you would fill in some fields on a CICS screen and hit some PF key. Then, a TDQ (extra-?) would have be to be defined which would execute as soon as (with trigger level, maybe) TDQ is loaded.
Surely, Superk, the above requirement would justify dynamic submission of jobs? If it is a batch job creating jobs and then submitting them, I am against it too. A scheduler would be the best solution in this case.
The other case maybe, when the demand is not urgent. Just store 'triggers' somewhere in database. In the nightly process, you can have multiple jobs to scan the database, format/modify data and then put in a pretty format which would then be finally routed to a printer.
Personally, I do not like dynamic jobs too. The most irritating question that comes up is about restarting. How do I ensure correct restart if the submitted job abends (at a step that was executing a PROC  ) ? But, there are few situations, where it helps.
_________________
ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes. |
|
| Back to top |
|
|
mok
Beginner
Joined: 16 May 2003
Posts: 12
Topics: 0
Location: paris
|
| Posted: Thu May 13, 2004 1:45 pm Post subject: |
|
|
Hi all,
| Quote: |
nor can I imagine any modern IT shop that would allow this practice to occur.
|
I agree with you it is not a modern processing but I worked in Cameroon, in 2001 and they didn't have any scheduler so I automated all the production with INTRDR.
IF JOBA rc = 0 Then Submit JOBB and so on.
It was helpfull for us. The payroll batch ran during 5 days ! and after that pseudo automatization, 2 days were enough. |
|
| Back to top |
|
|
SureshKumar
Intermediate
Joined: 23 Jan 2003
Posts: 211
Topics: 21
|
| Posted: Fri May 14, 2004 10:13 am Post subject: |
|
|
Andy,
Just a practical experience, I use it in one of my applications. There is a necessity where in a transaction can request a Fax of a account information. Since we have to ftp the information to a fax server, we build a jcl dynamically and submit it. This is needed to keep the fax process to be asynchronous from the transaction. Thanks |
|
| Back to top |
|
|
slade
Intermediate
Joined: 07 Feb 2003
Posts: 266
Topics: 1
Location: Edison, NJ USA
|
| Posted: Sun May 16, 2004 1:01 pm Post subject: |
|
|
Hi Andy,
The use that I've most often come across is when a CICS transaction is asked to provide voluminous o/p on an ad hoc request. Rather than attempt to produce the report on local printers designed for low volume situations, a JOB is created to produce the o/p on a hi-vol printer.
Regards, Jack. |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
