View previous topic :: View next topic
|
Author |
Message |
Manikandesvaran D
New User
Joined: 05 Dec 2013 Posts: 11 Location: india
|
|
|
|
Folks,
I am getting the below ERROR when i process my JCL
IGD330I ERROR OCCURRED DURING CBRXLCS PROCESSING-
VOLUME REQUESTED BY SPECIFIC VOLUME SERIAL IS A SCRATCH VOLUME
THE FAILING VOLSER IS 0HD307
IGD306I UNEXPECTED ERROR DURING ?CBRXLCS PROCESSING
RETURN CODE 8 REASON CODE 51
THE MODULE THAT DETECTED THE ERROR IS IGDCAT01
SMS MODULE TRACE BACK - CAT01 CAT00 SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00012
It seems the volume went on SCRATCH and i want to bring it back to PRIVATE again.Could anyone please help on This..Probably a JCl to bring back the VOLUME from SCRATCH to PRIVATE will help.
Thanks in Advance
Mani |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
That error is not produced by JCL but the program that is being executed. JCL alone will not do what you want but your TLMS may - if you get the control cards right (refer to manual or your tape librarian). |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
pic.dhe.ibm.com/infocenter/zos/v1r13/topic/com.ibm.zos.r13.idar100/r1172.htm
Quote: |
You cannot call for scratch volume by specific-volser. If you are attempting
write new data to a new tape; it should be without a volser and just select the next scratch volume. If you are attempting to read or mod data onto an existing tape; the tape has been scratched (why?) inside the robot. In that case, you would need to "un-scratch" the tape (change its status to PRIVATE) using the ISMF panels and then re-submit the job. |
|
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
It seems the volume went on SCRATCH and i want to bring it back to PRIVATE again |
Contact your site support group!
If the volume has been scratched, at some sites that means the data is overwritten and hence even if you change the status from SCRATCH to PRIVATE, you will be unable to recover any of the data. If the volume has merely been marked SCRATCH without being written to, you can recover the data. But only your site support group can help you -- and they should have been your FIRST call when you discovered the problem. If the tape has been written to since you posted here, then you have lost the data -- period. |
|
Back to top |
|
|
Manikandesvaran D
New User
Joined: 05 Dec 2013 Posts: 11 Location: india
|
|
|
|
Thanks Robert for your help. |
|
Back to top |
|
|
Manikandesvaran D
New User
Joined: 05 Dec 2013 Posts: 11 Location: india
|
|
|
|
Rohit Umarjikar wrote: |
http://pic.dhe.ibm.com/infocenter/zos/v1r13/topic/com.ibm.zos.r13.idar100/r1172.htm
Quote: |
You cannot call for scratch volume by specific-volser. If you are attempting
write new data to a new tape; it should be without a volser and just select the next scratch volume. If you are attempting to read or mod data onto an existing tape; the tape has been scratched (why?) inside the robot. In that case, you would need to "un-scratch" the tape (change its status to PRIVATE) using the ISMF panels and then re-submit the job. |
|
Thanks Rohit.The files has not been used for a longer time and it went on SCRATCH.I have generated new files and that worked.I am coping the data from the Dataset to other Dataset for a transmit operation.But i am just checking the possible ways to bring the files back to PRIVATE.
Could you let me know how to make the status PRIVATE using ISMF panels please ? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Robert Sample wrote: |
Quote: |
It seems the volume went on SCRATCH and i want to bring it back to PRIVATE again |
Contact your site support group!
If the volume has been scratched, at some sites that means the data is overwritten and hence even if you change the status from SCRATCH to PRIVATE, you will be unable to recover any of the data. If the volume has merely been marked SCRATCH without being written to, you can recover the data. But only your site support group can help you -- and they should have been your FIRST call when you discovered the problem. If the tape has been written to since you posted here, then you have lost the data -- period. |
Adding to what Robert has said, and I really do recommend that you follow his advice and contact the support group responsible - If the volume is VTS resident, depending on the settings at YOUR SITE even if the volume serial number has not been reused it may well be useless anyway. If the volume header information is deleted from the VTS control file then the volume will be totally useless. |
|
Back to top |
|
|
Manikandesvaran D
New User
Joined: 05 Dec 2013 Posts: 11 Location: india
|
|
|
|
Thanks expat for your help |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
Mani, I am not sure if you can use IEHMOVE. May be experts here could tell more on what you have asekd. |
|
Back to top |
|
|
Manikandesvaran D
New User
Joined: 05 Dec 2013 Posts: 11 Location: india
|
|
|
|
Thanks Rohit For your suggestion.I have contacted my CA-1 support team in my end.
But your suggestion also Sounds good.i will try to check IEHMOVE over my end.
Thanks
Mani |
|
Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
|
|
|
|
I spent some time looking up the IGD330I message. The message description referred me to DFSMS Diagnosis for a description of return code 8, reason code 51. Guess what: "Specific volume serial request for a scratch volume."
In my career I don't think I ever encountered this message. On numerous occasions I have encountered a situation where a volume is in scratch status and I've been able to recover its contents provided it was not written over. However, these were all real tapes.
As others have noted, if the volume is a "virtual" volume in some sort of virtual tape system, I suspect it will not be possible to recover the data, but I'm no expert in these systems.
Somewhere someone suggested using IEHMOVE. All IEHMOVE does is sort of fake out JCL. Once it has done that it uses standard z/OS data management services. If you can't use JCL to specify the data, I don't think IEHMOVE will help you. On the other hand, I could be wrong; it can't hurt to try. |
|
Back to top |
|
|
|