AS/400 field modification impact on other related objects

22917

560 pts.

Tags:

AS/400 database

AS/400 Fields

DSPF

PRTF

I have a file field which we are planning to expand. The same field name is used in some of the files, DSPF's and PRTF's. If a program A has this impacted file declared, how can I find the other objects which are impacted due to this modification?

Software/Hardware used:
AS400

Asked: January 6, 2011 4:15 AM Last updated: January 6, 2011 11:11 PM

Answer Wiki

Last updated: January 6, 2011 2:33 PM GMT

CharlieBrowne62,340 pts.
History
Contributors
- Ordered by most recent
- CharlieBrowne62,340 pts.

Thanks. We'll let you know when a new response is added.

Unless you have a sofware package that builds a file for you, you have some work cut out for you.
You can use FNDSTRPDM over your source files and file all members that contain the value of the field name. Then you need to look at each one to see if you need to make any changs.
Also you need to file and recompile all programs that use the file you are changing where you use that field or not. Else you will get a level check.

Discuss This Question: 1 Reply

TomLiotta Jan 6, 2011 11:11 PM GMT

Part of it depends on how well the application was set up. If it was done right, there might not be anything you need to do at all, or you might get by with running DSPPGMREF over your executable objects to list references into a file that you can query. Note that DSPPGMREF can handle *PGM, *SQLPKG, *SRVPGM and *MODULE objects (or *ALL at once). Ideally, things like *CMDs all use PARMs that specify FILE() usage whenever a file name is referenced. That way, you'll be alerted even to CL programs where a file name might be in a variable. In any case, without knowing a lot about how your applications were developed and what standards might have been used, we have no way of knowing where your references might be. If you start with a logical file or VIEW for the file you're checking, you need to shift to the underlying physical file or TABLE. Then create a list of related files -- use the DSPDBR command to get an idea of how many files you might need to track. Use the DSPPGMREF list together with the DSPDBR list to find guaranteed references. Other references for unnamed files will require looking at any related source. Hopefully, your expanded field isn't used in every program. Programs that don't use the field should be referencing logical files or VIEWs that omit that field. If so, you won't need to do anything with those programs. You'll be lucky if that's the case. Tom

125,585 pointsBadges:

report