Adding a new logical or index will have NO direct bearing on the physical file
In this instance - there is no need to make a copy of the physical file
Adding a new field - as long as it is at the end of the record layout. There should be no need to make a copy of the file
Adding a new field - NOT at the end of the record layout, but in between 2 existing fields - the question I would ask is - why is it being done this way. If it DOES need to be changed this way - then as a precaution, I would make a copy of the file
Changing an existing field - changing the size, changing from an alpha to a numeric field (for whatever reason), then as a precaution, I would make a copy of the file
Alan Shore
Solutions Architect
IT Supply Chain Execution
[NHScsignaturelogo]
60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx
'If you're going through hell, keep going.'
Winston Churchill
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Wednesday, November 24, 2021 10:56 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: [EXTERNAL] RE: Deploying DB2 Table Changes
Right. Thus the complexity.
In my scenario you can assume V7R3 and higher.
There could be: DDL, DDS, add new fields, remove fields, resize fiels, add indexes, add logical files, the list is endless.......
And any one of these things can then cause level checks for RPG, COBOL or CL programs.
I knew this wouldn't be a simple question, but I'm curious where to start.
And in the end the answer may be: manually rename/move old table, manually stage the new table and copy data back, then recompile all the associated objects to avoid level checks.
Which also begs the question as to whether DSPPGMREF has any alternatives to id potentially affected changed programs.
I'm working with a IBMi dev team who is going from single box development to have a dev/test machine and production machine and trying to make their deployment options easier.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net<
http://www.richardschoen.net>
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
----------------------------------------
message: 6
date: Wed, 24 Nov 2021 14:37:37 +0000
from: Alan Shore via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
subject: RE: Deploying DB2 Table Changes
Hi Richard
The answer to your question is tape recording number 26 It depends First - what release are you on? If you are on an extremely old (decades) release, you may have no choice What change are you doing?
Adding one or more new fields?
Changing an existing field - if so - from what to what
Alan Shore
Solutions Architect
IT Supply Chain Execution
[NHScsignaturelogo]
60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx<mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l<
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com<
https://amazon.midrange.com>
midrange.com
