Belkin F5D5230-F Installationshandbuch PDF herunterladen (Seite 105)

105

userids needed passwords! In such special cases, ACF2 allowed

userids to not have a password.

For these surrogate and started-task userids, we simply gave passwords

that were hard to guess, and forgot about them. We later learned that

there are RACF add-on packages that will take care of passwords for

these userids. We were also told that IBM has been requested to

provide for no-password userids.

We also found that the OPERATIONS attribute of RACF is not as

powerful as its ACF2 counterpart, the NON-CANCEL attribute.

Because of this, during testing, we found userids with OPERATIONS

attribute failing on some accesses. Most of these failures were

resolved during the tests.

GOING LIVE WITH RACF

Finally, the day came to go live with RACF. We chose a Monday, so

we had the weekend to do last-minute preparations.

On this first day, the biggest headache was not any technical difficulty,

but password changes! We had assigned new passwords to all userids.

Also, the RACF sign-on screens were slightly different. This caused

confusion among some infrequent users of the system, and they had

problems signing on to the system that first day. RACF revoked their

userids after they reached the maximum number of allowable sign-on

attempts. The Help Desk was kept busy helping these people sign on

correctly.

To ease this situation somewhat, we increased the maximum allowable

sign-on attempts in RACF, just for that first day. This gave the users

extra chances to sign on correctly that first day.

SUMMARY

Since security software is at the heart of the operating system, this type

of conversion should be handled with care. Backing out of the change

is difficult, and would affect the entire user community. For this

reason, a lot of planning and testing is required. But it can be done.

1 2 ... 100 101 102 103 104 105 106 107 108 109 110 ... 114 115

Keine Kommentare

Belkin F5D5230-F Installationshandbuch Seite 105