|
Many thanks for all your responses. The consensus seems to create a calendar. I have not done this before so will read up on it. By the way, Blair, my programming stills aren't as good as the products Timex sells, hence the date question. At least it wasn't a TIME question. Sheri -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rpg400-l-request@xxxxxxxxxxxx Sent: January 10, 2007 9:45 PM To: rpg400-l@xxxxxxxxxxxx Subject: RPG400-L Digest, Vol 6, Issue 31 Send RPG400-L mailing list submissions to rpg400-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/rpg400-l or, via email, send a message with subject or body 'help' to rpg400-l-request@xxxxxxxxxxxx You can reach the person managing the list at rpg400-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of RPG400-L digest..." *** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful. Today's Topics: 1. Overlaying program Parmeters (Richard C Carpenter) 2. RE: Optimize *FULL (Richter,Steve) 3. Re: Optimize *FULL (Rory Hewitt) 4. RE: Optimize *FULL (Richter,Steve) 5. Re: Optimize *FULL (Simon Coulter) 6. Re: Optimize *FULL (Rory Hewitt) 7. RE: How would you code an infinite RPG loop - Was 1 <> 1 is true??? (Dave Murvin) 8. Re: Optimize *FULL (Steve Richter) 9. Re: Optimize *FULL (Simon Coulter) ---------------------------------------------------------------------- message: 1 date: Wed, 10 Jan 2007 13:49:50 -0800 (PST) from: Richard C Carpenter <richard_c_work@xxxxxxxxx> subject: Overlaying program Parmeters I am changing an RPG program called from the web by Visual basic. Original program had a limit of how many items it could display. Well there are more items that need to be displayed. And when the program started to place those items into the parameters, from a working field data structure, it went over the limit. But that's beside the point. When I try to recompile the program, to address the limits, I am have an overlay problem. There are elevan (11) parameters, 10, 7, 8, 11, 12, 80, 3, and four 30,000 in length with htmnl code and item information. The 80 length field is for error messages, and only errors have been going out with no data. I'm trying to pass the information we have on, and an error message. However, the error field is overlaying the 3 postion field, a count of how many items, and the fourteen (14) bytes of the first 30,000 field. Anyone have any suggestios? The original RPG/400 program at V5R, works; when I debug it; no overlays. We are on V5R3. Regards, Richard Carpenter. --------------------------------- Everyone is raving about the all-new Yahoo! Mail beta. ------------------------------ message: 2 date: Wed, 10 Jan 2007 17:18:04 -0500 from: "Richter,Steve" <Steve.Richter@xxxxxxxxxxxxxxx> subject: RE: Optimize *FULL -----Original Message----- From: Rory Hewitt [mailto:roryhewitt@xxxxxxxxx] Sent: Wednesday, January 10, 2007 4:42 PM To: RPG programming on the AS400 / iSeries Subject: Re: Optimize *FULL
The calls to QbnStartPreProcessor() and QbnAddAssociatedSpaceEntry() show no errors, but the call to QbnEndPreProcessor() always throws a CPF5D23 ("Source file member has been changed."). I'm stumped - I'm not actually changing the source member at all - just reading it. The change date timestamp on the member isn't changing at all...
Rory, try to delete the remove and then add the srcmbr back again. the preprocessor APIs use the associated space of the srcmbr to store some info, and I forget the details, but doing that can clear up this error in some cases ;)
Then, of course, because the QbnRetrieveAssociatedSpace() API uses a relative call stack entry rather than a qualified program name, the ability to retrieve this information is dependent on the debugged program being in the call stack. In other words, I'd need to have a call within each module I'd want to debug in this way to the procedure which retrieves the PAS and gets the source (and potentially starts debug).
pretty useless, heh? I never used it, but I suspect the pre ILE version of this api work better. When I was trying to get the associated space APIs to work I hit a hard limitation that the "associated space identifier" parm could only contain a value of *PREPROC. Depending on what you want to do, if you want your preprocessor to be able to store info in the module to be retrieved at runtime, then way to do this is to define this info as constants in the compiled code. -Steve ------------------------------ message: 3 date: Wed, 10 Jan 2007 14:34:00 -0800 from: "Rory Hewitt" <roryhewitt@xxxxxxxxx> subject: Re: Optimize *FULL Steve, Do you mean delete the *source member* and then recreate it prior to calling QbnStartPreProcessor? Thanks, Rory ------------------------------ message: 4 date: Wed, 10 Jan 2007 18:06:40 -0500 from: "Richter,Steve" <Steve.Richter@xxxxxxxxxxxxxxx> subject: RE: Optimize *FULL Yes. remove it and then add it back. This might not be your error, but what happened to me was my preprocessor code crashed halfway thru the process and the info it stores in the associated space was left hanging. When I called support I was told to remove the srcmbr and add it back to clear that space. If you get the StoreAssociatedSpace API to work I would like to know about it because it got the better of me. But I think there is still a way to do what you want, with the storing and encoding of the source code. Have the preprocessor store the code as constants in the module being compiled. Then export a procedure from the module which in effect materializes those constants as an array that is returned to the caller. -Steve -----Original Message----- From: Rory Hewitt [mailto:roryhewitt@xxxxxxxxx] Sent: Wednesday, January 10, 2007 5:34 PM To: RPG programming on the AS400 / iSeries Subject: Re: Optimize *FULL Steve, Do you mean delete the *source member* and then recreate it prior to calling QbnStartPreProcessor? Thanks, Rory
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.