|
View previous topic :: View next topic
|
| Author |
Message |
mrright
New User
Joined: 07 Jan 2004
Posts: 4
|
|
|
|
| Can anyone help me to trap the error efficiently while running a cobol program in batch? |
|
| Back to top |
|
 |
mmwife
Super Moderator
Joined: 30 May 2003
Posts: 1592
|
|
|
|
Hi Mrr,
Not sure I get your drift. What do you intend to do when you "trap??" it? Where do you want to trap it? When do you want to trap it?
Regards, Jack. |
|
| Back to top |
|
|
karpagam
New User
Joined: 14 Feb 2004
Posts: 1
|
|
|
|
| mrright wrote: |
| can anyone help me to trap the error efficiently while running a cobol prg running thru jcl |
U can use sysprint statement within the jcl top trap the error effectively from the spool area.
From
N Karpagam |
|
| Back to top |
|
|
veenag_gopal
New User
Joined: 14 Nov 2005
Posts: 14
Location: India
|
|
|
|
| if it is a logical error use sysprint and try to see the sysout.it will give file related errors. |
|
| Back to top |
|
|
priyamnavada
New User
Joined: 24 Dec 2005
Posts: 52
Location: hyderabad
|
|
|
|
| Xpedit the COBOL program, you can trap errors easily. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If you post what problem you are having, we can offer suggestions.
Are you trying to trap errors in an existing production program or a program that is in test? |
|
| Back to top |
|
|
|
|
