|
View previous topic :: View next topic
|
| Author |
Message |
satheeshkamal
New User
Joined: 09 Jan 2007
Posts: 28
Location: Chennai
|
|
|
|
Guys,
We are trying to run an EZT program and getting S46D abend, Reason Code = 14.
Large number of input records are used for processing.
If we process with few number of records, the program is executing absolutely fine. This abend occurs only when processing large number of records.
We tried giving REGION=0M for the whole job, the result is same.
We also tried increasing EZTVFM size, the result is same.
EZT program logic:
Read two input files (INPT1 and INPT2) using GET statement (GET is used as both the files contain duplicate keys for matching) and match them on a particular key.
For each key matching from INPT1 on INPT2, store the records from INPT2 into an array and also process INPT2 records to set indicators on INPT2 and write output file OTP1.
Use the array later to decide on setting indicators for the record in INPT1 to write output file OTP2.
(Array size is 109 bytes and 500 occurrences)
The program code is really big to post it.
We could not relate the error to the program.
Any ideas please? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
satheeshkamal
New User
Joined: 09 Jan 2007
Posts: 28
Location: Chennai
|
|
|
|
Thanks enrico,
| Quote: |
14
The ESPIE RESET macro passed an incorrect TOKEN parameter. TOKEN is incorrect for one of these reasons:
The TOKEN itself is not valid.
The exit that the TOKEN represents has been deleted |
What is meant by TOKEN parameter?
Could you explain what actually this message is trying to point?
Thanks very much. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you look for the solution in the application code. Things like the ESPIE and TOKEN are not really the problem but rather the symptom.
The application code has "run amuck" somehow and the abend is the result of this (most likely).
If you cannot isolate the problem by experimenting with different versions of the application code, you may want to open an issue with CA support (as previously suggested). |
|
| Back to top |
|
|
|
|
