IDMS

We have an DC COBOL program that makes a call to a web service developed in Java on Linux server. The service call has been working fine until a few days ago when it stopped working. The only change we have done to the mainframe is z/OS update from 2.2 to 2.3. It is failing trying to do a WSREQUEST call to establish the connection. We have logging turned on and here is what the log messages are:

IDMS DC504700 V21 T325 IDMSWSSC START PROGRAM

IDMS DC504700 V21 T325 IDMSWSSC Start of WSREQUEST call

IDMS DC504702 V21 T325 IDMSWSSC --- ERROR: SERVICE LENGTH REQUIRED

IDMS DC504400 V21 T325 SPSDC60 00000000 00000000

IDMS DC504500 V21 T325 IDMSWSRM Start of WSRELEASE call

IDMS DC504500 V21 T325 IDMSWSRM ABOUT TO CLOSE SOCKET FOR SOCKET DESCRIP

IDMS DC504500 V21 T325 IDMSWSRM AFTER CLOSE SOCKET

IDMS DC504500 V21 T325 IDMSWSRM ** A TCP/IP ERROR HAS OCCURRED. **

IDMS DC504500 V21 T325 IDMSWSRM --- RETURN CODE: -1, NUMBER: +

IDMS DC504500 V21 T325 IDMSWSRM REASON: +0, DURING: CLOSE

IDMS DC504500 V21 T325 IDMSWSRM Request Released. Request#: 10000001

IDMS DC504500 V21 T325 IDMSWSRM End of WSRELEASE call

I have filed a ticket with CA but was wondering if anyone in the community faced a similar issue and have resolved it. The high lighted message cannot be found in any manuals. The field field WS-REQ-MSG-BUFF-LEN in record WS-REQUEST-MSG-DESCRIPTOR has been set to 669 (Request buffer in our case). Any help will be appreciated. 

Thanks

Sat Pal

Did you do a fixcat listing for category z/os 2.3 for idms? I don’t know if there ARE any fixes, but it is usually good to check

Chris Hoelscher

Technology Architect, Database Infrastructure Services

Technology Solution Services

Humana Inc.

123 East Main Street

Louisville, KY 40202

Humana.com

(502) 476-2538 or 407-7266

Thanks Chris. Yes, we had done the check.

It turned out to be that the service name was spaces. The message was not clear about the issue. CA Support helped identify the issue.

Thanks

Sat Pal

Hello Sat Pal,

Just as an FYI, we are looking into your feedback concerning the unclear message.  I've added a work item to our backlog to address this concern.

Thank you!

Nakesha Newbury

Sr. Product Owner, IDMS

Hi, regarding the comment that the message cannot be found in any manuals, you can find the explanation of all CA IDMS Messages in DocOps at: CA IDMS Messages - Home - CA IDMS Messages - CA Technologies Documentation.

Thanks,

Pam Sarantos

Sr. Information Engineer, CA IDMS

Thanks Pam. I should clarify. We did find the highlighted message in the manual, which is a generic message. The  specific component is the one that was the issue. In this case the "service length" did not mean the service request length but meant that the service name was missing. The service request length was correctly populated, I think it will be good to get some clarity in messages, if possible for these situations.  

Sat Pal

Great! Thanks for letting me know that you found the message in DocOps. I saw Nakesha's message that we are working on clarifying the message.

Pam

Hi Pam,

We have an item in the backlog to address the concern. But the solution isn't around fixing this error message, but adding additional logic that could detect other errors, and this case, be more relevant, to the real problem.

Thanks,

Nakesha Newbury

Agree completely. Logic needs to be changed for the error message to be more relevant.

Sat Pal