Dear Russell Witt,
Thanks for your information.
Regards,


On 12/3/07, Russell Witt <[EMAIL PROTECTED]> wrote:
>
> 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.
>
> Russell Witt
> L2 Support Manager
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
> Behalf Of RHK HK
> Sent: Monday, December 03, 2007 6:37 AM
> To: [email protected]
> Subject: ATL 3590 problem
>
>
> We are facing following problem with some Scratch tapes
> Please help up.
> Regards
> [EMAIL PROTECTED]
> RETURN CODE 8 REASON CODE 51
> THE MODULE THAT DETECTED THE ERROR IS IGDIDMUS
> SMS MODULE TRACE BACK - IDMUS IDMSU IDM00 SSIRT
> SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00042
>
> IGD330I ERROR OCCURRED DURING CBRXLCS PROCESSING-
> VOLUME REQUESTED BY SPECIFIC VOLUME SERIAL IS A SCRATCH VOLUME
> THE FAILING VOLSER IS VOL244
> IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING
> RETURN CODE 8 REASON CODE 51
> THE MODULE THAT DETECTED THE ERROR IS IGDIDMUS
> SMS MODULE TRACE BACK - IDMUS IDMSU IDM00 SSIRT
> SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00042
>
>
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to