View previous topic :: View next topic
|
Author |
Message |
akashs
New User
Joined: 24 Nov 2005 Posts: 49 Location: chennai
|
|
|
|
hi,
iam recovering gdgs from tape ,using IEBGENER iam taking their backups,iam frequently facing S813 ,SA13 abends and also flushed is coming...plz tell whts the reason behind it
regards,
akash |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
|
|
Post your job & abending messages here...
Why dont you give a try thru IDCAMS.
Code: |
//COPY EXEC PGM=IDCAMS
//INDD DD DSN=HLQ.DSNAME.TAPE,DISP=SHR
//OUTDD DD DSN=HLQ.DSNAME.DISK,
// DCB=(BLKSIZE=XXXX,LRECL=XXX,RECFM=XX),
// DISP=(,CATLG,DELETE)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO INFILE(INDD) OUTFILE(OUTDD)
/* |
Regards,
Priyesh. |
|
Back to top |
|
|
sbalajibe
New User
Joined: 15 Aug 2005 Posts: 62
|
|
|
|
hi ,
please find the reasons for the abends mentioned
S813
The data set name in the JCL did not match the data set name on the tape.
1. The JCL volume serial number was wrong.
2. The data set name in the JCL was misspelled.
3. The wrong tape was mounted.
4. The incorrect data set sequence number was specified in the label parameter.
5. The data set does not exist on the magnetic tape.
Verify that the JCL is correct, and resubmit the job.
SA13
An error occurred in opening a tape data set.
1. The file sequence number was wrong on a multi-volume tape data set.
2. The file sequence number was wrong, or it was less than that of the first data set on the tape.
3. The volume serial number was wrong.
4. The job which wrote the tape did not write all the data sets.
1. Verify that the JCL is correct, and resubmit the job.
2. If the desired data set does not exist on the tape, recreate the tape.
u can also use sort utility to copy from tape to dasd |
|
Back to top |
|
|
rhutwik.mokashi
New User
Joined: 16 Nov 2005 Posts: 1
|
|
|
|
hi man
use ERROR ASSIST ti solve any difficulty in error codes it is very good tool in this context. |
|
Back to top |
|
|
|