DataMuseum.dk

Presents historical artifacts from the history of:

CR80 Wang WCS documentation floppies

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about CR80 Wang WCS documentation floppies

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦b41a044f5⟧ Wang Wps File

    Length: 5476 (0x1564)
    Types: Wang Wps File
    Notes: PROP F DEV. SYSTEM        
    Names: »3905A «

Derivation

└─⟦2939611b6⟧ Bits:30006177 8" Wang WCS floppy, CR 0350A
    └─ ⟦this⟧ »3905A « 

WangText




…02… 3905A/jaa 

…02… AG/830805…02……02…#
PROPOSAL FOR DEVELOPMENT SYSTEM
…02……02…CAMPS









                    T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲




  1 DEVELOPMENT SYSTEM - WHAT IS RATIONAL .....     
    FOR CONFIGURATION? ........................     

  2 WHY CAN'T THE DEVELOPMENT SYSTEM BE .......     
    COMBINED WITH AN OPERATIONAL SITE? ........     

  3 WHY NOT COMBINE DEVELOPMENT & TDS SYSTEMS?.     

  4 WHY NOT COMBINE DEVELOPMENT/REF.SYST ......     

  5 WHY CAN'T THE REF.SYSTEM DRIVE ITSELF? ....     


1 D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲S̲Y̲S̲T̲E̲M̲ ̲-̲ ̲W̲H̲A̲T̲ ̲I̲S̲ ̲R̲A̲T̲I̲O̲N̲A̲L̲ ̲F̲O̲R̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲?̲

         .5 VDUs           -    a number of people may work
                                in parallel on different problems.

         .2 DISCS               2 x SMDs for copying purposes
                                disc/disc for config. management
                                + preparation for issue.

         .2xFloppy discs   -    For preparation and incorporation
                                of small changes.

                           -    For programmer files prior to
                                passing to librarian (configuration
                                control).

                           -    For incorporation into library
                                files by librarian.

         . Line Printer    -    For fast output of listings
                                and test results.

                           -    Shared between users to save
                                costs.

         . Tape Unit       -    For archive purposes

                           -    For capture of NICS-TARE routing
                                data base or other IBM compatable
                                data.

         . KEY/PRINTER
           CONSOLE         -    To record error codes & results.
                                Reasons for failure


      2 W̲H̲Y̲ ̲C̲A̲N̲'̲T̲ ̲T̲H̲E̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲S̲Y̲S̲T̲E̲M̲ ̲B̲E̲ ̲C̲O̲M̲B̲I̲N̲E̲D̲
                 ̲W̲I̲T̲H̲ ̲A̲N̲ ̲O̲P̲E̲R̲A̲T̲I̲O̲N̲A̲L̲ ̲S̲I̲T̲E̲?̲


         I̲M̲P̲A̲C̲T̲ ̲O̲N̲ ̲O̲P̲N̲L̲ ̲S̲I̲T̲E̲ ̲O̲F̲ ̲L̲I̲M̲I̲T̲E̲D̲ ̲D̲E̲V̲E̲L̲ ̲C̲A̲P̲.̲

         a.   A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲

              .      No automatic switchover to the redundant
                     hardware is possible. Must be manual. This
                     could cause loss of the jobs in progress
                     on the on-line and off-line side with possible
                     disc/data corruption.
                     Hence loss two ways

              .      Start-up from SMD is impossible unless
                     system disk is manually loaded.

              .      Hardware has to be reconfigured so that
                     devices assigned to on and off-line revert
                     to original configuration.

         b.   F̲a̲c̲i̲l̲i̲t̲i̲e̲s̲

              .      Retrieval becomes impossible if off-line
                     disc is in use.

              Problems are because of shared disks and use of
              redundant equipment provided for availability
              purposes. Availability depends critically on the
              switchover time to redundant equipment which must
              be as short as possible. It involve minutes for
              manual operation whereas automatic switchover
              normally takes place in seconds.

         c.   S̲W̲

              OFF LINE SW IS: completely different from on-line.
              


         I̲M̲P̲A̲C̲T̲ ̲O̲N̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲S̲Y̲S̲T̲E̲M̲ ̲O̲F̲ ̲C̲O̲M̲B̲I̲N̲A̲T̲I̲O̲N̲ ̲W̲I̲T̲H̲ ̲O̲P̲N̲L̲
         ̲S̲Y̲S̲T̲E̲M̲

         a.   D̲i̲s̲c̲ ̲U̲s̲e̲

              .      No disc/disc copy is possible since another
                     SMD not available.

              .      MMD not available due to mirrored disc
                     arrangement in CAMPS.

         b.   P̲r̲i̲n̲t̲e̲r̲

              .      No fast printer with paralled interface
                     available.

         c.   T̲a̲p̲e̲ ̲U̲n̲i̲t̲

              .      No tape unit available.

         S̲U̲M̲M̲A̲R̲Y̲     -     HW required is different

                     -     SW used is different

                     -     Combination reduces capability of
                           both systems. Availability and facilities
                           of OPNL System down. Necessary features
                           of Development System impossible.


        3 W̲H̲Y̲ ̲N̲O̲T̲ ̲C̲O̲M̲B̲I̲N̲E̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲&̲ ̲T̲D̲S̲ ̲S̲Y̲S̲T̲E̲M̲

         E̲f̲f̲i̲c̲i̲e̲n̲c̲y̲

         .    Cannot be used concurrently for both tasks.

         .    Software packages are completely different and
              assume different hardware configuration.

         .    HW Configuration would have to be switched one
              to another with possible degradation. HW required
              is different.

         .    Development System & TDS will be heavily used
              and TDS will be left running for long periods
              - perhaps days/weeks testing the software.

              e.g.   recalcitrant faults
                     or regression tests

              Remember that the system underwent about 100 days
              of test prior to first release. To re-release
              a certified system will need extensive test time.
              The TDS will just n̲o̲t̲ be available for other purposes.


          4 W̲H̲Y̲ ̲N̲O̲T̲ ̲C̲O̲M̲B̲I̲N̲E̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲/̲R̲E̲F̲ ̲S̲Y̲S̲T̲

         .    Ceases to be a reference system if split in two
              for this purpose.

         .    Does not have all hardware required for all functions
              (ADDING IT IS COUNTER TO REF.SYSTEM)

         .    In some cases the failures invoked will be due
              to dualised nature of system - such faults cannot
              be investigated if system is split. (COUNTER TO
              PURPOSE OF REF.SYSTEM)

         .    Impossibility of use of MMD's as configured for
              on line/off line work.

         .    Software for development & operations are completely
              different.

         .    Ref.Systems will be almost always up & running
              tests.

         .    Interference with ref. system connectivity (VDUs
              etc)

         I̲n̲ ̲s̲u̲m̲      -     HW required is different

                     -     To add HW to ref. system makes it
                           a non reference system.



      5 W̲H̲Y̲ ̲C̲A̲N̲'̲T̲ ̲T̲H̲E̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲ ̲S̲Y̲S̲T̲E̲M̲ ̲D̲R̲I̲V̲E̲ ̲I̲T̲S̲E̲L̲F̲?̲

         a.   Splitting reference system and putting different
              SW on standby makes it a n̲o̲n̲ r̲e̲f̲e̲r̲e̲n̲c̲e̲ system.

         b.   Failures having to do with SW over start-up cannot
              be found.

         c.   Number of ports on Reference System would have
              to be increased.

         d.   SW is completely different from operational SW.

         e.   Off line features of Operational SW impossible
              e.g. retrieval.

         H̲e̲n̲c̲e̲:      -     HW required is different
                           SW is different
                           Impossible to use it as a reference
                           system.
                           Degradation of facilities.
                           Inconvenient.