Topic
1 reply Latest Post - ‏2010-07-14T16:35:16Z by BradSmalley
SystemAdmin
SystemAdmin
6042 Posts
ACCEPTED ANSWER

Pinned topic Invalid segment length (LL) of [1804] in input object-Using J2C Connector

‏2008-08-04T14:42:44Z |
Hello,

I have been struggling with this issue for the past 1 week .I am using J2C Connector tools to generate beans that lets us to communicate cobol programs.

In cobol code we have declared LL as like this.

05 LL PIC S9(4) COMP.
05 ZZ PIC XX.

Using J2C Connector tools for this cobol programs(input and output records) total 5 fils are generated. Those are
InputRecord.java,OutputRecord.java,
java beans:Interface1.java,Interface1Impl.java
Command Bean: RetrieveDetails.java.

Here on i am setting all screen values and IMS related stuff in inputrecord
and executing with this input on commandbean object,then we will get the output record contains all the output data.

Here the problem is when i am setting the LL value like this and executing i am getting the follwing error.
InputRecord inputRocord = InputRecord();
inputrecord.setL1((short) 1804);

RetrieveDetails commandBean= RetrieveDetails();

commandBean.set(inputrecord);
commandBean.execute();

javax.resource.ResourceException: ICO0024E: com.ibm.connector2.ims.ico.IMSTCPIPManagedConnection@5039056a.buildInputMsg(Record)
error. Invalid segment length (LL) of 19200 in input object. com.ibm.ims.ico.IMSInputOTMAMsg@574b456a.setAppData(byte[):

And one more quetion is in set() method which type of parameter we can set?
what i think is , 1804 is total length of variables of cobol file.is it right or not?

Could anyone help me out this problem.Help would be greatly appreciated.Its very urgent..please.......

if you drop a mail also to vinayakavara@gmail.com would be better.

Thanks in advance.
venkat.
Updated on 2010-07-14T16:35:16Z at 2010-07-14T16:35:16Z by BradSmalley
  • BradSmalley
    BradSmalley
    2 Posts
    ACCEPTED ANSWER

    Re: Invalid segment length (LL) of [1804] in input object-Using J2C Connector

    ‏2010-07-14T16:35:16Z  in response to SystemAdmin
    I stuggled with this issue myself over the past two days and web searches failed to yield the answer.

    Make sure the correct environment is selected when you use the J2C Tools to create IMS/CICS Bindings. I had this problem when I improperly generated the input and output classes with "win32" selected. When I re-generated the classes with z/OS selected they worked fine. I think this is largely a big/little endian problem.

    Hope this helps.