Modify SDF parameters
Component: | SDF |
Functional area: | SDF control |
Domain: | SDF |
Privileges: | TSOS |
Routing code: | * |
Function
The MODIFY-SDF-PARAMETERS command enables systems support to exchange the system syntax file or subsystem syntax files, to allocate group syntax files to users and to define system-wide LOGON or LOGOFF procedures (each consisting of a call procedure and an include procedure).
Systems support can also define when and for how long these declarations are to take effect:
effective immediately for the current session only
effective immediately for an unlimited time
effective as of the next session for an unlimited time.
The definitions are entered in the SDF parameter file. The name of the SDF parameter file is defined in the DSSM catalog for SDF. If no SDF parameter file was entered there, the SDF parameter file with the default name $TSOS.SYSPAR.SDF is cataloged. If no SDF parameter file exists, it is created with the name from the DSSM catalog or with the default name.
A user is assigned a group syntax file indirectly with use of user catalog . A profile ID (PROFILE-ID operand in the ADD-USER/MODIFY-USER-ATTRIBUTES command; output in PROFILE-ID field via SHOW-USER-ATTRIBUTES) may be entered in the user catalog. The SDF parameter file contains the allocations of profile IDs to group syntax file, which are assigned to a user with the corresponding profile ID.
Since an assigned group syntax file is activated during LOGON processing, any modification in the SDF parameter file or in the user catalog is effective only for tasks whose LOGON is issued afterwards. An exchange of the system syntax file, however, also affects running tasks.
An SDF parameter file can be created or modified off-line using the SDF-PAR utility routine. This utility is described in the “SDF Dialog Interface” manual [15].
Format
MODIFY-SDF-PARAMETERS | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
SCOPE =
Specifies the scope of the activation which is being made.
For SCOPE = *TEMPORARY or *PERMANENT, it is not possible to deactivate the group syntax file, which belongs to the systems support profile ID. For SCOPE=*PERMANENT or *NEXT-SESSION, an SDF parameter file is created if it does not already exist.
SCOPE = *TEMPORARY
For a system syntax file:
The specified subsystem syntax file is activated or deactivated system-wide for all user jobs. However, it is not entered in the SDF parameter file and is ignored for the subsequent session.
For a subsystem syntax file:
The specified subsystem syntax file is activated or deactivated system-wide for all user jobs. However, it is not entered in the SDF parameter file and is ignored for the subsequent session.
For a group syntax file:
The specified group syntax file is assigned to the specified profile ID. This assignment only takes effect for subsequent user jobs (from the next LOGON in the current session). User jobs which are already in progress are not affected by the change.
The specified group syntax file is not entered in the SDF parameter file and is therefore ignored for the subsequent session. In the case of a deactivation (*NONE), the existing profile ID and its associated group syntax file name are not deleted from the SDF parameter file.
With SYSTEM-LOGON-PROC or SYSTEM-LOGON-INCL = *NO:
Deactivates the system-wide LOGON procedure (call or include procedure) for the next LOGON processing activities in the current session. The SDF parameter file is not modified.
With SYSTEM-LOGON-PROC or SYSTEM-LOGON-INCL = <filename 1..54> or *STD:
Activates the specified system-wide LOGON procedure (call or include procedure) for the all subsequent LOGON processing activities in the current session. As the SDF parameter file is not modified, this specification will apply only for the current session.
With SYSTEM-LOGOFF-PROC or SYSTEM-LOGOFF-INCL = *NO:
The system-wide LOGOFF procedure is deactivated for all subsequent LOGOFF processing in the current session. The SDF parameter file is not changed.
With SYSTEM-LOGOFF-PROC or SYSTEM-LOGOFF-INCL = <filename 1..54> or *STD:
The specified system-wide LOGOFF procedure is activated for all subsequent LOGOFF processing in the current session. Since the SDF parameter file is not modified, the specification applies only to the current session.
SCOPE = *PERMANENT
For a system syntax file:
The specified system syntax file is activated system-wide for all user jobs. In addition, the system syntax file name is entered in the SDF parameter file. It is therefore used in the next session.
For a subsystem syntax file:
The specified subsystem syntax file is activated system-wide for all user tasks. In addition, the syntax file name is entered in the SDF parameter file; it is therefore used in the next session. If a subsystem syntax file is being deactivated, the names of the subsystem and the associated subsystem syntax file are deleted from the SDF parameter file.
For a group syntax file:
The specified group syntax file is assigned to the specified profile ID. This assignment only takes effect for subsequent user jobs (from the next LOGON in the current session). User jobs which are already in progress are not affected by the change.
The specified group syntax file is entered in the SDF parameter file and is therefore used in the next session. In the case of a deactivation (*NONE), the existing profile ID and its associated group syntax file name are deleted from the SDF parameter file.
With SYSTEM-LOGON-PROC or SYSTEM-LOGON-INCL = *NO:
Deactivates the system-wide LOGON procedure (call or include procedure) for the next LOGON processing activities in the current session. Its name is deleted from the SDF parameter file. If one is available, the system-wide LOGON procedure with the default name will be used, starting from the next session.
With SYSTEM-LOGON-PROC or SYSTEM-LOGON-INCL = <filename 1..54> or *STD:
Activates the specified system-wide LOGON procedure (call or include procedure) for the all subsequent LOGON processing activities in the current session. Its name is stored in the SDF parameter file, and will therefore be used again in the next session.
With SYSTEM-LOGOFF-PROC or SYSTEM-LOGOFF-INCL = *NO:
The system-wide LOGOFF procedure is deactivated for all subsequent LOGOFF processing in the current session. Its name is deleted from the SDF parameter file. If present, the system-wide LOGOFF procedure with the default name is used as of the next session.
With SYSTEM-LOGOFF-PROC or SYSTEM-LOGOFF-INCL = <filename 1..54> or *STD:
The specified system-wide LOGOFF procedure is activated for all subsequent LOGOFF processing in the current session. Its name is stored in the SDF parameter file and is therefore also evaluated in the following session.
SCOPE = *NEXT-SESSION(...)
For a system syntax file:
The specified system syntax file name is stored in the SDF parameter file, and will be used in the next session. The current session is not affected by this.
For a subsystem syntax file:
The specified subsystem syntax file name is stored in the SDF parameter file, and will be used in the next session. The current session is not affected by this. If a subsystem syntax file is being deactivated, the names of the subsystem and the associated subsystem syntax file are deleted from the SDF parameter file (the current session is not affected by this).
For a group syntax file:
The specified group syntax file is assigned to the specified profile ID in the SDF parameter file. This assignment only takes effect in the next session. User jobs which are already in progress, and subsequent ones in the present session, are not affected by the change. In the case of a deactivation (*NONE), the existing profile ID and its associated group syntax file name are removed from the SDF parameter file. The group syntax file which belongs to the systems administration profile ID need only be shareable if it will also be used by other user IDs.
The specified syntax file name is not checked before being stored in the SDF parameter file. Checking will take place in the next session.
With SYSTEM-LOGON-PROC or SYSTEM-LOGON-INCL = *NO:
The name of the system-wide LOGON procedure (call or include procedure) is deleted from the SDF parameter file. This has no effect on the current session. If one is available, the system-wide LOGON procedure with the default name will be used, starting from the next session.
With SYSTEM-LOGON-PROC or SYSTEM-LOGON-INCL = <filename 1..54> or *STD:
The name of the specified system-wide LOGON procedure (call or include procedure) is stored in the SDF parameter file. This specification will apply from the next session, and has no effect on the current session.
With SYSTEM-LOGOFF-PROC or SYSTEM-LOGOFF-INCL = *NO:
The name of the system-wide LOGOFF procedure is deleted from the SDF parameter file. If available, the system-wide LOGOFF procedure with the default name is used as of the next session. This specification does not affect the current session.
With SYSTEM-LOGOFF-PROC or SYSTEM-LOGOFF-INCL = <filename 1..54> or *STD:
The name of the specified system-wide LOGOFF procedure is stored in the SDF parameter file. The specification applies as of the next session and does not affect the current session.
PARAMETER-FILE-NAME = *CURRENT / <filename 1..54>
Specifies the name of the parameter file which is to be created or updated.
PARAMETER-FILE-NAME = *CURRENT
Identifies the parameter file name for the current session.
SYNTAX-FILE-TYPE =
Specifies the type of syntax file concerned.
SYNTAX-FILE-TYPE = *SYSTEM(...)
The syntax file is a system file.
NAME = <filename 1..54>
Specifies the name of the file to be used as the (basic) system syntax file.
SYNTAX-FILE-TYPE = *GROUP(...)
The syntax file is a group file.
NAME =
Specifies the name of the file to be used as the group syntax file.
NAME = *NONE
Deletes the assignment of the group syntax file to the specified profile ID.
NAME = <structured-name 1..30>
The specified group syntax file is assigned to the specified profile ID.
PROFILE-ID = <structured-name 1..30>
Defines the profile ID which was (or is to be) assigned to the group syntax file.
HIERARCHY =
Specifies whether the SDF file hierarchy is to be retained for the syntax analysis of the commands/statements in a user job with the specified profile ID, i.e. whether the system syntax file is to be referred to in making the syntax analysis.
HIERARCHY = *YES
By default, the system syntax file is activated when a user ID is set up.
HIERARCHY = *NO
The system syntax file is deactivated immediately after LOGON processing. For users with the specified profile ID, the definitions in the system syntax file then become irrelevant. The only definitions which apply are those stored in the assigned group syntax file. A group syntax file which is defined using HIERARCHY = *NO must contain, in addition to the global information, at least the EXIT-JOB or LOGOFF command. Otherwise, it is not possible to terminate a user job which has the specified profile ID assigned to it.
SYNTAX-FILE-TYPE = *SUBSYSTEM(...)
The syntax file is a subsystem syntax file.
NAME = *NONE / <filename 1..54>
Specifies the name of the file which is to be used as the subsystem syntax file. If *NONE is specified, the subsystem syntax file which belongs to SUBSYSTEM-NAME is deactivated.
SUBSYSTEM-NAME = <structured-name 1..8>
Specifies the name of the subsystem to which the subsystem syntax file belongs.
SYSTEM-LOGON-PROC =
Specifies whether a system-wide LOGON procedure is to run as a call procedure. The specifications made for a system-wide LOGON call procedure have different effects, depending on what is specified for the SCOPE operand.
SYSTEM-LOGON-PROC = *UNCHANGED
There is to be no change in the system-wide LOGON call procedure.
SYSTEM-LOGON-PROC = *STD
The system-wide LOGON call procedure with the default name TSOS.SYS.SDF.LOGON.SYSPROC is activated for all subsequent LOGON operations in the current session (see the SCOPE operand).
SYSTEM-LOGON-PROC = *NO
Deactivates the system-wide LOGON call procedure (see the SCOPE operand).
SYSTEM-LOGON-PROC = <filename 1..54>
Activates the specified system-wide LOGON call procedure (see the SCOPE operand).
SYSTEM-LOGON-INCL =
The specified system-wide LOGON include procedure is activated. The specifications for the system-wide LOGON include procedure have different effects depending on the SCOPE operand.
SYSTEM-LOGON-INCL = *UNCHANGED
There is to be no change in the system-wide LOGON include procedure.
SYSTEM-LOGON-INCL = *STD
The system-wide LOGON include procedure with the default name TSOS.SYS.SDF.LOGON.SYSINCL is activated for the next LOGON operations in the current session (see the SCOPE operand).
SYSTEM-LOGON-INCL = *NO
Deactivates the system-wide LOGON include procedure (see the SCOPE operand).
SYSTEM-LOGON-INCL = <filename 1..54>
Activates the specified system-wide LOGON include procedure (see the SCOPE operand).
SYSTEM-LOGOFF-PROC =
Specifies whether a system-wide LOGOFF procedure is to run as a call procedure. The specifications made for the system-wide LOGOFF call procedure have a different effect depending on the value of the SCOPE operand.
SYSTEM-LOGOFF-PROC = *UNCHANGED
No change to the system-wide LOGOFF call procedure.
SYSTEM-LOGOFF-PROC = *NO
The system-wide LOGOFF call procedure is deactivated (see also the description of the SCOPE operand).
SYSTEM-LOGOFF-PROC = *STD
The system-wide LOGOFF call procedure with the default name $TSOS.SYS.SDF.LOGOFF.SYSPROC is activated (see also the description of the SCOPE operand).
SYSTEM-LOGOFF-PROC = <filename 1..54>
The specified system-wide LOGOFF call procedure is activated (see also the description of the SCOPE operand).
SYSTEM-LOGOFF-INCL =
Specifies whether a system-wide LOGOFF procedure is to run as an include procedure. The specifications made for the system-wide LOGOFF include procedure have a different effect depending on the value of the SCOPE operand.
SYSTEM-LOGOFF-INCL = *UNCHANGED
No change of the system-wide LOGOFF include procedure.
SYSTEM-LOGOFF-INCL = *NO
The system-wide LOGOFF include procedure is deactivated (see also the description of the SCOPE operand).
SYSTEM-LOGOFF-INCL = *STD
The system-wide LOGOFF include procedure with the default name $TSOS.SYS.SDF.LOGOFF.SYSINCL is activated (see also the description of the SCOPE operand).
SYSTEM-LOGOFF-INCL = <filename 1..54>
The specified system-wide LOGOFF include procedure is activated (see also the description of the SCOPE operand).
Return codes
(SC2) | SC1 | Maincode | Meaning/Guaranteed messages |
|---|---|---|---|
0 | CMD0001 | No error | |
2 | 0 | CMD0677 | Access rights for the system syntax file have been changed (warning) |
2 | 0 | CMD0689 | HIERARCHY=*NO is not included in the current parameter file |
1 | 32 | CMD0500 | Invalid syntax specification in the current syntax file |
64 | CMD0556 | Command executed unsuccessfully | |
1 | 64 | CMD0601 | Command reserved for use by systems support |
Notes
Access to the SDF parameter file (MODIFY-SDF-PARAMETERS command) is possible only for a task under the TSOS ID. Concurrent accesses of further tasks are rejected with an error message.
The group syntax file allocated to the profile ID of user ID TSOS need not be shareable unless it is used by other user IDs. If the file is protected by BASIC-ACL or GUARDS, the user IDs must have at least execute permission.
If SCOPE=*NEXT-SESSION is specified, specified syntax file names and the procedure names are stored in the parameter file without being checked. Checking does not take place until the start of the next session.
File names specified without a user ID are given the current catalog ID or user ID of the task.
When replacing alias names, only the real file names are entered.
Global information from subsystem syntax files is ignored.
If SCOPE=*TEMPORARY or *PERMANENT is specified, the TSOS group syntax file cannot be deactivated.
A subsystem syntax file may also be activated automatically by DSSM when the subsystem is started (defined in the subsystem declarations). If a subsystem syntax file has already been declared and hence activated for the subsystem in the SDF parameter file, only the last syntax file activated for the subsystem is evaluated. A syntax file automatically activated by DSSM cannot be removed for the subsystem by means of MODIFY-SDF-PARAMETERS; it can only be exchanged. Syntax files automatically activated by DSSM are deactivated again by DSSM when the subsystem is shut down. Syntax files activated by means of the SDF parameter file must in all cases be deactivated with a suitable MODIFY-SDF-PARAMETERS command.