MVSFORUMS.com

mm_ak81

Hi,

We are implementing socket programming in ADSO. The system we are trying to connect is developed in Java. In our MF we have CP1148 as code page.

Whatever text I need to transfer to other side from my socket, it expects some header information. This header information contains values like SOH, STX, ETX etc.

I defined one variable
02 START-OF-HEADER PIC X(1).

when I am trying to issue the following statement in my ADSO Process,

MOVE X'01' TO START-OF-HEADER.

it is throwing following message.

12000 MOVE X'01' TO HEADER-IN-START-OF-HEADER.
$ $
<E> DC164076 ILLEGAL DATANAME PARSED. STMT FLUSHED.
<E> DC161001 SOURCE DATANAME, EXPR, OR NUMBER NOT FOUND. STMT FLUSHED.

Can you people help me in this regard, how to handle these control characters in ADSO Dialog process?

Thanks.
Anil Manepalli
_________________
Regards,
Anil Manepalli

dbzTHEdinosauer · Posted: Mon Nov 24, 2008 10:43 am Post subject:

why is the message

mm_ak81 · Posted: Mon Nov 24, 2008 11:14 am Post subject:

This is the message I am getting

[code:1:b776344e83] 11600 INITIALIZE(HEADER-IN).
11800 MOVE 1 TO HEADER-IN-MSGCLASS.
<E> (X)
11900 MOVE X'01' TO HEADER-IN-START-OF-HEADER.

_________________
Regards,
Anil Manepalli

Nic Clouston · Posted: Mon Nov 24, 2008 3:10 pm Post subject:

If compiler option APOST is not specified then the delimiter is " not ' i.e. X"01".
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

dbzTHEdinosauer · Posted: Tue Nov 25, 2008 3:21 am Post subject:

The
_________________
Dick Brenholtz
American living in Varel, Germany

mm_ak81 · Posted: Tue Nov 25, 2008 11:35 am Post subject:

Guys,

When I pasted for first time, its a format issue. Thats the reason I pasted the error what I was getting once again.

Nic, the problem is I am compiling this piece of code thru ADSC (ADS Compiler) not thru a JCL. I tried with X"01" instead of X'01', even that also it throwed me the following error.

Nic Clouston · Posted: Tue Nov 25, 2008 4:12 pm Post subject:

My mistake - I was thinking COBOL, not ADSO. Not quite the same thing. Fortunately I have an ADSO manual at home so I have looked it up and it does not appear to have a Hexadecimal datatype - Group, EBCDIC, Zoned Decimal, Packed Decimal, Binary, Multibit Binary and Floating point but no Hexadecimal. I suggest you use binary. The example my manual gives is:

mm_ak81 · Posted: Fri Nov 28, 2008 10:22 am Post subject:

I think even Binary also I tried but it didnt fitted my requirement.

I had written a small DC Program which returns me the header and trailer which are needed for message. Its working fine.

Thanks Guys for your responses.
_________________
Regards,
Anil Manepalli