|
> Would anybody happen to know of a way to determine model number, serial > number, number of processors, number of LPARs, and current LPAR through an > FTP connection? No. Why are you using FTP for this? why not use something like TELNET or REXEC? I mean, you're always talking about how you've written a 5250 emulator. Surely you could write a simple sockets program that that does nothing more than log on, print some values to the screen, and return those values? You could implement a basic NVT or VT100 interface if you didn't want all the overhead of implementing 5250. > We have a small program we upload ahead of the product in our web-based > installation utility, that retrieves that information (so a trial-period > authorization code can be automatically generated and installed) and puts > it into an escape message (using CPF9898), which was the only way I could > find at the time for a program to return its output through an FTP > connection. > > It works beautifully on V4R2 through V5R2. I think it may also work on > V3R2. But on V5R3, it fails. Instead of > > >> ftp> quote rcmd call rtnmodser > >> 550-Error occurred on command call rtnmodser. > >> 550 Model 170 Serial 1047YBM Processors 1 LPARS 01 > CurrPar 00 > >> ***************. > >> ftp> > > It comes back with > > >> ftp> quote rcmd call qgpl/rtnmodser > >> 550-Error occurred on command call qgpl/rtnmodser. > >> 550 Cause code is CPF9898; message text not available. > >> ftp> > > Yet it works fine in a terminal session. Frankly, you're using the wrong tool for the job. FTP was never designed to run commands -- the FTP standards do not include that capability. Running a command is a proprietary IBM extension to the protocol. Then, to expect errors that the command generates to be returned in a particular manner? Even though it's not documented to do so? That seems like a kludge to me. FTP was never designed for this. Use the right tool for the job. If you MUST use FTP, then generate a file and download it. That's what FTP is designed for -- downloading files.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.