Re:
> CM programs still existing in the SYS account on 7.0! Would anyone have an
> explanation of why this is so? Our system monitoring tool (SOS/3000) shows
> lots ("lots" being one of those highly technical terms) of switching between

Why?  Because:

  - some programs are OS-bound or file-system-bound, and moving them to
    NM won't appreciably help them (i.e., there might be better places to
    use the time/energy it takes to convert to NM)

  - some programs are difficult to move to NM because of the language
    they are written in (BASIC, FORTRAN/V), and the cost of porting to
    NM might be more than the value derived from being in NM.

  - some programs might use features available in CM that aren't
    readily available in NM (note: there aren't many left)
    E.g., variable-record KSAM files ... if you're file-system bound,
    you *might* get better performance from a CM program working with
    a KSAM file than from an NM program (we're *not* talking KSAM/iX here!),
    because you don't need to do switch-to-CM (which is expensive).

CM programs are a lot smaller, and that's an advantage in some cases.

Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *