Versions Compared

Old Version 3

changes.mady.by.user user-2c621

Saved on

compared with

New Version 4

changes.mady.by.user user-2c621

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Appears when defining a new partition or changing an existing partition. Requests that you specify whether or not SAA/CUA (System Application Architecture / Common User Access) standards apply to objects created within this partition.

Allowable values are:

YES

SAA/CUA standards apply to this partition.

NO

SAA/CUA standards do not apply to this partition.

The default value is YES.

...

It is recommended that all partitions are defined as multilingual even if they will be used with only one language.

Allowable values are:

YES

Multilingual support is required for this partition.

NO

Multilingual support is not required for this partition.

The default value is YES.

...

Before changing or creating a partition that uses multilingual support, read Setting Up LANSA to Run Multilingual Applications in the LANSA Multilingual Application Design Guide as well as the Note following.


Note

Note:

There are some important things that you should know about multilingual support before you attempt to turn it on (or off):

  • Providing (or not providing) multilingual support in your applications is an important application design decision that you should make decisively, even before LANSA installation. Changing your mind later (or changing your mind multiple times) may lead to unnecessary and avoidable maintenance and deployment issues. Refer to Imports with the LANSA IBM i Software in the Installing LANSA on IBM i Guide for a list of LANSA software that requires a multilingual partition.
  • There are important procedures, considerations and guidelines that you should understand and then follow when converting a partition from monolingual form to multilingual form (or vice versa).
  • Changing a partition to multilingual or monolingual form impacts the repositories in attached Visual LANSA development workstations. You must take steps to ensure that your central repository and all attached Visual LANSA workstation repositories are changed in a synchronized fashion. In outline, the simplest way to ensure this synchronization is as follows:
  • Check in all new or modified objects from all attached Visual LANSA workstations into the central repository.
  • Delete the partition from all attached Visual LANSA workstations.
  • Change the central repository to/from multilingual form.
  • Make the changes to object definitions in the central repository as specified in the LANSA Multilingual Application Design Guide.
  • Set up the partition again on all attached Visual LANSA workstations as if it was a brand new partition, and then verify that it now has the correct multilingual characteristics (or not). 
  • Check out all required objects to each attached Visual LANSA workstation.

Help Option on Menus

Appears when defining a new partition or changing an existing partition. Requests that you specify whether or not a 'help' option is to appear on process menus, and if it is to appear, what the text that is to be displayed should be.

...

Appears when defining a new partition or changing an existing partition. Requests that you specify whether or not:

DDS

(Data Description Specifications) translated from your LANSA requests should be permanently kept.

RPG

(Report Program Generator) source statements translated from your LANSA requests should be permanently kept.

The default for both these options is NO (source statements are not to be kept). Keeping source statements in most situations is just a waste of disk space.

...

1. Is Task Tracking active within this partition?

Allowable values are:

YES

Task Tracking is active in this partition, object and task authority checks will be performed and all events that have taken place for work performed on objects will be recorded.

NO

Task Tracking is not active in this partition.

The default value is NO.

2. Does the user require a task identifier to do work?

Allowable values are:

YES

User does require a task identifier before any work can be performed on a selected object.

NO

User does not require a task identifier to do work, until work has been completed on a selected object, where on he/she will be prompted by a POPUP window to allocate a task identifier against the selected object.

The default value is NO.

Note
Note: This option will be ignored if Task Tracking is not active in this partition.

3. Prompt/Confirm task identifier?

Allowable values are:

YES

Prompt/confirm task identifier is required when work has completed on a selected object. The user will be prompted with the 'Prompt/Confirm POPUP Window' to confirm or change (if CHANGE function key is enabled) the task identifier to be allocated for work performed on the selected object.

NO

Prompt/confirm task identifier is not required. The task identifier specified for this job (on entry into LANSA or by a previous request to specify a task identifier for the job via the 'Prompt/Confirm POPUP Window'), will be automatically confirmed as the task identifier for work performed on the selected object.

The default value is NO.

Note
Note: This option will be ignored if Task Tracking not active in this partition.

4. Allow user to change tasks while working?

Allowable values are:

YES

User is allowed to change the task identifier that is allocated to the selected object on which work was performed but only if the user is authorized to the task identifier, OR, if the 'Prompt/Confirm POPUP Window' is displayed, the CHANGE function key will be enabled to allow the user to change task identifiers manually.

NO

User not allowed to change tasks.

The default value is NO.

Note
Note: This option will be ignored if Task Tracking is not active in this partition.

5. Disable Special 'Work with Tasks' Security?

Allowable values are:

YES

Disable the special security checks within the 'Work with Tasks' option.

NO

The special security checks within the 'Work with Tasks' option are active.

The default value is NO.

This option will be ignored if Task Tracking is not active in this partition.

6. Activate Task Tracking for Import jobs?

Allowable values are:

YES

Task tracking is active for import jobs

NO

Task tracking is not used for import jobs.

The default value is NO.

This is only used if Task Tracking is active in a partition.

...