Re: Automate PuTTY via batch and execute the ERRLOG command

I am brand new to PuTTY. I am trying to automate retrieving ERRLOG data via
batch. FWIW, I installed “Simon Tatham Putty .76” on Windows 10 and am
using the Windows command line. Here’s where I’m at so far:



putty.exe -ssh user@SERVER -pw TheActualPassword

^ This brings up the terminal with the user successfully logged in:

Using username "user".

Last unsuccessful login: Tue Dec 26 11:26:13 EST 2023 on ssh from
111.15.171.117

Last login: Mon Mar 11 23:23:59 EDT 2024 on ssh from 111.15.171.117

$



I type in ERRLOG, press Enter, get:

IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION

60D73419 0305122424 I S vnicserver0 VNIC Client Login

<and several more lines>

$



I reviewed the documentation and discover command line options, such as -m,
which tells PuTTY to “read a remote command or script from a file”. I
created a test file named ErrlogCommands.txt, and there is one line:

ERRLOG



Now, I try:

putty.exe -ssh user@SERVER -pw TheActualPassword -m ErrlogCommands.txt



The terminal literally flashes on and then off. It took me several tries,
but I was able to capture it before it disappeared:

Using username “user”

rksh: ERRLOG: not found.



I also tried:

putty.exe -ssh user@SERVER -pw TheActualPassword -m ErrlogCommands.txt >
a.txt

but this simply created an empty file named a.txt.



PLINK looked interesting, so I tried

PLINK.exe -ssh user@SERVER -pw TheActualPassword -m ErrlogCommands.txt

No terminal popped up, but the command line had this response:

Access granted. Press Return to begin session. (I pressed Enter here, then
got:)

rksh: ERRLOG: not found.



What am I missing? Does the ErrlogCommands.txt file require control
characters of some sort?



- Dan
--
This is the PC Technical Discussion for IBM i (AS/400 and iSeries) Users
(PcTech) mailing list
To post a message email: PcTech@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/pctech.