Focal Point
[SOLVED] COMP-3 field value being identified as an amper variable.

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/8987013686

May 03, 2017, 12:04 AM
JimmyRedBank
[SOLVED] COMP-3 field value being identified as an amper variable.
The problem, essentially, appears to be that a COMP-3 field value, which contains a hex value of ‘50’ (which is the hex representation of an ‘&’), is being treated as an Amper Variable. This causes an error, because the Amper Variable is not resolved, and prevents the rest of the procedure being completed.

TABLE FILE H2RSKWBL
PRINT D_CLAUSES AS CLAUSES
BY D_RISK_KEY AS COY_RISK_KEY
WHERE H2RSKWBL.RISK_NO EQ ZRISKKE1.RISK_NO
AND H2RSKWBL.DATE_EFFECTIVE EQ
ZRISKKE1.DATE_EFFECTIVE
WHERE D_CLAUSES NE ' '
ON TABLE HOLD AS H2RSKBLX END
NUMBER OF RECORDS IN TABLE= 3 LINES= 3
HOLDING...
ERROR AT OR NEAR LINE 2 IN PROCEDURE EXZURRSAFOCEXEC
(FOC295) A VALUE IS MISSING FOR: BUILDERS

The following shows the hex value of the data and it can be seen, clearly, where the
“&..BUILDERS” variable is coming from.

The rejected Amper Variable actually spans two fields, neither of which are referenced in the query.

NSW...............H.....&..BUILDERS OPEN COVER
DEE000000000021000C00000500CECDCCDE4DDCD4CDECD
52600000000007000080000200F2493459206755036559

A section of the MFD details for the data in question follows, beginning with
‘RSKW_RISK_STATE_BL’ (‘NSW’ in the details above), and ending with the involved fields, ‘RSKW_RATE_BL’ (8 bytes immediately prior to 'BUILDERS', above) and
‘RSKW_RISK_DET_BL_01’ (starting with
‘BUILDERS’, above).

FIELDNAME =RSKW_RISK_STATE_BL ,E24 ,A003 ,A03,$
FIELDNAME =RSKW_CO_INS_BL ,E25 ,P004 ,P08,$
FIELDNAME =RSKW_SUM_INS_BL ,E26 ,I09 ,I04,$
FIELDNAME =RSKW_EXCESS_BL ,E27 ,I09 ,I04,$
FIELDNAME =RSKW_RATE_BL ,E28 ,P7.07 ,P08,$
FIELD = RSKW_RISK_DET_BL_01 ,E29 ,A060 ,A60,$

Being a test environment, I was able to delete the offending record and rerun the extract, only for it to fall over at the next problem ‘variable’.

This file has been processed four times, in succession, printing different fields, before it fails in this, the fifth execution.

I have set this up in a stand-alone test, and it completes successfully.

This is my first time on this forum, for many years, and I apologize for not being able to explain my problem better. I would have liked to include a few images, but wasn't able to determine how to do that.

Any assistance would be greatly appreciated.

This message has been edited. Last edited by: FP Mod Chuck,


WebFOCUS 7.7.05
IBM MVS 7.7.03 / ZOS 10.1
Text, Excel, PDF
May 03, 2017, 02:02 AM
Waz
Hey Jimmy,

Hows it going ?

so it fails on reading the data ? or writing it to the hold file ?

It is interesting that it says ERROR AT OR NEAR LINE 2....


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

May 03, 2017, 04:18 AM
Danny-SRL
Hi Jim,

Could this have something to do with the last line of your request:
ON TABLE HOLD AS H2RSKBLX END

END should always be on a line by itself

About your data, is it EBCDIC? If so, the HEX of NSW should be D5E2E6. If not, then what is it?


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

May 04, 2017, 12:59 AM
JimmyRedBank
Hi Waz. Everything is going well, thank you, as I hope it is with yourself.
Thanks to both of you for responding to my request. I have found out what the cause of dilemma was, and it has nothing to do with the direction I had taken. It was the result of sloppy coding (not mine) and naming conventions, which resulted in a "-INCLUDE" of a HOLD file, literally reading each record as a line of code.
All good now.
Jimmy


WebFOCUS 7.7.05
IBM MVS 7.7.03 / ZOS 10.1
Text, Excel, PDF
May 04, 2017, 01:43 AM
Waz
Sloppy coding...

Eeker

Good to see its all OK now.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!