Interesting question. This client is a TSS shop so it wouldn't be ICH408I, but
I could look in the log for a corresponding TSS message. Let's see, the
problem (as I said in a later email) turned out to be that the user ID didn't
have a GID (which I should have looked for right off). I guess
Are you seeing an ICH408I message in SYSLOG?
On Sat, 22 Jun 2024 at 05:46, Mike Schwab <
05962a42dc49-dmarc-requ...@listserv.ua.edu> wrote:
> Well, if it stopped working before the upgrade, the upgrade is not
> the problem. Possibly somebody else tried to login with the wrong
> value and
On Fri, 21 Jun 2024 15:26:16 -0400, Bob Bridges wrote:
>I was going to explain, in addition, that I did check on the ID's OMVS
>segment, and instead it dawned on me that I hadn't checked for a valid default
>group. The ID had no GID, that's all. It does now, and the problem went
>away, or at
Well, if it stopped working before the upgrade, the upgrade is not
the problem. Possibly somebody else tried to login with the wrong
value and locked it up. Has it been reset, or did somebody disable it
otherwise?
On Fri, Jun 21, 2024 at 2:11 PM Bob Bridges
I was going to explain, in addition, that I did check on the ID's OMVS segment,
and instead it dawned on me that I hadn't checked for a valid default group.
The ID had no GID, that's all. It does now, and the problem went away, or at
least I can now connect manually so I assume the script
My client just asked me to look into an FTP.bat script that started failing
after we upgraded to z/OS 2.2. It's odd; it says the PASS command fails, but
a) the password in the script matches the password that's expected, and b) it
looks like the password is being correctly transmitted during
