Activate ACS for current BS2000 session
Component: | ACS |
Functional area: | File processing |
Domain: | FILE |
Privileges: | ACS-ADMINISTRATION |
Function
The system administration uses the START-ACS command to make the ACS function available to all users. Following the loading of the ACS subsystem by a START-
SUBSYSTEM command, it is then possible to make the settings required for the session by means of the ADD-ACS-SYSTEM-FILE and MODIFY-ACS-OPTIONS commands, after which the nonprivileged users can access ACS.
Format
START-ACS |
ACS-ID = *NONE / <x-string 1..8> / <c-string 1..4> ,SECURITY-LEVEL = *HIGH / *LOW |
Operands
ACS-ID =
Defines a character string which is copied into the file in encrypted form every time that a virtual alias catalog is saved (STORE-ALIAS-CATALOG), and is checked when the catalog is loaded (LOAD-ALIAS-CATALOG); if the strings do not match, the LOAD-ALIAS-CATALOG command will be rejected.
ACS-ID = *NONE
Default value: no string is declared.
ACS-ID = <x-string 1..8> / <c-string 1..4>
String (as EBCDIC characters, or in hexadecimal form) which is to be copied into the file every time that an alias catalog is saved.
SECURITY-LEVEL =
Determines whether the subsystem is to be operated as a higher security system - in the ACS sense. The main effect of the increased security requirements is on the availability of individual ACS user commands.
SECURITY-LEVEL = *HIGH
Due to the increased security requirements, the commands ADD-ALIAS-CATALOG-ENTRY, MODIFY-ALIAS-CATALOG-ENTRY and LOAD-ALIAS-CATALOG ALIAS-CAT-ID=*OWN are prohibited to the nonprivileged user.
SECURITY-LEVEL = *LOW
The security requirements are not increased; the commands mentioned above are (except where prohibited by the syntax files) available to the user.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Command executed correctly | |
1 | 0 | CMD0001 | No action |
Notes
If the ACS subsystem is terminated by a STOP-SUBSYSTEM ACS, and then later, i.e. within the same session, is restarted by a START-SUBSYSTEM, the following points should be noted:
the options set by the ACS administrator before the STOP-SUBSYSTEM continue to apply;
all the ACS system file declarations which applied before the subsystem was unloaded will still apply;
the SECURITY-LEVEL parameter must be redefined during START-ACS.
If the ACS subsystem is terminated by a STOP-SUBSYSTEM ACS, SUBSYSTEM-PARAMETER =‘RESET’, and is then restarted within the same session by a START-SUBSYSTEM, the following points should be noted:
the default declarations for the ACS options will apply
there will be no valid declarations for the ACS system files
the SECURITY-LEVEL parameter must be redefined during START-ACS.
The following always apply when the ACS subsystem is halted by a HOLD-SUBSYSTEM or unloaded by a STOP-SUBSYSTEM:
Tasks which have already called an ACS command can continue to use ACS.
Tasks which have not yet been connected to the ACS subsystem can no longer make such a connection
Tasks which were only connected to ACS as a result of a spool pubset declaration, but which have not yet themselves invoked any ACS commands, will be disconnected the next time that they call the function “Complete-Filename”.