March 26, 2007, 07:42 AM
manashAbend Error U0602
I ran a focus program in mainframes using JCL with 90000 records in the input file.
The record length on input file is 95. The DISP parameters for the output file was gives as follows -
DISP=(NEW,CATLG),SPACE=(CYL,(50,10)),UNIT=SYSDA.
The output file has been created for all the data but the job is not getting completed but getting ABENDED.
It is giving an error code of U0602.
How to eliminate this error.
March 26, 2007, 07:47 AM
Danny-SRLmanash,
This is what I found on the internet:
FDR124 FORMAT 4 ERROR REASON=n
Reason: FDR detected an error with the Format 4 DSCB.
The VTOC may be improperly formatted.
REASON CODE EXPLANATION
1 -- More than one (1) Format 4 was found, or the
first entry in the VTOC was not a Format 4. This
may be due to an IBM problem.
2 -- FDR found the Format 4 contained zero (0) free
DSCB's plus the high water mark was set to the
first
Format 5.
This is the condition in which CPK would leave
the volume if an ABEND or system crash occurred
during the restore phase. This volume may be
partially restored. This is a very serious
problem. The volume should be placed offline
until the error is corrected. See Section 40.23
on a procedure to recover the volume. If you must
dump the volume, specify PROT=NONE on the DUMP
TYPE= command.
Action: A U0602 Abend will be issued. Contact
INNOVATION for assistance with an
IEHLIST LISTVTOC DUMP listing.
I would suggest you contact your systems people!
March 26, 2007, 08:18 AM
RichHHi Manash,
In general a U602 abend indicates an issue with a file.
Below are some possible causes of this abend:
A partitioned dataset was allocated instead of a physical sequential dataset.
(A -WRITE was executed against a partitioned dataset instead of a physical sequential dataset).
A FOCUS workfile, like FOCSTACK, was allocated to a partitioned dataset instead of a sequential dataset.
A Dynam FREE was executed against a load module that had already been freed.
The wrong load libraries are allocated to a job.
If none of these help, open a ticket with IBI.
Regards,
Rich
March 26, 2007, 08:47 AM
Jim_at_LMquote:
UNIT=SYSDA.
Manesh:
Some type of I/O error is occurring. Some IBM sites limit use of SYSDA in BATCH JOBs and system management may be flagging as a user error since it may be requiring the output to be on a permanent device (like PRDDA or TSTDA -check with your site on the names used there).
It would help if you posted the DDs from the JCL for both the input and output datasets, and used "XXX.yyy..zzz" etc. to keep the dataset names confidential. If your DD is not accurate, the OS will assume a file type that you may not want.
March 26, 2007, 09:43 AM
LeahDon't use the mainframe any more, and yes concur with all the others, do you have your DCB coded in the JCL stream? This may be where your issue really lies.
March 26, 2007, 11:58 PM
manashThanx to u all for your suggestions. Will try to figure it out.