Author: Tracy Hansen
Subject: Read of TDQ fails in LENGERR
Posted: Wed Apr 05, 2017 12:10 am (GMT 5.5)
Basic issue: Read of TDQ fails in LENGERR even though length does not exceed the defined length.
Background: I am testing a process that is completely successful in production, but is failing in test. The process is new in test because we have moved to a new mainframe. The new mainframe had to create the TDQ for test.
This is the failing read:
EXEC CICS
READQ TD QUEUE(WS-TD-QUEUE)
INTO(WS-IMPORTED-RCD)
LENGTH(WS-IMPORTED-LENGTH)
END-EXEC.
WS-IMPORTED-LENGTH is hard coded to +10007.
The returned length upon the LENGERR is +00699.
The returned string is not accurate; only the first six characters are returned (based on a display via tracing with the IBM Debug Tool) with the rest of the string displaying as spaces.
A visual display of the TDQ in TSO shows the data set does have a length of 10007; the first record has data present through column 3415.
The database staff have confirmed that all components are set up in test as they are in production.
One of the staff suggested that perhaps something was out of sync in test, but I have not found anything that appears out of sync.
Any help would be extremely appreciated.
Thank you in advance.
Subject: Read of TDQ fails in LENGERR
Posted: Wed Apr 05, 2017 12:10 am (GMT 5.5)
Basic issue: Read of TDQ fails in LENGERR even though length does not exceed the defined length.
Background: I am testing a process that is completely successful in production, but is failing in test. The process is new in test because we have moved to a new mainframe. The new mainframe had to create the TDQ for test.
This is the failing read:
EXEC CICS
READQ TD QUEUE(WS-TD-QUEUE)
INTO(WS-IMPORTED-RCD)
LENGTH(WS-IMPORTED-LENGTH)
END-EXEC.
WS-IMPORTED-LENGTH is hard coded to +10007.
The returned length upon the LENGERR is +00699.
The returned string is not accurate; only the first six characters are returned (based on a display via tracing with the IBM Debug Tool) with the rest of the string displaying as spaces.
A visual display of the TDQ in TSO shows the data set does have a length of 10007; the first record has data present through column 3415.
The database staff have confirmed that all components are set up in test as they are in production.
One of the staff suggested that perhaps something was out of sync in test, but I have not found anything that appears out of sync.
Any help would be extremely appreciated.
Thank you in advance.