Re: PGUP/PGDWN Indicator Assistance

Thank you Glenn I will try that

I was thinking this would cause an error if I listed my subfile size to 1
similar to the page as I could have fifty or so records potentially in a
subfile

I'll give it a shot

Thanks

Sent from my iPhone

On Mar 4, 2016, at 1:20 PM, Glenn Gundermann <glenn.gundermann@xxxxxxxxx>

wrote:

Make sure your subfile size and subfile page have the same value.
It's called load one page at a time.


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144


On 4 March 2016 at 13:14, <RWesh@xxxxxxxxxxx> wrote:

Good Afternoon

I was hoping someone could explain to me how to properly code for an
instance when the user presses the Page Up or Page Down key while in a
subfile.

I have the following in my DDS

A DSPSIZ(24 80 *DS3)
A PRINT
A CA01(01 'MAIN MENU')
A CA02(02 'NEXT QUERY')
A CA03(03 'PREVIOUS')
A PAGEUP(81 'PAGE UP')
A PAGEDOWN(82 'PAGE DOWN')

This allows me to utilize *IN81 and *IN82 however it seems like my code

is

only run when the keys hit the end of the subfile.

For example, I have code that should evaluate a Y/N field in a subfile
record and turn on a protect indicator when one of the Page keys are
pressed.
If my subfile has 3 records the logic only runs when I press Page Down

on

the third record OR when I press Page Up on the first record. Nothing
occurs in between.

The screen only shows 1 subfile record at a time.

Please note I am coding in RPG III.

Thank you for any assistance that can be provided.





This document should only be read by those persons to whom it is

addressed

and is not intended to be relied upon by any person without subsequent
written confirmation of its contents. Accordingly, Sumitomo Machinery
Corporation disclaims all responsibility and accept no liability

(including

in negligence) for the consequences for any person acting, or

refraining

from acting, on such information prior to the receipt by those persons

of

subsequent written confirmation. If you have received this e-mail

message

in error, please notify us immediately by telephone. Please also

destroy

and delete the message from your computer. Any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this e-mail message is strictly prohibited.
--
This is the RPG programming on the IBM i (AS/400 and iSeries)

(RPG400-L)

mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)

mailing list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Email scanned & secured by the Sumitomo Chesapeake CheckPoint Firewall.

This document should only be read by those persons to whom it is addressed
and is not intended to be relied upon by any person without subsequent
written confirmation of its contents. Accordingly, Sumitomo Machinery
Corporation disclaims all responsibility and accept no liability (including
in negligence) for the consequences for any person acting, or refraining
from acting, on such information prior to the receipt by those persons of
subsequent written confirmation. If you have received this e-mail message
in error, please notify us immediately by telephone. Please also destroy
and delete the message from your computer. Any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this e-mail message is strictly prohibited.