The GSO OPTS record field ACCESS|NOACCESS allows use of the ACCESS command. Is there any reason why an installation would not want to change the default NOACCESS to ACCESS?
Article ID: 60785
Updated On:
Products
Issue/Introduction
The GSO OPTS record field ACCESS|NOACCESS allows use of the ACCESS subcommand.
Is there any reason why an installation would not want to change the default NOACCESS to ACCESS?
If you want to use the ACCESS subcommand then you will need to change the GSO OPTS record field NOACCESS into ACCESS.
Setting the OPTS record to ACCESS will cause the LID/UID cross-reference table to be built at the startup of ACF2.
The LID/UID cross-reference table was the biggest enhancement to the ACCESS subcommand processing.
Prior to this process, the lids database was searched for matching logonid records - which was very costly as far as performance was concerned.
Now that the table is in storage there should be no major concern.
Note: A refresh of the GSO OPTS record and a F ACF2,NEWUID operator command to build the LID/UID cross-reference table are required to activate the ACCESS subcommand.
Environment
Component:
Resolution
If you want to use the ACCESS subcommand then you will need to change the GSO OPTS record field NOACCESS into ACCESS.
Setting the OPTS record to ACCESS will cause the LID/UID cross-reference table to be built at the startup of ACF2.
The LID/UID cross-reference table was the biggest enhancement to the ACCESS subcommand processing.
Prior to this process, the lids database was searched for matching logonid records - which was very costly as far as performance was concerned.
Now that the table is in storage there should be no major concern.
Note: A refresh of the GSO OPTS record and a F ACF2,NEWUID operator command to build the LID/UID cross-reference table are required to activate the ACCESS subcommand.
Feedback
