Hello: I am fairly new to the PF world so bear with me for a second while I explain my situation. I am performing a simple AGS call to return all (every page) of data and have discovered that the AGS call will begin looping after page2 has displayed successfully even though the position-to field is populated. Any help would be greatly appreciated.
What you should be doing is using the Position To field with an Inquire. Pass the value from AGS_PT_JBC_JOB_CODE to the next Inquire you perform. Your AGS call would include: &FC=I&JBC-COMPANY=71&PT-JBC-JOB-CODE=10050 to get to the 2nd page and &FC=I&JBC-COMPANY=71&PT-JBC-JOB-CODE=11040 to get to the 3rd page and so forth Why aren't you using a DME call against the HR system table JOBCODE?
i have a similar problem. I am using AGS call in a loop for the program to change some data in the AC13.1 form. The AGS query works fine when I pass the Position To field, but in this case an activity might have different set of attributes.
All the activities in AC13.1 will have the attributes whose values that I am trying to load, but they will also have other attributes which might not be the same as every other activity. When I pass FC=PageDown it only goes to the 2nd page, and I can't seem to get to 3rd or 4th page. How can I go to these pages without using the position to field?
Thanks a lot in advance
Lawson forms that have detail lines have position to fields, they are not necessarily visible on the form. If you use the AGS wizard in ProcessFlow it will show you the hidden fields as well. As a general rule (there are exceptions) the position to fields start with PT- and there may be more than one. if the key fields for the record it is read has more values than whats displayed then the rest of the key is probably hidden pt fields.
Some times you actually have to look at the COBOL logic for the Page Down to see the exceptions.
Gary Davies
www.automated-workflow.com