IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

VVDS error when MOVE large files to another SMS volume...


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Victor Niu

New User


Joined: 11 Mar 2010
Posts: 59
Location: China,Shanghai

PostPosted: Mon Oct 25, 2010 1:25 pm
Reply with quote

When MOVE file SMF.PLEXSP1.DAILY.CICS.** from mod 3390-3 to 3390-9 volume, system error found.
The message is ADR231E (001)-SB113(01), ERROR WHILE ACCESSING VVDS FOR DATA SET SMF.PLEXSP1.DAILY.CICS.D101007 ON VOLUME DC6C0C. OP=0, VVDS RC=012.

This job ran twice,still the same probles,at last,I re-inited and defined a larger VVDS(10 cyls),the MOVE OK.

I checked other systems,the vvds information almost is
" * DEFAULT VVDS SPACE = ( 10, 10) TRKS "

Pls can anyone say something for this problem?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Mon Oct 25, 2010 1:29 pm
Reply with quote

What did you find out when you read the manual and investigated ADR213E.

You did do that, didn't you ?
Back to top
View user's profile Send private message
Victor Niu

New User


Joined: 11 Mar 2010
Posts: 59
Location: China,Shanghai

PostPosted: Mon Oct 25, 2010 1:39 pm
Reply with quote

in my opinion,the file is too large for the destination volume and no free space to allocate vvds file,
then I did test to allocate a large empty file for a empty sms volume and found the system will force deserving 10 trks space for the vvds file.
Back to top
View user's profile Send private message
Victor Niu

New User


Joined: 11 Mar 2010
Posts: 59
Location: China,Shanghai

PostPosted: Mon Oct 25, 2010 2:02 pm
Reply with quote

3.2.124 ADR231E

ADR231E (xxx)-mmmmm(yy), ERROR WHILE ACCESSING VVDS FOR DATA SET dsname ON
VOLUME volume_serial_number. OP=operation_code, VVDS
RC=return_code

Explanation: The VVDS is accessed for the specified call during a DUMP, DEFRAG,
CONVERTV, data set COPY, or data set RESTORE. The operation code can be:

0 Insert a VVR/NVR

1 Get a VVR/NVR for update

2 Put a VVR/NVR for update

3 Generic read of components of a cluster

4 Read a VVR/NVR

5 Delete a VVR/NVR


The return_code is the return code from the VVDS manager. See the reason code under
return code 50 in message IDC3009I.

System Action: If the operation is DEFRAG, the extent is not relocated. If the operation
is data set RESTORE, the affected data set is not restored. Other messages identifying
the affected data set accompany this message. The return code is set to 8.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 582
Location: London

PostPosted: Thu Oct 28, 2010 8:10 pm
Reply with quote

It would help if you provided the Reason Code from the message your job output.

It sounds like you may have sorted the problem by creating a larger VVDS on the target volume. The default 10,10 trks is barely adequate on l3390-9/27/54 volumes if they have alot of small files like DB2 tables. There is a parmlib member now that can change the VVDS default size from 10,10 trks to a larger value. We go for about 9,1cyls on our VVDS's for SMS managed volumes..
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Compare 2 files and retrive records f... DFSORT/ICETOOL 3
No new posts Compare 2 files(F1 & F2) and writ... JCL & VSAM 8
No new posts How to split large record length file... DFSORT/ICETOOL 10
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
Search our Forums:

Back to Top