gtpd2m0pData Communications Services Reference

Installation Information

The code contained in the CRAS package is released with the following characteristics:

The degree to which the system can be controlled during online operation is based on the configuration of the command editor tables. For example, if no message is defined as restricted, the authorization function of the ZACRS message is meaningless. Hence, it is suggested that the user carefully analyze these tables to ensure their conformity to installation requirements, and modify them as appropriate. Procedures for modifying these characteristics to fit specific installation requirements have been outlined elsewhere in this manual.

With the attempt to aid the user in initially configuring the command editor tables to best utilize the support, the following discussion of the philosophy behind the design of the CRAS package is provided. Since the amount of operator involvement required to run a multiprocessor, multisubsystem TPF complex is much greater than in previous TPF systems, more system control messages (that is, commands) are necessary to run the system.

In previous releases, alternate CRAS terminals could be used to divide the workload among multiple operators, each operator having the ability to run the entire system, since all commands were accepted from any CRAS terminal. The current support provides additional ways of dividing the workload among multiple operators, while at the same time allows dynamic modification of the degree of system control. With this support, as system activity increases/decreases the need for more operators, the restricted message support can be used to dynamically modify the number of CRAS terminals which have authorization to input certain restricted messages. This facility still requires one system operator who controls the entire system, granting/rescinding authorization to other auxiliary operators as needed.

Alternatively, the operation of the system can effectively be broken down by function. For example, by defining all TAPE messages as restricted to the TAPE function, authorizing one alternate CRAS CRT to input TAPE messages, and assigning a TAPE FSC for output, the effect is a TAPE operator who has ultimate control over all tape activity. Within this scenario, the tape operator's input device is the only device (other than PRC) authorized to input tape messages, and all tape-related output messages will appear on the tape operator's hardcopy output device (the TAPE FSC). If this concept is extended to other functional areas, the effect is to functionalize the system operation. Hence, instead of requiring all operators to know all areas of the system, the system could be run with a TAPE operator, a DASD operator, a COMM operator, etc., requiring each operator to be knowledgeable in only one specific area.

In any case, the decisions for how the system will be run and controlled should be made at system installation time to provide the maximum/minimum required degree of control. It is important that the user understand the installation requirements and the use of this support in order to best define the initial CRAS configuration for his installation. Once the system is operational, the CRAS support is flexible within the confines of its initial definition. An alternative method is to change the definition online.