6.2.5 Execution and Security Settings
To display the screen, select from the Main System Menu (Advanced), choose from the and then select from the menu.
|
|
The Work with are shown on two screens. The page up and down keys may be used to move from one screen to the other. Changes are not committed until your press Enter on the second screen.
|
Date determination
Positions 488-493 in data area DC@A01.
These three values are used to determine the century for six and four character dates. Such dates have their year compared to the value.
The first century., the is used if the year is less than or equal to the comparison year value. The second century, the is used if the year is greater than the comparison year value.
You must set these values.
Reclaim resources on exit from LANSA
Position 480 in data area DC@A01.
When this value is set to "Y" a RCLRSC (reclaim resources) command will be executed on exit from LANSA.
Replace library list on exit from LANSA
Position 481 in data area DC@A01.
When this value is set to "Y", a RPLLIBL (replace library list) command will be executed on exit from LANSA. This command resets the job's library list to what it was on entry to LANSA.
Exchange all fields between functions on prompt
Position 499 in data area DC@A01.
When this value is set to "Y", all other fields used by a function that will fit into the space left in the exchange list will be exchanged on a prompt request.
Allow LANSA exchange for RPG, etc
Position 487 in data area DC@A01.
A value of "Y" for this option allows the EXCHANGE list capability in RPG / CL / COBOL etc programs so that values can be returned from LANSA to these programs (using EXCHANGE). Also values can be put on the LANSA exchange list from RPG / CL / COBOL etc programs. Refer to the EXCHANGE command for more details. Recompilation is necessary for changes to this setting to take effect.
N is the default.
Enable cursor location sensitivity (prompt, help)
Position 436 in data area DC@A01.
This value must be set to "Y" to enable field prompting and field level help. Recompilation is necessary for changes to this value to take effect.
Enable LANSA attention key
Position 462 in data area DC@A01.
When this option is enabled, the use of the attention key will result in the main system menu being re-displayed for you to select what you want to do. At any time the task/activity that you were performing before using the attention key can be resumed by using function key 3. Note also that some entries on the field, file, process or housekeeping menus may be displayed with a message indicating they are "Suspended or N/A". This indicates that they cannot be effectively used in conjunction with the activity that is currently suspended (usually because program recursion would occur). If you select one of these "Suspended or N/A" entries your suspended activity will be immediately resumed just as if you had used function key 3.
Suppress "Process in interpretative mode" message
Position 495 in data area DC@A01.
Controls the display of the "Process will run in interpretive mode, compiled version not usable" message. This message is displayed as a warning when a process has been selected for use, informing the user that a "new" compiled version of a Process should be created.
Y - Do not display warning message.
N - Display warning message. This is the default.
Generate field level help from dictionary
Position 476 in data area DC@A01.
Set this value to "Y" to enable the automatic generation of field level help text from dictionary definitions and validation rules. This automatically generated help text is appended to any applicable user defined help text.
Use Panel Groups for user defined help text
Setting *UIMHELP in data area DC@OSVEROP.
Set this value to "Y" to set the *UIMHELP option. This indicates that the IBM's Panel Groups are to be used for the presentation of user defined help text, rather than the LANSA help text display facility. The setting *V2WINDOWS must also be set. The *V2WINDOW option may be set in the 6.2.6 Display and Print Controls setting .
Allow permanent file overrides
Setting *PERMFILOVR in data area DC@OSVEROP.
Set this value to "Y" to set the *PERMFILOVR option. Setting this option allows permanent file overrides to be used. When you specify permanent file overrides you are telling LANSA that "every time I use this file, I really want to use this other file". This is useful when you want to use files with names that are not acceptable to LANSA, such as files with a 10 character file name or with a full stop (.) in their name. Refer to The Permanent File Overrides Facility for details and examples.
Use function routing table from *LIBL
Setting *FUNRTRLIBL in data area DC@OSVEROP.
Set this value to "Y" to set the *FUNRTRLIBL option. When this option is set the Function Routing table X_FUNRTR will be accessed from *LIBL. If this is not set the Function Routing table in the partition module library will be used. Refer to Function Routing for further details.
Import user exit program
Positions 601 - 610 in data area DC@A07.
During a standard import these bytes are tested. If non-blank they are assumed to identify a user exit program that should be invoked each time that an IBM i level object is created or changed during the import. Such a program must receive 3 x Char(10) parameters identifying: (1) the object name, (2) the library, and, (3) the object type (in IBM i "*" style object type notation). This facility is provided only for IBM i.
Set environment user exit program
Positions 611 - 620 in data area DC@A07.
After LANSA has set up its environment for the partition these bytes are tested. If non-blank they are assumed to identify a user exit program that should be invoked each time that a LANSA partition is entered. Such a program must receive 3 parameters identifying: (1) the LANSA program library Char(10), (2) the partition ID Char(3), and (3) the language code Char(4).
SUBMIT command user exit program
Positions 621 - 630 in data area DC@A07.
The first time a LANSA function is submitted these bytes are tested. If non-blank they are assumed to identify a user exit program that should be invoked each time a function is submitted. Such a program must receive one parameter Char(2000) containing the SBMJOB command about to be used. The user exit program can modify the SBMJOB command before exiting and passing back the parameter.(e.g. Add MSGQ() parameter to SBMJOB).
Call user defined prompt key handler
Position 498 in data area DC@A01.
Set this value to "Y" to indicates that a user defined prompt key message handler program should be called in preference to the LANSA prompt key message handler, when the prompt key function key has been selected. If this value is set to "Y", a user defined prompt key message handler program name must be specified.
Name of user defined prompt key handler
Positions 11 - 20 in data area DC@A07.
If the "Call user defined prompt key handler" is set to "Y", then an attempt will be made to call the user defined prompt key message handler program specified in this option when the prompt key function key is used in your LANSA application.
Name of user defined program/file error handler
Positions 1 - 10 in data area DC@A07.
If non-blank this value should identify a user defined error handler. During LANSA execution, an attempt will be made to call this user defined program/file error handler program by the LANSA program/file error routine. The user defined program/file error handler can be used to update audit/error logs external to the LANSA system.
User defined LANSA access check program and library
Positions 669 - 688 in data area DC@A07.
If this value is non-blank, the specified program in the specified library will be called during LANSA access checking. The user-defined program can manipulate the processing of the LANSA access check for an object and it will return two parameters that will influence the processing The library may be *LIBL.
For details, refer to User Exit LANSA Security Check.
User defined LANSA IJDT access check program and library
Positions 689 - 708 in data area DC@A07.
If this value is non-blank, the specified program in the specified library will be called before the LANSA IJDT is executed. The user-defined program can manipulate the processing of the LANSA IJDT (I Just Did This) and will return two parameters that will influence the processing. The library may be *LIBL.
For details, refer to User Exit IJDT (I Just Did This).
User defined CIDT program and library
Positions 709 - 728 in data area DC@A07.
If this value is non-blank, the specified program in the specified library will be called during LANSA access checking. The user-defined program can manipulate the processing of the LANSA access check for an object and it will return two parameters that will influence the processing The library may be *LIBL.
For details, refer to User Exit CIDT (Can I Do This).
Execution locking on process
Position 422 in data area DC@A01.
If this value is set to "Y", a shared lock will be set on the process during execution. If a shared lock on the process can not be established then execution of the process will fail.
Use function level security
Position 475 in data area DC@A01.
If this value is set to "Y", LANSA function level security is enabled. Otherwise, process level security is used. Refer to LANSA Objects and Security for full details on LANSA security.
Note that using function level security increases overall system resource use. Processes (NOT functions) compiled prior to a change to this value will ignore the change and should be recompiled.
External security matching for LANSA files
Position 486 in data area DC@A01.
This is set to a "Y" to indicate that LANSA database security should be reflected into IBM i object level security. This option only applies to files set up and maintained by LANSA. It does not apply to "OTHER" files.
Refer to External Security Matching and Reviewing and Changing Access to LANSA Objects before changing security settings.
Disable end user process and function security
Position 496 in data area DC@A01.
A value of "Y" indicates that end user process and function level security is disabled in this system. This setting will improve system performance, because no security checking is performed before accessing end user applications. This flag has no effect on access to process or function definition details in a development environment. This setting is appropriate for installations that use an external menu system to control and secure access to LANSA applications.
The setting of this flag is interpreted dynamically by applications. That is, it does not remain as set when the code is compiled, but is evaluated at runtime.
Refer to Reviewing and Changing Access to LANSA Objects before changing security settings.
Disable end user file level security
Position 497 in data area DC@A01.
A value of "Y" indicates that end user file level security is disabled in this system. This setting will improve system performance, because no file level security checking is performed in end user applications. This flag has no effect on access to file definition details in a development environment. This setting is appropriate for installations that use the approach "if the program is accessible from your menu .... then you can access all the files the program requires".
The setting of this flag is interpreted dynamically by applications. That is, it is not statically set when the code is compiled, but is evaluated at runtime.
Refer to Reviewing and Changing Access to LANSA Objects before changing security settings.
Relax restrictions on trigger functionality
Setting *EXTENDED_TRIGGERS in data area DC@OSVEROP.
A value of "Y" will set the option *EXTENDED_TRIGGERS which indicates that the normal LANSA rules that prevent database event triggers from calling other functions and using "user interface" commands should be relaxed.
This use of this option is not recommended in most circumstances.