IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Error with WRITEQ - TSQ


IBM Mainframe Forums -> CICS
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
balukanna

New User


Joined: 09 Apr 2008
Posts: 41
Location: USA

PostPosted: Wed Oct 23, 2013 2:20 am
Reply with quote

Hi,

During the TSQ write, The ITEM number gets increased abnormally.

First step in the program - Delete TSQ
Second - Write TSQ (Header)
Third - Write TSQ (Detail) - Here my ITEM number is 2, executing at the first time. But After Write process the ITEM number shows some 52 or 26 something. While seeing the output in the screen, First page is being shown at the last.

I am not sure, where i am doing wrong.. I have did programs with similar logic and didn't faced such issue.

Could anyone help me on this.
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA

PostPosted: Wed Oct 23, 2013 3:21 am
Reply with quote

Is your ITEM-NUMBER defined as a binary-halfword - S9(04) COMP?

How did you determine the ITEM-NUMBER, via an INQUIRE TSQUEUE API?
Back to top
View user's profile Send private message
balukanna

New User


Joined: 09 Apr 2008
Posts: 41
Location: USA

PostPosted: Wed Oct 23, 2013 5:06 am
Reply with quote

Yes it's defined as half word binary
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA

PostPosted: Wed Oct 23, 2013 6:28 am
Reply with quote

Is the TSQ Name unique and does any other program have access to it together with your program? If your answer is NO, then you've got a real dilemma as I've never heard of an error such as this.

When you issue a WRITEQ TS, the Item-Number is automatically incremented by 1 in the CICS Internals or you have the option of specifying the ITEM and NUMITEMS (binary-halfword) in the READQ TS. If you specify NEXT (omit ITEM) in the TSQ READ, the internals will get you the NEXT Item in the TSQ. If you raise the ITEMERR, this means you've reached the end of the TSQ and there aren't any more "Records" (Items) in the TSQ. If you issue a TSQ READ, specifying a value in ITEM (omit NEXT), then you'll either get that "Record" (Item) or you'll raise the ITEMERR. In either example, specifying NUMITEMS for either type of TSQ READ might be beneficial in obtaining the actual number of Items in the TSQ.

You can also issue an INQUIRE TSQUEUE API, to obtain TSQ characteristics. The syntax for this can be found in the System Programmer Reference or you can experiment using CECI (if you're authorized and hopefully not in Production).

That's about all I can offer....
Back to top
View user's profile Send private message
balukanna

New User


Joined: 09 Apr 2008
Posts: 41
Location: USA

PostPosted: Fri Oct 25, 2013 12:19 am
Reply with quote

I found "MY" mistake..

I have 3 TSQ's in the same program..
Initially while doing delete i haven't gave the TSQ name correctly for First TSQ, so it was not deleted.
Hence During WriteQ the Item numbers were increased automatically.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CICS

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts Error while running web tool kit REXX... CLIST & REXX 5
No new posts Getting Error while trying to establi... DB2 3
Search our Forums:

Back to Top