×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 01 Feb 2013 10:29, rob@xxxxxxxxx wrote:
OK, I am thinking if your old box has TCP/IP then it is NOT M36 but
it is OS/400 with the S/36 environment installed. Even the first
AS/400's didn't have TCP/IP. Can the box do any os/400 commands at
all? Well, duh, Rob, of course it does. If he can save it to save
files it must be S/36 environment and not M36.
TCP/IP has been around since long before the OS/400 V4R3 that the OP
notes is installed, running a *M36. The above quoted reply seems to
muddle the difference between the actual system models that were
effectively the S/36 running on a RISC system and the *M36. The system
model was almost indistinguishable from an AS/400 IIRC, and was called
the "Advanced 36". The Machine-36 hosted partitions\systems were
running instead, on a RISC AS/400 with OS/400; there could be multiple
*M36 objects on one AS/400. A system running its S/36 applications
running in a "machine 36" object [see CRTM36 CL command] need not ever
have installed the S/36E feature to do that, because the applications
could all be running in those hosted "machines".
The first two lines of Jim Franz's reply earlier in the thread
suggests that the *M36 is "like the Advanced 36-236 or 436", but that it
is "hosted on a OS400"; albeit the text was rearranged from how I quoted
it here, so that may be confusing to those who are not aware of both as
being distinct entities:
http://archive.midrange.com/midrange-l/201302/msg00002.html
"M36 is a true look a like of a System 36, hosted on a OS400 - like the
Advanced 36-236 or 436
..."
I believe the *M36 also implemented virtual communication between
that system partition to the OS/400 so data could be sent betwixt; and
for all I know, there may have even been a FTP client made available to
the Advanced 36 and thus to the *M36 which was effectively that OS [SSP
on RISC].
Anyhow the old TCP/IP for OS/400 was written in PASCAL, but it did
exist, as the following IBM i 7.1 doc suggests the TCP/IP utilities were
available since before v3r1m0:
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/cl/cvttcpcl.htm
Convert TCP/IP CL Source (CVTTCPCL)
"The Convert TCP/IP CL Source (CVTTCPCL) command is used to convert
TCP/IP commands from releases prior to Version 3 Release 1 Modification
0 (V3R1M0) to the command syntax for the current release. The pre-V3R1M0
TCP/IP CL commands to be converted must exist in a source physical file.
..."
As an Amazon Associate we earn from qualifying purchases.