Re: Negative response code... RNX1251

[Jerry Adams <jerry@xxxxxxxxxxxxxxx>]

The reason this happens is that most people change the QSYS command 
which, in my opinion, is bad practice.  The command should be copied to 
a library higher than QSYS in the library list.  (One you create and 
position with a system default.)  Even then the default should be 
changed via a CL program; otherwise, when the new release comes out you 
lose the change (as Joe points out), or you spend an inordinate amount 
of time trying to remember / recreate the changes. 


With the new release you need to copy the command(s) (again) from QSYS 
to your library and run your change procedure.  Why?  Because IBM may 
have changed ("enhanced") the command, and you don't want to deal with 
old (missing?) parameters.



        * Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Joe Giusto II wrote:

> when is the last time that you did an upgrade?  i have had to reset this default
> in the past after a release upgrade.
>
> ----- Original Message ----- 
> From: "John Wallroff" <jwallroff@xxxxxxxxxxxxxxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Wednesday, April 26, 2006 5:14 PM
> Subject: RE: Negative response code... RNX1251
>
>
> I have been a programmer here for over 9 years.  The screen that has the
> problem has been here longer then I have. We have literally hundreds of
> programs that work the same way.  Neither I nor anyone else here has
> ever seen that error and none of us have ever had to change the RSTDSP
> parm.  In fact none of us generally use the option 14-CRTDSPF command,
> we normally have been use to using option 17-Change using SDA and upon
> exiting SDA compiling the display file.  Even though I am using WDSCi
> and Code to work on my display files I still compile them this way out
> of habit.  There is no way that I can figure out to even get to the
> RSTDSP parm from the "Save DDS - Create Display file" screen that you
> get upon exiting SDA.
>
> I've looked around and our existing display file objects have RSTDSP set
> to *YES.  I went ahead and asked all the programmers if anyone had
> happened to change the default on the CRTDSPF parm RSTDSP to *NO just to
> be sure and of course no one has but the default on it is *NO never the
> less and appears to have always been.
>
> Does the "Save DDS - Create Display file" when exiting SDA use the
> CRTDSPF command?
>
> I understand your reply Vern but I'm pretty sure something has change in
> the system behavior somehow at least on our system and I'd like to know
> what.
>
> John.
>
>
>