Path: utzoo!attcan!telly!lethe!torsqnt!jarvis.csri.toronto.edu!rutgers!gatech!ncar!bierstadt!morreale
From: morreale@bierstadt.ucar.edu (Peter Morreale)
Newsgroups: comp.unix.cray
Subject: Re: Whats Missing?
Message-ID: <4438@ncar.ucar.edu>
Date: 22 Sep 89 21:58:49 GMT
References: <3199@amelia.nas.nasa.gov>
Sender: news@ncar.ucar.edu
Reply-To: morreale@bierstadt.UCAR.EDU (Peter Morreale)
Distribution: comp.unix.cray
Organization: Scientific Computing Division/NCAR, Boulder CO
Lines: 30

In article <3199@amelia.nas.nasa.gov> ciotti@orville.nas.nasa.gov (Robert B. Ciotti) writes:
>If you had your wish, what would you add to UNICOS 5.0 
>or what in your opinion is missing? 
>
>
>Bob

    A decent Fortran/shell interface.  The problem with the supplied 
    interface (ishell) is that it reproduces the parents memory image.

    Users at this site (COS) are heavily dependent on Fortran-callable 
    JCL for re-start capability.  Rolling out a 5+MW job to do an
    " IERR=ISHELL('assign <args> ')" is an unacceptable solution.
    (Fortran-callable JCL also allowed access to our Mass Storage
    System through local extensions)

    Currently I am diving deep into the bowels ;-) of UNICOS to create a
    socket for such a purpose.  Good learning experience, but I'm
    surprised that some type of solution wasn't part of the plan from
    CRI.

    I understand that BSD's "vfork" solves this problem, as opposed to
    "fork" (which ISHELL uses).


-PWM
-----------------
Peter W. Morreale                   
Nat'l Center for Atmos. Research, Scientific Computing Division       
morreale@ncar.ucar.edu  (303) 497-1293