Thanks. That was it.

Mark Jacobs

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&[email protected]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, July 31, 2020 11:58 AM, Gormley, Steve <[email protected]> wrote:

> CAUTION EXTERNAL EMAIL: This email originated from outside of the 
> organization. Do not click links or open attachments unless you recognize the 
> sender and know the content is safe.
>
> When dealing with volume entries in IDCAMS I believe you have to add a 'V' in 
> front of the volser name - VDS0001
>
> Steve
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [email protected] On Behalf Of 
> Mark Jacobs
>
> Sent: Friday, July 31, 2020 4:06 PM
> To: [email protected]
> Subject: IDCAMS Alter volumeentry not working
>
> We have an MTL that's not under RMM control. The MTL internally scratches 
> tapes that have reached their expiration date daily, but the entries in the 
> volcat are showing them as private. When I attempt to manually alter them to 
> scratch status, IDCAMS isn't liking either format of the command (that I've 
> read in the FM). What am I doing wrong?
>
> ALTER DS0001 VOLUMEENTRY USEATTRIBUTE(SCRATCH) LIBRARYNAME(DEVLVTL) IDC3012I 
> ENTRY DS0001 NOT FOUND IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON 
> CODE IS IGG0CLEG-42 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
>
> ALTER VOLUMEENTRY(DS0001) USEATTRIBUTE(SCRATCH) LIBRARYNAME(DEVLVTL) IDC3203I 
> ITEM 'VOLUMEENTRY(DS0001)' DOES NOT ADHERE TO RESTRICTIONS IDC3202I ABOVE 
> TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12
>
> Sent from ProtonMail, Swiss-based encrypted email.
>
> GPG Public Key - 
> https://api.protonmail.ch/pks/lookup?op=get&[email protected]
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> [email protected] with the message: INFO IBM-MAIN
>
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to