MVSFORUMS.com

[vak255]

I have this query from longtime in mind.
whenever an abend occurs in production, all I do is recreate the abend in test region and resolve using the DDIO file and Abend Aid but this takes lot of time. This I usually follow for Bad data.
If the job abends for more SPACE then I am lucky. otherwise I have to follow the above process frequently.

The problem I face is that I could not test it in production as I could not transmit the DDIO file from Test region to production.

I feel I am missing something, Can anyone suggest me a better way?.

[kolusu]

vak255,

Do you have abend-aid installed in your production site? If you don't have then Check this post which explains in detail about solving abends

http://www.mvsforums.com/helpboards/viewtopic.php?t=214


Hope this helps...

Cheers

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[dbzTHEdinosauer]

vak255,
my mainline code consists of 2 parts:

1. plausi-proofing
2. mainline processing

1 pre-proofing or plausibility proofing is interrogating with code, every variable that is input to my program, whether it comes from a file, sysin, or DB2.

Other that DB2 sources:
all fields are tested to insure that their contents conforms to the datatype. e.g. IF var NUMERIC. Fortunately, DB2 will not allow non-numeric data in a numeric column.

Including DB2 sources:
all field contents are validated to insure that they conform to values (ranges, etc..) that I expect - or programmed for. If a field is a code and it needs to be A, B, C, 1 or space, and is not, I handle the error in the pre-proofing stage.

All rejections are handled with error routines that provide enough information so that I, another programmer or a user knows what was rejected and why. All errors are classified as:

1. catastrophic - program must end in an orderly manner
2. uncorrectable error
   • data is invalid, record can not be processed
   • program must skip a record and then go on (after reporting)
3. correctable error
   • data is invalid, use default and report
   • process with default

2 mainline processing is what most programs are, blindly manipulating data and blissfully unaware that numeric fields have spaces and codes are incorrect. But, my numeric fields have nothing except numbers and the codes contain values that conform to the application. WHEN OTHER in an EVALUATE statement should not allow processing of invalid data.

There is no such thing as bad data; there is only unacceptable data and bad code.
_________________
Dick Brenholtz
American living in Varel, Germany

[vak255]

Thnaks Kolusu, I have gone thru this link before and its really helpful and informative.
I have abend Aid installed in production but i don't have a DDIO file to find the exact location of the error and there by i could not know what data is causing the abend and in which line.

if u have the ddio file, u get this information in no time.

Thanks for your time.

[vak255]

Thx dbzTHEdinosauer, I am in support so got to handle lot of BAD CODE which passes down BAD data to downstream application...

[kolusu]

[vak255]

Unfortunately nobody knows much about it in my team. All are much comfortable with the way they use to trace it without abend aid. I too use the Abend aid to get some basic information like the below info.