Page 1 of 1

need solution for A004 catastrophic error in easytrive

PostPosted: Wed Sep 09, 2015 11:28 pm
by Arun7818
Hi, when I try to run a easytrive program which creates multiple files I get 'A004 catastrophic error in module' as error mesaage, my EZTVFM space is (4096,(16000,16000)), can anybody help me to resolve this please...Thank-you !

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 12:07 am
by BillyBoyo
Not with what you have shown.

Was it a failure in the compiling stage, or in the run? Can you post the end of the output listing, and the program if possible.

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 12:08 pm
by Arun7818
Thanks billy,
I tried to run the jcl which has easytrieve program
//Eztrive1 exec pgm=module1,Region=10000k,time=480
//sysprint dd sysout=*
//sysout dd sysout=*
//report1 dd dsn= xxxx.xxxx.xxxx,
Disp=(New,catlg,delete),dataclas=large3,
Unit=sysallda,
Unit =(trk,(15,15),else),
Dcb =(recfm=fb,lrecl=133)
//EZTVFM dd unit= disk, space =(4096,(96000,96000))

But I get the error as A0004 catastrophic error in
Module -A140 0A 13BA

Corrected JCL inserted by moderator:
//EZTRIVE1 EXEC PGM=MODULE1,REGION=10000K,TIME=480
//SYSPRINT DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//REPORT1  DD DSN=XXXX.XXXX.XXXX,
//            DISP=(NEW,CATLG,DELETE),DATACLAS=LARGE3,
//            UNIT=SYSALLDA,
//            SPACE=(TRK,(15,15),RLSE),
//            DCB=(RECFM=FB,LRECL=133)
//EZTVFM   DD UNIT=DISK,SPACE=(4096,(96000,96000))

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 1:16 pm
by BillyBoyo
So copy and paste from your emulator the parts of the listing I asked for.

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 2:38 pm
by enrico-sorichetti
what happened when You looked at the easytrive manuals
or googled with easytrive A004 catastrophic error ?

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 3:16 pm
by NicC
Please use the code tags when presenting data and code - search if you do not know how to use them but it is pretty obvious when you use the POSTREPLY button rather than the QuickReply button.

As posted your JCL will fail for numerous reasons - spaces where ther should be no spaces, no leading // on some cards, multiple use of UNIT on one DD etc. I have corrected it as best I can and added it to your post (using the code tags).

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 3:46 pm
by BillyBoyo
Taking enrico's advice, it looks like you need more space for your EZTVFM. Why not allocate in cylinders. Work out approximately how much space should be used (by consulting the information about your source datasets and seeing what use of the VFM there is).

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 5:13 pm
by Arun7818
Hai ericho bfiles,and nic,
I tried to Google it states us to increase the size of EZTVFM i made it to cyls but I get the same issue...it was also suggested that to use report work files but I don't have any idea how to use Report work files, is this something like sort work ???
This is the link from where I got the info
googleweblight.com/?lite_url=http://customerconnect.ca.com/cc/kbtech?docid%3D265273%26searchID%3DTEC265273&ei=sYovtr_P&lc=en-IN&geid=150&s=1&m=836&ts=1441885029&sig=APONPFlw0ntnNcehFbNScqMdQ8xCPrqDEw

Please guide me to resolve this guys... This is stopping my testing.
Thankyou!!

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 5:51 pm
by enrico-sorichetti
Please guide me to resolve this guys... This is stopping my testing.


Remember... replying to forum questions
is done on voluntary base, on our own time, free of charge

if You have time issues - a forum is not the best place to ask for help.

Again, look at the easytrive manuals

and work with Your support

Re: need solution for A004 catastrophic error in easytrive

PostPosted: Thu Sep 10, 2015 6:11 pm
by BillyBoyo
Have you estimated the space you will need from what you are writing to the files?

If you don't have any DO loops, and no stupid hand-built loops, it is just a question of space. You may have changed to CYLs, but you have to supply enough.

If you do have any DO loops or stupid GO TOs, post the code here.

You're not doing a lot to help yourself. For the third time, I'll ask you to post the "bottom" of the output listing, showing the file-usage completed before the crash.