Versions Compared

Old Version 4

changes.mady.by.user Fabiola Arias Navia

Saved on

compared with

New Version Current

changes.mady.by.user Fabiola Arias Navia

Saved on

Key

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

...

  • MENU: Specifies that the Main System Menu (Advanced if DEVELOPER(*ADVANCED) is specified) is to be presented on entry to LANSA. This is the default action, and the one most likely to be used by developers.
  • RUN: Specifies that a process or a function is to be used. This allows a process or a function to be called without going through the normal LANSA menus. Refer to Using a Process or Function from Your Own Application for more details.
  • SUBMIT: Specifies that a process is to be submitted to batch. This allows a process to be submitted without going through the normal LANSA menus. Refer to Submitting A Process To Batch Directly From Your Own Application for more details.
  • EXPORT: Specifies that an AS/400 export list is to be exported directly. This allows an export list to be exported without going through the normal LANSA menus. Refer to Direct Exporting of Objects in a List for more details.
    It is not recommended that this facility be used interactively (i.e. directly from a workstation) because of the relatively large number of database I/Os performed. To use this request, the user profile being used must have access to Work with Lists of Objects to Be Exported in the Housekeeping Menu. Refer to User Access to the LANSA System for information.
  • IMPORT: Specifies that the import facility is to be used directly. This allows an import to be done without going through the normal LANSA menus. Refer to Direct Importing of Objects for more details.
    It is not recommended that this facility be used interactively (i.e. directly from a workstation) because of the relatively large number of database I/Os performed. To use this request, the user profile being used must have access to Import objects into this Partition in the Housekeeping Menu. Refer to User Access to the LANSA System for information.
  • REORG: Specifies that the re-organization facility be executed directly. This allows a LANSA re-organization to be run without going through the normal LANSA menus. Refer to Remotely Invoke the Reorganization Facility for more details.
    It is not recommended that this facility be used interactively (i.e. directly from a workstation) because of the relatively large number of database I/Os performed. To use this request, the user profile being used must have access to Submit job to reorg LANSA internal database in the Housekeeping Menu. Refer to User Access to the LANSA System for information.
  • LICENSE or LICENCE: Specifies that the LANSA License Facility be invoked. This cannot be accessed via normal LANSA menus.
    Refer to The LANSA License Facility on the LANSA web site for more information.
  • EXPORTMSGS: Specifies that developer messages are to be exported. This cannot be done via normal LANSA menus. Refer to Export Developer Messages for more details. It is not recommended that this facility be used interactively (i.e. directly from a workstation) because of the relatively large number of database I/Os performed.
  • IMPORTMSGS: Specifies that developer messages are to be imported. This cannot be done via normal LANSA menus. Refer to Import Developer Messages for more details. It is not recommended that this facility be used interactively (i.e. directly from a workstation) because of the relatively large number of database I/Os performed.
  • LCOE: Specifies that LANSA Open is to be used. This is used internally by LANSA Open and is not usable in a normal LANSA invocation.
  • FIELDS: Specifies that the Field Control Menu (Work With Fields screen if DEVELOPER(*ADVANCED)) is to be presented on entry to LANSA. To use this request, the user profile being used must have access to Work with fields, Advanced menu. Refer to User Access to the LANSA System for information.
  • FILES: Specifies that the File Control Menu (Work With Files screen if DEVELOPER(*ADVANCED)) is to be presented on entry to LANSA. To use this request, the user profile being used must have access to the Work with files, Advanced menu. Refer to User Access to the LANSA System for information.
  • PROCESSES: Specifies that the Process Control Menu (Work With Processes screen if DEVELOPER(*ADVANCED)) is to be presented on entry to LANSA. To use this request, the user profile being used must have access to the Work with processes, Advanced menu. Refer to User Access to the LANSA System for information.
  • STRMONITOR: This is no longer available.
  • STRMON: Specifies that the host monitor for Visual LANSA is to be started. This is used internally by Visual LANSA and is not usable in a normal LANSA invocation.
  • PCMAINT: Specifies that the PC Maintenance for Visual LANSA is to be started. This allows definition of information for Visual LANSA. Refer to Maintaining the PC Definition File for more details.
  • PCEXPORT: Specifies that a PC export list is to be exported directly. This allows a PC export list to be exported directly without going through the normal LANSA menus.
    Refer to Direct Exporting of Objects in a List for more details. It is not recommended that this facility be used interactively (that is, directly from a workstation) because of the relatively large number of I/Os performed. To use this request, the user profile being used must have access to the Work with list of objects to be exported in the Housekeeping Menu. Refer to User Access to the LANSA System for information.
  • VERIFYFRT: Causes a Function Routing Table (FRT) to be verified. Refer to What is Function Routing? for more detailed information about this facility.
  • STRLISTEN: Specifies that the LANSA Communications Extensions Listener Job is to be started. Refer to the LANSA Communications Setup Guide for details of how and when to use this option.
  • CONFIGURE: Specifies that the LANSA Work with Configuration Items Facility be invoked. This cannot be accessed via normal LANSA menus. Refer to the Working with Configuration Items for details of how to use this facility.
  • ABOUT: Causes the details of this LANSA system, such as LANSA version number, OS version number, libraries and IFS to be displayed on the LANSA Configuration Details screen. (This is sometimes referred to as the LANSA About screen.) You can capture this data on a Save file, to send to LANSA Support in the event of a query. The save file is DCXSUPDTA and it will be saved in the LANSA_XXXPGMLIB/SUPPORT directory.
    This same information can also be captured using a web interface with the URL:

    http://123.45.67.89/cgi-bin/lansaweb?procfun+lansaweb+about+dem
     
    In this case the information can be saved to a save file or, if your email is configured, emailed directly to your LANSA support desk.

...

If the request is EXPORT, this is the languages language to be exported. Up to 64 language codes can be specified or *ALL to export all languages. It 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

...

If the request is EXPORT, this is do does not save to media - leave in QTEMP. (YES or NO) Default is NO if not specified. It can be up to 3 characters in length.

If the request is IMPORT, this is the languages language to be imported. Up to 64 language codes or *ALL to import all languages in exported data. Only applicable to multilingual partitions. It 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

...

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

...

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

...

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 ParametersParameters in the Technical Reference Guide for details of X_RUN parameters.

For examples, refer to 1.4.2 Execute RDMLX function.