OPNO field mistake when inserting operation via REXX/PIF

autobox · New User Joined: 19 Aug 2005 Posts: 51

Hi All,

I drafted a REXX to run some adhoc jobs by scheduling them in an OPC application, and I referred to OPC/TWS sample EQQPIFOP to insert operations. The rexx uses a function to transfer the operation OPNO into OPC/TWS format:

prino · Posted: Tue Apr 24, 2012 1:25 pm

And if my grandfather had been a woman, she would have been my grandmother.

Your post is a great example of posting something that is totally useless for each and every one of us. You show some command ("FWDHEX") some output, but nothing in between.

Try a

autobox · New User Joined: 19 Aug 2005 Posts: 51

Hi,

Let me clarify something:
1. FWDHEX is the source code from IBM supplided sample EQQPIFOP, I don't think it can be paste here. Please refer to the supplied sample for details.
2. Everything goes well in my exec. Just before the instert the OPNO is shown what I wanted, but in the OPC application occurrance, it turns strange.

Thanks.

PeterHolland · Posted: Tue Apr 24, 2012 2:01 pm

You changed or took code from EQQPIFOP. So my guess is that you messed up the parameterlist to EQQYCOM.
Does the original sample works as expected?

And for the rest what Prino commented.

autobox · New User Joined: 19 Aug 2005 Posts: 51

I did not make any changes to EQQYCOM parameter list from EQQPIFOP. If the problem is parameter list, why only 130 and 150 turned wrong?
And I traced my code, everything goes well before the insert.

And, I tested this strange thing with little changes to the original sample EQQPIFOP. The same thing happened.

Thanks.

autobox · New User Joined: 19 Aug 2005 Posts: 51

Found the problem: a subroutine translated the OPNO value.

Thanks guys!