I need help with DSPF…

235 pts.
Tags:
AS/400 DB2
DSPF
RPG/400
SDA
Hi everybody,

i try explain my need.

I have one RPG pgm with several DSPF, and for this work well, i have a OVRDSPF.

My problem is when other people make any changes in one DSPF we have a level check, i know that, but because of this i need a idea for make an ALERT inside of DSPF source code in RED blink , i don't know, but anything who advise the guy about the fields position, and the format match, and the rest.

First i put this alert inside of the source code in pgm and dspf but if the guy go by SDA is other problem.

I accept any idea or way to put this alert in all this sources.

regards for everybody.

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    I have one RPG pgm with several DSPF... ...and... ...when other people make any changes in one DSPF... ...and... ...put this alert in all this sources. Several? One? All? It's not clear if you want to protect a particular DSPF source member or all source members for all of the possible DSPFs that you might override to in a particular program or something else. When you override any file, tools like DSPPGMREF can be misleading. It's harder for another programmer to know that your program is using some DSPFs because the names don't show up in a cross-reference. I assume that that is the basis for your problem. However, inserting non-text characters into a source member is also a problem. They can cause errors when the source member is transferred to a different system for maintenance. A programmer might download a source member to a PC to edit it in WDSC or RDi, or the member might be copied between a production and a development system and the system CCSID might be wrong on one of the systems. At some point, the edited source member is uploaded back to the original system to be compiled. The non-text characters might be translated in both directions incorrectly. There is no way to predict what the result will be. (Most of us have seen how even viewing a source member in a terminal session with certain text characters is a problem. I always use "*OR" in CL programs instead of the vertical-bar symbol because of that. It gets worse with non-text characters.) So you want to notify a future programmer to be careful when changing some source members. You would like bright colors, but SDA will still be a problem anyway. (WDSC and RDi or other PC editors can be worse than SDA for this.) Am I understanding the problem so far? Tom
    125,585 pointsBadges:
    report
  • BUG68
    Thanks Tom, i agree with you, but let me give an example of my reality: CALL MM1285 PARM(&ORCTOP &WECTP &DSPF) IF (&WECTP = 'C') THEN(DO) OVRDSPF FILE(MMM118E) TOFILE(&DSPF) OVRSCOPE(*CALLLVL) CALL PGM(MMM118) PARM(&$IND &$PCMD &$TTR &MMPERC) ELSE DO OVRDSPF FILE(MMM115E) TOFILE(&DSPF) OVRSCOPE*CALLLVL) CALL PGM(MMM115) PARM(&$IND &$PCMD &$TTR &MMPERC ) ENDDO and when i make any change in one of this dspf i need the same in all dspf source because, you know, when i open the DSPF i have level check if they don't match for each of format inside, in field position or name or size. rpg source: Fmmm115e cf e workstn usropn F infds($ids01) i hope this,clarify your doubt, anyway my problem is when other people change that DSPF i have problems ,because they know but they forget. thanks again, and if you have more ideas about a way of put an alert in a DSPF and RPG . regards
    235 pointsBadges:
    report
  • philpl1jb
    You could add another record at the top of the dspf and with a lower record name than any other (so it appears first in SDA}. The record name might be something like a_PGM_WARN. Past your instructions in there as text to display. So if it's open in SDA the programmer will read it. Phil
    51,365 pointsBadges:
    report
  • TomLiotta
    I can't think of anything better than Phil's suggestion. You might add a record format at the beginning:
         A          R WARNING
         A                                  1  2'DO NOT CHANGE THESE FIELD NAMES -
         A                                      OR LENGTHS OR CHANGE HE ORDER OF -
         A                                      FIELDS IN BUFFERS WITHOUT -
         A                                      RECOMPILING THESE PROGRAMS'
         A                                  3 10'MMM118'
         A                                  4 10'MMM115'
    A record format name like WARNING would be an eye-catcher even in SDA. I also thought that you could simply place comments at the top:
    A**********************************************************
    A**********************************************************
    A***                                                    ***
    A***       aa      ll      eeeeee  rrrrr     tttttt     ***
    A***      aaaa     ll      ee      rr  rr      tt       ***
    A***     aa  aa    ll      eeee    rrrrr       tt       ***
    A***     aaaaaa    ll      ee      rr  rr      tt       ***
    A***     aa  aa    ll      ee      rr   rr     tt       ***
    A***     aa  aa    llllll  eeeeee  rr    rr    tt       ***
    A***                                                    ***
    A**********************************************************
    A**********************************************************
    A***                                                    ***
    A***      Do Not change the structure of this display   ***
    A***      file without recompiling MMM118 to correct    ***
    A***      potential level check errors.                 ***
    A***                                                    ***
    A**********************************************************
    Eye-catchers come in various styles. My only recommendation is not to violate the fundamental data types that are allowed. It risks unpredictable trouble in the future. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following