RE: [U2] Universe SHOW Command and Group Locks
I wasn't aware of the PAKTIME param. Thanks for the pointer. Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ray Wurlod Sent: Thursday, November 11, 2004 3:25 PM To: [EMAIL PROTECTED] Subject: Re: [U2] Universe SHOW Command and Group Locks If you're part way through a group with a LIST (or other query, including SHOW) a group latch is held indicating that it's not desirable for the group to be updated. This can be important if the group is heavily overflowed. After a certain amount of time (configured by the PAKTIME tuneable - PAK stands for "press any key"), the group latch is released. You can ameliorate your situation by reducting PAKTIME from its default of five minutes to, say, one or two minutes, which should be long enough for most folks to inspect a screen full of information. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe SHOW Command and Group Locks
Once upon a time, on a McDonald Douglas system I was doing a LIST and got a GFE. When we tried to figure out why, it turned out that the only possibility was the next record in the group that was displaying had been deleted, so it wasn't a 'real' GFE (we used to call them 'Gone For Ever'). I imagine the lock is to prevent false reporting of GFE's to people listing data..don't know for sure, just a guess. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott Ballinger Sent: Thursday, November 11, 2004 13:16 To: [EMAIL PROTECTED] Subject: RE: [U2] Universe SHOW Command and Group Locks Ok, I am confused. Under what circumstances does a LIST... statement hold a lock? Certainly such a lock would not be an item-lock. If LIST actually sets group locks, those locks would only be held during the group read and would be released immediately after. I tries LIST.READU EVERY and it never shows any group locks stemming from LIST... Is there somewhere else I should be looking to see these locks? Or is this a UD thing in spite of the subject line? Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Leach Sent: Thursday, November 11, 2004 11:21 AM To: [EMAIL PROTECTED] Subject: RE: [U2] Universe SHOW Command and Group Locks Anthony, One thing you might want to look at is the PAKTIME tuneable. This holds the number of seconds the system will wait at a 'Press any key to continue' message before releasing a held group lock. It defaults to 300: you might want to reduce that. Another option might be to set an autologout for that user. AFAIR the group lock is set by the list processor scanning the group, so anything that takes the list out of this situation will help. For example, a paragraph to DIVERT.OUT the listing and then show the final results should bypass this issue. Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Dzikiewicz Sent: 11 November 2004 16:52 To: [EMAIL PROTECTED] Subject: [U2] Universe SHOW Command and Group Locks Hello Everyone, The situation is this. A user is running a paragraph from a menu. That paragraph simply LISTs the contents of a file. When there is more than one page of data to display, you get the "press any key" message. We have had situations when the person doing this LIST has walked away from the terminal and caused recordlock situations for other users. Mostly all of our READU's have LOCKED clause that gets STATUS() and reports the user number that is holding them up. In this case, I don't believe the locked clause is kicking in (I would have to further test on this not 100% sure). So, what happens is that the guy that walked away from his list starts to lockup other people. Im not sure of the inner workings here on the LIST, but I think I remember it having something to do with a group lock ? I was wondering if anyone would know if switching to the SHOW command would overcome the problem. It's kind of a hard one to test, because it doesn't happen all the time either. I thought someone with internals knowledge might shed some light on this for me. Thanks Anthony Dzikiewicz --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe SHOW Command and Group Locks
Well, that's what I like about this list. You learn something new every day. After seeing Ray's post (he is exactly right) I tested this circumstance with a modulo 1 file, and yes it happens as described. You cannot readu or write a record in the affected group because of the group lock asserted by the LIST command. Weird. I had never heard of nor seen this before. Obviously that's why the PAKTIME parameter was introduced... Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ray Wurlod Sent: Thursday, November 11, 2004 12:25 PM To: [EMAIL PROTECTED] Subject: Re: [U2] Universe SHOW Command and Group Locks If you're part way through a group with a LIST (or other query, including SHOW) a group latch is held indicating that it's not desirable for the group to be updated. This can be important if the group is heavily overflowed. After a certain amount of time (configured by the PAKTIME tuneable - PAK stands for "press any key"), the group latch is released. You can ameliorate your situation by reducting PAKTIME from its default of five minutes to, say, one or two minutes, which should be long enough for most folks to inspect a screen full of information. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe SHOW Command and Group Locks
Ok, I am confused. Under what circumstances does a LIST... statement hold a lock? Certainly such a lock would not be an item-lock. If LIST actually sets group locks, those locks would only be held during the group read and would be released immediately after. I tries LIST.READU EVERY and it never shows any group locks stemming from LIST... Is there somewhere else I should be looking to see these locks? Or is this a UD thing in spite of the subject line? Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Leach Sent: Thursday, November 11, 2004 11:21 AM To: [EMAIL PROTECTED] Subject: RE: [U2] Universe SHOW Command and Group Locks Anthony, One thing you might want to look at is the PAKTIME tuneable. This holds the number of seconds the system will wait at a 'Press any key to continue' message before releasing a held group lock. It defaults to 300: you might want to reduce that. Another option might be to set an autologout for that user. AFAIR the group lock is set by the list processor scanning the group, so anything that takes the list out of this situation will help. For example, a paragraph to DIVERT.OUT the listing and then show the final results should bypass this issue. Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Dzikiewicz Sent: 11 November 2004 16:52 To: [EMAIL PROTECTED] Subject: [U2] Universe SHOW Command and Group Locks Hello Everyone, The situation is this. A user is running a paragraph from a menu. That paragraph simply LISTs the contents of a file. When there is more than one page of data to display, you get the "press any key" message. We have had situations when the person doing this LIST has walked away from the terminal and caused recordlock situations for other users. Mostly all of our READU's have LOCKED clause that gets STATUS() and reports the user number that is holding them up. In this case, I don't believe the locked clause is kicking in (I would have to further test on this not 100% sure). So, what happens is that the guy that walked away from his list starts to lockup other people. Im not sure of the inner workings here on the LIST, but I think I remember it having something to do with a group lock ? I was wondering if anyone would know if switching to the SHOW command would overcome the problem. It's kind of a hard one to test, because it doesn't happen all the time either. I thought someone with internals knowledge might shed some light on this for me. Thanks Anthony Dzikiewicz --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe SHOW Command and Group Locks
If you're part way through a group with a LIST (or other query, including SHOW) a group latch is held indicating that it's not desirable for the group to be updated. This can be important if the group is heavily overflowed. After a certain amount of time (configured by the PAKTIME tuneable - PAK stands for "press any key"), the group latch is released. You can ameliorate your situation by reducting PAKTIME from its default of five minutes to, say, one or two minutes, which should be long enough for most folks to inspect a screen full of information. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe SHOW Command and Group Locks
Anthony, One thing you might want to look at is the PAKTIME tuneable. This holds the number of seconds the system will wait at a 'Press any key to continue' message before releasing a held group lock. It defaults to 300: you might want to reduce that. Another option might be to set an autologout for that user. AFAIR the group lock is set by the list processor scanning the group, so anything that takes the list out of this situation will help. For example, a paragraph to DIVERT.OUT the listing and then show the final results should bypass this issue. Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Dzikiewicz Sent: 11 November 2004 16:52 To: [EMAIL PROTECTED] Subject: [U2] Universe SHOW Command and Group Locks Hello Everyone, The situation is this. A user is running a paragraph from a menu. That paragraph simply LISTs the contents of a file. When there is more than one page of data to display, you get the "press any key" message. We have had situations when the person doing this LIST has walked away from the terminal and caused recordlock situations for other users. Mostly all of our READU's have LOCKED clause that gets STATUS() and reports the user number that is holding them up. In this case, I don't believe the locked clause is kicking in (I would have to further test on this not 100% sure). So, what happens is that the guy that walked away from his list starts to lockup other people. Im not sure of the inner workings here on the LIST, but I think I remember it having something to do with a group lock ? I was wondering if anyone would know if switching to the SHOW command would overcome the problem. It's kind of a hard one to test, because it doesn't happen all the time either. I thought someone with internals knowledge might shed some light on this for me. Thanks Anthony Dzikiewicz --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/