× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2012

Re: Issue with Protect Field Using And Indicators. V7R1

Michael,
Glad that that worked for you.

From the DDS Reference Manual:

When a message is displayed because of either the ERRMSG or the ERRMSGID
keyword, all fields on the display are kept, including the field the
message is associated with. Except for option indicators, data in the
output buffer is ignored (that is, any new data from the program is not
sent to the display).
This will explain why the field attribute did not get reset when the
ERRMSGID was in effect.

On Tue, Jul 10, 2012 at 11:19 AM, Michael Schutte <mschutte369@xxxxxxxxx>wrote:

Thanks Luis.

But I changed the ERRMSGID to use indicator 63 and it was still happening
where I had 98N62 as the protect. Anyway, it's been resolved now. I
made 63 the opposite of 62. so that it now has 98 63 on the protect. This
allows the program to work as designed. 62 is back on the ERRMSGID.



On Tue, Jul 10, 2012 at 10:33 AM, Luis Rodriguez <luisro58@xxxxxxxxx>
wrote:

Michael,

Again, it has been a long time since I have done any significant work
with
*DSPF files and, even so, I don't remember using ERRMSGID very much...

As I see it, what happened in your case was that, as soon as the ERRMSGID
was sent and "responded to" (Rest Error), the system turned off *IN62,
which was the condition specified for DSPATR(PR). The "DDS for display
Files" manual states that (emphasis are mine):

*********
The response indicator, if specified, should be the same as the option
indicator used to condition the ERRMSGID keyword. *On the subsequent
input
operation, after the display of the error message, the OS/400 program
turns
off the indicator. *
*********
Anyway, whatever the reason behind your problem was, I'm glad you could
solve it...


Best Regards,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--




On Tue, Jul 10, 2012 at 9:39 AM, Michael Schutte <mschutte369@xxxxxxxxx
wrote:

Jeff,

I don't think that is completely correct. I have resolved the issue
using
a different indicator. I'm now using indicator 63 and making it the
opposite of 62 after 62 is set. So now instead of using "98N62", I
have
"98 63" on the errmsgid and it now works as expected.

I still don't understand why 98N62 wouldn't work. But anyway, thanks
for
all your help.


On Tue, Jul 10, 2012 at 9:53 AM, Jeff Young <jyoung0950@xxxxxxxxx>
wrote:

Michael,
Using the ERRMSG/ERRMSGID keywords prevents any data or attributes to
be
changed on the screen. It will do a position cursor, reverse image
on
the
field, but will not allow any data or attributes to be changed.

As was suggested earlier, I would change the ERRMSGID to a DSPATR(RI
PC)
and add a ERRMSG field to the bottom of the screen that would be
populated
with your message text.




On Mon, Jul 9, 2012 at 4:33 PM, Michael Schutte <
mschutte369@xxxxxxxxx
wrote:

File level identifier . . . . . . . . . . . :
1120709155111
*****
Format Fields Length Identifier Type
DETALWDW 35 183 19B326CFBFDF5 WINDOW
Text . . . . . . . . . . . . . . . . . . . :

I didn't see OVRATR in DSPFD, DSPFFD or in the source.

Thank you,


On Mon, Jul 9, 2012 at 4:29 PM, Luis Rodriguez <luisro58@xxxxxxxxx

wrote:

Oops, sorry... Meant "protecting the FIELD again"...

My apologies.

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--




On Mon, Jul 9, 2012 at 3:57 PM, Luis Rodriguez <
luisro58@xxxxxxxxx

wrote:

Michael,

It has been a long time since I have written a complex 5250-DDS
program
but as I see it, after the display of the ERRMSGID, *IN62 would
be
set
to
*OFF, so the 98N62 DSPATR line would be valid, protecting the
filed
again.

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--




On Mon, Jul 9, 2012 at 3:35 PM, Michael Schutte <
mschutte369@xxxxxxxxx
wrote:

We've just upgraded to V7R1 not sure if it makes a difference.
However,
I'm having this strange issue with field protection on this
single
record
format display.

*In98 is turned on when it's time for the user to scan in a
location
to
put
product away. When 98 is on, I want to protect the @QTY field
from
being
changed. However, there's a check after the scanned location
is
validated
where the quantity entered is compared to the amount of space
that
is
left
in the scanned location. If the quantity entered is greater
than
the
room
left in the location, indicator 62 is turned on and
re-displayed
to
the
user however, the field is still protected. I'm just not
seeing
why I
cannot type in that field now. I know that "98N62" is an AND
condition.
Could someone please point out my error?

I know that 62 is turned on because the @QTY is highlighted
and
positioned
too. I know that 98 is on because the location field is still
shown
on
the
display. I've also debugged the program and checked the
values
prior
to
EXFMT being executed. I thought maybe the screen was locked
because
of
the
error. But I've pressed reset and tried, still not able to
type
in
the
field.

A @QTY 16A B 5 6

A 62 DSPATR(RI)

A 62 DSPATR(PC)

A 52 ERRMSGID(IDU0503
*LIBL/WISDOMSG
52)

A 62 ERRMSGID(CAP0001
*LIBL/ODWMSGF2
62
-

A &RPLTXT)

A 98N62 DSPATR(PR)
A* suggested putaway location and actual putaway.
A 98 11 1'Sug:'
A DSPATR(HI)
A 98 @SUGLC 16A O 11 6TEXT('Location')
A 53 ERRMSGID(ILU0504
*LIBL/WISDOMSG
53)
A 98 12 1'Loc:'
A COLOR(WHT)
A DSPATR(HI)
A 98 @LOCAT 16A B 12 6TEXT('Location')
A 53 ERRMSGID(ILU0504
*LIBL/WISDOMSG
53)

Let me know if you need more information. I cannot think of
anything
else
that you would need. Maybe a PTF is needed?

Here is a screen shot after the capacity check is made.
http://tinypic.com/r/20kf4fa/6

Thank you in advanced.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




--
Jeff Young
Sr. Programmer Analyst
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.