Network Adds

Adding a network is similar to adding a job. The primary method is to use the ADD function on the DB.5 panel. For new users or users making multiple changes to their networks, other methods can be used.

If the network information already exists in machine-readable form, writing a program to produce batch terminal network commands can be an advantage. The database can then be updated using the Batch Terminal Interface (BTI) facility.

Note: For more information about BTI, the Interface Reference Guide.

The following items are something to remember when adding a network:

On the DB.5 panel, stations must be defined in the chronological order in which they are used.
The DMDNW and RUNNW commands do not add a network to the database. These commands require that the network is defined in the database with some type of schedule before the commands can act on the network.
Input networks can be connected to one or more CPU jobs, in which case, they have a predecessor/dependency relationship with those jobs. These connections are defined using the DB.3.4 panel functions.
Input networks that are not handled on an on-request basis must have a calendar-based schedule defined. This definition is done with the DB.2.2 panel.
Output networks are scheduled to be run because of their connection to a job. When the connected CPU job is scheduled into the queue, the output network is brought into the postprocess queue.
Output networks must be logically connected with the DB.3.4 panel. Scheduling parameters must be entered through the DB.2.3 panel, but the schedule is not resolved against a calendar.

(More information:

Batch Input