RE: Alternate to iSeries

There is no CL required and no reporting, query or other type of utilities
like that.  But we do make use of Data Queues and ICF for our mirroring.
The mirroring can be re-written to use TCP/IP.  This is a straight DDS RPGLE
server program that calls several RPGLE programs.  We have our own service
programs which is why it has to be ILE.  The only API's are for TCP/IP
communications, STD and SSL as well as that Data Queue processing.  We have
ICF over V.24 and V.35 using x.25.  Lots of communications with IVR DOS PC's
Web servers and box X running x.25.  (Not our hardware and no console so I
do not know exactly what it runs just how to communicate with it.)

The main server job is updated on a regular basis as we offer new option to
our service or receive data from a new POS terminal.  I would like that to
be the same on all platforms.  The communications can be specific to the
platform.  The data queues would be really nice to have but we can re-write
the entire system to use some other way of moving transaction data from the
comm processes to the application processes.  Currently we have 40 comm
processes queuing transactions to 3 application processes.  (Ok jobs on the
iSeries.)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, December 16, 2004 12:11 PM
To: Midrange Systems Technical Discussion
Subject: RE: Alternate to iSeries

Which also begs the questions:
API's?
CL?
Possible rewrite of commands like:  SNDDST, RUNQRY, etc
And I've got a few operations I'd wonder about in RPG that I am loathe to 
bring up because I wouldn't want anyone not to use them in case their boss 
goes off the deep end too and they have to worry about portability - 
especially since I don't know if they are even a valid concern.