Fragile: All the more reason for IBM to come up with an "official" version.
I only suggested "site submit" and lpr/lpd as stopgap substitutes for the functionality. For printing, I can see MANY better alternatives than an NJE variation. There's no point to sending the report to a Linux system when you can print directly to an IP print server. I'll leave the issue of forms and fancy formatting as an exercise for the masochistic. I supported NPF on zOS here for some time, and it was a pain in the neck. The TCPIP addon for VPS is a little better, but VERY expensive. There are products that do AFP-to-PCL or Postscript translation, but they're also expensive and complicated. For job submission, there are also many alternatives. It wouldn't be hard to use the lpr mechanism to queue site submits, hiding the mechanics from the end user. When I read back through the original notes though, I got the (belated) impression that what he REALLY wants here is to send files via SENDFILE/XMIT, mainly because there's no other cheap/free method supported on zOS. (Am I right?) But in principle, we're in agreement here, near as I can tell. zOS and zVM should be trying harder to keep up with the rest of the world now they IBM has supposedly committed to Open Standards. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > David Boyes > Sent: Wednesday, March 24, 2004 10:22 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] NJE functionality using a linux server? > > > > How about sshd for USS, IBM? > > There is a port; it's more than a little fragile, though. > > > Back on the topic at hand, why not use something like "site > > submit" for incoming jobs, and LPR/LPD printing for output > > coming back? You can set up destinations via NPF (or it's > > successor) on zOS. > > Then we're back to automating FTP, and LPR/LPD don't support > forms well, > or a number of other useful printing features. It's not that there > aren't other ways to do this, it's that the other ways are poorly > integrated and really feel like what they are: afterthoughts > grudgingly > bolted on the side to make it work, rather than doing the > extra work to > make the integration seamless. > > > What is real NJE going to buy you? You can't RUN the jobs on > > the Linux node. > > Here's a few I can think of: > > Access to superior (IMHO) interactive editing environments > Access to industry standard source code management tools > Unattended operation of file transfers > Automated queuing and retry if destination host unavailble > Implied sequencing of file transfers > multifile parallel transfer support (possible with gridftp, but z/OS > doesn't speak gridftp yet w/o my Globus port) > Single auditing point for information transfer. > Single connection between hosts (easier on FWs) > TCPNJE is trivially SSL-wrappable > Transparent output routing from batch (can be done with NPF, but w/o > full forms processing capability) > etc... > > Linux/Solaris/AIX/HPUX and even the Windows goons are already moving > past LPR/LPD and SMB to IPP. Time for VM and z/OS to do the same. > Easiest way to do that: put IPP support in RSCS and use NJE from z/OS > and VM to deliver the goods to RSCS or a Linux guest. Zero > mods on z/OS, > some work on VM or Linux, everybody wins. We also need TCPNJE > support on > z/OS. > > I argued this back on the VMESA-L mailing list a while back: if > channel-attached printing is really dying off, then it's time > to finish > the job on integrating printing and output management into > RSCS and make > it the de facto output manager for VM. PRINT and friends need to start > being cognizant of that fact. It's the right thing to do. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ============================================================================== If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. <http://www.ml.com/email_terms/> ============================================================================== ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
