|
View previous topic :: View next topic
|
| Author |
Message |
d_sarlie
New User
Joined: 22 Apr 2008
Posts: 42
Location: coimbatore
|
|
|
|
Hi,
Is that possible for us to increase the version of V00
XK.LM.S010F01.G0147V00
Thanks for the help. |
|
| Back to top |
|
 |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
Yes, just catalog a new dataset:
| Code: |
//STEPXXXX EXEC PGM=ICEGENER
//SYSUT1 DD DSN=XK.LM.S010F01.G0147V00,DISP=SHR
//SYSUT2 DD DSN=XK.LM.S010F01.G0147V01,
// DISP=(,CATLG,DELETE),UNIT=....
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
|
after which the existing GDS entry XK.LM.S010F01.G0147V00 will be rolled off and uncataloged and replaced with the new entry XK.LM.S010F01.G0147V01. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Why do you believe you want to do this? |
|
| Back to top |
|
|
d_sarlie
New User
Joined: 22 Apr 2008
Posts: 42
Location: coimbatore
|
|
|
|
HI...
I want to know the functionality of V00. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
It is a version (rather than a generation).
It (version) is nearly never used for files created by a business application. . . .
Unless there is some pressing business reason to use this, suggest you be aware of version and then never use it. . .  |
|
| Back to top |
|
|
d_sarlie
New User
Joined: 22 Apr 2008
Posts: 42
Location: coimbatore
|
|
|
|
| Thanks for the info. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Quote: |
| I want to know the functionality of V00. |
If generation A.B.C.G0001V00 is cataloged and you now create and catalog A.B.C.G0001V01, the new entry is cataloged in the location previously occupied by A.B.C.G0001V00. The old entry is removed from the catalog, to make room for the newer version, and may or may not be scratched depending on what limit processing options are specified for the GDG base.
For SMS DSNs, if scratch is specified, the older version is scratched from the volume. If noscratch is specified, or if the attempt to scratch the DSCB fails, the older version is not scratched and the generation data sets is recataloged as a non-VSAM data set with the GnnnnVnn name not associated with the GDG base.
For non-SMS DSNs, if noscratch is specified for the base, the older GDS version is not scratched.
Try allocating a new "version" for an existing GDG & look the entris in 3.4, you might get hands-on experience... |
|
| Back to top |
|
|
|
|
