After selecting the menu item 'Selection' the following pulldown menu appears:
The pulldown menu 'Selection' refers to a set of objects which has to be specified in a dialog box by means of search patterns and search arguments. Here basically the same functions are offered as with 'Object'.
Example: Defaults of a Dialog Box
As default the current database user and the version of the last displayed list are proposed. Instead of unique program and module names search patterns can be used to limit the eligible programs and modules. '*' stands for any number of characters and '?' for exactly one arbitrary character.
Example: Filled Dialog Box
Version can be set to:
Version = TEST | PROD | HIST | WORK | ALL
As search argument the type of module, the state or the date can be specified.
Search argument = FORM | PROC | HELP | FUNC |
DBPROC | DBFUNC | TRIGGER | EDIT |
DEBUG | RUN | ->DB | +DB |
NOCALL | =date | <date | >date
The date must be entered in the format as specified in SET and displayed in the module list. The date must be preceded by an operator with the following meaning:
'=' : corresponds exactly to the specified date
'<' : older than the specified date
'>' : younger than the specified date
The search argument 'NOCALL' refers to all modules which are not called by other modules, e.g. start modules or dead code.
If the form was correctly filled in and confirmed with START or the 
key, the selected function is executed.
'Selection/Show'
provides the following submenu:
'Selection/Show/Module'
A dialog box for specifying a certain module is displayed. The input arguments must describe a particular module, i.e. they cannot be search patterns. The editor is called in order to modify the specified module. The editing functions are described in the ADABAS User Manual.
(Command: 'EDIT')
'Selection/Show/Module List'
A dialog box appears where a search pattern for program and module names, the desired version and, if needed, a search pattern can be specified in order to have a list of modules displayed.
(Command: 'MLIST')
'Selection/Show/Program List'
A dialog box appears where a search pattern for the program name and the desired version can be specified in order to have a list of programs displayed.
(Command: 'PLIST')
'Selection/Show/DB Procedure'
requires that in a dialog box a search pattern is specified for the program name of one or more DB procedures. Then a list is output containing all DB procedures with this name stored in the database.
(Command: 'PSHOW')
Example:
'Selection/Show/Trigger'
requires that in a dialog box a search pattern is specified for the program name of one or more triggers. Then a list is output containing all triggers stored in the database that underlie these programs.
(Command: 'TSHOW')
Example:
'Selection/Run'
A dialog box for the specification of a certain module is displayed. The input arguments must describe a particular module, i.e. they cannot be search patterns. Parameters separated from each other by blanks can be specified. They are assigned to the formal parameters of the routine. The module must have the RUN state (see state in the module list) and belong to a program for which one has the execute privilege. If no module name is specified, the module 'START' is called, if such a module exists. For programs of other users a module name has to be specified.
To be able to test with the SQL-PL debugger, the command DEBUG ON must have been issued and the module to be tested must have been stored again. The debugger will be activated when executing the program. For precise information see chapter The Debugger.
(Command: 'RUN')
'Selection/Compile'
A dialog box appears for specifying a search pattern for program and module names, the desired version and an optional search argument. The set of modules described by the arguments is syntactically checked and, if this check was successful, stored as executable object with the 'RUN' state. In the case of an error, an error text is output and the module obtains the state 'EDIT'.
The modules of the PROD and HIST version can also be recompiled e.g. in order to make changed literal contents known to the program.
(Command: 'STORE')
'Selection/Release Version'
makes a production version from a test version. In this case the arguments in the dialog box must describe a program or a set of programs. If the field '->HIST' is filled with 'Y', a production version which might already exist will be saved as historical version. For the specified program there must be at least one module in the TEST version. Modules which are in EDIT or DEBUG state are compiled and entered into the Data Dictionary.
(Command: 'MKPROD')
'Selection/Recall Version'
cancels the release of a version, i.e. the historical version becomes a production version again and the previous production version becomes the test version. The command is rejected, if there are already modules in the test version.
(Command: 'GETHIST')
'Selection/Delete'
removes the specified program or module from the user's SQL-PL library. This function must be confirmed - in order to prevent a handling error. Applied to a foreign program, the execute privilege is deleted.
(Command: 'DROP' or 'DEL')
'Selection/Print'
outputs the contents of the specified set of modules on the printer specified in SET. This function must be confirmed - in order to prevent a handling error.
(Command: 'PRINT')
'Selection/Copy From'
copies the desired program of the specified owner into the user's own SQL-PL library. Prerequisite is that the owner has granted a copy privilege. All modules are copied in the original state and existing version.
(Command: 'COPY')
'Selection/Export'
writes the selected set of programs or modules into an operating system file. The modules are separated from each other by ENDMODULE. Privileges granted are written into the export file in form of workbench commands. If in the dialog box in the field 'Append (y/n) :' 'y' is entered, the commands are added to an existing file.
(Command: 'EXPORT')
'Selection/Import'
reads programs from an operating system file that contains exported modules. The individual modules are expected to be separated from each other by ENDMODULE. The privileges commands contained in the file are executed.
(Command: 'IMPORT')
'Selection/Create in DB'
A module can be created in the database kernel, when it was defined with the module type 'DBPROC' or 'TRIGGER' and if there is no module with the same name in another version in the database.
If the function was successfully executed, the main module (main procedure) to be called is given the state '->DB' in the module list and all subprocedures used the state ' +DB'.
A DB procedure or a trigger with the state '->DB' or '+DB' cannot be modified. To be able to change them, they must be removed from the DB kernel. This function affects marked objects as well.
(Command: 'PCREATE' or 'TCREATE')
'Selection/Remove from DB'
removes the DB procedure or trigger from the database kernel. Afterwards the module can be changed.
Subprocedures are only removed from the DB kernel if they are not used by other DB procedures or triggers created in the DB kernel. After successful execution the state in the module list is set to 'RUN' again.
(Command: 'PDROP' or 'TDROP')