The AccuRecord Generic OS network version runs on Intel-based personal computers running Windows/NT.  Each PC is connected to a Novell NETWARE network which supports communication between the separate system components.  The ARGOS network programs use the SAP (Service Advertise Protocol) call to establish connections between the different components and then use IPX/SPX communications protocol for inter-module communication.  The Netware file server is used to store the ARGOS and CURE^© system files which include ARGOS executable files, ARGOS configuration files, ARGOS output files, CURE load modules, CURE support files, JCL files, and CURE data files.  The Network version of ARGOS is organized into five components: the scheduler, initiator, timeshare initiator, writer and workstation.  These components are described in the following paragraphs.

Scheduler:
The scheduler is the backbone of the ARGOS network system. It maintains and controls the connections between all other components.  When the scheduler starts it reads a configuration file into memory and then notifies the server that ARGOS is operational.  The scheduler then allows initiators, timeshare initiators and writers that it can identify and relate by node address to an entry in the configuration file, to be started.   When any of these three types of components are started the scheduler passes them their configuration information and then monitors each machine periodically.  The scheduler also monitors all ARGOS workstations.  However, it does not require any configuration information for these machines. The scheduler also maintains the system-wide serial resource protection tables and maintains a log of all system activity.

Workstation:
The ARGOS Workstation component runs on a PC under Windows/95, Windows/NT or DOS.  The PC running the Workstation component must be attached to the network either directly, or through some attachment facility such as the access server or a modem/network interface unit. Using the Workstation component, the user can submit batch jobs, access CURE through the timeshare facility, view and control the input, output, and active queues, edit JCL and source transactions, and shell out to DOS.

Initiator:
The job of the initiator is to process batch jobs.  A batch job is a unit of work defined by JCL.  JCL identifies programs to be executed and files to be used along with additional external parameters and control information. Batch jobs originate from workstation submissions. When submitted, the job is placed on an input queue based on job class and priority.  Jobs remain on the input queue until the scheduler determines that an initiator is available to process the job.  At that time the scheduler directs the initiator to begin executing a particular job.  Each initiator can process only one job at a time.  Once the job has been selected, the initiator executes the job, step by step, until the job completes, keeping the scheduler advised of the its progress.  At this point any output from the job will be found on the output queue and the initiator is available to run another job.

The initiator contains all System/370 emulation logic.

Timeshare Initiator:
The timeshare initiator can be viewed as multiple instances of an initiator running in a single machine.  In batch, having multiple copies of an initiator wouldn't buy anything since batch jobs are primarily CPU bound.  However, timesharing users have a lot of think time between transactions and it would be a waste of a high performance PC to not share it between users. When an ARGOS Workstation selects Timeshare and enters a CURE plan-id the scheduler connects the user to an available timeshare session which starts CURE.  At this point the user's workstation is acting as a terminal on the Timeshare Initiator.  All screens and keystrokes are sent over the network to the Timeshare Initiator where they are processed and returned to the user.

Writer:
The ARGOS writer services a pre-configured destination.  The configuration file associates a writer with a destination, Netware queue name, classes to be serviced and machine node id.  The writer monitors the output queue.  When it finds a job that is not held and has the correct class and destination it formats the output and spools it to the appropriate Netware queue for printing.

Hardware Requirements
The following hardware is recommended to run the ARGOS NETWORK system:

Workstation machines will operate under Windows/95, Windows/NT, or DOS.  All other machines will run under Windows NT.  The supported network operating system is Novell Netware V3.11 or higher.

  Return to our Home Page.