documentation.HELP! Visual LANSA Admins Documentation

Visual LANSA Administrator's Guide

Visual LANSA Admins

Table of contents

• Visual LANSA Administrator's Guide
  • 1. Planning Your Site
    • 1.1 LANSA Software Components
      • 1.1.1 LANSA System Definitions
      • 1.1.2 LANSA Repository Data
    • 1.2 LANSA Development Models
      • 1.2.1 IBM i Slave Systems
      • 1.2.2 Local Client to a Slave Server
      • 1.2.3 Network Client to a Slave Server
      • 1.2.4 Independent Windows Server
      • 1.2.5 Local Client to an Independent Windows Server
      • 1.2.6 Network Client to an Independent Windows Server
      • 1.2.7 Independent Windows Workstation to a VCS Master
      • 1.2.8 Windows Build Machine
      • 1.2.9 Master and Slave System Configurations
      • 1.2.10 Synchronizing Master and Slave Systems
      • 1.2.11 LANSA for the Web Development Models
        • LANSA for the Web Administrator
        • Multilingual Considerations
        • IBM i Software Components
        • Windows Software Components
    • 1.3 Choosing a Development Model
      • 1.3.1 IBM i Master for Development?
      • 1.3.2 Local Client or Network Client?
      • 1.3.3 Windows Master for Development?
    • 1.4 Recommended Development Models
      • 1.4.1 Recommended IBM i Development Model
        • Setup - Partitions
        • Setup - Task Tracking IBM i
        • Setup - Task Tracking Visual LANSA
        • Setup - Repository Synchronization
        • Lock by PC Name
        • Setup - Change Management/Version Control Strategy
      • 1.4.2 Recommended Windows Development Model
        • What is a Version Control System?
        • Why do I need a Version Control System?
        • Visual LANSA Development using a Version Control System
    • 1.5 Promotion & Deployment
      • 1.5.1 IBM i Master Deployment Options
      • 1.5.2 Windows Master Deployment Options
    • 1.6 LANSA for the Web Deployment Models
      • 1.6.1 Considerations for the Windows Multi-Tier Deployment Model
      • 1.6.2 Considerations for the Mixed Multi-Tier Deployment Model
      • 1.6.3 Multi-Homing with LANSA for the Web
    • 1.7 LANSA Integrator Development/Deployment Components
      • 1.7.1 Studio
      • 1.7.2 JSM Server
      • 1.7.3 JSM Proxy
      • 1.7.4 RFI
      • 1.7.5 User Agent
  • 2. Getting Started with Administration
    • 2.1 Installing LANSA
      • 2.1.1 Installing Visual LANSA
      • 2.1.2 Upgrading Visual LANSA
      • 2.1.3 Applying EPCs
      • 2.1.4 Visual LANSA Administration
    • 2.2 Independent System Administration with a VCS Master
    • 2.3 Independent System Administration
      • 2.3.1 Maintaining System Definitions on Independent Systems
      • 2.3.2 Maintaining Partition Definitions on Independent Systems
      • 2.3.3 Maintaining Users and Tasks on Independent Systems
    • 2.4 Slave System Administration
      • 2.4.1 Maintaining System Definitions on Slave Systems
      • 2.4.2 Maintaining Partition Definitions on Slave Systems
      • 2.4.3 Maintaining Users and Tasks on Slave Systems
      • 2.4.4 Configure LANSA Communications Software
    • 2.5 Development Environment Administration
      • 2.5.1 Controlling How Developers Work
      • 2.5.2 Controlling What Developers Can Build
      • 2.5.3 Import/Export Operations
      • 2.5.4 Development Environment Settings
      • 2.5.5 Setting Systems Information
  • 3. Visual LANSA Logon
    • 3.1 Visual LANSA Logon without a VCS Master
    • 3.2 Visual LANSA Logon with a VCS Master
    • 3.3 Logon Parameters
      • 3.3.1 User ID
      • 3.3.2 Password
      • 3.3.3 Use Windows Credentials
      • 3.3.4 Partition
      • 3.3.5 Current Language
      • 3.3.6 Task ID
      • 3.3.7 Messages
      • 3.3.8 Database Login
  • 4. Visual LANSA Initialization
    • 4.1 VCS Master Setup
      • 4.1.1 Considerations when Installing a New VCS Master
      • 4.1.2 Migrating a Partition from a Slave to a VCS Master
      • 4.1.3 Setting up 2nd and Subsequent Developers to use a VCS Master
      • 4.1.4 Release Management with a VCS Master
      • 4.1.5 Upgrading a VCS Master
    • 4.2 System Initialization
      • 4.2.1 Restricted System Initializatior when another user is logged into Visual LANSA
      • 4.2.2 LANSA System Type
      • 4.2.3 Connect to Master
      • 4.2.4 Location of Imports
      • 4.2.5 RDML Command Definitions
      • 4.2.6 Standard Application Templates
      • 4.2.7 Standard Built-in Function Definitions
      • 4.2.8 Standard System Message File
      • 4.2.9 Standard System Variables
      • 4.2.10 Standard Web Definitions
      • 4.2.11 Example User/Task
      • 4.2.12 Example Partition Definition
      • 4.2.13 Enrolled PC Names
      • 4.2.14 Enrolled PC Users
      • 4.2.15 Current Task List
      • 4.2.16 Partition Definitions
      • 4.2.17 Master's LU Name
      • 4.2.18 Master's User Name
      • 4.2.19 Master's Password
      • 4.2.20 Use Windows credentials
      • 4.2.21 Client -> Server Translation Table
      • 4.2.22 Server -> Client Translation Table
      • 4.2.23 Show Last Log
    • 4.3 Partition Initialization
      • 4.3.1 Mandatory Partition Initialization
      • 4.3.2 Visual LANSA Framework
      • 4.3.3 Enable for the Web
      • 4.3.4 LANSA Client field and file definitions
      • 4.3.5 Personnel System Demonstration
      • 4.3.6 Run Demonstration
      • 4.3.7 Show Last Log
    • 4.4 Single Sign-On (SSO)
      • 4.4.1 How LANSA SSO Works
  • 5. Remote Systems
    • 5.1 Concepts
      • 5.1.1 Remote System Terms
      • 5.1.2 Host Monitor Concepts
        • Connect Master and Slave Systems
        • Host Monitor and Visual LANSA Slave Repositories
        • Access the Master System
        • Example Development Cycle (with Master)
      • 5.1.3 Deliver To Concepts
        • Restrictions and Assumptions
        • Linux Deployment System Development Cycle Example
        • IBM i Deployment System Development Cycle Example
    • 5.2 Host Monitor
      • 5.2.1 Check Out
        • Check Out Options
      • 5.2.2 Check In
        • Check In Options
        • Check In Joblog Viewer
      • 5.2.3 Propagation
      • 5.2.4 Start and Stop the Host Monitor
      • 5.2.5 Refresh Master Object List
    • 5.3 Other Remote System Monitors
      • 5.3.1 Define a Deployment System
      • 5.3.2 Refresh System Information from the Deployment System
      • 5.3.3 Initialize the Partition on the Deployment System
      • 5.3.4 Deliver To
        • Deliver To Options
        • Deliver to Joblog Viewer
      • 5.3.5 Disconnect from a Remote System Monitor
    • 5.4 Job Status and Messages
      • 5.4.1 Detailed Messages
  • 6. Change Management
    • 6.1 Change Management Concepts
      • 6.1.1 Object Locking Concepts
      • 6.1.2 Task Tracking Concepts
      • 6.1.3 Impact Analysis Concepts
      • 6.1.4 Deployment Concepts
      • 6.1.5 Third Party Packages
    • 6.2 Using Task Tracking in LANSA
      • 6.2.1 Introduction to Task Tracking
        • Tracked Objects
        • Task Identifier Rules
      • 6.2.2 Approaches for using Task Tracking
        • Choose Your Task Tracking Approach
        • Full Task-Oriented Tracking
        • Tracking by Product
        • Tracking By Developer
        • Minimum Tracking
        • Combined Approaches
      • 6.2.3 Task Tracking Set up
        • Set Task Tracking System Options
        • Set Task Tracking Partition Options
        • Set Special Task ID
        • Define Task IDs
        • Share Task IDs
        • Change Current Task
        • Unlock Objects in Task Tracking
        • Process/Function Locking
        • Transfer Object Locks
        • Task Tracking and Repository Synchronization
        • Special Authorities and Task Tracking
        • Task Tracking Recommendations
        • Task Tracking in Master/Slave Systems
        • Task Tracking on Independent Systems
      • 6.2.4 What Happens When Task Tracking Is Active?
      • 6.2.5 Typical Development Cycle Example
      • 6.2.6 Task Tracking and Import/Export
    • 6.3 Repository Synchronization
      • 6.3.1 Repository Synchronization Concepts
      • 6.3.2 What Are Repository Groups?
      • 6.3.3 What are Work Groups?
      • 6.3.4 Rules for Repository Synchronization
      • 6.3.5 Synchronization Options in Visual LANSA
      • 6.3.6 PC Options on Server
      • 6.3.7 Repository Synchronization Tips & Techniques
  • 7. System Information
    • 7.1 System Definitions
      • 7.1.1 Export and Import
      • 7.1.2 Task tracking
      • 7.1.3 Field and File defaults
      • 7.1.4 Compile and Edit Options
      • 7.1.5 Execution and Security
      • 7.1.6 Display and Print controls
      • 7.1.7 General Information
    • 7.2 X_LANSA.PRO Maintenance
    • 7.3 Partitions
      • 7.3.1 RDML and RDMLX Partitions Concepts
        • LANSA RDML Object Types
        • LANSA RDMLX Object Types
        • RDML and RDMLX Object Deployment
      • 7.3.2 Partition Definition Tab
        • Partition Name
        • Partition Description
        • Unique Object Prefix
        • Partition Security Officer
        • Module library
        • Default file library name
        • Include in library list
        • Partition is Multilingual
        • Web Enabled
        • SAA/CUA standard apply
        • Enable Documentor
        • User access enforced
        • Perform checks before propagated
        • Ignore propagated deletes
        • *ENDWHERESQL
      • 7.3.3 Task Tracking Partition Settings
        • Enable task tracking
        • Task is required
        • Confirm Task required
        • Allow Task to be Changed
        • Disable Task "work with" security
        • Active Task Tracking on Imports
      • 7.3.4 RDMLX Partition Settings
        • Enable partition for full RDMLX
        • Create Fields as RDMLX
        • Create File as RDMLX
        • Create Component as RDMLX
        • Create Function as RDMLX
        • Enable Short Char
      • 7.3.5 Enable Existing Partitions for Full RDMLX
        • Update LANSA for iSeries Partition Definition
        • Refresh Visual LANSA Systems
        • Initialize LANSA for iSeries Partition
        • Deploying RDMLX Applications to an IBM i
      • 7.3.6 Available Field Types in Partition
        • Common and Specialized Field Types
        • Field Type Enabled in Partition
      • 7.3.7 Universal interface options
        • Process Menu style
        • Uppercase process title
        • Uppercase function title
        • Display process date and time
        • Display function date and time
        • Display panel ID
        • Function key lines
        • Message line number
        • Border fill - top corner
        • Border fill – top and bottom
        • Border fill - sides
        • Border fill - bottom corner
      • 7.3.8 Supported Database Products
        • Database ID
        • Database Description
        • Database Enabled
    • 7.4 Language Settings
      • 7.4.1 Language Definition
        • Partition description
        • Partition language code
        • Partition language description
        • Character set code page
        • Default language
        • Development language
        • DBCS support required
        • RLTB support required
        • Locale uppercasing required
        • IGC conversion required
        • IGC Function key
        • IGC Conversion Description
        • IGC Conversion Line number
        • IBM i EBCDIC CCSID
        • Windows ANSI code page
        • ISO language code
        • User Message files
      • 7.4.2 Menu Option Text
        • Process Menu Prompt Line
        • Help Option
        • Return Prefix
        • Exit Option
      • 7.4.3 Function Keys
    • 7.5 Frameworks
      • 7.5.1 Identifier 1
      • 7.5.2 Identifier 2
      • 7.5.3 System framework
      • 7.5.4 Short name
      • 7.5.5 Long name
    • 7.6 Groups
      • 7.6.1 Identifier 1
      • 7.6.2 Identifier 2
      • 7.6.3 System group
      • 7.6.4 Short name
      • 7.6.5 Long name
    • 7.7 Primitives
    • 7.8 Remote Systems
    • 7.9 User and Security Maintenance
      • 7.9.1 LANSA User Profiles and Security
      • 7.9.2 Types of User Profiles
      • 7.9.3 Create a User
        • User ID
        • Password
        • Confirm Password
        • Group Profile
      • 7.9.4 Maintain a User's Definition
        • Supplementary Groups
        • Kerberos Principal Names
      • 7.9.5 Maintain a User's Privileges
        • Field Privileges
        • File Privileges
        • Function Privileges
        • Process and Component Privileges
        • Multilingual Variable Privileges
        • System Variable Privileges
        • System Information Privileges
        • Visual LANSA Specific Privileges
    • 7.10 Task Maintenance
      • 7.10.1 Task Identifier
      • 7.10.2 Task Description
      • 7.10.3 Task Status
      • 7.10.4 Authorized Users
    • 7.11 Object Maintenance
      • 7.11.1 Object Maintenance Concepts
      • 7.11.2 Object name
      • 7.11.3 User Id
      • 7.11.4 Authority to Object Definition
      • 7.11.5 Authority to Object Data
    • 7.12 Application Templates
      • 7.12.1 Template Name
      • 7.12.2 Template Description
      • 7.12.3 Display sequence
      • 7.12.4 Extended description
      • 7.12.5 Initial public access
  • 8. Environment Settings
    • 8.1 LANSA Editor Settings
    • 8.2 Design View Language
    • 8.3 Development Language
    • 8.4 Object Locking
    • 8.5 Workstation Locks
    • 8.6 Language Options
      • 8.6.1 Message File Name
      • 8.6.2 Field Prefix Character
      • 8.6.3 Substitution Character for the @ Character
      • 8.6.4 Substitution Character for the $ Character
    • 8.7 Message File Maintenance
      • 8.7.1 1st level text contains
      • 8.7.2 2nd level text contains
      • 8.7.3 ID from
      • 8.7.4 ID to
      • 8.7.5 Add/Change Message Text
        • Message ID
        • First Level Text
        • Second Level Text
        • Substitution Variables
        • Substitution Variable Type
        • Substitution Variable Length
        • Substitution Variable Decimals
    • 8.8 Export and Import
      • 8.8.1 Quick Export
      • 8.8.2 LANSA Import
      • 8.8.3 Import Considerations
      • 8.8.4 LIMPORT
      • 8.8.5 LIMPORT (from IBM i)
  • 9. Compiler Settings
  • 10. Troubleshooting
    • 10.1 Reporting Problems to LANSA Support
      • 10.1.1 Problem Analysis
      • 10.1.2 Problem Details Checklist
      • 10.1.3 Procedure for Reporting Application Failures and Exceptions
      • 10.1.4 Requesting new Product Features and Enhancements
    • 10.2 Gathering Information About LANSA
      • 10.2.1 About LANSA for iSeries
      • 10.2.2 About Visual LANSA
      • 10.2.3 EPC Listings
      • 10.2.4 X_ERR.LOG Files
      • 10.2.5 Dump Files
      • 10.2.6 Producing Debug Symbols for Your LANSA Application
      • 10.2.7 x_tracennn.txt files
  • Appendix A. LANSA's Customer Services
    • Education Services
    • Conferences and User Groups
    • LANSA Customer Support
    • Consulting Services

next page

Get in touch

Submit feedback about this site to:

• [email protected]