View previous topic :: View next topic
|
Author |
Message |
Satya786
New User
Joined: 02 Feb 2006 Posts: 7 Location: Denmark
|
|
|
|
Problem: User logon to the system and typed the transaction to view the amounts on the screen.The amounts are incorrect. After a minute he once again typed the same transaction and found that the amount details were correct.
They reported the problem.
Investigation: The program write the data into the TS-Queue from DB2 and populates into the screen.The data displayed as an error is the data of different user.
Progam related checks done: Initialiation,writing into the queue,picking data from database is absolutely OK.
Queue related checks done: The TS-queue name is defined as terminal-id + transaction ID.When shifting for present screen screens the queues are deleted.
Can anybody guide me what else can I need to check if this type of problem occur. |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
Depending upon how your programs write the TSQ;
If TS-queue is termID+transactionID, then if 2 different users
are using the same terminal, seems to me this could occur.
This requires reveiwing your program(s) logic. Good Luck ! |
|
Back to top |
|
|
Satya786
New User
Joined: 02 Feb 2006 Posts: 7 Location: Denmark
|
|
|
|
Do you think that same terminal can be used by 2 different users at a time...!! |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
Problem: User logon to the system and typed the transaction to view the amounts on the screen.The amounts are incorrect. After a minute he once again typed the same transaction and found that the amount details were correct. |
Sounds like the delete of the TSQ is in the wrong place. Definitely a program logic error! |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
Do you think that same terminal can be used by 2 different users at a time...!!
I certainly have never seen 2 users on same terminal at the same
time.
But I have seen more than 1 user use the same terminal at different times. Often within in minutes of each other.
You have a program logic problem. REVIEW your logic and fix it. |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
If the network autogenerates the LU name and CICS autoinstalls the four character terminal name based upon the eight character LU name, dups can occur.
Different connected regions will allow the dups to exist in a common region, not as termids, but as part of the queue naming scheme. |
|
Back to top |
|
|
Satya786
New User
Joined: 02 Feb 2006 Posts: 7 Location: Denmark
|
|
|
|
This problem occured after 6 years of the system is installed... |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
and absolutly nothing has changed. |
|
Back to top |
|
|
Satya786
New User
Joined: 02 Feb 2006 Posts: 7 Location: Denmark
|
|
|
|
Yes, there is no change in the system, not touched these programs, and around 30 users use this system every day.. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
there is no change in the system, not touched these programs |
Actually, something changed. It could be an operating system upgrade, CICS upgrade, terminal emulator change, VTAM change, system program change or something application related but working programs just don't suddenly change their behavior. If the behavior has changed, you need to find out what could be the cause and assuming that there's been no change in the system is not the way to start. |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
Robert is correct, something in the enviornment has changed, and the
programs have a bug that has always been there.
Use a debugger' to resolve the problem or hire a consultant. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
Yes, there is no change in the system, |
There may have been no intentional change, but (to echo the others) something has changed.
Is there a record of when this first happened? By chance the Monday after some weekend "unrelated" hardware/software addition/upgrade?
Knowing exactly when the problem behavior started may be a big help in determining what triggered these inconsistencies.
As was also mentioned, the problem is not new, just not discovered 'til now. |
|
Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
|
|
|
|
In order to write exclusive TSQ Queue's for a given user, you could switch to using the 16-Byte TSQ-Name option instead of the default 8-Byte name, which would then allow greater TSQ-Name uniqueness, using a format of 'USERID+EIBTRNID+EIBTRMID' or whatever format you choose.
I know this doesn't answer your question as to why this TSQ error is suddenly occurring.
Just a thought....
Regards,
Bill |
|
Back to top |
|
|
kick_support
New User
Joined: 09 Mar 2006 Posts: 2 Location: Peoria, IL
|
|
|
|
Just a far-fetched thought...
Have there been any changes to the system to delete CICS terminals after a period of inactivity? This could result in temp queues using the termid/transid naming convention getting stranded which could later be picked up if the same terminal ID is assigned to a different user via autoinstall. |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1205 Location: Dublin, Ireland
|
|
|
|
Again, a possibility....
Is there any chance that some working-storage is not re-entrant? Saw a similar problem a few years ago where a PL/1 program had STATIC variables declared. This seemed to work fine until two users executed simultaneously and one overwrote the other's working storage.
Garry. |
|
Back to top |
|
|
|