When an individual separates from the university their CICS access will immediately be revoked. The date that the REVOKE status is placed on the account depends on when the individual comes off the university payroll and when the Employee Exit/Termination Form is turned into the Computing Center.
Each night the system automatically checks to see that the CWID associated with each CICS user ID is still listed as an active employee CWID. If the CWID for a user ID drops from the list of active CWIDs, that user ID is HELD on z/VM and REVOKED on z/OS. At this point the account is still fully defined, just unavailable for use.
When an employee leaves the university, they are required to carry an Employee Exit/Termination Form around to various departments to get department head signatures. The Computing Center is one of these departments. If the Computing Center receives the exit form while the person is still technically listed as an active employee, the user IDs associated with the individual will be REVOKED at that time or set to be REVOKED on the date listed on the exit form. This covers instances where a person’s last few days or weeks with the university are actually the use of annual/sick leave.
In addition to being REVOKED, the CICS user will also lose all individual access authorities to z/OS resources according to a two week automation process. When the separation is detected by the automation process, a two week timer is started. Emails are sent out notifying the individual and IT staff that the user ID has been selected for loss of CICS access. If no intervention has been made by the end of the two week process, the user ID will have all z/OS permissions removed. An individual who leaves the university and then returns at a later date, will have to request any needed CICS access through their department and from the administrative departments whose data they need access to.