(FOC198) FATAL ERROR IN DATABASE I/O in IBATCH JCL
Has anybody experienced getting a "(FOC198) FATAL ERROR IN DATABASE I/O..." error when using the IBATCH JCL to run multiple WebFocus reports? It appears to happen right on the MATCH FILE command. Funny, when I run the report in IBATCH by itself, it runs fine. But when I run multiple reports, then it breaks. I was running 3 reports and the MATCH FILE command is in the last report. Here is the simple IBATCH jcl step:
And here is the MATCH FILE statement that breaks it:
MATCH FILE APU1 SUM APUCT AS 'APUCT' BY WEEK AS 'WEEK' RUN FILE INT2 SUM INTCT AS 'INTCT' BY WEEK AS 'WEEK' AFTER MATCH HOLD AS INTER1 OLD-OR-NEW RUN FILE CCD3 SUM CCDCT AS 'CCDCT' BY WEEK AS 'WEEK' AFTER MATCH HOLD AS INTER OLD-OR-NEW END -RUN
This is a legacy report from FOCUS 7.0.9 that I am trying to convert to WebFocus.
Please advise if anybody had experienced this and found a way around it.
Thanks in advance for replying.
Thanks, Ronnel C WebFocus 7.1.5 IBM ZOS 1.6
June 08, 2007, 05:04 AM
hammo1j
"(FOC198) FATAL ERROR IN DATABASE I/O..."
That's FOCSORT bombing out. I am guess that the DD statement that allocs this file in the new proc is allowing smaller initial and extents in comparison to the original JCL.
Look for the original FOCSORT DD card on the 7.0.9 proc and use it to override on the new proc. (Used to be good at this for o/n failures etc but I have forgotten it all!)
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
June 08, 2007, 10:08 AM
Ronn
I see the FOCSORT DD stmt in our Focus 7.0.9 production sysout for that report and it's set to "UNIT=SYSDA,SPACE=(CYL,(4,4))". But I don't see the FOCSORT in my IRUNJCL job or even in the IBATCH job. Although when viewing the WebFocus SYSOUT for my report that bombed with an I/O error, I see where the FOCSORT appears, there's an MVS error saying "Inaccessible storage".
I tried hardcoding "FOCSORT DD UNIT=SYSDA,SPACE=(CYL,(4,4))" in my IRUNJCL job but that did not change anything.
I also tried harcoding "TSCOM300.FOCSORT DD UNIT=SYSDA,SPACE=(CYL,(4,4))" in my IBATCH job but that also did not change anything.
My problem right now is I can't find where that FOCUS or TSCOM300 proc is so I can code it directly in it. But coding it in the IBATCH or IRUNJCL should be good enough, right?
Thanks, Ronnel C WebFocus 7.1.5 IBM ZOS 1.6
June 08, 2007, 10:14 AM
Francis Mariani
4 initial cylinders and 15 extensions of 4 cylinders may not be enough disk space for FOCSORT.
(I haven't worked with mainframe JCL in quite a while).
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
June 08, 2007, 02:01 PM
Ronn
I added the ff in my IRUNBATT proc:
INTER DD UNIT=SYSDA,SPACE=(CYL,(1000,100),RLSE),DCB=BLKSIZE=0, DISP=(,CATLG,DELETE) INTER1 DD UNIT=SYSDA,SPACE=(CYL,(1000,100),RLSE),DCB=BLKSIZE=0, DISP=(,CATLG,DELETE)
But still got the same error message.
Thanks, Ronnel C WebFocus 7.1.5 IBM ZOS 1.6
June 11, 2007, 04:50 AM
hammo1j
To solve this one I think you need to see how big the focsort grows on the original jcl by allocing FOCSORT to a permenant dataset on your 7.0.6 run and seeing what size you get.
Do the same on wf and if its much bigger when it busts - its probably an out of control table request that's internally looping for some reason.
If this is the case you will have to play with the code and reorder the order of your fields etc until you come up with something that works.
The other thing you can try quickly is setting the new XFOCUS features on SET XFOCUS=ON in your code and hope that the new version of FOCSORT cures your problem. Worth a try as it s quick.
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo