In order to support the optimum use of working memory, UDS/SQL is supplied as a subsystem. This includes object module files for the UDS-SQL and UDS-D subsystems.
The UDS-SQL subsystem includes the shareable code that is needed to run UDS/SQL locally. It can generally be used in combination with linked-in and independent applications.
The UDS-D subsystem includes the shareable code required for the supplementary use of UDS-D.
The subsystems can be incorporated in an existing or supplementary subsystem catalog by the BS2000 system administrator by using subsystem management resources (see the “Subsystem Management in BS2000” manual for details).
If UDS-SQL or UDS-D was installed with IMON, the user ID under which the subsystems were installed will be known to the system.
If UDS-SQL or UDS-D was not installed with IMON, the subsystems are searched under the default user ID (usually $TSOS). If they are installed under some other user ID, the BS2000 system administrator must copy the library SYSLNK.UDS-SQL.029 or SYSLNK.UDS-D.029 to the default user ID or change the INSTALLATION- parameter (see below) to match the installation user ID.
The BS2000 system administrator must add the subsystem to the subsystem configuration (DSSM command ADD-SUBSYSTEM). From now on, assignment to this subsystem is possible via the BS2000 command SELECT-PRODUCT-VERSION.
With the BS2000 command MODIFY-SUBSYSTEM-PARAMETER, the BS2000 system administrator can modify the attributes of the subsystem. However, only changes to the following operands are advisable:
INSTALLATION-USERID
If UDS-SQL was installed with IMON, the installation user ID is used.
If UDS-SQL was not installed with IMON, the default user ID (usually $TSOS) is used. In this case, the LLM modules of the subsystem must be available under the default user ID in the library from which the subsystem is to be loaded (LIBRARY parameter).
If the subsystem is to be loaded from some other user ID, the BS2000 system administrator can also set that user ID by means of the INSTALLATION-USERID parameter.
LIBRARY
Default value: SYSLNK.UDS-SQL.nnn (nnn=version)Designates the library from which the subsystem is to be loaded.
MEMORY-CLASS
Default value: *SYSTEM-GLOBALLoads the subsystem into class-3/class-4 memory. The use of class-5 memory (LOCAL-PRIVILEGED) is advantageous only in exceptional cases (see the section “Memory and task concept” in the "Subsystem Management in BS2000" manual).
SUBSYSTEM-ACCESS
Default value: *HIGH
Loads the subsystem above 16 Mbytes so that it can be used by all XS-compatible applications and UDS/SQL tasks.
If the subsystem is to be used by non-XS-compatible applications, the BS2000 system administrator can also load the subsystem below 16 Mbytes (SUBSYSTEM-ACCESS=*LOW). This is, however, subject to certain restrictions (see the corresponding notes in the “Memory and task concept” section of the "Subsystem Management in BS2000" manual).
In some cases, an attempt is initially made in application programs to load the UDS/SQL connection modules below 16 Mbytes. If the subsystem has been loaded high (with the parameter SUBSYSTEM-ACCESS=*HIGH), this could result in the following error message for each dynamically loaded connection module:
BLS0061 AMODE OF SYMBOL ’....’ INVALID IN THIS ENVIRONMENT. LOADING ABORTED.
UDS/SQL loads the UDS/SQL connection module again with modified parameters. If no further errors are reported, these messages from the Binder-Loader system may be ignored.
The subsystem is activated by the BS2000 system administrator with the DSSM command START-SUBSYSTEM. If several subsystem versions are to be active in parallel, the following specification must be made in the START-SUBSYSTEM command: VERSION-PARALLELISM=*COEXISTENCE-MODE