In the following example, an installation has several computer centers linked together by a corporate network. There is a large central site and the remaining sites are smaller and provide more localized data processing facilities. The installation has set up its CA SOLVE:FTS operational environment as follows:
The following types of private CA SOLVE:FTS users can operate in this network:
These users are responsible for maintenance and support of systems in remote sites. They need unrestricted access to facilities. They sometimes may want to transmit data sets at short notice or as an urgent requirement. These users have been given privileges that allow them to define their own transmission requests and to issue those requests at any time.
These users are usually members of a development project team. Individually, they use CA SOLVE:FTS on an infrequent basis; therefore, they do not each require CA SOLVE:FTS privileges. However, because their total intermittent requirements amount to regular usage of CA SOLVE:FTS facilities by the project team as a whole, a single member of the team can request a particular private transmission request, which has been defined for the project team.
The project team owns a data set in each site and any information transmitted for a member of the team is copied to the project data set first, and then transmitted. It is the responsibility of the team members to schedule who transmits and when they transmit.
The following categories of system users are defined:
The operators are all given system request privileges and they all have a system access mask that allows unrestricted access to any system request. None of the operators have any private privilege because none of them have any requirement to initiate their own personal transmissions, preventing them from requesting anyone else's private transmissions. They do, however, have unrestricted authority over active private requests.
The operators monitor activity and can modify initiators, interrupt transmissions, restart failed requests after the cause of failure has been eliminated, and so on.
There is a small group of users who are allocated system definition privilege. These people are part of an operational support group and are responsible for setting up the system definitions that are used to effect the transmissions associated with ordinary operations. These users are not usually allowed any other privilege, in particular, system request privilege. This isolates the authority to set up a system transmission request definition from the authority to request CA SOLVE:FTS to execute such a definition, which prevents any one individual from getting CA SOLVE:FTS to access and transmit a production data set.
The transmission classes serviced by the transmission initiators to any destination are organized by priority and category of transmission request. Initiators may be allocated high or normal priority. Initiator classes may change during the day as transmission requirements change.
Example: Transmission Classes
The following shows a typical set of initiators to a particular destination.
|
Initiator |
Classes |
Priority |
Used for |
|---|---|---|---|
|
1 |
J, K, L |
High |
High priority production transmissions |
|
2 |
A, B |
Normal |
Report transmissions |
|
3 |
A, B |
Normal |
Report transmissions |
|
4 |
A, B, C, D, E |
Normal |
Reports and general production transmissions |
|
5 |
P |
Normal |
All private transmissions |
|
616 |
|
|
Unused |