|
View previous topic :: View next topic
|
| Author |
Message |
Laxminarsimharao
New User
Joined: 08 May 2007
Posts: 26
Location: hyderabad
|
|
|
|
How to convert GDG of length 103 to 150 (LRECL) with the increased bytes filled with default values 
Is there any process of direct convertion (i.e. change of LRECL for the GDG) ? |
|
| Back to top |
|
 |
murmohk1
Senior Member
.jpg)
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Laxminarsimharao,
| Quote: |
| Is there any process of direct convertion (i.e. change of LRECL for the GDG) ? |
Do you want to increase the record lenght of existing generations or the generations you would create in future(if at all)? |
|
| Back to top |
|
|
Laxminarsimharao
New User
Joined: 08 May 2007
Posts: 26
Location: hyderabad
|
|
|
|
murmohk1,
Yes, I wanted to change it for existing generation |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
Your best bet is to use DFSORT to copy the data to the new required length, and update the version so that the position of the generation in the GDG doesn't change:
| Code: |
//STEPX EXEC PGM=ICEMAN
//SORTIN DD DISP=SHR,DSN=THE.EXISTING.GDG.GxxxxV00
//SORTOUT DD DSN=THE.EXISTING.GDG.GxxxxV01,
// DISP=(,CATLG,DELETE),UNIT=SYSDA,SPACE=.....
//SYSOUT DD SYSOUT=*
//SYSIN DD *
OPTION COPY
OUTREC FIELDS=(1:1,103,150:X)
/*
|
where xxxx is the existing generation number (0001-9999). |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Superk has given the best solution, however, call me old fashioned, but I would take a backup of the generations before starting - just in case. |
|
| Back to top |
|
|
|
|
