Re: [Bulk] Re: [Bulk] Re: How to diagnose a gateway problem in TCP/IP?

2006-07-31 Thread Kris Buelens
I've got a ZAPCP EXEC that can reset the invamid pasword counts for LINK and AUTOLOG (available on request), also CP SET JOURNAL OFF and ON used to clear certain counters; but not all, otherwise I woudn't have coded ZAPCP Kris, IBM Belgium, VM customer support I don't understand what you mean

Re: [Bulk] Re: [Bulk] Re: How to diagnose a gateway problem in TCP/IP?

2006-07-30 Thread Rob van der Heij
On 7/29/06, Tom Cluster [EMAIL PROTECTED] wrote: Well, I just did a test. Remember, we have no ESM. I logged on as a user who does not have LNKNOPAS. I issued a LINK command to Maint's 191 with the wrong pw 5 times, and I got this message. But when I gave it the correct password on the 6th

Re: [Bulk] Re: [Bulk] Re: How to diagnose a gateway problem in TCP/IP?

2006-07-30 Thread Tom Cluster
I don't understand what you mean by anone with TCPIP access. Are you talking about people who use TN3270 through this server? You can't be seriously saying that because of TCPIP's having LNKNOPAS that they can link to all disks, are you? Thanks for the information about journaling. I'll

Re: [Bulk] Re: [Bulk] Re: How to diagnose a gateway problem in TCP/IP?

2006-07-29 Thread Alan Altmark
On Friday, 07/28/2006 at 07:42 MST, Tom Cluster [EMAIL PROTECTED] wrote: Well, I just did a test. Remember, we have no ESM. I logged on as a user who does not have LNKNOPAS. I issued a LINK command to Maint's 191 with the wrong pw 5 times, and I got this message. But when I gave it the

Re: [Bulk] Re: [Bulk] Re: How to diagnose a gateway problem in TCP/IP?

2006-07-28 Thread Rob van der Heij
On 7/27/06, Tom Cluster [EMAIL PROTECTED] wrote: apparently some bug in the password passing routine. From what I remember it does not use the CMS tokenizer but has its own, and requires blanks around the opening parenthesis to ensure parsing. Rob

Re: [Bulk] Re: [Bulk] Re: How to diagnose a gateway problem in TCP/IP?

2006-07-28 Thread Tom Cluster
Well, I just did a test. Remember, we have no ESM. I logged on as a user who does not have LNKNOPAS. I issued a LINK command to Maint's 191 with the wrong pw 5 times, and I got this message. But when I gave it the correct password on the 6th try it worked. I suppose one way to get around