Versions Compared

Key

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

REQUEST

This is the action requested to be performed within LANSA. The action requested can be up to 10 characters in length. The actions that may be requested include:

...

  • X_RUN: Specifies that an RDMLX function is to be executed on IBM i.

PROCESS

This parameter is used to specify the name of the process to RUN, SUBMIT or X_RUN. It can be up to 10 characters in length.

FUNCTION

This parameter is used to specify the name of the function to RUN or X_RUN. It can be up to 7 characters in length.

PARM01

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Change Work Spaces parameter and valid values are N, Y and blank. If the value is blank the default value is 'N"

PARM02

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Total FFC parameter and valid values are 1 to 99 and blank. If the value is blank the default value is 99

PARM03

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Total Compiles parameter and valid values are 1 to 99 and blank. If the value is blank the default value is 20

PARM04 

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Remove Multilingual support parameter and valid values are N, Y and blank. If the value is blank the default value is N

PARM05

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Purge Developer Message starting from date parameter and valid value is a date format in CCYYMMDD and blank. If the value is blank the default value is 00000000. The date must be a valid date, as it is not validated.

PARM06

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Delete Deleted Partition Language Extensions and valid values N, Y and blank. If the value is blank the default value is N

PARM07

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Reorganize Shared LANSA system files and valid values N, Y and blank. If the value is blank the default value is N

PARM08

This parameter can be up to 256 characters in length.

...

If the request is REORG, this acts as Purge Task History starting from date parameter and valid value is a date format in CCYYMMDD and blank. If the value is blank the default value is 00000000. The date must be a valid date, as it is not validated.

PARM09

This parameter can be up to 256 characters in length.

...

If OPT, all $$ file processing is ignored. This means that you must have a viable back-up of all files being imported, and any existing $$ files for files being imported will remain. CHGPF will be used on files being imported that are DDS-based, while the SQL DDL CREATE OR REPLACE will be used on files being imported that are SQL-created.

PARM10

This parameter can be up to 256 characters in length.

...

Use characters 17 –19 to specify whether or not to omit frameworks and groups. (YES or NO). Defaults to NO if not specified.

PARTITION

This parameter is used to specify the name of the partition to be used. It can be up to 3 characters in length.

If not specified, the partition defaults to the SYS partition.

LANGUAGE

This parameter is used to specify the language to be used. It can be up to 4 characters in length.

...

If not specified, the language defaults to the partition default language.

TASK_ID

This parameter is used to specify the task identifier to be used for development work. It can be up to 8 characters in length.

PC_TYPE

This parameter is used to specify the type of PC used with the GUI. This is 1 character in length.This is used internally by LANSA and is not usable in a normal LANSA invocation.

DEVELOPER

This parameter is used to specify whether LANSA presents a command line and work with interface. It is up to 9 characters in length.

  • *NO, N: Specifies that the LANSA menus are presented in the traditional style without a command line.
  • *YES, Y: Specifies that the LANSA menus are presented in the traditional style with a command line.
    If access is given to developer services (see ALLOW_MSGS), then the options to execute an operatig system command and execute user defined developer services exit programs will be available.
  • *ADVANCED, A: Specifies that the LANSA menus are presented in the work with style with a command line.
    If access is given to developer services (refer to ALLOW_MSGS), then the options to execute an operating system command and execute user defined developer services exit programs will be available.

ALLOW_MSGS

This parameter is used to specify whether or not access is given to developer services. It is up to 4 characters in length.

  • *NO, N: Specifies that no access is given to developer services. This includes the notification of developer messages.
  • *YES, Y: Specifies that access is given to developer services.

DATE_SRCE

This parameter is used to specify where to retrieve the date and date format from. It is up to 7 characters in length.

  • *SYSTEM, S: Specifies that the date and date format are to be retrieved from the system values. This is the default.
  • *JOB, J: Specifies that the date and date format are to be retrieved from the job attributes.

BDEBUG

This parameter is used to specify that batch debug of LANSA RDML functions is required.  This is used internally by LANSA and is not useable in a normal LANSA invocation.

BDEBUG_DEV

This parameter is used to specify the name of the display device to be used for debugging batch RDML functions. This is used internally by LANSA and is not useable in a normal LANSA invocation.

BDEBUG_MSG

This parameter is used to specify the name of the message queue to be used to issue messages when using batch debugging. This is used internally by LANSA and is not useable in a normal LANSA invocation.

X_RUNADPRM

This parameter is used to specify additional parameters for an X_RUN request. These additional parameters must be specified in the X_RUN format, e.g. PRTR=*PATH. Refer to Standard X_RUN Parameters in the Technical Reference Guide for details of X_RUN parameters.

...