|
View previous topic :: View next topic
|
| Author |
Message |
santoshkumarmanilakkoju
New User
.jpg)
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
One of the production FOCUS job failed with error FOC198.
The error is:
(FOC198) FATAL ERROR IN DATABASE I/O. FOCUS TERMINATING ERROR WRITING NATAGS , PAGE 25166, CODE 0xaa000003
The issue is with one file which gets updated with 10 focus jobs.
I have tested the job by incraesing the space to 4,000 cylinders Primary and secondary and the job executed fine.
How can I increase space to an existing GDG which would be used by the present run. |
|
| Back to top |
|
 |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
I may not understand, but didn't you answer your own question:
| Quote: |
| I have tested the job by increasing the space to 4,000 cylinders Primary and secondary and the job executed fine. |
So, if you create and catalog a new GDG version for the same generation (notice I'm talking about the Version, not the Generation) with these new attributes, copying the old version's contents, doesn't that address your problem? |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 581
Location: London
|
|
|
|
If you want to allow an existing GDS to increase in size (as opposed to creating a new (+1) generation) then you could do an IDCAMS ALTER gds.name ADDVOL(* * * ....etc) to add candidate volumes for it to extend to, up to the maximum 59 volumes and write to it with DISP=MOD. If the file is Extended Format it can then take up to 7257 extents altogther in theory, depending on how many volumes the eligible storgrp actually has.
Otherwise if you're going to recreate the GDS as a new version you could ensure it has more appropriate SPACE defined and see if you have Dataclases available that provide Space Constraint Relief that can dynamically add volumes as required (the DYNVOLCOUNT), and possibly Compression and Extended Format. If no Dataclas available has DYNVOLCOUNT set then add VOL=(,,,59) to the JCL. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Is the problem dataset a FOCUS Master File? These are typically NOT defined as a gdg. . .
Is the real question even related to generation data sets? Or possibly, is the question how to make a FOCUS Master File larger. . .? |
|
| Back to top |
|
|
santoshkumarmanilakkoju
New User
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
Hi d.sch
The file is GDG generation file which is modified by 7 series of FOCUS jobs with 7 months of data. So the data is added for every run.
Now the problem is the FOCUS production program is coded to take (-1) / (0) generation of the GDG.
The first job is failing when the (-1) generation is modified with FOC198 error.
When I tested the code with dumped data into flat file from (-1) generation the job did fine. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
To repeat - is the problem file a FOCUS file or is it simply a qsam (flat) file?
Why is the -1 generation being modified? Seems like this would be questionable at best. . . Regardless of file organization. Why update the "old stuff" when there is "newer stuff" available?
What is "dumped data"?
Until much more clear information is posted, it will be difficult for someone to provide a useful reply. Someone may make a lucky guess, but so far, nothing has been posted we could use to help solve the problem. |
|
| Back to top |
|
|
|
|
