|
Joep, Follow this link, http://www.iseriesnetwork.com/Resources/ClubTech/TNT400/bo400ng/as400qry key.htm and http://code.midrange.com/index.php?id=c13e35a409. The OP asked about using SEU in browse mode only, also. Thank you, Matt Tyler WinCo Foods, LLC mattt@xxxxxxxxxxxxxx -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joep Beckeringh Sent: Wednesday, October 26, 2005 11:45 PM To: RPG programming on the AS400 / iSeries Subject: Re: How to track the key stroke of a screen displayed by executing a CL command inside a RPGLE program Rory, > The Cancel and Exit flags are set after every return from an IBM > program, including SEU. As Tom says, using QUSRJOBI will retrieve > these flags. I use this method from a CL program to determine whether > a user changed a batch FTP script prior to running it. Are you sure this works? You can only leave SEU with F3 in edit mode. I just tested with QUSRJOBI. First I executed STRSEU unprompted (via QCMDEXC and a wrapper) and called QUSRJOBI after. 'Cancel' en 'exit' were both '0', whether I changed the member or not. Then I executed STRSEU prompted: - When I canceled the prompt with F12 'cancel' was '1', 'exit' was '0' - When I canceled the prompt with F3 both 'cancel' and 'exit' were '0' - When I entered SEU both 'cancel' and 'exit' were '0'. The second case seems strange: I would have expected 'exit' to be '1'. Don't know why that is; documentation says no more then 'Whether the user pressed the cancel/exit key ' and 'The application or command that was called before this API determines how the key is set'. (BTW: SEU issues a message EDT0229 when it actually changes a member. In a similar case like yours I check for this message to determine whether the user changed the member.) Joep Beckeringh
As an Amazon Associate we earn from qualifying purchases.
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.