|
View previous topic :: View next topic
|
| Author |
Message |
sasi_msis
New User
Joined: 02 Nov 2007
Posts: 6
Location: Bangalore
|
|
|
|
Hi,
We run Full Backup every week and some times we are getting problems during the backup step. The backup step got RC 16 and job terminated with system abend code 714-0C.
Please see the joblog inforamtion.
IEC215I7140C,IFG0200Z,BKBEPTRF,BACKUP,BACKUP,05B1,001051,BACKUP.BEPTR.FULLDSN
IEF234E K 05B1,001051,PVT,BKBEPTRF,BACKUP
The sysprint of backup step shows ADR347E PERMANENT I/O ERROR showing one of the datasets during the backup
0ADR347E (001)-IOWT (01), PERMANENT I/O ERROR ON DDNAME BACKUP , BKBEPTRF,BACKUP ,05B1,T,BACKUP ,01- OP,DATA CHECK
,0000442339,EXCP
I have verified few manuals regarding IEC215I and it states that 714-0C occurs an i/o error occured writing tapemark during close macro instruction. The manual says possible reasons could be defective tape or volume.
I have opened the dataset in one of our dataset and could not see any problem in that.
We are getting this problem only few times if the job runs for next we are not getting these problems. I am just hoping this is tape/device problem but the sysprint of backup steps shows permanent i/o error for one of the backup datasets.I am just confused whether it is related to tape/device problem or dataset problem.
Please some one let me know the exact problem which causing this problem if someone encoutnered these type of problems earlier. Why the same dataset has backed out successfully the next time without any errors. |
|
| Back to top |
|
 |
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
Old tape...
Badly placed EOV reflective marker...
Dirty read/write heads....
Keep track of the drive and tape volsers, there might be a pattern.... |
|
| Back to top |
|
|
sasi_msis
New User
Joined: 02 Nov 2007
Posts: 6
Location: Bangalore
|
|
|
|
Did you mean to say the problem is with the tape/volume in which the EOV marker is not placed properly?
Could you please let me know about the drive and volsers pattern? If there is pattern is missing will it be a problem?
The tape/volume will be placed by the operators.As a programmer do i need to do anything regarding this?
Thanks for the quick response. |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
| sasi_msis wrote: |
| Did you mean to say the problem is with the tape/volume in which the EOV marker is not placed properly? |
Yes, the problem is hardware, maybe toe EOV marker, maybe dirty read/write heads, maybe old/bad tape media....
| Quote: |
| Could you please let me know about the drive and volsers pattern? If there is pattern is missing will it be a problem? |
If this is happening regularly, operations should be looking at the EREP reports to see if a pattern is visible - one tape drive that this occurs on most ofter or a set of tapes from the same maker and batch....
| Quote: |
| The tape/volume will be placed by the operators.As a programmer do i need to do anything regarding this? |
Talk to ops, find out if they are looking into this, it is their problem..... |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| As a programmer do i need to do anything regarding this? |
As a programmer You should not even be concerned about such events..
Backup responsibility ( once the testing has been completed )
is ALWAYS on operations teams
After a recovery anyhow, the application team might be responsible
for checking the congruence of the restored scenario |
|
| Back to top |
|
|
sasi_msis
New User
Joined: 02 Nov 2007
Posts: 6
Location: Bangalore
|
|
|
|
Same problem is happened earlier few times. I hope ops may have EREP reports. I shall let them know the same info i got thru this forum.
Thanks once again to all for the quick reply. Have good day  |
|
| Back to top |
|
|
|
|
