Who's On?

	Membership:
	Latest: Brady
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5274

	People Online:
	Visitors: 395
	Members: 0
	Total: 395

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

Looking for help with AGS Call

4 Replies

0 Subscribed to this topic

27 Subscribed to this forum

Sort:

Author

Messages

LauraP

Advanced Member Send Private Message

Posts: 28

6/21/2012 12:59 PM

We are still on release 8.0.3/Unix/Oracle.

We have several Visual Basic programs that do AGS calls to various Lawson forms (OE10, RQ10 for example).

In some cases, when passing the FC value (for a change for example) - the VB app passes a "C" and in other cases it passes the whole word "CHANGE".

We have an issue now where VB apps that used to pass the whole word 'CHANGE' via the AGS call are no longer working - they have to be changed to pass just the "C".

We are trying to figure out 2 things (because this was done back in 2004 by a developer who is no longer here):

1. What is the difference between passing "C" or "CHANGE"?
2. What would cause the requirement to change from "CHANGE" to "C" (possibly answering the first question will, by default, answer the second one)?

We have a major upgrade going on to our WMS system which interfaces with our Lawson system.

Thanks in advance - this is a high priority issue for us and I can't find anything on the KB about this.

- Laura

Kwane McNeal

Veteran Member Send Private Message

Posts: 479

6/21/2012 1:14 PM

Laura,
The requirement never changed. Lawson *did* tighten up their code. FC and _PFC have *always* been PIC X(1). The issue is that Lawson didn't bounds check the input values.

Previously, they effectively did a LEFT(1) on the input. That left them open to buffer overruns. Now they reject the value.

This was also an issue with things like COMPANY.

Historically if you passed in more than four digits, I had seen it treated as a LEFT(4), now they reject the value fully (as they should).

Your VB programmers got lucky that they could pass the same value to FC as they passed to _EVT, and in some cases _PFC.

Today, the rules are hardened, and they are
FC PIC X(1)
_PFC = same as FC
_EVT = CHANGE or ADD (I think you can pass INQUIRE, but I can't recall)

Kwane

Phil Romov

Veteran Member Send Private Message

Posts: 44

6/21/2012 3:42 PM

_EVT is actually ADD/CHG

CHANGE just seems like a gross error to me, to be supported only by mistake on lawson's part.

Extra note: the FC is program defined, it can be A, C, I, X, Y, Z, etc. But the _EVT affects how lawson interfaces with the program - on ADD there's just a basic one-way interaction, on CHG lawson first automatically inquires, then continues as if it was an "ADD".

All of this can be reviewed in lawson's "Doc for Developers: IOS Application Program Interfaces" for reference

shreekant

New Member Send Private Message

Posts: 1

5/17/2013 4:46 PM

shreekant can u explain me what is AGS calls Do?and actual what it dose?Or any link which help me to understand AGS calls?or if possible send me data mail id-:wagh.shreekant@gmail.com

Shane Jones

Veteran Member Send Private Message

Posts: 460

5/20/2013 2:14 AM

Shreekant,
Can you tell me .... Are you just looking to learn what an AGS call is compared to say... a DME?